similar to: Db4 ldap smldap-tools samba

Over the weekend my workstation (still on CentOS 3) started showing SMART errors, so we shut it down and moved everything onto a new drive. On reboot, the RPM database reports as corrupted and "rpm --rebuilddb" segmentation faults. Is there any reasonable way to recover from this, short of a complete reinstall? The machine is otherwise up though it''s quite likely some files

I'm currently re-installing db41 port. Earlier using 'innodb_force_recovery = 6' seemed to fix that PANIC error. But I don't understand this permission error. I've tried various permissions as well 777, 766, 666, 760, etc etc. I've also ran mysqld_safe as root user, but with same permission error. Also tried different directories without luck. When I log in to the

This is a cross post to <xen-devel@lists.sourceforge.net> and <user- mode-linux-user@lists.sourceforge.net> Dear lists, Anybody successfully running cyrus-imapd in FC2/3+Xen/UML? When i tried to run cyrus-imapd in a virtual FC3 (Xen or UML) i got lot''s of DBERROR db4: Berkeley DB library configured to support only DB_PRIVATE environments DBERROR:

I have been testing with openldap_2.2.13-2 and have experience on 2 occasions lockups where the ldap server does not respond (slapcat will just hang). I have upgraded to openldap_2.2.13-4. Is there a recommended version of openldap for SambaPDC? Does anyone have a system in production using openldap_2.2.13-2 or openldap_2.2.13-4? I'm currently using samba3-20b any recommendations for a

Hello, I've a Debian 3.1 box with Samba 3.0.9 acting as a PDC with OpenLDAP 2.1.30, smbldap-tools 0.8.5, libnss-ldap version 220-1. The problem is this: Yesterday suddenly a user from a workstation already joined to the domain could not log on any more. The log message was: Workstation HPDX02$: no account in domain Digging into LDAP I've found that the entry in the LDAP DB exists (I

Hi folks: I've recently migrated one of my production servers (bad Jason!) from WBEL to CentOS 3.3 using Donavan's instructions in the FAQ (http://www.centos.org/modules/smartfaq/faq.php?faqid=19). While it was as painless as the document suggests, I've run into problems with postgrey (a postfix greylisting daemon) on my server. Whenever I try to start postgrey, I get the

CentOS Errata and Bugfix Advisory 2012:0452 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0452.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0a466556f5dd693a22fe8b60a17f36ee520a86709a2bb8f9890892a744b5f744 db4-4.7.25-17.el6.i686.rpm f3ea647e99d9c6025aa9d52c0ea5a8fe6c87882983f96da7962ddae77f7fcd39

CentOS Errata and Bugfix Advisory 2013:1258 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 67a2836f2a8c6d1e97781136e9c0045cb1d56ab977748c5943fd1f6f29082777 db4-4.7.25-18.el6_4.i686.rpm 0760af1c325d15f4d516f2df0f883a45552be54bdda03d43aad6cc9c058efe64

CentOS Errata and Bugfix Advisory 2015:1085 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1085.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 543f20c2dcb5f1c6ff74acd32f4bb038e1efa8e2ba9d8c9296fff59ae595ea68 db4-4.7.25-19.el6_6.i686.rpm bd94ffa5b16c4ca1c16112879dff571276141f3466859dd19d935d2853b37ec4

CentOS Errata and Bugfix Advisory 2015:1809 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1bbe6a2090411a8ecec459f1bc94ebfa586f40a3a4f0c4e440e0e3bb06eb7ba5 db4-4.7.25-20.el6_7.i686.rpm 8a54c443ba848d8d110834daa07987e7b259a1e7d455f186701cd583b5eb34f9

CentOS Errata and Bugfix Advisory 2017:0035 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0035.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0e38b3d3bfd03d4d4fcd6068b70793f15e383aa63002f293bf361301db018949 db4-4.7.25-20.el6_8.1.i686.rpm

CentOS Errata and Bugfix Advisory 2010:0517 Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0517.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 039f5a1f262fb5aa5391b6532952eae3 db4-4.3.29-10.el5_5.2.i386.rpm ef21f675cfdddefe847c8cfb15bab92a db4-4.3.29-10.el5_5.2.x86_64.rpm

CentOS Errata and Bugfix Advisory 2010:0517 Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0517.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 30f28f608285751a871bb2358d6c76a2 db4-4.3.29-10.el5_5.2.i386.rpm 141902fd5cfad65752dd8a5b609866d5 db4-devel-4.3.29-10.el5_5.2.i386.rpm

Hi *, i run several CentOS4 systems as xen3 domU, and all of them suffer from the well-known-to-this-list db4/nptl bug: <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91933> so that i needed to rebuild db4 to make cyrus-imapd work. But a member of the centos devel ML reported that he has no problem at all running cyrus-imapd. Our setups are almost identical (dom0=FC6,

(Me Too ++: I''m running into the same issues with a non-nptl DB4 and rpm on rhel4) And making it even more interesting: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/as-x86/ "Red Hat Enterprise Linux 5 will no longer include support for LinuxThreads. Therefore, applications that require LinuxThreads support must be updated before they will be able to

Hi, I just started to set up a test ldap server and followed some tutorials. One topic is the tuning/monitoring of the bdb. So I installed the db4-utils and executed a "db_stat -h /var/lib/ldap/ -m". The answere is no stat, but: db_stat: Program version 4.3 doesn't match environment version db_stat: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch The

Hi Folks, I have problems with delivering of mails. In /var/log/maillog are these error messages Mar 3 16:00:42 server pop3[15665]: DBERROR db4: Logging region out of memory; you may need to increase its size Mar 3 16:00:42 server pop3[15665]: DBERROR: opening /var/lib/imap/tls_sessions.db: Cannot allocate memory Mar 3 16:00:42 server pop3[15665]: DBERROR: opening

Hello, I just have a minor question. (Using Fedora 16) My current dovecot (2.2.10) was compiled with db4 (4.8.30). I am thinking of recompiling same dovecot (2.2.10) with libdb (5.2.36). I will be trying on live server so just wanted to know if this will this break any indexing or anything else? (Recompiling for Heartbleed, so might as well switch db version) AM.

We have had a Samba LDAP-PDC-BDC system setup for close to 3 months with about 60 computers in the domain. Earlier we had a power outage and about 30 computers no longer were able to log into the domain or authenticate. Some were NT Workstations and some were W2k. But not all NT or W2K workstations were affected. If we went to network neighborhood we would see the error message "

Hi this is more of an OpenLDAP issue, but since it is mostly used with Samba, some experience would be helpful. We have a SLES9 PDC, running samba-3.0.14a, openldap 2.2.6 Sometimes, the OpenLDAP gets corrupted, no ideas why. It's a bad thing. We have 100+ computers, 300+ users, which shall get 350 computers and 800 users. What would you suggest in order to be reliable ? Reliability is