[Samba] Samba just died? smbd/sec_ctx.c:set_sec_ctx(241)

[David C. Rankin]

Jeremy Allison wrote:
> On Mon, Aug 11, 2008 at 06:07:10PM -0500, David C. Rankin wrote:
>> Listmates,
>>
>> 	Running 3.2.1-0.1.126-1867-SUSE-SL10.3 (in standalone) I was quite 
>> 	surprised samba DOA. Further research show that it died shortly after 
>> midnight with the last relevant log entries being:
>>
>> [2008/08/10 00:24:15, 3] smbd/sec_ctx.c:set_sec_ctx(241)
>>   setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
>> [2008/08/10 00:24:15, 3] smbd/connection.c:yield_connection(69)
>>   Yielding connection to
>> [2008/08/10 00:24:15, 3] smbd/server.c:exit_server_common(768)
>>
>> 	After running samba since 2.0.7, this is the first time I have had 
>> 	it just die on me without me doing something to cause it to die. Any 
>> thoughts on the matter? Can I provide additional information?
> 
> This doesn't look like death, but orderly termination.
> 
> Jeremy.
> 

Jeremy,

	That is the mystery. A further look at syslog shows that the shutdown occurred 
as part of the package update (at Aug 10 00:01:47):

Aug  9 23:42:25 bonza sshd[13848]: Accepted publickey for david from 
66.76.63.120 port 51503 ssh2
Aug  9 23:59:39 bonza sudo:    david : TTY=pts/1 ; PWD=/home/david ; USER=root 
; COMMAND=/usr/bin/zypper up
Aug 10 00:01:47 bonza sudo:    david : TTY=pts/1 ; PWD=/home/david ; USER=root 
; COMMAND=/usr/bin/zypper up -t package
Aug 10 00:15:04 bonza syslog-ng[2875]: STATS: dropped 0
Aug 10 00:24:13 bonza shadow[16389]: group already exists - group=ntadmin, by=0
Aug 10 00:24:15 bonza nmbd[2944]: [2008/08/10 00:24:15, 0] 
nmbd/nmbd.c:terminate(58)
Aug 10 00:24:15 bonza nmbd[2944]:   Got SIGTERM: going down...

	The bigger questions is why, during an update, did the package manager fail to 
restart smbd or nmbd? I'll pass this along to Lars as well. May be a package 
problem. On all previous updates the services have automatically been 
restarted, I guess by the post-install script. That didn't happen here. There 
was no problem with the config, I just issues a simple rscmb restart and (1) 
found out smbd wasn't running, and (2) it started without any problems or 
warnings. So it looks like the start command was never given after package update.

-- 
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com