Winbind on Ubuntu 17.04 will not start
Multi tool use
I apologize in advance as my Linux knowledge is very limited.I've installed Ubuntu 17.04 Server in a test environment and attempted to install Samba. During the installation the winbind daemon will not start. I've ran apt update && upgrade before installing Samba however it seems that it didn't help out. I've tested Ubuntu version 16.04 LTS and it works without any errors. I'm a bit lost as to why Winbind will not work on 17.04, Google search results didn't help. If anyone needs more info I'll gladly provide it but you'll probably need to show me the command to do it.
Thank you
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'.
There's almost a similar question but the question assumes that it worked on 17.04
Link to the similar question: Winbind Broken on Reboot In Ubuntu 17.04
UPDATE 1: After following andreas advice in running testparm, it found some lines that were old so I've removed them and restarted the winbind service. Still does an error but the systemCTL has found something that might pin point a bit better where the issue is.
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'.
samba 17.04 services
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
add a comment |
I apologize in advance as my Linux knowledge is very limited.I've installed Ubuntu 17.04 Server in a test environment and attempted to install Samba. During the installation the winbind daemon will not start. I've ran apt update && upgrade before installing Samba however it seems that it didn't help out. I've tested Ubuntu version 16.04 LTS and it works without any errors. I'm a bit lost as to why Winbind will not work on 17.04, Google search results didn't help. If anyone needs more info I'll gladly provide it but you'll probably need to show me the command to do it.
Thank you
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'.
There's almost a similar question but the question assumes that it worked on 17.04
Link to the similar question: Winbind Broken on Reboot In Ubuntu 17.04
UPDATE 1: After following andreas advice in running testparm, it found some lines that were old so I've removed them and restarted the winbind service. Still does an error but the systemCTL has found something that might pin point a bit better where the issue is.
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'.
samba 17.04 services
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
Run "testparm" and see if it complains about anything in your smb.conf file
– Andreas Hasenack
Jun 23 '17 at 17:24
Hello, thank you for answering, I've run testparm command and there's nothing out of the ordinary in it. Besides a few deprecated lines. I've decided to remove those lines anyway and restart the winbind services. It still does an error but the systemctl seems to have found something interesting. I've edited the question with the new information.
– ShinraCorp
Jun 26 '17 at 14:16
you should paste the output of testparm. It will say some configs are deprecated with a WARNING label, and say they were ignored, but if they are mandatory settings then the net effect is the same as not having specified them, which will be a failure.
– Andreas Hasenack
Jun 28 '17 at 12:30
add a comment |
I apologize in advance as my Linux knowledge is very limited.I've installed Ubuntu 17.04 Server in a test environment and attempted to install Samba. During the installation the winbind daemon will not start. I've ran apt update && upgrade before installing Samba however it seems that it didn't help out. I've tested Ubuntu version 16.04 LTS and it works without any errors. I'm a bit lost as to why Winbind will not work on 17.04, Google search results didn't help. If anyone needs more info I'll gladly provide it but you'll probably need to show me the command to do it.
Thank you
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'.
There's almost a similar question but the question assumes that it worked on 17.04
Link to the similar question: Winbind Broken on Reboot In Ubuntu 17.04
UPDATE 1: After following andreas advice in running testparm, it found some lines that were old so I've removed them and restarted the winbind service. Still does an error but the systemCTL has found something that might pin point a bit better where the issue is.
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'.
samba 17.04 services
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
I apologize in advance as my Linux knowledge is very limited.I've installed Ubuntu 17.04 Server in a test environment and attempted to install Samba. During the installation the winbind daemon will not start. I've ran apt update && upgrade before installing Samba however it seems that it didn't help out. I've tested Ubuntu version 16.04 LTS and it works without any errors. I'm a bit lost as to why Winbind will not work on 17.04, Google search results didn't help. If anyone needs more info I'll gladly provide it but you'll probably need to show me the command to do it.
Thank you
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'.
There's almost a similar question but the question assumes that it worked on 17.04
Link to the similar question: Winbind Broken on Reboot In Ubuntu 17.04
UPDATE 1: After following andreas advice in running testparm, it found some lines that were old so I've removed them and restarted the winbind service. Still does an error but the systemCTL has found something that might pin point a bit better where the issue is.
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'.
samba 17.04 services
samba 17.04 services
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
edited Jun 26 '17 at 14:23
ShinraCorp
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
asked Jun 14 '17 at 15:05
ShinraCorpShinraCorp
113
113
Run "testparm" and see if it complains about anything in your smb.conf file
– Andreas Hasenack
Jun 23 '17 at 17:24
Hello, thank you for answering, I've run testparm command and there's nothing out of the ordinary in it. Besides a few deprecated lines. I've decided to remove those lines anyway and restart the winbind services. It still does an error but the systemctl seems to have found something interesting. I've edited the question with the new information.
– ShinraCorp
Jun 26 '17 at 14:16
you should paste the output of testparm. It will say some configs are deprecated with a WARNING label, and say they were ignored, but if they are mandatory settings then the net effect is the same as not having specified them, which will be a failure.
– Andreas Hasenack
Jun 28 '17 at 12:30
add a comment |
Run "testparm" and see if it complains about anything in your smb.conf file
– Andreas Hasenack
Jun 23 '17 at 17:24
Hello, thank you for answering, I've run testparm command and there's nothing out of the ordinary in it. Besides a few deprecated lines. I've decided to remove those lines anyway and restart the winbind services. It still does an error but the systemctl seems to have found something interesting. I've edited the question with the new information.
– ShinraCorp
Jun 26 '17 at 14:16
you should paste the output of testparm. It will say some configs are deprecated with a WARNING label, and say they were ignored, but if they are mandatory settings then the net effect is the same as not having specified them, which will be a failure.
– Andreas Hasenack
Jun 28 '17 at 12:30
Run "testparm" and see if it complains about anything in your smb.conf file
– Andreas Hasenack
Jun 23 '17 at 17:24
Run "testparm" and see if it complains about anything in your smb.conf file
– Andreas Hasenack
Jun 23 '17 at 17:24
Hello, thank you for answering, I've run testparm command and there's nothing out of the ordinary in it. Besides a few deprecated lines. I've decided to remove those lines anyway and restart the winbind services. It still does an error but the systemctl seems to have found something interesting. I've edited the question with the new information.
– ShinraCorp
Jun 26 '17 at 14:16
Hello, thank you for answering, I've run testparm command and there's nothing out of the ordinary in it. Besides a few deprecated lines. I've decided to remove those lines anyway and restart the winbind services. It still does an error but the systemctl seems to have found something interesting. I've edited the question with the new information.
– ShinraCorp
Jun 26 '17 at 14:16
you should paste the output of testparm. It will say some configs are deprecated with a WARNING label, and say they were ignored, but if they are mandatory settings then the net effect is the same as not having specified them, which will be a failure.
– Andreas Hasenack
Jun 28 '17 at 12:30
you should paste the output of testparm. It will say some configs are deprecated with a WARNING label, and say they were ignored, but if they are mandatory settings then the net effect is the same as not having specified them, which will be a failure.
– Andreas Hasenack
Jun 28 '17 at 12:30
add a comment |
1 Answer
1
active
oldest
votes
Ill just throw this here for anyone having the same problem as me. When you start winbind and it just says "Failed to start Samba Winbind Deamon." you are having a problem whith the log being deprecated and therefore aren't seeing what is really going wrong.
Run testparm (just as andreas said). It will show you a warning about deprecated stuff. What you are looking for is syslog being deprecated. It might not show up at first until you solve other warnings.
'Syslog = 0' should be 'logging = syslog@1 /var/log/samba/log.%m'
Now, when starting winbind you will get a message about what went wrong in journalctl -xe. See: WARNING "syslog" option is deprecated for more information.
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f925355%2fwinbind-on-ubuntu-17-04-will-not-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ill just throw this here for anyone having the same problem as me. When you start winbind and it just says "Failed to start Samba Winbind Deamon." you are having a problem whith the log being deprecated and therefore aren't seeing what is really going wrong.
Run testparm (just as andreas said). It will show you a warning about deprecated stuff. What you are looking for is syslog being deprecated. It might not show up at first until you solve other warnings.
'Syslog = 0' should be 'logging = syslog@1 /var/log/samba/log.%m'
Now, when starting winbind you will get a message about what went wrong in journalctl -xe. See: WARNING "syslog" option is deprecated for more information.
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
add a comment |
Ill just throw this here for anyone having the same problem as me. When you start winbind and it just says "Failed to start Samba Winbind Deamon." you are having a problem whith the log being deprecated and therefore aren't seeing what is really going wrong.
Run testparm (just as andreas said). It will show you a warning about deprecated stuff. What you are looking for is syslog being deprecated. It might not show up at first until you solve other warnings.
'Syslog = 0' should be 'logging = syslog@1 /var/log/samba/log.%m'
Now, when starting winbind you will get a message about what went wrong in journalctl -xe. See: WARNING "syslog" option is deprecated for more information.
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
add a comment |
Ill just throw this here for anyone having the same problem as me. When you start winbind and it just says "Failed to start Samba Winbind Deamon." you are having a problem whith the log being deprecated and therefore aren't seeing what is really going wrong.
Run testparm (just as andreas said). It will show you a warning about deprecated stuff. What you are looking for is syslog being deprecated. It might not show up at first until you solve other warnings.
'Syslog = 0' should be 'logging = syslog@1 /var/log/samba/log.%m'
Now, when starting winbind you will get a message about what went wrong in journalctl -xe. See: WARNING "syslog" option is deprecated for more information.
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
Ill just throw this here for anyone having the same problem as me. When you start winbind and it just says "Failed to start Samba Winbind Deamon." you are having a problem whith the log being deprecated and therefore aren't seeing what is really going wrong.
Run testparm (just as andreas said). It will show you a warning about deprecated stuff. What you are looking for is syslog being deprecated. It might not show up at first until you solve other warnings.
'Syslog = 0' should be 'logging = syslog@1 /var/log/samba/log.%m'
Now, when starting winbind you will get a message about what went wrong in journalctl -xe. See: WARNING "syslog" option is deprecated for more information.
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
answered Apr 12 '18 at 11:56
BelowAverageJoeBelowAverageJoe
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f925355%2fwinbind-on-ubuntu-17-04-will-not-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
JasjBf,3vRIyHP,U0raaDR9,N31j8ICWY9IjHG2s 2s4,24PDQ,q3qbDP
Run "testparm" and see if it complains about anything in your smb.conf file
– Andreas Hasenack
Jun 23 '17 at 17:24
Hello, thank you for answering, I've run testparm command and there's nothing out of the ordinary in it. Besides a few deprecated lines. I've decided to remove those lines anyway and restart the winbind services. It still does an error but the systemctl seems to have found something interesting. I've edited the question with the new information.
– ShinraCorp
Jun 26 '17 at 14:16
you should paste the output of testparm. It will say some configs are deprecated with a WARNING label, and say they were ignored, but if they are mandatory settings then the net effect is the same as not having specified them, which will be a failure.
– Andreas Hasenack
Jun 28 '17 at 12:30