389ds can't start after "db error (no disk space)" ... space problem has been resolved

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi there, we have four IPA servers 4.4.0 and 389-ds is 1.3.5.10-11, and there is multi master replication among some of them. 

There is daily backup via ipa-backup, and on one server it failed because of disk space. The /var/log/dirsrv/slapd-EXAMPLE-COM/errors read: 

- NSMMReplicationPlugin - changelog program - _cl5WriteEntryCount: failed to write count entry for file /var/lib/dirsrv/slapd-EXAMPLE-COM/cldb/2acb5f15-a8ef11e6-81cbc137-643887ad_57be0c5f000000040000.db; db error - 28 No space left on device
- NSMMReplicationPlugin - changelog program - _cl5WriteRUV: failed to write purge RUV for file /var/lib/dirsrv/slapd-EXAMPLE-COM/cldb/2acb5f15-a8ef11e6-81cbc137-643887ad_57be0c5f000000040000.db; db error - 28 (No space left on device)
- NSMMReplicationPlugin - changelog program - _cl5WriteRUV: failed to write upper bound RUV for file /var/lib/dirsrv/slapd-EXAMPLE-COM/cldb/2acb5f15-a8ef11e6-81cbc137-643887ad_57be0c5f000000040000.db; db error - 28 (No space left on device)
- NSMMReplicationPlugin - changelog program - _cl5WriteEntryCount: failed to write count entry for file /var/lib/dirsrv/slapd-EXAMPLE-COM/cldb/6070479f-a8ef11e6-81cbc137-643887ad_57be0cb8000000600000.db; db error - 28 No space left on device

Disk space is resolved by growing logical volume, but 389ds fails to start with messages:

- NSMMReplicationPlugin - changelog program - cl5Open: failed to open changelog
- NSMMReplicationPlugin - changelog program - changelog5_init: failed to start changelog at /var/lib/dirsrv/slapd-EXAMPLE-COM/cldb
- Failed to start object plugin Multimaster Replication Plugin
- Error: Failed to resolve plugin dependencies

Can you please advise about possible resolution. Thanks in advance, Zarko
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux