** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706990
Title:
With samba installed on Kubuntu 17.04, nmbd.service causes a 10
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706990
Title:
Thanks for the thorough investigation, Andreas! So do you suspect that
there is a bug in systemd-analyze for reporting an erroneous 10s boot
time delay?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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, 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
Attached. I can't tell whether wifi is connected at the login screen
since the Breeze sddm login screen theme doesn't display wifi status.
But FWIW, I get a "wifi connected" notification as soon as the desktop
appears.
** Attachment added: "Logs after reboot"
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
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
So far I have not been able to reproduce the 10s delay after boot. It
only seems to happen on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706990
Title:
With samba installed on Kubuntu
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"
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"
I really appreciate your willingness to work with me on this issue,
Andreas! On second look, it appears that only sometimes does something
else start a new daemon:
Jul 31 15:40:35 Spectre systemd[1]: Starting Samba NMB Daemon...
Jul 31 15:40:35 Spectre systemd[1]: nmbd.service: Supervising
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
Bugs, which is subscribed to Ubuntu.
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.
The network is wireless, managed entirely from the KDE control panel's
GUI.
If I `systemctl restart` the nmbd service, it comes up in the same way
every time, always saying it's supervising a non-child process. However,
the PID of that process changes with every restart. It's like the
restart
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.
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
I've attached all the requested files inside a gzipped tar archive, as
there were a lot of files. The systemctl command output (in a file
called "systemctl-status-output.txt") does not include the output of
winbind.service, since that unit is not active.
** Attachment added: "Archive of all
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
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
21 matches
Mail list logo
