Re: [RAS] Cron <aras@nebka> /usr/bin/db4.6_recover -h ~/acis/RI/data ; /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data && /usr/bin/db4.6_archive -d -h ~/acis/RI/data
We again look to have a problem. I did only one software change, took citatation change out of APU to try rid us from the overload.... Cron Daemon writes
db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2696775, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2696775, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_checkpoint: /home/aras/acis/RI/data/ACIS/records: unable to flush: No such file or directory db4.6_checkpoint: txn_checkpoint: failed to flush the buffer cache: No such file or directory db4.6_checkpoint: txn_checkpoint: No such file or directory
-- Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
This may not be related to citations processing or APU, actually. This might have been triggered by lack of diskspace or i don't know what. -i On Sat, Jan 8, 2011 at 6:16 AM, Thomas Krichel <krichel@openlib.org> wrote:
We again look to have a problem. I did only one software change, took citatation change out of APU to try rid us from the overload....
Cron Daemon writes
db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2696775, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2696775, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493362/2132591, past end of log at 493362/1823218 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_checkpoint: /home/aras/acis/RI/data/ACIS/records: unable to flush: No such file or directory db4.6_checkpoint: txn_checkpoint: failed to flush the buffer cache: No such file or directory db4.6_checkpoint: txn_checkpoint: No such file or directory
--
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
_______________________________________________ RAS-run mailing list RAS-run@lists.openlib.org http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run
Ivan Kurmanov writes
This may not be related to citations processing or APU, actually.
I think this is a bit of an understatment ;-)
This might have been triggered by lack of diskspace or i don't know what.
It's probably more the latter rather than the former. A sense of humour is when one is still laughing... Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
participants (2)
-
Ivan Kurmanov -
Thomas Krichel