[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
William, You are right. I remember the blank line. I will try that in the morning when I am fresh. Thanks for your help Bob -Original Message- From: William Brown [mailto:wbr...@suse.de] Sent: Monday, September 23, 2019 20:58 To: 389-users@lists.fedoraproject.org Subject: [389-users] R

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread William Brown
Okay, so you need to create the domain objects then. I'm not sure your ldapadd file is correct though, I think you need a blank line between the two entries? > On 24 Sep 2019, at 12:55, rtb...@granitemountain.com wrote: > > William, > > The result was the same except that the base was > wit

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
William, The result was the same except that the base was with scope subtree instead of with scope subtree Bob -Original Message- From: William Brown [mailto:wbr...@suse.de] Sent: Monday, September 23, 2019 20:43 To: 389-users@lists.fedoraproject.org Subject: [389-users] Re: Configu

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread William Brown
You need to quote it because else the shell thinks it's two arguments? > On 24 Sep 2019, at 12:31, rtb...@granitemountain.com > wrote: > > William - > > I did it with this command: > ldapsearch -b dc=granitemountain, dc=com -h $HOSTNAME -x -D 'cn=Directory > Manager' -W > > The results wer

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
William - I did it with this command: ldapsearch -b dc=granitemountain, dc=com -h $HOSTNAME -x -D 'cn=Directory Manager' -W The results were: # extended LDIF # # LDAPv3 # base with scope subtree # filter: dc=com # requesting: ALL # # search: results search: 2 result: 32 No such object # numR

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread William Brown
Can you do an ldapsearch -b dc=granitemountain, dc=com -h ... -x -D ... -W and see what exists already? > On 24 Sep 2019, at 10:39, rtb...@granitemountain.com > wrote: > > William, > > I was trying it as you suggested. It now gets past the password issue. > However, I am not hitting anoth

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
William, I was trying it as you suggested. It now gets past the password issue. However, I am not hitting another roadblock. The original entries in the file I created are: dn: dc=granitemountain, dc=com objectClass: domain dc: granitemountain dn: dc=pki, dc=gra

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread William Brown
Can you try the -f /file/of/changes rather than redirecting into the command? > On 24 Sep 2019, at 10:16, rtb...@granitemountain.com wrote: > > William, thanks for responding. In the original command string I used -w > redhat123 instead of -W which causes a prompt for the password. In both > c

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
William, thanks for responding. In the original command string I used -w redhat123 instead of -W which causes a prompt for the password. In both cases, I got the same error. -Original Message- From: William Brown [mailto:wbr...@suse.de] Sent: Monday, September 23, 2019 18:12 To: 389-us

[389-users] Re: Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread William Brown
> On 24 Sep 2019, at 09:46, rtb...@granitemountain.com > wrote: > > I have hit a roadblock and would appreciate any help I can get. I am running > in a VM Workstation virtualization platform on a Windows 10 host machine. > > I created a LAMP version of Fedora 30 using mariadb instead of mys

[389-users] Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
I have hit a roadblock and would appreciate any help I can get. I am running in a VM Workstation virtualization platform on a Windows 10 host machine. I created a LAMP version of Fedora 30 using mariadb instead of mysql. I changed the host name to cn-poc-pki.granitemountain.com rebooted the sys

[389-users] Configuring the 389-ds-base on Fedora 30

2019-09-23 Thread rtb...@granitemountain.com
I have hit a roadblock and would appreciate any help I can get. I am running in a VM Workstation virtualization platform on a Windows 10 host machine. I created a LAMP version of Fedora 30 using mariadb instead of mysql. I changed the host name to cn-poc-pki.granitemountain.com rebooted the sys

[389-users] Re: sudoers tree missing on a 389-ds replica

2019-09-23 Thread Sergei Gerasenko
The compat plugin was disabled. After enabling, issue was fixed. Hope it helps somebody. > On Sep 23, 2019, at 12:12 PM, Sergei Gerasenko wrote: > > Looking closer, I see that the sudorules,dc=DC,dc=DC is there, but the combat > tree (ou=sudoers,dc=DC,dc=DC) is not. Do you maintain the compat

[389-users] Re: sudoers tree missing on a 389-ds replica

2019-09-23 Thread Rob Crittenden
Sergei Gerasenko wrote: > Looking closer, I see that the sudorules,dc=DC,dc=DC is there, but the combat > tree (ou=sudoers,dc=DC,dc=DC) is not. Do you maintain the compat plugin? The freeIPA team maintains the slapi-compat plugin. I gather you aren't using this in the context of freeIPA? rob >

[389-users] Re: sudoers tree missing on a 389-ds replica

2019-09-23 Thread Sergei Gerasenko
Looking closer, I see that the sudorules,dc=DC,dc=DC is there, but the combat tree (ou=sudoers,dc=DC,dc=DC) is not. Do you maintain the compat plugin? > On Sep 23, 2019, at 10:15 AM, Sergei Gerasenko wrote: > > Hello, > > I’ve run into an interesting situatuion with the sudoers tree in 389-ds.

[389-users] Re: sudoers tree missing on a 389-ds replica

2019-09-23 Thread Mark Reynolds
On 9/23/19 11:15 AM, Sergei Gerasenko wrote: Hello, I’ve run into an interesting situatuion with the sudoers tree in 389-ds. All the nodes in the 389-ds cluster have it, but one doesn’t. I’ve tried dumping the database on a good node with db2ldif and reloading on the bad node with ldif2db, b

[389-users] sudoers tree missing on a 389-ds replica

2019-09-23 Thread Sergei Gerasenko
Hello, I’ve run into an interesting situatuion with the sudoers tree in 389-ds. All the nodes in the 389-ds cluster have it, but one doesn’t. I’ve tried dumping the database on a good node with db2ldif and reloading on the bad node with ldif2db, but the situation is not changing. I’ve also trie