perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Alex,

I’m not sure what would cause that error. Try running:

rm -f /var/lib/rpm/__db*
rpm –rebuilddb
yum clean all

Cheers,

Aaron

On Jun 19, 2014, at 2:11 PM, Alex Moura <> wrote:

Hey Aaron,

Thanks for the reply. I was trying the 'yum update' you recommended, but got stumped by another problem:

   [root@localhost ~]# yum update

   rpmdb: Thread/process 13680/140031832131328 failed: Thread died in Berkeley DB library

   erro: error db3 (-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery

   erro: it was not possible to open the index Packages using db3 -  (-30974)

   error: is was not possible to open the database at /var/lib/rpm

   CRITICAL:yum.main:

   Error: rpmdb open failed 

I suspect this was caused by lack of available RAM memory in the VM during the update process. 

(I did request the VM to be configured with 786MB RAM as per recommendation in pS docs).

Thanks,

Alex

On Wed, Jun 18, 2014 at 3:27 PM, Aaron Brown <> wrote:

Hey Alex,

I think that may have been caused by a buggy version of XML::RPC that EPEL6 started providing (overriding the one we distributed). I’ve put a patched version of the module into the yum repository so you should be able to do a “yum update”, and reboot, and it should start working.

Cheers,

Aaron

On Jun 18, 2014, at 11:02 AM, Alex Moura <> wrote:

Hello,

I one of our pS hosts, while trying to save the basic host configurations, the pS-Toolkit displays this message:

Problem saving configuration or restarting services: RequestError: Unable to load https://200.133.192.50/toolkit/admin/administrative_info/?fname=save_config&session_id=3bb227979cc327042734df6a680b3366 status: 504 

I am unable to save the config info.

Thanks,

Alex