Re: [Samba] What could cause an "unclean shutdown" of process?
Hello, I added "printcap cache time = 0" to my smb.conf and the printcap related messages disappeared from my log. Thank you very much for that!! But the 'unclean shutdown of PID xxx' was not related to printcap. (If you look in the log, you see that it happens 12 minutes after the last printcap rescanning and one minutes before the next.) I made more tests, and the programs that are running on the windows clients keep crashing. The only two things that I see in samba logs are these 'unclean shutdown of PID xxx' messages in log.smbd and a sudden stop in a long long list of transactions in log.. There are minimal logs on the client side where I can see: "Error caused by: java.io.IOException: The specified network name is no longer available". (The client error seems to be logged 1 second after the server error, but their clock might not perfectly synchronized, so I can't say for sure what happens first.) I need to fix this problem, but I don't know how. So far, Google has brought me to similar problems (e.g. http://lists.samba.org/archive/samba/2010-August/157948.html), but to no solution :( Any help would be greatly appreciated! Frederic On Wed, Aug 29, 2012 at 12:24 PM, David Disseldorp wrote: > Hi Frederic, > > On Wed, 29 Aug 2012 11:58:38 -0400 > Frederic Fournier wrote: > > > Thanks for the tip, I was also looking for a way to get rid of those > > Printcap messages that pops up every 13 minutes. (especially since there > is > > no printer on this server). > > > > But I only included those messages to give a bit of context: its the > three > > messages in the middle that cause me trouble: > > smbd/server.c:292 Unclean shutdown of pid 32526 > > Scheduled cleanup of brl and lock database after unclean shutdown* > > Cleaning up brl and lock database after unclean shutdown* > > > > Do you know how I could find what causes the server to do an unclean > > shutdown of one of its process (and how to prevent it)? Because when > there > > is such an unclean shutdown, there is also a crash on the client side. > (Or > > maybe it's the other way around?) How could I find more about it? > > The 'cleanup...after unclean shutdown' messages are also caused by the > printcap process. It does not register it's pid which results in > the parent smbd process complaining on SIGCHLD when the printcap process > exits. > > Cheers, David > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] What could cause an "unclean shutdown" of process?
Hello David, Thanks for the tip, I was also looking for a way to get rid of those Printcap messages that pops up every 13 minutes. (especially since there is no printer on this server). But I only included those messages to give a bit of context: its the three messages in the middle that cause me trouble: smbd/server.c:292 Unclean shutdown of pid 32526 Scheduled cleanup of brl and lock database after unclean shutdown* Cleaning up brl and lock database after unclean shutdown* Do you know how I could find what causes the server to do an unclean shutdown of one of its process (and how to prevent it)? Because when there is such an unclean shutdown, there is also a crash on the client side. (Or maybe it's the other way around?) How could I find more about it? Thank you very much for your help!! Frederic On Wed, Aug 29, 2012 at 11:46 AM, David Disseldorp wrote: > Hi Frederic, > > On Wed, 29 Aug 2012 11:04:22 -0400 > Frederic Fournier wrote: > > > I notice this in the log.smbd at the time of the crash: > > [2012/08/28 17:25:21.980609, 3] > smbd/server.c:629(smbd_parent_housekeeping) > > Printcap cache time expired. > > [2012/08/28 17:25:21.980679, 3] printing/pcap.c:138(pcap_cache_reload) > > reloading printcap cache > > [2012/08/28 17:25:21.980756, 3] printing/pcap.c:189(pcap_cache_reload) > > reload status: ok > > *[2012/08/28 17:37:08.715154, 3] smbd/server.c:292(remove_child_pid)* > > * smbd/server.c:292 Unclean shutdown of pid 32526* > > *[2012/08/28 17:37:08.715318, 1] smbd/server.c:300(remove_child_pid)* > > * Scheduled cleanup of brl and lock database after unclean shutdown* > > *[2012/08/28 17:37:28.722037, 1] smbd/server.c:272(cleanup_timeout_fn)* > > * Cleaning up brl and lock database after unclean shutdown* > > [2012/08/28 17:38:22.509303, 3] > smbd/server.c:629(smbd_parent_housekeeping) > > Printcap cache time expired. > > [2012/08/28 17:38:22.509403, 3] printing/pcap.c:138(pcap_cache_reload) > > reloading printcap cache > > [2012/08/28 17:38:22.509499, 3] printing/pcap.c:189(pcap_cache_reload) > > reload status: ok > > I don't see anything that catches my eye in the other logs (log.nmbd, > > log., log., log.winbindd). The log. > > shows a very long list of transactions that stops suddently at the time > of > > the 'unclean shutdown'. > > These messages are the side effect of the asynchronous printcap update > process exiting normally, and should not be causing any problems. > To confirm this, you could change the "printcap cache time" setting to > 0. > > Cheers, David > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] What could cause an "unclean shutdown" of process?
Hello everyone, I've been experiencing many problems recently with windows software parsing large text files stored on a samba share (smb version 3.6.3 on ubuntu12.04). The software, which are running on windows XP stations, are crashing quite often. I notice this in the log.smbd at the time of the crash: [2012/08/28 17:25:21.980609, 3] smbd/server.c:629(smbd_parent_housekeeping) Printcap cache time expired. [2012/08/28 17:25:21.980679, 3] printing/pcap.c:138(pcap_cache_reload) reloading printcap cache [2012/08/28 17:25:21.980756, 3] printing/pcap.c:189(pcap_cache_reload) reload status: ok *[2012/08/28 17:37:08.715154, 3] smbd/server.c:292(remove_child_pid)* * smbd/server.c:292 Unclean shutdown of pid 32526* *[2012/08/28 17:37:08.715318, 1] smbd/server.c:300(remove_child_pid)* * Scheduled cleanup of brl and lock database after unclean shutdown* *[2012/08/28 17:37:28.722037, 1] smbd/server.c:272(cleanup_timeout_fn)* * Cleaning up brl and lock database after unclean shutdown* [2012/08/28 17:38:22.509303, 3] smbd/server.c:629(smbd_parent_housekeeping) Printcap cache time expired. [2012/08/28 17:38:22.509403, 3] printing/pcap.c:138(pcap_cache_reload) reloading printcap cache [2012/08/28 17:38:22.509499, 3] printing/pcap.c:189(pcap_cache_reload) reload status: ok I don't see anything that catches my eye in the other logs (log.nmbd, log., log., log.winbindd). The log. shows a very long list of transactions that stops suddently at the time of the 'unclean shutdown'. Do you have any idea what could cause this 'unclean shutdown'? What would be the best way to further diagnose this problem? I've looked into the servers' log without noticing anything strange? Thank you very much for your help, Frederic -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] "Network name no longer available" and other problems on windows client
Hello, I have a samba server with a public share containing large text files that are used as databases by software running on windows clients (Windows XP x64 sp2 for the most part). Recently, I made some changes to my pipeline: I changed the hardware of the samba server, and I upgraded the OS from Ubuntu 10.04 to 12.04 (which meant also upgrading smbd from 3.4.7 to 3.6.3). In the mean time, the version of the softwares using the share was also upgraded. After all those changes, on the surface, everything works: I can map the share to a drive on the win clients, open the share, and read or write files. The softwares using the share are also able to read and write to the mapped share. But those softwares often crash, or worse, have one of their subprocess go in an infinite loop and never exit. And this does not happen if I put the large text files locally on the windows workstation, so the problems seems to have something to do with samba. When the software crashes, I can often see a "Network name no longer available" in their error logs. When their subprocess goes AWOL, I don't see any error message. Here is my smb.conf: [global] >workgroup = PROTEOMIQUE >server string = %h server (Samba, Ubuntu) >wins support = yes >name resolve order = wins lmhosts host bcast >dns proxy = no >#name resolve order = lmhosts host bcast > wins >local master = yes >preferred master = yes >domain master = yes >host msdfs = yes >interfaces = eth0 lo >bind interfaces only = yes >hosts allow = 192.168.128.10 192.168.128.11 192.168.128.12 > 192.168.128.13 [...] >log level = 3 >log file = /var/log/samba/log.%m >syslog only = no >syslog = 0 >max log size = 1 >panic action = /usr/share/samba/panic-action %d >encrypt passwords = true >passdb backend = tdbsam >obey pam restrictions = yes >unix password sync = yes >passwd program = /usr/bin/passwd %u >passwd chat = *Enter\snew\s*\spassword:* %n\n > *Retype\snew\s*\spassword:* %n\n *password\supdated\\ > ssuccessfully* . >pam password change = yes >map to guest = bad user > >## FF : Disabling printing > functionality: >load printers = no >printing = bsd >printcap name = /dev/null >disable spoolss = yes > > [Databases] >path = /pubseq >read only = no >guest ok = yes >msdfs root = yes > I have set samba to log level 3, and I have been searching around and investigating this matter for the last few days. But I have little experience with network and samba administration and I'm way in over my head with this and the many thousand lines of logs generated by the server. Any help or any pointer as to how to diagnose and solve this problem would be greatly appreciated!!! Frederic -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
