We have seen the database get corrupted so many times that we keep an empty database ready to be used in place of the corrupted database.
We haven't had a crash and corruption recently and I did discover on a recent apparent corruption that the problem was really that the execd thought that it had jobs to run that the master did not know about. We need to use bdb spooling because of the rate at which we spool and run jobs. Simon On Tue, Aug 30, 2016 at 1:41 AM, William Hay <w....@ucl.ac.uk> wrote: > On Fri, Aug 26, 2016 at 01:35:06PM +0100, Ram??n Fallon wrote: >> Thanks for the reply, William. >> >> Yes, that's true. >> >> It's a pity there's not a way to reset gridengine to begin anew on a new >> database for example. >> >> It seems quite a radical step to have to re-install gridengine just >> because of the database. Decidedly unmodular. But, I suppose, that's the >> nature of Berkeley DB ... I do however miss the stressing of this point in >> the documentation. Oh well, my turn to do it now, I expect. Cheers! >> >> Any other suggestions are still welcome! > > You should be able to get away with just wiping the cell and running sge_inst > now that I think about it. > > William > > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users > _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
