Please make sure that your system is connected to the Internet.

One of the configured repositories failed (Unknown),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum –disablerepo= …

4. Disable the repository permanently, so yum won’t use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use –enablerepo for temporary usage:

yum-config-manager –disable
or
subscription-manager repos –disable=

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager –save –setopt=.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64

I got around this by doing:
ldapadd -x -W -D “cn=ldapadm,dc=xys,dc=co,dc=uk” -f base.ldif -H ldap://localhost

thanks a lot!

Hello,

I had the same problem.
Be careful when copying and pasting, a space can be added between each block.
Make sure there is no space.

Regarding the error with certs.ldif, try changin the order and put the key first, like this:

——————————————————–
dn: cn=config
changetype: modify
replace: olcTLSCertificateKeyFile
olcTLSCertificateKeyFile: /etc/openldap/certs/myldap.field.linuxhostsupport.com.key

dn: cn=config
changetype: modify
replace: olcTLSCertificateFile
olcTLSCertificateFile: /etc/openldap/certs/myldap.field.linuxhostsupport.com.cert
—————————————————————–

Regarding the password, you are supposed to use the plain text version of the password. So if your password is “supersecretpassword”, write that. You might want to check that you entered hashed version at the bottom of the db.ldif file.
It’s a generic line there that should be changed to the hashed password.

….
olcRootPW: hashed_output_from_the_slappasswd_command

I have exactly the same issue nothing helps, chmod, swapping key with cert order. any other suggestions??

I’ve enabled debug mode and get this output from ldapmodify command

