Hey guys, Just an update to let you know that apparently overnight the messages stopped.
Best regards, Gustavo Gustavo Silva <beat...@gmail.com> escreveu no dia sáb, 14/11/2015 às 03:24: > Hey guys, > > just started experiencing the same issue on a 5208R after last update. > It doesnt seem to break anything, just the logging thats curious: > > (snip) > > /var/log/messages > > Nov 14 03:11:29 cloud pam-abl[10246]: The database environment could not > be opened > Nov 14 03:13:04 cloud pam-abl[10292]: DB_RUNRECOVERY: Fatal error, run > database recovery (-30974) while opening the database environment > Nov 14 03:13:04 cloud pam-abl[10292]: DB_RUNRECOVERY: Fatal error, run > database recovery (-30974) while Creating database environment. > > Nov 14 03:14:25 cloud pam-abl[10292]: Invalid argument (22) while opening > the database environment > Nov 14 03:14:25 cloud pam-abl[10292]: Invalid argument (22) while Creating > database environment. > Nov 14 03:14:25 cloud pam-abl[10292]: The database environment could not > be opened > > Nov 14 03:15:03 cloud auth[10292]: pam_succeed_if(dovecot:auth): error > retrieving information about user t...@xxx.xxx.com > > (snip) > > /var/log/maillog > > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: Log sequence > error: page LSN 1 17495; previous LSN 1 17733 > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: Recovery > function for LSN 1 17802 failed on forward pass > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: PANIC: Invalid > argument > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: unable to join > the environment > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: Log sequence > error: page LSN 1 17495; previous LSN 1 17733 > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: Recovery > function for LSN 1 17802 failed on forward pass > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: PANIC: Invalid > argument > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: unable to join > the environment > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: Log sequence > error: page LSN 1 17495; previous LSN 1 17733 > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: Recovery > function for LSN 1 17802 failed on forward pass > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: PANIC: Invalid > argument > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: unable to join > the environment > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: DB_REGISTER > limits processes to one open DB_ENV handle per environment > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: DB_REGISTER > limits processes to one open DB_ENV handle per environment > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: DB_REGISTER > limits processes to one open DB_ENV handle per environment > Nov 14 03:14:24 cloud dovecot: auth-worker: Error: pam-abl: DB_REGISTER > limits processes to one open DB_ENV handle per environment > Nov 14 03:14:25 cloud dovecot: auth-worker: Error: pam-abl: DB_REGISTER > limits processes to one open DB_ENV handle per environment > Nov 14 03:14:25 cloud dovecot: auth-worker: Error: pam-abl: DB_REGISTER > limits processes to one open DB_ENV handle per environment > > Best regards, > Gustavo > > > Keith Richardson @Mister Safety Shoes Inc <i...@mistersafetyshoes.com> > escreveu no dia seg, 9/11/2015 às 13:12: > >> HI Michael, >> >> >> >> This seems to be happening daily. >> >> I’m running the /sbin/service pam_abl restart each morning but I get the >> message the following morning >> >> >> >> --------------------- Connections (secure-log) Begin >> ------------------------ >> >> >> >> >> >> **Unmatched Entries** >> >> pam-abl: DB_RUNRECOVERY: Fatal error, run database recovery (-30974) >> while Creating host database.: 2 Time(s) >> >> pam-abl: DB_RUNRECOVERY: Fatal error, run database recovery (-30974) >> while opening or creating database: 2 Time(s) >> >> pam-abl: DB_RUNRECOVERY: Fatal error, run database recovery (-30974) >> while starting transaction: 3 Time(s) >> >> pam-abl: DB_RUNRECOVERY: Fatal error, run database recovery (-30974) >> while starting transaction to update_status.: 3 Time(s) >> >> pam-abl: The database environment could not be opened: 2 Time(s) >> >> ---------------------- Connections (secure-log) End >> ------------------------- >> >> >> >> Any idea why this keeps coming back after running the repair? >> >> >> >> >> >> >> >> *Regards,* >> >> *Keith* >> >> >> >> >> >> *Keith Richardson* | Information Services| *Mister Safety Shoes Inc* | >> 2300 Finch Ave W, Unit 6| Toronto, Ont M9M 2Y3 | Phone 416-746-3000 Ext >> 228|1-800-707-0051 Ext 228 | http://www.mistersafetyshoes.com >> >> >> _______________________________________________ >> Blueonyx mailing list >> Blueonyx@mail.blueonyx.it >> http://mail.blueonyx.it/mailman/listinfo/blueonyx >> >
_______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
