[Date Prev][Date Next]
Re: Help on "Resource temporarily unavailable" (Urgent -Thanks)
Is there any workaround (short-term solution) for the the slave in
interim perioid? It is because the master will then need to handle the full
workload, and upgrade may need some testing, and takes time.
From: Pierangelo Masarati <firstname.lastname@example.org> on 2001/10/11 06:07 PM
To: Wilson KH Sheh/ITSD/HKSARG@ITSD
Subject: Re: Help on "Resource temporarily unavailable" (Urgent -Thanks)
Wilson KH Sheh wrote:
> Dear All,
> I have 2 Openldap 2.0.7 running on Red Hat 7.0. They are in
> master-slave relationship. They are in two good condition since
> on April - i.e. correct in data replication and referral from slave to
> But recently, I find that the time stamps of the database files on
> slave sever is at Sep 7. It seems that the slave Openldap could not
> the database files, but only can be queried. Then I try to see the log
> using loglevel -1, the messages below appear. On the other hand, in the
> master server, the /var/lib/ldap/replica/slurpd.replog is full of
> modification entries. It seems that the master can send the replication
> entries to the slave, but the slave cannot update to the slave database.
> the slave log file, I can only find "resource temporarily unavailable"
> Do you know what's happens to my slave Openldap server? I have
> the permission of the slave database. They are identical to the master.
> probably it's not related to file permission. Moreover, as my master
> slurpd.replog is full of entries, does it means that the slave could not
> update it's database. Is it normally the slurpd.replog should be empty
> after replication?
> Thanks for your attention and help!
You need to upgrade to the latest release; from the changelog
> OpenLDAP 2.0.14 Release
> Fixed slurpd billionth second bug (ITS#1323)
Dr. Pierangelo Masarati | voice: +39 02 2399 8309
Dip. Ing. Aerospaziale | fax: +39 02 2399 8334
Politecnico di Milano | mailto:email@example.com
via La Masa 34, 20156 Milano, Italy |