Hi Viktor,
thanks a lot for testing and finding that. I did not catch that.
Thanks for the support. I will try to use the recreated instance.
Kind regards,
Ralf
Am Do., 4. Juli 2024 um 14:08 Uhr schrieb Viktor Ashirov <
vashi...@redhat.com>:
> Hi Ralf,
>
>
> On Thu, Jul 4, 2024 at 1:43 PM Ralf Sp
Hi Ralf,
On Thu, Jul 4, 2024 at 1:43 PM Ralf Spenneberg
wrote:
> I will recreate the instance. Meanwhile here is the log
>
I don't see errors in your log.
I tried to reproduce your issue by copying /etc/dirsrv and
/var/lib/dirsrv/slapd-localhost from EL7 to EL9 and on startup I see in the
logs
Ok. Recreating the instance apparently solves the problem. And the hash
migration works as well.
Thanks a lot.
Am Do., 4. Juli 2024 um 13:43 Uhr schrieb Ralf Spenneberg <
rspenneb...@gmail.com>:
> I will recreate the instance. Meanwhile here is the log
>
> Kind regards,
> Ralf
>
>
> Am Do., 4. J
I will recreate the instance. Meanwhile here is the log
Kind regards,
Ralf
Am Do., 4. Juli 2024 um 13:24 Uhr schrieb Viktor Ashirov <
vashi...@redhat.com>:
> Hi Ralf,
>
> On Thu, Jul 4, 2024 at 12:54 PM Ralf Spenneberg
> wrote:
>
>> Hi Viktor,
>>
>> I do not see any errors. I attached the log
Hi Ralf,
On Thu, Jul 4, 2024 at 12:54 PM Ralf Spenneberg
wrote:
> Hi Viktor,
>
> I do not see any errors. I attached the log but nothing stands out to me.
>
I don't see the log attached, could you please send it again?
>
> It was not a fresh instance but the migrated instance.
>
> Then I remove
On 7/4/24 12:54, Ralf Spenneberg wrote:
Hi Viktor,
I do not see any errors. I attached the log but nothing stands out to me.
It was not a fresh instance but the migrated instance.
Then I removed the database:
dsconf -D "cn=Directory Manager" -W ldap://localhost backend delete
spenneberg_net -
Hi Viktor,
I do not see any errors. I attached the log but nothing stands out to me.
It was not a fresh instance but the migrated instance.
Then I removed the database:
dsconf -D "cn=Directory Manager" -W ldap://localhost backend delete
spenneberg_net --do-it
Deleting Backend cn=spenneberg_net,cn
Hi Ralf,
On Thu, Jul 4, 2024 at 11:29 AM Ralf Spenneberg
wrote:
> Hi Viktor,
> thanks a lot for the suggestion.
> So I did an export of the old tree running on 1.3.11 using db2dif:
> db2ldif -s "dc=xxx,dc=net" -a /tmp/userRoot.ldif
> And I did an import in the new tree running on 2.4:
>
Is it a
Hi Viktor,
thanks a lot for the suggestion.
So I did an export of the old tree running on 1.3.11 using db2dif:
db2ldif -s "dc=xxx,dc=net" -a /tmp/userRoot.ldif
And I did an import in the new tree running on 2.4:
dsconf -D "cn=Directory Manager" -W ldap://localhost backend import
dc=...,dc=net /user
On Wed, Jul 3, 2024 at 3:48 PM Ralf Spenneberg
wrote:
> Actually I just upgrade the system from centos7 to almalinux9 using
> elevate. Essentially this is similar to a copy of the /etc/dirsrv and
> /var/lib/dirsrv directories and started the new ldapserver.
>
We don't support or test in-place upg
Ralf Spenneberg wrote:
> Actually I just upgrade the system from centos7 to almalinux9 using
> elevate. Essentially this is similar to a copy of the /etc/dirsrv and
> /var/lib/dirsrv directories and started the new ldapserver.
> Directly afterwards I was not able to login using the cn=Directory
>
Actually I just upgrade the system from centos7 to almalinux9 using
elevate. Essentially this is similar to a copy of the /etc/dirsrv and
/var/lib/dirsrv directories and started the new ldapserver.
Directly afterwards I was not able to login using the cn=Directory Manager.
I checked the hashed pass
Hi Ralf,
On Tue, Jul 2, 2024 at 2:29 PM Ralf Spenneberg
wrote:
> Hi there,
> I am trying to update a ldap tree from 389ds 1.3.11 (centos7) to 2.4.5
> (almalinux9). After migrating the tree all passwords stop working including
> the Directory Manager. The old tree used SSHA. Setting the
> rootpw
Hi William,
I know that. But it would be great if for migration purposes the old hashes
would work. I do not know the passwords of all users in the existing tree.
What I would like to use afterwards is the
nsslapd-enable-upgrade-hash: on
feature. So, is there a possibility to support SSHA hashes
Do you actually have a real technical requirement for SSHA? In 2024 it is
functionally plaintext, so unless you have a true requirement to use SSHA, then
you should follow the secure defaults.
> On 2 Jul 2024, at 22:25, Ralf Spenneberg wrote:
>
> Hi there,
> I am trying to update a ldap tree
15 matches
Mail list logo
