William,

Here's:

VM1:
4GB RAM
4vCPUs

VM2: 
2GB
2vCPUs


Both filesystem are clean (for sure). I tend to think that's not the case, once I downgraded the 389 version and everything is working properly now. Could not see anything related monitoring the machine (no alarms about memory or CPU consumption).

The steps I followed:
1. My 389 was already stopped due to DB error (version 1.4.3.1.20200116git4f9aafca9)
2. Downgrade the 389 to version 1.4.2.4 (just replaced the binaries and other staff)
3. Started 389 (Even with the error, the 389 started what was not happening in version 1.4.3.1)
4. Removed all my replications (windows and other 389)
5. Restarted 389 (stop to see any error in log related to DB)
6. Reconfigured all my replications

2 others info:
- I run a db_recover before downgrade, but I'm  not sure if helped to start 389 in 1.4.2.4 version (db_recover -c -f -v).
- I saw the exactly same error in both machines (first in VM1, and maybe a hour later in VM2 too).

I remember that in the past was a recommendation about that (at least about memory), but could not found in rhds11 docs, or 389 page.

I'm on vacation right now, when I come back, I'will try to reproduce the problem and maybe give you guys more logs (or trace it).

Thanks

Alberto Viana



On Sun, Jan 19, 2020 at 9:43 PM William Brown <wbrown@suse.de> wrote:
I'd like to confirm with you if you are able to check this machines memory or filesystem as clean. This kind of corruption concerns me, and could have factors outside of just 389-ds involved.

Thanks,

> On 18 Jan 2020, at 03:41, Alberto Viana <albertocrj@gmail.com> wrote:
>
> Mark,
>
> Sorry, I couldnt wait, its a system in production.
>
>  I downgraded to 1.4.2.4 and worked fine (with same DB, didnt change anything but the ns-slapd binary version), removed all my replications e created again (seems that the problem might be related to my replication)
>
> Soon I will recreate my lab environment and I will test this version again.
>
> Yesterday during my upgrading, it happened the exactly same problem, but I though that was something casual, and just destroyed my VM and recreate it and worked fine.
>
> Thanks anyway for the help.
>
>
>
>
> On Fri, Jan 17, 2020 at 12:56 PM Mark Reynolds <mreynolds@redhat.com> wrote:
>
>
> On 1/17/20 10:51 AM, Alberto Viana wrote:
>> Mark,
>>
>>
>> Here's the files:
>>
>> ~]# ls -lha  /var/lib/dirsrv/slapd-RNP/db/
>> total 11M
>> drwxrwx---. 3 dirsrv dirsrv   61 Jan 17 12:16 .
>> drwxrwx---. 6 dirsrv dirsrv   58 Jan 16 20:04 ..
>> -rw-------. 1 dirsrv dirsrv   51 Jan 17 01:31 DBVERSION
>> -rw-------. 1 dirsrv dirsrv  10M Jan 17 12:19 log.0000000003
>> drwx------. 2 dirsrv dirsrv 4.0K Jan 17 12:04 userroot
> Please tail the errors log, and try starting the server again.  Please provide the entire error log output.
>
> Thanks,
> Mark
>
>>
>>
>> Thanks
>>
>> On Fri, Jan 17, 2020 at 12:49 PM Mark Reynolds <mreynolds@redhat.com> wrote:
>>
>>
>> On 1/17/20 10:25 AM, Alberto Viana wrote:
>>> Mark,
>>>
>>> There's nothing else in the log.
>>>
>>> There's no file like /var/lib/dirsrv/slapd-YOUR_INSTANCE/db/__db.*
>>>
>>> also tried a db_recover but without success.
>>>
>>> Do you recommend to downgrade my version?
>> No.
>>
>> What files do you see under:  /var/lib/dirsrv/slapd-YOUR_INSTANCE/db/
>>
>> <please replace YOUR_INSTANCE with your server's instance name>
>>
>> Thanks,
>>
>> Mark
>>
>>>
>>> Thanks
>>>
>>>
>>> On Fri, Jan 17, 2020 at 12:08 PM Mark Reynolds <mreynolds@redhat.com> wrote:
>>>
>>>
>>> On 1/17/20 9:55 AM, Alberto Viana wrote:
>>>> Hi Guys,
>>>>
>>>> 389-Directory/1.4.3.1.20200116git4f9aafca9
>>>>
>>>> Start to get this error:
>>>> [17/Jan/2020:11:49:56.436658541 -0300] - NOTICE - bdb_start - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
>>> Anything else in the log?
>>>
>>> We are seeing some libdb issues where the mmaped region files are getting corrupted.  Try deleting these files and try starting the server again:    /var/lib/dirsrv/slapd-YOUR_INSTANCE/db/__db.*
>>>
>>>>
>>>> And 389 do not start anymore.
>>>>
>>>> Thanks
>>>>
>>>>
>>>> _______________________________________________
>>>> 389-users mailing list --
>>>> 389-users@lists.fedoraproject.org
>>>>
>>>> To unsubscribe send an email to
>>>> 389-users-leave@lists.fedoraproject.org
>>>>
>>>> Fedora Code of Conduct:
>>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>>>
>>>> List Guidelines:
>>>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>>>
>>>> List Archives:
>>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
>>> --
>>>
>>> 389 Directory Server Development Team
>>>
>>>
>>>
>>> _______________________________________________
>>> 389-users mailing list --
>>> 389-users@lists.fedoraproject.org
>>>
>>> To unsubscribe send an email to
>>> 389-users-leave@lists.fedoraproject.org
>>>
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>>
>>> List Guidelines:
>>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>>
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
>> --
>>
>> 389 Directory Server Development Team
>>
>>
>>
>> _______________________________________________
>> 389-users mailing list --
>> 389-users@lists.fedoraproject.org
>>
>> To unsubscribe send an email to
>> 389-users-leave@lists.fedoraproject.org
>>
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>
>> List Guidelines:
>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
> --
>
> 389 Directory Server Development Team
>
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org


Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org