ber_scanf fmt ({) ber:
ber_dump: buf=0x5640523751a0 ptr=0x5640523751a5 end=0x564052375205 len=96
0000: 66 5e 04 09 63 6e 3d 63 6f 6e 66 69 67 30 51 30 f^..cn=config0Q0
0010: 4f 0a 01 02 30 4a 04 18 6f 6c 63 54 4c 53 43 65 O…0J..olcTLSCe
0020: 72 74 69 66 69 63 61 74 65 4b 65 79 46 69 6c 65 rtificateKeyFile
0030: 31 2e 04 2c 2f 65 74 63 2f 6f 70 65 6e 6c 64 61 1..,/etc/openlda
0040: 70 2f 63 65 72 74 73 2f 6c 64 61 70 2d 63 70 34 p/certs/ldap-cp4
0050: 73 2e 64 61 72 6b 64 6f 74 2e 63 6f 2e 6b 65 79 s.darkdot.co.key
ber_flush2: 101 bytes to sd 4
0000: 30 63 02 01 02 66 5e 04 09 63 6e 3d 63 6f 6e 66 0c…f^..cn=conf
0010: 69 67 30 51 30 4f 0a 01 02 30 4a 04 18 6f 6c 63 ig0Q0O…0J..olc
0020: 54 4c 53 43 65 72 74 69 66 69 63 61 74 65 4b 65 TLSCertificateKe
0030: 79 46 69 6c 65 31 2e 04 2c 2f 65 74 63 2f 6f 70 yFile1..,/etc/op
0040: 65 6e 6c 64 61 70 2f 63 65 72 74 73 2f 6c 64 61 enldap/certs/lda
0050: 70 2d 63 70 34 73 2e 64 61 72 6b 64 6f 74 2e 63 p-cp4s.darkdot.c
0060: 6f 2e 6b 65 79 o.key
ldap_write: want=101, written=101
0000: 30 63 02 01 02 66 5e 04 09 63 6e 3d 63 6f 6e 66 0c…f^..cn=conf
0010: 69 67 30 51 30 4f 0a 01 02 30 4a 04 18 6f 6c 63 ig0Q0O…0J..olc
0020: 54 4c 53 43 65 72 74 69 66 69 63 61 74 65 4b 65 TLSCertificateKe
0030: 79 46 69 6c 65 31 2e 04 2c 2f 65 74 63 2f 6f 70 yFile1..,/etc/op
0040: 65 6e 6c 64 61 70 2f 63 65 72 74 73 2f 6c 64 61 enldap/certs/lda
0050: 70 2d 63 70 34 73 2e 64 61 72 6b 64 6f 74 2e 63 p-cp4s.darkdot.c
0060: 6f 2e 6b 65 79 o.key
ldap_result ld 0x564052367480 msgid 2
wait4msg ld 0x564052367480 msgid 2 (timeout 100000 usec)
wait4msg continue ld 0x564052367480 msgid 2 all 1
** ld 0x564052367480 Connections:
* host: (null) port: 0 (default)
refcnt: 2 status: Connected
last used: Sun Jul 26 21:20:28 2020

** ld 0x564052367480 Outstanding Requests:
* msgid 2, origid 2, status InProgress
outstanding referrals 0, parent count 0
ld 0x564052367480 request count 1 (abandoned 0)
** ld 0x564052367480 Response Queue:
Empty
ld 0x564052367480 response count 0
ldap_chkResponseList ld 0x564052367480 msgid 2 all 1
ldap_chkResponseList returns ld 0x564052367480 NULL
ldap_int_select
read1msg: ld 0x564052367480 msgid 2 all 1
ber_get_next
ldap_read: want=8, got=8
0000: 30 0c 02 01 02 67 07 0a 0….g..
ldap_read: want=6, got=6
0000: 01 50 04 00 04 00 .P….
ber_get_next: tag 0x30 len 12 contents:
ber_dump: buf=0x5640523761f0 ptr=0x5640523761f0 end=0x5640523761fc len=12
0000: 02 01 02 67 07 0a 01 50 04 00 04 00 …g…P….
read1msg: ld 0x564052367480 msgid 2 message type modify
ber_scanf fmt ({eAA) ber:
ber_dump: buf=0x5640523761f0 ptr=0x5640523761f3 end=0x5640523761fc len=9
0000: 67 07 0a 01 50 04 00 04 00 g…P….
read1msg: ld 0x564052367480 0 new referrals
read1msg: mark request completed, ld 0x564052367480 msgid 2
request done: ld 0x564052367480 msgid 2
res_errno: 80, res_error: , res_matched:
ldap_free_request (origid 2, msgid 2)
ldap_parse_result
ber_scanf fmt ({iAA) ber:
ber_dump: buf=0x5640523761f0 ptr=0x5640523761f3 end=0x5640523761fc len=9
0000: 67 07 0a 01 50 04 00 04 00 g…P….
ber_scanf fmt (}) ber:
ber_dump: buf=0x5640523761f0 ptr=0x5640523761fc end=0x5640523761fc len=0

ldap_msgfree
ldap_err2string
ldap_modify: Other (e.g., implementation specific) error (80)

ldap_free_connection 1 1
ldap_send_unbind
ber_flush2: 7 bytes to sd 4
0000: 30 05 02 01 03 42 00 0….B.
ldap_write: want=7, written=7
0000: 30 05 02 01 03 42 00 0….B.
ldap_free_connection: actually freed

ive done both, swapping the sequence nor chown..but still get the same error

Argh… figured #3 out. Changed “dc=field,dc=linuxhostsupport” to match my server and it worked….

Any ideas?
Thanks, Mike

Greg, if you edit in vi use :set list to view the hidden characters. You will find an extra character on line 5 that you need to delete.
Mike

Please check each line for trailing spaces.

here my db.ldif
[root@LDAP slapd.d]# cat db.ldif
dn: olcDatabase={2}hdb,cn=config
changetype: modify
replace: olcSuffix
olcSuffix: dc=field,dc=tenedis,dc=com

dn: olcDatabase={2}hdb,cn=config
changetype: modify
replace: olcRootDN
olcRootDN: cn=ldapadm,dc=field,dc=tenedis,dc=com

dn: olcDatabase={2}hdb,cn=config
changetype: modify
replace: olcRootPW
olcRootPW: hashed_output_from_the_slappasswd_command

any ideas ?

thanks 🙂

It works for me. Thanks a lot Mike!

may be the same mistake as I did initially…in step Configure OpenLDAP you should enter as password the complete line returned from slappasswd command, including {SSHA}…at least this was the issue I had

Hi, I have an same problem , after following all steps to the one character , I got the message for the last step : Enter LDAP Password: ldap_bind: Invalid credentials (49).. I tried to change the password, once again and the same. Only error I got from the OS , was after edit the certs.ldif.
ldapmodify -Y EXTERNAL -H ldapi:/// -f certs.ldif
…
modifying entry “cn=config”
ldap_modify: Other (e.g., implementation specific) error (80)

I will little play with that 🙂 but I typing the password correctly

Nice day and thank you for post.. Really helpfull

Did you generate a certificate and private key for your server hostname?

Above line is my hostname.
When I was try to modify certs.ldif file .
I got ” modifying entry “cn=config”
ldap_modify: Other (e.g., implementation specific) error (80) ”

vim certs.ldif
dn: cn=config
changetype: modify
replace: olcTLSCertificateFile
olcTLSCertificateFile: /etc/openldap/certs/myldap.field.linuxhostsupport.com.cert

dn: cn=config
changetype: modify
replace: olcTLSCertificateKeyFile
olcTLSCertificateKeyFile: /etc/openldap/certs/myldap.field.linuxhostsupport.com.key

May I how how can I trace to solve it.

# ldapmodify -Y EXTERNAL -H ldapi:/// -f certs.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry “cn=config”
ldap_modify: Other (e.g., implementation specific) error (80)

Please may I know which state has wrong?

i need change the password

fixed this by swapping the order of the key/cert entries in certs.ldif.

I encountered the similar problem, I found a workaround by splitting the file in two, and load each section in two different ldap_modify command. Perhaps try that?

I have the same problem and the password is definitely correct. The ldapadm dn is mine too.

What else could the problem be?

OK i have it :D. To all others. In the 2 new lines there are white spaces you must delete them ;).

What do you mean ? I have the same error, can you send the correct version please ?

Please try to change the permissions of the ‘/etc/openldap/certs’ directory:

chown -R ldap:ldap /etc/openldap/certs

It was a space in a new line.

I encountered this on Centos 7. The problem was SElinux.

edit /etc/selinux/config

SELINUX=enforcing can be changed to SELINUX=disabled

See if that fixes it.

yes…what to do?

I need to use encrypted password o clear password?
It does not work in both cases.

Thanks

Hi Ruben,

Try using ‘dc=cycleon’ instead of ‘dc: admin’ on the second line of the file.

dn: cn=admin,dc=cycleon,dc=com
objectClass: organizationalRole
cn: admin
description: LDAP Admin

dn: ou=People,dc=cycleon,dc=com
objectClass: organizationalUnit
ou: People

dn: ou=Group,dc=field,dc=com
objectClass: organizationalUnit
ou: Group

when trying the last command:
]# ldapadd -x -W -D “cn=admin,dc=cycleon,dc=com” -f base.ldif
Enter LDAP Password:
adding new entry “dc=cycleon,dc=com”
ldap_add: Naming violation (64)
additional info: value of single-valued naming attribute ‘dc’ conflicts with value present in entry

