MasterTacoChief
Explorer
- Joined
- Feb 20, 2017
- Messages
- 67
I had smbd crash this evening. It did not automatically restart or send a report email like it did with the issue in 9.10.2-U4. The result was the server could be pinged, but could not connect to network shares in Windows. After about 4 days of uptime.
I checked /var/log/messages and found this:
Manually stopped/started SMB from the web interface and got this output:
This is on the main machine in my signature.
I checked /var/log/messages and found this:
Jun 13 23:10:26 nas kernel: Failed to write core file for process smbd (error 14)
Jun 13 23:10:26 nas kernel: Failed to write core file for process smbd (error 14)
Jun 13 23:10:26 nas kernel: pid 92231 (smbd), uid 0: exited on signal 6
Manually stopped/started SMB from the web interface and got this output:
Jun 14 00:41:18 nas notifier: winbindd not running? (check /var/run/samba/winbindd.pid).
Jun 14 00:41:18 nas notifier: smbd not running? (check /var/run/samba/smbd.pid).
Jun 14 00:41:18 nas notifier: nmbd not running? (check /var/run/samba/nmbd.pid).
Jun 14 00:41:31 nas notifier: Performing sanity check on Samba configuration: OK
Jun 14 00:41:31 nas notifier: Starting nmbd.
Jun 14 00:41:31 nas notifier: Starting smbd.
Jun 14 00:41:31 nas notifier: Starting winbindd.
This is on the main machine in my signature.