Actions
Bug #9882
closed
smbd: service exit timed out during terminating
Start date:
2018-10-10
Due date:
% Done:
0%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
smbd cannot be started after terminating (Bug #9881) due to previous instance of smbd is still in the kernel.
From dmesg:
Oct 10 16:01:20 oi-2018 svc.startd[9]: [ID 122153 daemon.warning] svc:/network/smb/server:default: Method or service exit timed out. Killing contract 101
From /var/svc/log/network-smb-server:default.log
[ Oct. 10 16:00:20 Stopping because process dumped core. ] [ Oct. 10 16:00:20 Executing stop method (:kill). ] [ Oct. 10 16:01:20 Method or service exit timed out. Killing contract 101. ] [ Oct. 10 16:01:21 Method or service exit timed out. Killing contract 101. ] [ Oct. 10 16:01:22 Method or service exit timed out. Killing contract 101. ] [ Oct. 10 16:01:23 Method or service exit timed out. Killing contract 101. ]
"~# ps |grep smbd" is empty
From mdb:
::ps!grep smbd R 102563 1 102563 102563 0 0xc2000002 ffffff0233127040 smbd
::threadlist -v
ffffff019e171480 ffffff0233127040 ffffff01b9dbc7c0 1 59 ffffff01d715dad0
PC: _resume_from_idle+0x126 CMD: /usr/lib/smbsrv/smbd start
stack pointer for thread ffffff019e171480: ffffff0004969920
[ ffffff0004969920 _resume_from_idle+0x126() ]
swtch+0x18a()
cv_wait+0x89()
taskq_wait+0xbb()
taskq_destroy+0x77()
smb_server_shutdown+0xef()
smb_server_delete+0x245()
smb_drv_close+0x1d()
dev_close+0x31()
device_close+0xd8()
spec_close+0x1d9()
fop_close+0x61()
closef+0x97()
closeall+0x82()
proc_exit+0x450()
exit+0x15()
psig+0x358()
post_syscall+0x895()
syscall_exit+0x70()
Related issues
Updated by Vitaliy Gusev over 4 years ago
- Related to Bug #9881: smbd terminated by SIGABRT after smb_account_free() added
Updated by Gordon Ross over 4 years ago
We did some fixes in that area. Some re-ordering of tear down, if I remember correctly.
(I really should upstream some later SMB server bits.)
Updated by Vitaliy Gusev over 4 years ago
::smbsess
SESSION IP_ADDR PORT DIALECT STATE ffffff06f05bc358 172.16.3.253 61240 0x210 DISCONNECTED
Other stacks that describe situation:
ffffff001f258c40 fffffffffbc38040 0 0 61 ffffff06f025a872
PC: _resume_from_idle+0x112 TASKQ: smb_workers
stack pointer for thread ffffff001f258c40: ffffff001f256450
[ ffffff001f256450 _resume_from_idle+0x112() ]
swtch+0x12e()
cv_wait+0x57()
cv_wait_sig+0x74()
str_cv_wait+0xa5()
strwaitq+0x2e5()
strread+0x139()
sotpi_recvmsg+0x102()
socket_recvmsg+0x1e()
ksocket_recvmsg+0x130()
smb_opipe_read+0x87()
smb_opipe_transceive+0xf1()
smb_opipe_fsctl+0x33()
smb2_ioctl+0x203()
smb2sr_work+0x5c9()
smb2_tq_work+0x47()
taskq_d_thread+0xae()
thread_start+8()
ffffff00230f7c40 fffffffffbc38040 0 0 60 ffffff06f024ee90
PC: _resume_from_idle+0x112 TASKQ: smb_receivers
stack pointer for thread ffffff00230f7c40: ffffff00230f7a40
[ ffffff00230f7a40 _resume_from_idle+0x112() ]
swtch+0x12e()
cv_wait+0x57()
smb_slist_wait_for_empty+0x32()
smb_session_cancel+0x30()
smb_session_receiver+0x8f()
smb_server_receiver+0x21()
taskq_d_thread+0xae()
thread_start+8()
Updated by Gordon Ross over 3 years ago
Updated by Gordon Ross over 2 years ago
- Status changed from New to Resolved
Assuming this has been resolved in more recent code.
Actions