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! On Fri, Aug 26, 2016 at 9:20 AM, William Hay <w....@ucl.ac.uk> wrote: > On Thu, Aug 25, 2016 at 04:40:55PM +0100, Ram??n Fallon wrote: > > * sgemaster still fails to come up. "messages" in > > $SGE_ROOT/$SGE_CELL/spool/qmaster now says: > > main|frontend0|W|local configuration frontend0 not defined - using > global > > configuration > > main|frontend0|E|global configuration not defined > > main|frontend0|C|setup failed > > * Seems to exonerate the database, but I'm not so sure ... database > repair > > was not "satisfying" > This would appear to be the sort of thing that backups are for. Your bdb > database is > now self-consistent but doesn't contain the data grid engine expects > anymore. If you don't have > a backup I suspect you'll probably need do a clean install somewhere. > > William >
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
