Author Topic: [SOLVED] Samba has stopped to work after upgrade to Zentyal 6.0  (Read 302 times)

devnull

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +3/-0
    • View Profile
Hi, after upgrade of the Zentyal 5.1 to 6.0 the samba module has stopped to work. Web interface has shown dialog to run "sudo dpkg --configure -a" but this ends with errors:

sudo dpkg --configure -a:
Code: [Select]
sudo dpkg --configure -a
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.15) ...
Job for samba-ad-dc.service failed because a timeout was exceeded.
See "systemctl status samba-ad-dc.service" and "journalctl -xe" for details.
invoke-rc.d: initscript samba-ad-dc, action "restart" failed.
● samba-ad-dc.service - Samba AD Daemon
   Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Sat 2020-03-14 12:33:15 CET; 8ms ago
     Docs: man:samba(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 10778 ExecStart=/usr/sbin/samba --foreground --no-process-group $SAMBAOPTIONS (code=exited, status=127)
 Main PID: 10778 (code=exited, status=127)

Mar 14 12:33:15 zentyal samba[10790]:   Exiting pid 10790 on SIGTERM
Mar 14 12:33:15 zentyal samba[10782]: [2020/03/14 12:33:15.808901,  0] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
Mar 14 12:33:15 zentyal samba[10782]:   Exiting pid 10782 on SIGTERM
Mar 14 12:33:15 zentyal samba[10793]: [2020/03/14 12:33:15.811795,  0] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
Mar 14 12:33:15 zentyal samba[10793]:   Exiting pid 10793 on SIGTERM
Mar 14 12:33:15 zentyal samba[10785]: [2020/03/14 12:33:15.813150,  0] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
Mar 14 12:33:15 zentyal samba[10785]:   Exiting pid 10785 on SIGTERM
Mar 14 12:33:15 zentyal systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=127/n/a
Mar 14 12:33:15 zentyal systemd[1]: samba-ad-dc.service: Failed with result 'timeout'.
Mar 14 12:33:15 zentyal systemd[1]: Failed to start Samba AD Daemon.
dpkg: error processing package samba (--configure):
 installed samba package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of zentyal-samba:
 zentyal-samba depends on samba; however:
  Package samba is not configured yet.

dpkg: error processing package zentyal-samba (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-mail:
 zentyal-mail depends on zentyal-samba; however:
  Package zentyal-samba is not configured yet.

dpkg: error processing package zentyal-mail (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-mailfilter:
 zentyal-mailfilter depends on zentyal-mail; however:
  Package zentyal-mail is not configured yet.

dpkg: error processing package zentyal-mailfilter (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-sogo:
 zentyal-sogo depends on zentyal-mail; however:
  Package zentyal-mail is not configured yet.

dpkg: error processing package zentyal-sogo (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
 samba
 zentyal-samba
 zentyal-mail
 zentyal-mailfilter
 zentyal-sogo


journalctl -xe
Code: [Select]
journalctl -xe
Mar 14 12:35:01 zentyal CRON[10818]: (root) CMD (/usr/share/zentyal-samba/slave-sync)
Mar 14 12:35:01 zentyal CRON[10817]: pam_unix(cron:session): session closed for user root
Mar 14 12:35:01 zentyal postfix/pickup[1004]: D4102206AB: uid=0 from=<root>
Mar 14 12:35:01 zentyal postfix/cleanup[10822]: warning: dict_ldap_connect: Unable to bind to server ldap://localhost:389 with dn CN=zentyal-mail-zentyal,CN=Users,DC=xd,D
Mar 14 12:35:01 zentyal postfix/cleanup[10822]: warning: ldap:/etc/postfix/valiases.cf lookup error for "root@zentyal.xd.local"
Mar 14 12:35:01 zentyal postfix/cleanup[10822]: warning: D4102206AB: virtual_alias_maps map lookup problem for root@zentyal.xd.local -- message not accepted, try again la
Mar 14 12:35:03 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:35:06 zentyal postfix/scache[10804]: statistics: start interval Mar 14 12:31:46
Mar 14 12:35:06 zentyal postfix/scache[10804]: statistics: domain lookup hits=0 miss=2 success=0%
Mar 14 12:35:06 zentyal postfix/scache[10804]: statistics: address lookup hits=0 miss=2 success=0%
Mar 14 12:35:17 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:35:37 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:35:46 zentyal postfix/pickup[1004]: EDEB1206AB: uid=0 from=<root>
Mar 14 12:35:46 zentyal postfix/cleanup[10822]: warning: dict_ldap_connect: Unable to bind to server ldap://localhost:389 with dn CN=zentyal-mail-zentyal,CN=Users,DC=xd,D
Mar 14 12:35:46 zentyal postfix/cleanup[10822]: warning: ldap:/etc/postfix/valiases.cf lookup error for "root@zentyal.xd.local"
Mar 14 12:35:46 zentyal postfix/cleanup[10822]: warning: EDEB1206AB: virtual_alias_maps map lookup problem for root@zentyal.xd.local -- message not accepted, try again la
Mar 14 12:35:48 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:36:01 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:36:20 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:36:34 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:36:45 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: AD1581FCC8: from=<root@zentyal.xd.local>, size=630, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: B885B1F651: from=<root@zentyal.xd.local>, size=1102, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: F03222068A: from=<root@zentyal.xd.local>, size=630, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: 75E3720691: from=<root@zentyal.xd.local>, size=630, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: 7F9642069C: from=<root@zentyal.xd.local>, size=630, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: 7E20F20696: from=<amavis@zentyal.xd.local>, size=712, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: 74C1E2069E: from=<root@zentyal.xd.local>, size=1102, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/qmgr[1005]: 0810C20689: from=<root@zentyal.xd.local>, size=630, nrcpt=1 (queue active)
Mar 14 12:36:46 zentyal postfix/pickup[1004]: F06D81F636: uid=0 from=<root>
Mar 14 12:36:46 zentyal postfix/cleanup[10822]: warning: dict_ldap_connect: Unable to bind to server ldap://localhost:389 with dn CN=zentyal-mail-zentyal,CN=Users,DC=xd,D
Mar 14 12:36:46 zentyal postfix/cleanup[10822]: warning: ldap:/etc/postfix/valiases.cf lookup error for "root@zentyal.xd.local"
Mar 14 12:36:46 zentyal postfix/cleanup[10822]: warning: F06D81F636: virtual_alias_maps map lookup problem for root@zentyal.xd.local -- message not accepted, try again la
Mar 14 12:36:46 zentyal postfix/smtp[10824]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Mar 14 12:36:46 zentyal postfix/smtp[10825]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Mar 14 12:36:46 zentyal postfix/smtp[10824]: AD1581FCC8: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=5205, delays=5205/0.01/0/0, dsn=4.4.1, status=defer
Mar 14 12:36:47 zentyal postfix/smtp[10825]: B885B1F651: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=4767, delays=4767/0.01/0/0, dsn=4.4.1, status=defer
Mar 14 12:36:47 zentyal postfix/smtp[10824]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Mar 14 12:36:47 zentyal postfix/smtp[10825]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Mar 14 12:36:47 zentyal postfix/smtp[10824]: F03222068A: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=2506, delays=2506/0.01/0.01/0, dsn=4.4.1, status=de
Mar 14 12:36:47 zentyal postfix/smtp[10825]: 75E3720691: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=2206, delays=2206/0.02/0/0, dsn=4.4.1, status=defer
Mar 14 12:36:47 zentyal postfix/error[10829]: 7F9642069C: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=1006, delays=1006/0.05/0/0, dsn=4.4.1, status=defe
Mar 14 12:36:47 zentyal postfix/error[10829]: 7E20F20696: to=<amavis@zentyal.xd.local>, orig_to=<amavis>, relay=none, delay=1118, delays=1118/0.05/0/0, dsn=4.4.1, status=
Mar 14 12:36:47 zentyal postfix/error[10830]: 74C1E2069E: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=1183, delays=1183/0.05/0/0, dsn=4.4.1, status=defe
Mar 14 12:36:47 zentyal postfix/error[10829]: 0810C20689: to=<root@zentyal.xd.local>, orig_to=<root>, relay=none, delay=2806, delays=2806/0.06/0/0, dsn=4.4.1, status=defe
Mar 14 12:37:00 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)
Mar 14 12:37:11 zentyal dhclient[682]: DHCPREQUEST of 192.168.84.60 on eth0 to 255.255.255.255 port 67 (xid=0x538e1cc5)



Please help.
« Last Edit: May 13, 2020, 08:37:21 pm by devnull »

devnull

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +3/-0
    • View Profile
Re: Samba has stopped to work after upgrade to Zentyal 6.0
« Reply #1 on: May 13, 2020, 08:35:26 pm »
Ok, I've resolved the issue some time ago. Now I'm back here to share the fix with you.

Code: [Select]
sudo systemctl stop smbd
sudo systemctl stop nmbd
sudo systemctl stop winbind
sudo apt-get purge zentyal-openchange
sudo dpkg --configure -a
sudo systemctl disable smbd
sudo systemctl disable nmbd


SamE

  • Zen Apprentice
  • *
  • Posts: 31
  • Karma: +2/-0
    • View Profile
Re: [SOLVED] Samba has stopped to work after upgrade to Zentyal 6.0
« Reply #2 on: May 14, 2020, 03:30:57 pm »
This worked for me. Thank you!