Joe Rhodes
2004-Apr-22 20:39 UTC
[Samba] lib/util.c:smb_panic yp_get_default_domain Samba 3.0.2a
Samba Folks:
I'm having what seems like a relatively benign issue with Samba 3.0.2a.
I'm running SuSE 9.0 (with all updates) on an Athlon XP, 512MB RAM,
RieserFS on SATA hard drives. Linux kernel version 2.4.21-202-athlon
(from SuSE).
I can repeatedly and predictably get the following error in the log.smbd
file when connecting via Mac OS X. (smb://serverIP/) I get the same
error occassionally when connecting with WindowsXP Pro/SP1, mostly when
shutting down the machine. Interestingly, the errors in the log file do
not seem to, in any way, affect the performace of the share. From the
client, there appear to be no problems.
Output of the log.smbd:
-------------------------
[2004/04/22 14:45:07, 0] smbd/server.c:main(747)
smbd version 3.0.2a started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/04/22 14:45:57, 0] lib/fault.c:fault_report(36)
==============================================================[2004/04/22
14:45:57, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 9058 (3.0.2a)
Please read the appendix Bugs of the Samba HOWTO collection
[2004/04/22 14:45:57, 0] lib/fault.c:fault_report(39)
==============================================================[2004/04/22
14:45:57, 0] lib/util.c:smb_panic(1400)
PANIC: internal error
[2004/04/22 14:45:57, 0] lib/util.c:smb_panic(1408)
BACKTRACE: 13 stack frames:
#0 /usr/local/sbin/smbd(smb_panic+0x181) [0x8187618]
#1 /usr/local/sbin/smbd [0x8177e3e]
#2 /usr/local/sbin/smbd [0x8177e93]
#3 /lib/i686/libc.so.6 [0x400e6aa8]
#4 /usr/lib/libldap.so.2 [0x402f9998]
#5 /usr/lib/libldap.so.2 [0x402e088b]
#6 /usr/lib/libldap.so.2 [0x4030524a]
#7 /lib/ld-linux.so.2 [0x4000dc44]
#8 /lib/i686/libc.so.6(exit+0x60) [0x400e9010]
#9 /usr/local/sbin/smbd(exit_server+0x1ff) [0x81daae9]
#10 /usr/local/sbin/smbd(main+0x6fe) [0x81db224]
#11 /lib/i686/libc.so.6(__libc_start_main+0xc7) [0x400d2d17]
#12 /usr/local/sbin/smbd(yp_get_default_domain+0x95) [0x8075821]
[2004/04/22 14:45:57, 1] smbd/service.c:make_connection_snum(705)
joe-rhodes-comp (192.168.2.50) connect to service jrhodes initially as
user jrhodes (uid=1002, gid=513) (pid 9070)
[2004/04/22 14:46:12, 1] smbd/service.c:close_cnum(887)
joe-rhodes-comp (192.168.2.50) closed connection to service jrhodes
I've compiled Samba from source, with the following configure line:
./configure --prefix=/usr/local --with-ldap --sysconfdir=/etc
--with-logfilebase=/var/log/samba
I'm using ldapsam passwd backend, connected to OpenLDAP 2.2.10. Here's
the relevant portions of my smb.conf file:
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2004/04/22 15:07:41
# Global parameters
[global]
workgroup = WORKGROUP
server string = File Server
password server passdb backend = ldapsam:ldap://127.0.0.1
preferred master = No
local master = No
domain master = No
ldap suffix = dc=joerhodes,dc=com
ldap machine suffix = ou=Computers
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap admin dn = cn=admin,dc=joerhodes,dc=com
ldap ssl = no
ldap passwd sync = Yes
[homes]
read only = No
I haven't yet got going on domain log-ins. That's next in the testing
phase. So far, everything seems to be working just fine. I can copy
files back and forth like a bandit. Printing seems to work fine.
Should I be worried about this error or is this just an over eager error
reporting function?
If it's not too much trouble, could you CC me directly. I'm getting the
digest version of the list. Thanks in advace for any help.
Cheers!
-Joe Rhodes
Andrew Bartlett
2004-Apr-24 00:46 UTC
[Samba] lib/util.c:smb_panic yp_get_default_domain Samba 3.0.2a
On Fri, 2004-04-23 at 06:38, Joe Rhodes wrote:> Samba Folks: > > I'm having what seems like a relatively benign issue with Samba 3.0.2a. > I'm running SuSE 9.0 (with all updates) on an Athlon XP, 512MB RAM, > RieserFS on SATA hard drives. Linux kernel version 2.4.21-202-athlon > (from SuSE). > > I can repeatedly and predictably get the following error in the log.smbd > file when connecting via Mac OS X. (smb://serverIP/) I get the same > error occassionally when connecting with WindowsXP Pro/SP1, mostly when > shutting down the machine. Interestingly, the errors in the log file do > not seem to, in any way, affect the performace of the share. From the > client, there appear to be no problems.If it is reproducible, then running Samba under 'valgrind', and reproducing the issue might give us some very useful feedback data. You could also just try 3.0.3rc1, in case we already fixed it, but I can't recall anything in particular. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040424/710d13c9/attachment.bin
I have spent the last week trying to figure out why the command smbclient -L win98server kept crapping out. After grepping through the source code, I figured out the error was in gethostbyname(I think). The solution to this problem is running the command smbclient -L win98server -R bcast instead. But that still leaves it to the next person to figure this all out, and that is not really a good solution. smbclient -L win98server should be a workable command. How do I go about reporting this error? I would also not mind taking the time to reprogram the code to fix this one bug, since it took me a week of frustration to find it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 blfs wrote: | How do I go about reporting this error? I would also | not mind taking the time to reprogram the code to fix | this one bug, since it took me a week of frustration to | find it. https://bugzilla.samba.org/ cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAinvZIR7qMdg1EfYRAjKGAJ9iygUxN+IAd+fZwUJWSuedL4noTgCfbOch CS37XpWV5q6PBtMZmlsUCSA=QLK4 -----END PGP SIGNATURE-----
----- Original Message ----- From: "Gerald (Jerry) Carter" <jerry@samba.org> To: "blfs" <blfs@comcast.net> Cc: <samba@lists.samba.org> Sent: Saturday, April 24, 2004 9:38 AM Subject: Re: [Samba] Verified bug in Woody Samba> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > blfs wrote: > > | How do I go about reporting this error? I would also > | not mind taking the time to reprogram the code to fix > | this one bug, since it took me a week of frustration to > | find it. > > https://bugzilla.samba.org/ > >OK, so I go to this page: https://bugzilla.samba.org/enter_bug.cgi Now what? Samba 2.2 is not listed.
I have spent the last week trying to figure out why the command smbclient -L win98server kept crapping out. After grepping through the source code, I figured out the error was in gethostbyname(I think). The solution to this problem is running the command smbclient -L win98server -R bcast instead. But that still leaves it to the next person to figure this all out, and that is not really a good solution. smbclient -L win98server should be a workable command. How do I go about reporting this error? https://bugzilla.samba.org/enter_bug.cgi has no category for Samba 2.2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 blfs wrote: | OK, so I go to this page: | | https://bugzilla.samba.org/enter_bug.cgi | | Now what? | | Samba 2.2 is not listed. Sorry. Thought you were on 3.0. There is no further development going on for the 2.2 branch. If you can reproduce this against 3.0.x, then let us know. cheers, jerry - ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "...a hundred billion castaways looking for a home." ----------- Sting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAjVmpIR7qMdg1EfYRAn6GAJ4gFWmwCHMaECTlBELJEkJQk5Ah8wCgt0Qg /600h394hWThqbgbOs2ixko=B7zT -----END PGP SIGNATURE-----
On Sat, Apr 24, 2004 at 03:41:18PM -0500, blfs wrote:> > ----- Original Message ----- > From: "Gerald (Jerry) Carter" <jerry@samba.org> > To: "blfs" <blfs@comcast.net> > Cc: <samba@lists.samba.org> > Sent: Saturday, April 24, 2004 9:38 AM > Subject: Re: [Samba] Verified bug in Woody Samba > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > blfs wrote: > > > > | How do I go about reporting this error? I would also > > | not mind taking the time to reprogram the code to fix > > | this one bug, since it took me a week of frustration to > > | find it. > > > > https://bugzilla.samba.org/ > > > > > > > OK, so I go to this page: > > https://bugzilla.samba.org/enter_bug.cgi > > Now what? > > Samba 2.2 is not listed.We are not accepting bugs against Samba 2.2 unless they are security problems. Samba2.x is no longer actively developed and is in security maintanence mode only. I suggest you file a bug with the Debian project and ask them to update to a maintained version of Samba. Cheers, Jeremy.