Quantcast
Channel: Sophos User Bulletin Board
Viewing all articles
Browse latest Browse all 14361

FATAL:DB in recovery mode

$
0
0
Hi all

Both my clients are offline and i am getting the following error "the database system is in recovery mode"

Code:

2012:12:16-22:33:12 ******* epsecd[5112]: >=========================================================================
2012:12:16-22:33:12 ******* epsecd[5112]: E id="4281" severity="critical" sys="System" sub="epsecd" name="DBIx::Class::ResultSet::search(): DBI Connection failed: DBI connect('host=localhost;port=5432;dbname=epp','epp',...) failed: FATAL: the database system is in recovery mode at /usr/local/ap510/site/lib/DBIx/Class/Storage/DBI.pm line 1262" effect="Can't talk to Sophos LiveConnect"
2012:12:16-22:33:12 ******* epsecd[5112]:
2012:12:16-22:33:12 ******* epsecd[5112]: 1. Epsec::Utils::Logging::_log:59() /</usr/local/bin/epp_client.plx>Epsec/Utils/Logging.pm
2012:12:16-22:33:12 ******* epsecd[5112]: 2. Epsec::Logic::Client::on_error:1088() /</usr/local/bin/epp_client.plx>Epsec/Logic/Client.pm
2012:12:16-22:33:12 ******* epsecd[5112]: 3. Epsec::Logic::Base::run:60() /</usr/local/bin/epp_client.plx>Epsec/Logic/Base.pm
2012:12:16-22:33:12 ******* epsecd[5112]: 4. main::top-level:62() client.pl
2012:12:16-22:33:12 ******* epsecd[5112]: <=========================================================================
2012:12:16-22:33:12 ******* epsecd[5112]: I id="4210" severity="info" sys="System" sub="epsecd" name="Sleeping for 300 seconds"

Any way to fix this?

PS Not sure if this error is related to the expired certificate of *.broker.sophos.com http://www.astaro.org/gateway-produc...tml#post221161

Code:

2012:12:16-22:33:05 ******* postgres[13406]: [106-1] WARNING:  terminating connection because of crash of another server process
2012:12:16-22:33:05 ******* postgres[15125]: [106-2] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2012:12:16-22:33:05 ******* postgres[13406]: [106-2] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2012:12:16-22:33:05 ******* postgres[15125]: [106-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2012:12:16-22:33:05 ******* postgres[13406]: [106-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2012:12:16-22:33:05 ******* postgres[13327]: [106-1] WARNING:  terminating connection because of crash of another server process
2012:12:16-22:33:05 ******* postgres[13327]: [106-2] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2012:12:16-22:33:05 ******* postgres[13327]: [106-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2012:12:16-22:33:05 ******* postgres[15124]: [106-1] WARNING:  terminating connection because of crash of another server process
2012:12:16-22:33:05 ******* postgres[15124]: [106-2] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2012:12:16-22:33:05 ******* postgres[15124]: [106-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2012:12:16-22:33:05 ******* postgres[13309]: [106-1] WARNING:  terminating connection because of crash of another server process

thanks

Viewing all articles
Browse latest Browse all 14361

Trending Articles