Bug#840608: systemd: nmbd.service long time to start when rebooting
No difference between allow-hotplug auto directives in /etc/network/interfaces. On 10/17/16, Kirill Sutulo wrote: > this is nmbd strace output > > On 10/13/16, Michael Biebl wrote: >> Am 13.10.2016 um 15:33 schrieb Kirill Sutulo: >>> I can not find someone waiting for this service. The problem persists >>> also at the two VMs. >>> >>> Maybe strace log helps? Or reportbug to samba package? >> >> A strace would be helpful. >> >>> On 10/13/16, Kirill Sutulo wrote: >>>> Yes. restarting service is very fast. >>>> >>>> On 10/13/16, Michael Biebl wrote: >>>>> Control: tags -1 + moreinfo >>>>> >>>>> Hi >>>>> Am 13.10.2016 um 10:33 schrieb kirill: >>>>> >>>>>> systemd-analyze blame | head -8 >>>>>> 22.026s nmbd.service >>>>>> 6.217s systemd-tmpfiles-setup.service >>>>>> 4.462s networking.service >>>>>> 3.521s alsa-restore.service >>>>>> 3.474s pppd-dns.service >>>>>> 3.473s incron.service >>>>>> 3.465s systemd-logind.service >>>>>> 3.456s rc-local.service >>>>>> --- >>>>>> systemd-analyze critical-chain >>>>>> >>>>>> graphical.target @36.509s >>>>>> └─multi-user.target @36.509s >>>>>> └─smbd.service @35.994s +514ms >>>>>> └─nmbd.service @13.967s +22.026s >>>>>> └─basic.target @13.946s >>>>>> └─paths.target @13.946s >>>>>> └─cups.path @13.946s >>>>>> └─sysinit.target @13.871s >>>>>> └─nfs-common.service @13.481s +389ms >>>>>> └─rpcbind.target @13.481s >>>>>> └─rpcbind.service @12.167s +1.313s >>>>>> └─network-online.target @12.167s >>>>>> └─network.target @12.167s >>>>>> └─ifup@eth0.service @12.167s >> >> If you change your network configuration in /etc/network/interface and >> you use "auto" instead of "allow-hotplug", does it make a difference? >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
Bug#840608: systemd: nmbd.service long time to start when rebooting
I can not find someone waiting for this service. The problem persists also at the two VMs. Maybe strace log helps? Or reportbug to samba package? Thank You! On 10/13/16, Kirill Sutulo wrote: > Yes. restarting service is very fast. > > On 10/13/16, Michael Biebl wrote: >> Control: tags -1 + moreinfo >> >> Hi >> Am 13.10.2016 um 10:33 schrieb kirill: >> >>> systemd-analyze blame | head -8 >>> 22.026s nmbd.service >>> 6.217s systemd-tmpfiles-setup.service >>> 4.462s networking.service >>> 3.521s alsa-restore.service >>> 3.474s pppd-dns.service >>> 3.473s incron.service >>> 3.465s systemd-logind.service >>> 3.456s rc-local.service >>> --- >>> systemd-analyze critical-chain >>> >>> graphical.target @36.509s >>> └─multi-user.target @36.509s >>> └─smbd.service @35.994s +514ms >>> └─nmbd.service @13.967s +22.026s >>> └─basic.target @13.946s >>> └─paths.target @13.946s >>> └─cups.path @13.946s >>> └─sysinit.target @13.871s >>> └─nfs-common.service @13.481s +389ms >>> └─rpcbind.target @13.481s >>> └─rpcbind.service @12.167s +1.313s >>> └─network-online.target @12.167s >>> └─network.target @12.167s >>> └─ifup@eth0.service @12.167s >>> └─networking.service @7.704s +4.462s >>> └─systemd-random-seed.service @7.249s +454ms >>> └─var.mount @6.357s +874ms >>> >>> └─systemd-fsck@dev-disk-by\x2duuid-0d8732cc\x2d691a\x2d41a0\x2d9266\x2d6690e358a902.service >>> @5.048s +1.309s >>> >>> └─dev-disk-by\x2duuid-0d8732cc\x2d691a\x2d41a0\x2d9266\x2d6690e358a902.device >>> @5.047s >> >> >> Can you find out, what nmbd is waiting for? >> That smells like a network issue. I assume if you use >> systemctl restart nmbd.service when the system is running it doesn't >> take 22 seconds? >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
Bug#840608: systemd: nmbd.service long time to start when rebooting
Yes. restarting service is very fast. On 10/13/16, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Hi > Am 13.10.2016 um 10:33 schrieb kirill: > >> systemd-analyze blame | head -8 >> 22.026s nmbd.service >> 6.217s systemd-tmpfiles-setup.service >> 4.462s networking.service >> 3.521s alsa-restore.service >> 3.474s pppd-dns.service >> 3.473s incron.service >> 3.465s systemd-logind.service >> 3.456s rc-local.service >> --- >> systemd-analyze critical-chain >> >> graphical.target @36.509s >> └─multi-user.target @36.509s >> └─smbd.service @35.994s +514ms >> └─nmbd.service @13.967s +22.026s >> └─basic.target @13.946s >> └─paths.target @13.946s >> └─cups.path @13.946s >> └─sysinit.target @13.871s >> └─nfs-common.service @13.481s +389ms >> └─rpcbind.target @13.481s >> └─rpcbind.service @12.167s +1.313s >> └─network-online.target @12.167s >> └─network.target @12.167s >> └─ifup@eth0.service @12.167s >> └─networking.service @7.704s +4.462s >> └─systemd-random-seed.service @7.249s +454ms >> └─var.mount @6.357s +874ms >> >> └─systemd-fsck@dev-disk-by\x2duuid-0d8732cc\x2d691a\x2d41a0\x2d9266\x2d6690e358a902.service >> @5.048s +1.309s >> >> └─dev-disk-by\x2duuid-0d8732cc\x2d691a\x2d41a0\x2d9266\x2d6690e358a902.device >> @5.047s > > > Can you find out, what nmbd is waiting for? > That smells like a network issue. I assume if you use > systemctl restart nmbd.service when the system is running it doesn't > take 22 seconds? > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#771386: pidgin: Can't connect to XMPP servers with self-signed certs and invalid
Package: pidgin Version: 2.10.10-1~deb7u1 Followup-For: Bug #771386 I copied the certificate file to ~/.purple/certificates/x509/tls_peers/myxmpp.server.name but keep getting the message > The certificate for localhost could not be validated. > The certificate chain presented is invalid. -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pidgin depends on: ii gconf2 3.2.5-1+build1 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38+deb7u6 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1+deb7u4 ii libdbus-glib-1-20.100.2-1 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgstreamer0.10-0 0.10.36-1.2 ii libgtk2.0-0 2.24.10-2 ii libgtkspell02.0.16-1 ii libice6 2:1.0.8-2 ii libpango1.0-0 1.30.0-1 ii libpurple0 2.10.10-1~deb7u1 ii libsm6 2:1.2.1-2 ii libx11-62:1.5.0-1+deb7u1 ii libxml2 2.8.0+dfsg1-7+wheezy2 ii libxss1 1:1.2.2-1 ii perl-base [perlapi-5.14.2] 5.14.2-21+deb7u2 ii pidgin-data 2.10.10-1~deb7u1 Versions of packages pidgin recommends: ii gstreamer0.10-plugins-base 0.10.36-1.1 ii gstreamer0.10-plugins-good 0.10.31-3+nmu1 Versions of packages pidgin suggests: ii libsqlite3-0 3.7.13-1+deb7u1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
