[GE users] Issue with upgrade to 6.0u3: inst_sge -bup fails (fwd)]

Andy Schwierskott andy.schwierskott at sun.com
Mon Jan 31 09:02:28 GMT 2005


"db_dump" in the courtesy binary distribution is a 64bit binary.

This means there is a bug with having the wrong "db_dump" utility in the

The binaries berkeley_db_svc, db_archive and db_checkpoint in
utilbin/sol-sparc64 are all 32bit binaries.

Could you pelase create an issue?


> Wilfried,
> the version of Berkeley Db we're currently using has problems with
> solaris 64.
> So we have decided to use the 32 bit linked berkeley db rpc server,
> but db_dump and db_load are still 64 bit binaries.
> Using the 32 bit db_dump and db_load makes it work.
> Please take the solaris binaries and it will work, I tested it on my machine
> The LD_LIBRARY_PATH has to be set to the 32 bit libdb-4.2.so too.
> Regards,
> Marco
> Wilfried Gaensheimer wrote:
>> On Tue, 25 Jan 2005, Marco Donauer wrote:
>> Marco,
>>> it looks like your using a bdb spooling server, is this right?
>> yes.
>>> In this case the inst_sge -bup is not working, because the bdb spooling server
>>> is currently not supported.
>> I just followed the install60patch.txt description step by step. The
>> step "6.1 Backup BDB" fails.
>>> You must login directly to the spooling server and execute this command:
>> Currently bdb spooling server and qmaster are the same server.
>>> - login to your bdb rpc server host
>>> - source the settings file
>>> - db_dump -f /tmp/backup.dump -h dbd_home (eg. /home/grid_f/6.0/muc/spooldb)
>>> sge
>> O.K., when I try that, db_dump hangs:
>> lwp_mutex_lock(0xFFFFFFFF7E300000) (sleeping...) ?
>> ...
>> I'll continue without a dump (test environment) but before release of
>> this version to production I would need a proper way for a db-backup.
>> Bye
>> Wilfried

To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list