在Ubuntu 17.04上的Winbind不会启动

Question

我很抱歉，因为我的Linux知识非常有限，我已经在一个测试环境中安装了Ubuntu17.04Server，并试图安装Samba。在安装过程中，winbind守护进程将不会启动。在安装Samba之前，我已经运行过apt update && upgrade，但是它似乎没有帮助。我已经测试了Ubuntu版本16.04 LTS，它工作正常，没有任何错误。我有点不明白为什么Winbind将不能在17.04，谷歌搜索结果没有帮助。如果有人需要更多的信息，我会很高兴地提供它，但你可能需要向我展示的命令来做。

谢谢

Jun 14 10:53:18 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jun 14 10:53:18 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 14 10:53:18 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.
Jun 14 10:53:30 UbtNicholas sudo[23772]: nilaberge : TTY=pts/0 ; PWD=/home/nilaberge ; USER=root ; COMMAND=/bin/su
Jun 14 10:53:30 UbtNicholas sudo[23772]: pam_unix(sudo:session): session opened for user root by nilaberge(uid=0)
Jun 14 10:53:30 UbtNicholas su[23773]: Successful su for root by root
Jun 14 10:53:30 UbtNicholas su[23773]: + /dev/pts/0 root:root
Jun 14 10:53:30 UbtNicholas su[23773]: pam_unix(su:session): session opened for user root by nilaberge(uid=0)
Jun 14 10:53:30 UbtNicholas su[23773]: pam_systemd(su:session): Cannot create session: Already running in a session
Jun 14 10:53:55 UbtNicholas systemd[1]: Starting Samba Winbind Daemon...
-- Subject: Unit winbind.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has begun starting up.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Supervising process 23803 which is not our child. We'll most likely not notice
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 10:53:55 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.

几乎有一个类似的问题，但这个问题假设它适用于17.04

链接到类似的问题：在Ubuntu17.04中重新启动时的Winbind中断

更新1:在运行testparm时遵循andreas的建议后，它发现了一些老行，因此我删除了它们，并重新启动了winbind服务。仍然存在一个错误，但是systemCTL已经发现了一些可能会更好地指向问题所在的地方。

Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.432130,  0] ../source3/winbindd/winbindd_cache.c:3244(initialize_winbindd_cache)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.435598,  0] ../source3/winbindd/winbindd_util.c:892(init_domain_list)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   Could not fetch our SID - did we join?
Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.436118,  0] ../source3/winbindd/winbindd.c:1401(winbindd_register_handlers)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   unable to initialize domain list
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 10:14:29 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.

Answer 1

我把这个扔给和我有同样问题的人。当您启动winbind时，它只写着“启动失败”。当日志被弃用时，您就有了问题，因此看不到到底出了什么问题。

运行testparm (正如andreas所说)。它会给你一个关于不受欢迎的东西的警告。你要找的是syslog被废弃了。在您解决其他警告之前，它可能一开始不会出现。

'Syslog = 0‘应该是'logging = syslog@1 /var/log/samba/log.%m’，现在启动winbind时，您将收到一条关于日志日志-xe中错误所在的消息。有关详细信息，请参阅：警告“syslog”选项被废弃。。