[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-07-31 Thread Andreas Hasenack
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 instead):

sudo systemctl status smbd.service nmbd.service winbind.service samba-
ad-dc.service


Thanks!


** Changed in: samba (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-07-31 Thread Andreas Hasenack
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 137 failed
...
  reload_interfaces: No subnets to listen to. Waiting..

How is the network brought up on this machine where you experience this
problem? Is it wired, wireless, managed by network-manager or
/etc/network/interfaces, etc?

Regarding the non-child process, do you experience the same delay and
message from systemd about non-child process if you restart nmbd after
boot? Try something like this:

$ sudo systemctl status nmbd.service
(should print basically the same that you showed in your first comment)

Then restart it, and get status again:
$ sudo systemctl restart nmbd.service
$ sudo systemctl status nmbd.service

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-07-31 Thread Andreas Hasenack
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.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-08-01 Thread Andreas Hasenack
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" showed the 10s delay. If it didn't, then repeat
from the top. And at the end also attach /var/log/samba/log.nmbd. Let's
see if we can catch it on the act.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-08-02 Thread Andreas Hasenack
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 networking (wifi) is only up at the very end has
something to do with it.

Is wifi connected at the login screen, or only after you login?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-08-30 Thread Andreas Hasenack
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 is what I observed:

- the boot never hangs
- systemd will give up on the nmbd job after 1min30s. Note that this wait 
happens in the background and doesn't block other jobs (unless they depend on 
nmbd, which isn't the case). If I login at the console (still no network) and 
run "systemd-analyze blame" before that timeout, it will say the system is 
still booting.
- nmbd actually starts as usual, detects there is no network, and wait for the 
network *forever*: there is no timeout. Its loop is essentially this:
while (iface_count_v4_nl() == 0) {
sleep(5);
load_interfaces();
}
- that's when it logs the message "No local IPv4 non-loopback interfaces 
available, waiting for interface...". It really waits forever.
- in that loop you will notice that it performs a check every 5s. That's why 
you see the "10s extra delay" every time with such precision: you probably 
logged between 5-10s after nmbd was started.
- if I run systemd-analyze blame after the 1min30s timeout, i.e., after systemd 
is "happy" that the system booted because it gave up on the nmbd job, then it 
will output nmbd.service at the very top with 1m30s, as expected.

To summarize, I believe what's happening is correct and normal for a
machine which only connects to the network after the user logs in. It's
not blocking your boot, nor delaying your login for an extra 10s: that
wait happens in the background, in parallel with all the rest that's
running. And as soon as the network is available, nmbd will detect that
in one if its 5s interval checks, and exit the loop and do its job.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1706990] Re: With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second boot time regression

2017-08-31 Thread Andreas Hasenack
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.
https://bugs.launchpad.net/bugs/1706990

Title:
  With samba installed on Kubuntu 17.04, nmbd.service causes a 10 second
  boot time regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1706990/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs