I think not. It's reporting how long each job took, not that the overall
boot time increased by 10s. The analyze output was accurate.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Ok, I did some testing. I setup a zesty vm, installed samba (smbd and
nmbd) on it, then configured it to not bring up the network at boot time
(/etc/network/interfaces <- remove "auto eth0"). I can then login at the
console and bring eth0 up or down with "ifup" and "ifdown" commands at
will.
Here
Ok, so please attach a fresh set of logs right after a reboot where the problem
happens. I would like:
- /var/log/syslog
- /var/log/samba/log.nmbd
- /var/log/samba/log.smbd
- ps fauxw output after boot
I'll correlate timestamps between them to try to see what's going on. I
suspect the fact that
Can you get a "ps fauxww" output right before and after the "systemctl
restart" when "status" shows the supervising message?
Something like this:
$ ps fauxw > ps-before.txt
$ sudo systemctl restart nmbd.service
$ sudo systemctl status nmbd.service
$ ps fauxw > ps-after.txt
but only if "status"
After you systemctl restart, do you also get a 10s delay between the
"supervising" and "started" lines in the output of systemctl status
nmbd.service?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Thanks.
I'm not seeing anything *immediately* wrong, just that nmbd sometimes either
can't find a network, or is getting errors trying to send packets to it. Like:
Packet send failed to 192.168.0.255(138) ERRNO=Invalid argument
...
send_netbios_packet: send_packet() to IP 192.168.0.255 port
Thanks for filing this bug in Ubuntu.
Could you please share the following files:
- /etc/samba/smb.conf
- /var/log/samba/log* (all files in /var/log/samba that begin with "log")
Finally, please also share the output of this command (you may redirect
the output to a file and attach that file
