Hey all,
I have been using my FreeIPA users to authenticate to Samba shares on my file server for some time now. All of a sudden the other day it stopped working and smb won't even start. It gives errors about ipasam: "No builtin nor plugin backend for ipasam found". The following is from the journal after a startup failure:
Jun 18 09:03:40 fs.cpms.byu.edu systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit smb.service has begun starting up. Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:40.444763, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:41.445977, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:42.447213, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:43.448469, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:44.449674, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:45.450791, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:46.452048, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:47.453281, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:48.454439, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:49.455579, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:50.456812, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:51.458054, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:52.459257, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:53.460436, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:54.461567, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:55.462721, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463513, 0] ipa_sam.c:4865(pdb_init_ipasam) Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: Failed to get base DN. Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463583, 0] ../../source3/passdb/pdb_inter> Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: pdb backend ipasam:ldaps// ipa2.cpms.byu.edu did not correctly> Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Failed with result 'exit-code'. Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit smb.service has failed.
Can anyone help me get this working again or even an idea of why it failed after working for months on end?
On pe, 19 kesä 2020, Kristian Petersen via FreeIPA-users wrote:
Hey all,
I have been using my FreeIPA users to authenticate to Samba shares on my file server for some time now. All of a sudden the other day it stopped working and smb won't even start. It gives errors about ipasam: "No builtin nor plugin backend for ipasam found". The following is from the journal after a startup failure:
You cannot get any meaningful help without providing real details on your deployment: OS, distribution version, what you did before the issue started to appear and so on, what is your Samba configuration, etc.
On Ubuntu Samba is built against Heimdal Kerberos implementation, while FreeIPA requires use of MIT Kerberos, so you cannot load ipasam.so in Samba there. Most likely it is not Ubuntu/Debian flavor that you use...
CentOS 8.1 had broken IdM build that wasn't rebuild after they built samba with a changed ABI, so loading ipasam.so always failed. Many people complained about it for more than five months and no rebuild was done, with unclear responses from CentoS people.
I haven't tried CentOS 8.2.2004 yet for that, may be it has another issue. At least, there are known problems with CentOS 8.2.2004 repositories which weren't properly synchronized to public when they announced 8.2 release.
If ipasam.so is not found, I don't understand how can you get those messages from smbldap in the logs -- what else is dring unless you are using pdb_ldap module.
ldap_initialize() is a function from OpenLDAP library code. If something is passing wrong initialization parameter, them more details are needed as well.
Jun 18 09:03:40 fs.cpms.byu.edu systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit smb.service has begun starting up. Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:40.444763, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:41.445977, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:42.447213, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:43.448469, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:44.449674, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:45.450791, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:46.452048, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:47.453281, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:48.454439, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:49.455579, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:50.456812, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:51.458054, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:52.459257, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:53.460436, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:54.461567, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:55.462721, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463513, 0] ipa_sam.c:4865(pdb_init_ipasam) Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: Failed to get base DN. Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463583, 0] ../../source3/passdb/pdb_inter> Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: pdb backend ipasam:ldaps// ipa2.cpms.byu.edu did not correctly> Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Failed with result 'exit-code'. Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit smb.service has failed.
Can anyone help me get this working again or even an idea of why it failed after working for months on end? -- Kristian Petersen System Administrator BYU Dept. of Chemistry and Biochemistry
Running rhel 8.2 as a VM in oVirt for the one running samba, rhel 8.1 for the one running IPA/IdM. It is also a VM in ovirt. All on the same subnet.
On Fri, Jun 19, 2020, 11:51 PM Alexander Bokovoy abokovoy@redhat.com wrote:
On pe, 19 kesä 2020, Kristian Petersen via FreeIPA-users wrote:
Hey all,
I have been using my FreeIPA users to authenticate to Samba shares on my file server for some time now. All of a sudden the other day it stopped working and smb won't even start. It gives errors about ipasam: "No builtin nor plugin backend for ipasam found". The following is from the journal after a startup failure:
You cannot get any meaningful help without providing real details on your deployment: OS, distribution version, what you did before the issue started to appear and so on, what is your Samba configuration, etc.
On Ubuntu Samba is built against Heimdal Kerberos implementation, while FreeIPA requires use of MIT Kerberos, so you cannot load ipasam.so in Samba there. Most likely it is not Ubuntu/Debian flavor that you use...
CentOS 8.1 had broken IdM build that wasn't rebuild after they built samba with a changed ABI, so loading ipasam.so always failed. Many people complained about it for more than five months and no rebuild was done, with unclear responses from CentoS people.
I haven't tried CentOS 8.2.2004 yet for that, may be it has another issue. At least, there are known problems with CentOS 8.2.2004 repositories which weren't properly synchronized to public when they announced 8.2 release.
If ipasam.so is not found, I don't understand how can you get those messages from smbldap in the logs -- what else is dring unless you are using pdb_ldap module.
ldap_initialize() is a function from OpenLDAP library code. If something is passing wrong initialization parameter, them more details are needed as well.
Jun 18 09:03:40 fs.cpms.byu.edu systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit smb.service has begun starting up. Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:40.444763, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:41.445977, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:42.447213, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:43.448469, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:44.449674, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:45.450791, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:46.452048, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:47.453281, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:48.454439, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:49.455579, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:50.456812, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:51.458054, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:52.459257, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:53.460436, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:54.461567, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:55.462721, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463513, 0] ipa_sam.c:4865(pdb_init_ipasam) Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: Failed to get base DN. Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463583, 0] ../../source3/passdb/pdb_inter> Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: pdb backend ipasam:ldaps// ipa2.cpms.byu.edu did not correctly> Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Failed with
result
'exit-code'. Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit smb.service has failed.
Can anyone help me get this working again or even an idea of why it failed after working for months on end? -- Kristian Petersen System Administrator BYU Dept. of Chemistry and Biochemistry
-- / Alexander Bokovoy Sr. Principal Software Engineer Security / Identity Management Engineering Red Hat Limited, Finland
On ma, 22 kesä 2020, Kristian Petersen via FreeIPA-users wrote:
Running rhel 8.2 as a VM in oVirt for the one running samba, rhel 8.1 for the one running IPA/IdM. It is also a VM in ovirt. All on the same subnet.
If this is RHEL with subscription, please open a customer case, attach SOS report there and let me know off the list.
On Fri, Jun 19, 2020, 11:51 PM Alexander Bokovoy abokovoy@redhat.com wrote:
On pe, 19 kesä 2020, Kristian Petersen via FreeIPA-users wrote:
Hey all,
I have been using my FreeIPA users to authenticate to Samba shares on my file server for some time now. All of a sudden the other day it stopped working and smb won't even start. It gives errors about ipasam: "No builtin nor plugin backend for ipasam found". The following is from the journal after a startup failure:
You cannot get any meaningful help without providing real details on your deployment: OS, distribution version, what you did before the issue started to appear and so on, what is your Samba configuration, etc.
On Ubuntu Samba is built against Heimdal Kerberos implementation, while FreeIPA requires use of MIT Kerberos, so you cannot load ipasam.so in Samba there. Most likely it is not Ubuntu/Debian flavor that you use...
CentOS 8.1 had broken IdM build that wasn't rebuild after they built samba with a changed ABI, so loading ipasam.so always failed. Many people complained about it for more than five months and no rebuild was done, with unclear responses from CentoS people.
I haven't tried CentOS 8.2.2004 yet for that, may be it has another issue. At least, there are known problems with CentOS 8.2.2004 repositories which weren't properly synchronized to public when they announced 8.2 release.
If ipasam.so is not found, I don't understand how can you get those messages from smbldap in the logs -- what else is dring unless you are using pdb_ldap module.
ldap_initialize() is a function from OpenLDAP library code. If something is passing wrong initialization parameter, them more details are needed as well.
Jun 18 09:03:40 fs.cpms.byu.edu systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit smb.service has begun starting up. Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:40.444763, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:40 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:41.445977, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:41 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:42.447213, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:42 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:43.448469, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:43 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:44.449674, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:44 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:45.450791, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:45 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:46.452048, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:46 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:47.453281, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:47 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:48.454439, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:48 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:49.455579, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:49 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:50.456812, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:50 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:51.458054, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:51 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:52.459257, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:52 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:53.460436, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:53 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:54.461567, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:54 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:55.462721, 0] ../../source3/lib/smbldap.c:65> Jun 18 09:03:55 fs.cpms.byu.edu smbd[13266]: ldap_initialize: Bad parameter to an ldap routine Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463513, 0] ipa_sam.c:4865(pdb_init_ipasam) Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: Failed to get base DN. Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: [2020/06/18 09:03:56.463583, 0] ../../source3/passdb/pdb_inter> Jun 18 09:03:56 fs.cpms.byu.edu smbd[13266]: pdb backend ipasam:ldaps// ipa2.cpms.byu.edu did not correctly> Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: smb.service: Failed with
result
'exit-code'. Jun 18 09:03:56 fs.cpms.byu.edu systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit smb.service has failed.
Can anyone help me get this working again or even an idea of why it failed after working for months on end? -- Kristian Petersen System Administrator BYU Dept. of Chemistry and Biochemistry
-- / Alexander Bokovoy Sr. Principal Software Engineer Security / Identity Management Engineering Red Hat Limited, Finland
freeipa-users@lists.fedorahosted.org