the base.ldif looks correct to me, can you please help?

I confirm that password entered is correct one.

I had this same problem. The default config of the database has directives that point to certain paths and files for certificates. You most likely don’t have those certificates in place yet. What you need to do is either comment out those lines that are looking for certs, or create certs and place them where those directives are looking for.

Ofcourse, since slapd is not running you cannot use ldapmodify to make these changes. See the answer to this post: https://serverfault.com/questions/863274/modify-openldap-cn-config-without-slapd-running

Once you either comment out those lines that are looking for certs, or place certs in the correct locations, you will be able to start slapd and use ldapmodify from then on.

Please double check the credentials you are using. The password you are entering seems to be incorrect.

Please help on this..

Are you getting an error message when trying to authenticate using ldap_bind(user,password)?

When deploying configuration changes to the OpenLDAP server you need to enter the LDAP root password you set up earlier. Thanks

I hope your found your answer, you can just reinstall openldap services again and start the process if you did not go far
sudo yum reinstall openldap compat-openldap openldap-clients openldap-servers openldap-servers-sql openldap-devel

[root@mspildapsrv lib]# systemctl status slapd.service
● slapd.service – OpenLDAP Server Daemon
Loaded: loaded (/usr/lib/systemd/system/slapd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-08-22 03:51:49 IST; 18s ago
Docs: man:slapd
man:slapd-config
man:slapd-hdb
man:slapd-mdb
file:///usr/share/doc/openldap-servers/guide.html
Process: 3571 ExecStart=/usr/sbin/slapd -u ldap -h ${SLAPD_URLS} $SLAPD_OPTIONS (code=exited, status=1/FAILURE)
Process: 3555 ExecStartPre=/usr/libexec/openldap/check-config.sh (code=exited, status=0/SUCCESS)

Aug 22 03:51:45 mspildapsrv.com slapd[3571]: ldif_read_file: checksum error on “/etc/openld…if”
Aug 22 03:51:49 mspildapsrv.com slapd[3571]: Could not get the realpath: No such file or di…ory
Aug 22 03:51:49 mspildapsrv.com slapd[3571]: main: TLS init def ctx failed: -1
Aug 22 03:51:49 mspildapsrv.com slapd[3571]: DIGEST-MD5 common mech free
Aug 22 03:51:49 mspildapsrv.com slapd[3571]: slapd stopped.
Aug 22 03:51:49 mspildapsrv.com slapd[3571]: connections_destroy: nothing to destroy.
Aug 22 03:51:49 mspildapsrv.com systemd[1]: slapd.service: control process exited, code=exi…s=1
Aug 22 03:51:49 mspildapsrv.com systemd[1]: Failed to start OpenLDAP Server Daemon.
Aug 22 03:51:49 mspildapsrv.com systemd[1]: Unit slapd.service entered failed state.
Aug 22 03:51:49 mspildapsrv.com systemd[1]: slapd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

Hi Sriram,

You can run the systemctl status slapd.service command as suggested, for more details about the issue.

systemctl start slapd
Job for slapd.service failed because the control process exited with error code. See “systemctl status slapd.service” and “journalctl -xe”