Dominique Northecide
1997-Sep-02 16:09 UTC
Syslog err msgs from samba-1.9.16p11 on HP-UX 10.10
To: Members of the SAMBA mailing list Does any one know of the cause/fix for the SMBD error messages below? I had been using samba-1.9.16p11 fine for quite a while, and noticed the following syslog entries as several NT 4.0 clients started to have problems doing some software builds (using Atria-ClearCase via SAMBA on HP-UX 10.10 servers). Please send responses to: <dominiqu@plhp002.comm.mot.com> Here are the four error messages: smbd[10572]: Error writing 101 bytes to client. -1. Exiting smbd[22574]: getpeername failed smbd[23902]: ... couldn't find free connection smbd[23902]: ... couldn't find service Any insight into the cause and fix will be greatly appreciated. TX -- Dominique Northecide <dominiqu@plhp002.comm.mot.com>
Stefaan A Eeckels
1997-Sep-03 19:44 UTC
Syslog err msgs from samba-1.9.16p11 on HP-UX 10.10
On 03-Sep-97 samba@samba.anu.edu.au wrote:> Does any one know of the cause/fix for the SMBD error messages below? > I had been using samba-1.9.16p11 fine for quite a while, and noticed > the following syslog entries as several NT 4.0 clients started to have > problems doing some software builds (using Atria-ClearCase via SAMBA on > HP-UX 10.10 servers). > > Please send responses to: <dominiqu@plhp002.comm.mot.com> > > Here are the four error messages: > > smbd[10572]: Error writing 101 bytes to client. -1. ExitingThis one should be fixed in 1.9.17 - it was caused by Samba trying to validate the guest account on the NT PDC. The guest account is indicated by an empty record, and NT seems to know no better but to simply hang up the connection. We had our power users (with oodles of shortcuts on their desktops) start up to 20 instances of smbd before finally settling down.> > smbd[22574]: getpeername failedThis one also should be fixed in 1.9.17. It was caused by the expansion routine calling getpeername before the socket had been opened (even though the % sequence requiring the call did not appear in the string). An unwelcome side effect was that the IP address of the client remained stuck at 0.0.0.0 for the remainder of the session> > smbd[23902]: ... couldn't find free connection > > smbd[23902]: ... couldn't find serviceNo idea for the last two - they look genuine. Maybe someone else has a better idea?>HTH Stefaan ___________________________________________________________________ Stefaan A Eeckels (Stefaan.Eeckels@ecc.lu) "The nice thing about standards is that there are so many of them to choose from." -- Andrew S Tanenbaum ___________________________________________________________________