Arch Linux

liticovjesac

Member

From: Stockholm-Belgrade-Köln

Registered: 2008-07-16

Posts: 110

[SOLVED] nmbd.service failed to start after update to samba 4.5.0.1

Hi,
I just update to latest samba 4.5.0.1 and nmbd failed to start.Thats what i see at least running systemctl.

nmbd.service                                           loaded failed failed 

I have checked /var/cache/samba searching for msg but there is only msg.lock folder
Any idea what should i do?

Last edited by liticovjesac (2016-09-11 13:51:50)

HiImTye

Member

From: Halifax, NS, Canada

Registered: 2012-05-09

Posts: 1,072

Re: [SOLVED] nmbd.service failed to start after update to samba 4.5.0.1

journalctl is useful for debugging failed services

firekage

Member

From: Eastern Europe, Poland

Registered: 2013-06-30

Posts: 617

Re: [SOLVED] nmbd.service failed to start after update to samba 4.5.0.1

Hi,
I just update to latest samba 4.5.0.1 and nmbd failed to start.Thats what i see at least running systemctl.

nmbd.service                                           loaded failed failed 

I have checked /var/cache/samba searching for msg but there is only msg.lock folder
Any idea what should i do?

Downgrade tevent package. You should see that on forum recently there are few topics about Samba, problems and crashing after the last update - this package is at fault. Yesterday, i lost half day trying to figure what is going on with Samba on my 3 machines... could not use it at all.

liticovjesac

Member

From: Stockholm-Belgrade-Köln

Registered: 2008-07-16

Posts: 110

Re: [SOLVED] nmbd.service failed to start after update to samba 4.5.0.1

This is what I am getting:

● nmbd.service - Samba NetBIOS name server
   Loaded: loaded (/usr/lib/systemd/system/nmbd.service; enabled; vendor preset: disabled)
   Active: failed (Result: core-dump) since Sun 2016-09-11 12:20:00 CEST; 5min ago
  Process: 581 ExecStart=/usr/bin/nmbd -D (code=exited, status=0/SUCCESS)
 Main PID: 596 (code=dumped, signal=ABRT)

Sep 11 12:20:00 vukodlak nmbd[596]:    #7 /usr/bin/nmbd(listen_for_packets+0xff) [0x563d9851cb2f]
Sep 11 12:20:00 vukodlak nmbd[596]:    #8 /usr/bin/nmbd(main+0xd02) [0x563d9850be42]
Sep 11 12:20:00 vukodlak nmbd[596]:    #9 /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7fa40e586291]
Sep 11 12:20:00 vukodlak nmbd[596]:    #10 /usr/bin/nmbd(_start+0x2a) [0x563d9850c20a]
Sep 11 12:20:00 vukodlak nmbd[596]: [2016/09/11 12:20:00.295824,  0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 11 12:20:00 vukodlak nmbd[596]:   dumping core in /var/log/samba/cores/nmbd
Sep 11 12:20:00 vukodlak nmbd[596]: 
Sep 11 12:20:00 vukodlak systemd[1]: nmbd.service: Main process exited, code=dumped, status=6/ABRT
Sep 11 12:20:00 vukodlak systemd[1]: nmbd.service: Unit entered failed state.
Sep 11 12:20:00 vukodlak systemd[1]: nmbd.service: Failed with result 'core-dump'.

At the same time I have noticed another failed message, something about network connection during boot process. I use gnome network manager and obviously i have connection but maybe is this somehow connected with samba problems since i havent seen thismessage before:

Sep 11 12:20:41 vukodlak kernel: wlp2s0: deauthenticating from c0:56:27:7f:70:17 by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 11 12:20:41 vukodlak avahi-daemon[347]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Sep 11 12:20:41 vukodlak NetworkManager[358]: <info>  [1473589241.6694] device (wlp2s0): set-hw-addr: set MAC address to B6:9D:72:85:3B
Sep 11 12:20:41 vukodlak wpa_supplicant[391]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=c0:56:27:7f:70:17 reason=3 locally_generated=1
Sep 11 12:20:41 vukodlak avahi-daemon[347]: Withdrawing address record for 192.168.1.102 on wlp2s0.
Sep 11 12:20:41 vukodlak avahi-daemon[347]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.102.
Sep 11 12:20:41 vukodlak avahi-daemon[347]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Sep 11 12:20:41 vukodlak NetworkManager[358]: <info>  [1473589241.6843] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Sep 11 12:20:41 vukodlak kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Sep 11 12:20:41 vukodlak dbus[348]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freede
Sep 11 12:20:41 vukodlak NetworkManager[358]: <warn>  [1473589241.7114] sup-iface[0x2443b60,wlp2s0]: connection disconnected (reason -3
Sep 11 12:20:41 vukodlak NetworkManager[358]: <info>  [1473589241.7116] device (wlp2s0): supplicant interface state: completed -> disco
Sep 11 12:20:41 vukodlak systemd[1]: Starting Network Manager Script Dispatcher Service...
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit NetworkManager-dispatcher.service has begun starting up.
Sep 11 12:20:41 vukodlak dbus[348]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 11 12:20:41 vukodlak systemd[1]: Started Network Manager Script Dispatcher Service.
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit NetworkManager-dispatcher.service has finished starting up.
-- 
-- The start-up result is done.
Sep 11 12:20:41 vukodlak nm-dispatcher[860]: req:1 'down' [wlp2s0]: new request (0 scripts)
Sep 11 12:20:41 vukodlak nm-dispatcher[860]: req:1 'down' [wlp2s0]: completed: no scripts
Sep 11 12:20:42 vukodlak dbus-daemon[663]: Activating service name='org.freedesktop.secrets'
Sep 11 12:20:43 vukodlak gnome-keyring-daemon[867]: couldn't access control socket: /run/user/1000/keyring/control: No such file or dir
Sep 11 12:20:43 vukodlak org.freedesktop.secrets[663]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No s
Sep 11 12:20:43 vukodlak dbus-daemon[663]: Successfully activated service 'org.freedesktop.secrets'

cod3poet

Member

Registered: 2016-09-11

Posts: 3

Re: [SOLVED] nmbd.service failed to start after update to samba 4.5.0.1

Issues with samba latest have been solved here - https://bbs.archlinux.org/viewtopic.php?id=216957 can give that a try.

---

Started with Slackware, will run Arch forever.

liticovjesac

Member

From: Stockholm-Belgrade-Köln

Registered: 2008-07-16

Posts: 110

Re: [SOLVED] nmbd.service failed to start after update to samba 4.5.0.1

Thanx to all.
I can confirm that downgrading of package tevent 0.9.30 to version 0.9.29 had fixed a problem. Samba works and I can access samba share. Now we have to wait for next tevent package. I will mark topic as solved.