enterprise-support team mailing list archive

Thread
Date

[Bug 1808117] Re: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.6 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1

To: enterprise-support@xxxxxxxxxxxxxxxxxxx
From: Andreas Hasenack <andreas@xxxxxxxxxxxxx>
Date: Thu, 13 Dec 2018 11:47:28 -0000
Reply-to: Bug 1808117 <1808117@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Thanks for filing this bug in Ubuntu.

This is the error that was reported:
Job for winbind.service failed because the control process exited with error code.
See "systemctl status winbind.service" and "journalctl -xe" for details.
invoke-rc.d: initscript winbind, action "restart" failed.
[0;1;31m●[0m winbind.service - Samba Winbind Daemon
   Loaded: loaded (/lib/systemd/system/winbind.service; enabled; vendor preset: enabled)
   Active: [0;1;31mfailed[0m (Result: exit-code) since Wed 2018-12-12 11:50:36 MSK; 46ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 26543 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS [0;1;31m(code=exited, status=1/FAILURE)[0m
 Main PID: 26543 (code=exited, status=1/FAILURE)

дек 12 11:50:34 kalach1 systemd[1]: Starting Samba Winbind Daemon...
дек 12 11:50:36 kalach1 winbindd[26543]: [0;1;31m[0;1;39m[0;1;31m[2018/12/12 11:50:36.179032,  0] ../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)[0m
дек 12 11:50:36 kalach1 winbindd[26543]: [0;1;31m[0;1;39m[0;1;31m  initialize_winbindd_cache: clearing cache and re-creating with version number 2[0m
дек 12 11:50:36 kalach1 winbindd[26543]: [0;1;31m[0;1;39m[0;1;31m[2018/12/12 11:50:36.252882,  0] ../source3/winbindd/winbindd_util.c:891(init_domain_list)[0m
дек 12 11:50:36 kalach1 winbindd[26543]: [0;1;31m[0;1;39m[0;1;31m  Could not fetch our SID - did we join?[0m
дек 12 11:50:36 kalach1 winbindd[26543]: [0;1;31m[0;1;39m[0;1;31m[2018/12/12 11:50:36.253026,  0] ../source3/winbindd/winbindd.c:1366(winbindd_register_handlers)[0m
дек 12 11:50:36 kalach1 winbindd[26543]: [0;1;31m[0;1;39m[0;1;31m  unable to initialize domain list[0m
дек 12 11:50:36 kalach1 systemd[1]: [0;1;39m[0;1;31m[0;1;39mwinbind.service: Main process exited, code=exited, status=1/FAILURE[0m
дек 12 11:50:36 kalach1 systemd[1]: [0;1;39m[0;1;31m[0;1;39mwinbind.service: Failed with result 'exit-code'.[0m
дек 12 11:50:36 kalach1 systemd[1]: [0;1;31m[0;1;39m[0;1;31mFailed to start Samba Winbind Daemon.[0m
dpkg: error processing package winbind (--configure):
 installed winbind package post-installation script subprocess returned error exit status 1

You seem to have a problem with the joined domain: winbind says it could
not fetch its SID.

This is unfortunately beyond the scope of a bug report, and is more
leaning towards support.


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

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

Title:
  package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.6 failed to
  install/upgrade: installed winbind package post-installation script
  subprocess returned error exit status 1

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

References

[Bug 1808117] [NEW] package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.6 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1
From: Stager, 2018-12-12