Article ID: 127444, created on Nov 17, 2015, last review on Nov 17, 2015

  • Applies to:
  • Plesk Automation 11.5

Symptoms

When trying to log in to the panel it is constantly loading and redirecting to itself. If go to the management node shell and try to restart pem service, it fails with the error:

# service pem start
Starting pleskd: terminate called after throwing an instance of 'CORBA::NO_PERMISSION'
SCMonitor::startAllSC failed:Failed to start sc Kernel(2)
                                                           [FAILED]

The following entries can be found in /var/log/pos.debug.log:

Nov 17 10:41:59 ppa : DBG [0:8140:f69eba30:2 1:8140:f56ffb90 Kernel]: [void<unnamed>::get_auth_systems] ===> ENTRY
Nov 17 10:41:59 ppa : DBG [0:8140:f69eba30:2 1:8140:f56ffb90 Kernel]: [DBS::checkSQLError] Diagnostic info about SQL error: sqlreturn=0 state=08001, nativeCode=101, description=[unixODBC]Could not connect to the server; Connection refused [172.16.254.36:5432]
Nov 17 10:41:59 ppa : DBG [0:8140:f69eba30:2 1:8140:f56ffb90 lib]: [DBS::Connection_impl::connect_] {module_id="db_service"; code="1"} '[unixODBC]Could not connect to the server; Connection refused [172.16.254.36:5432]' while 'Connecting'
Nov 17 10:41:59 ppa : DBG [0:8140:f69eba30:2 1:8140:f56ffb90 Kernel]: [void<unnamed>::get_auth_systems] <=== EXIT (by exception) [0.042335]
Nov 17 10:41:59 ppa : DBG [0:8140:f69eba30:2 1:8140:f56ffb90 Kernel]: [Authentication::AuthenticationManager_impl::authenticateUser] <=== EXIT (by exception) [0.044052]
Nov 17 10:41:59 ppa : ERR [0:8140:f69eba30:2 1:8140:f56ffb90 lib]: [hub_impl::acquire_own_cred] ExSystem: module_id:'db_service', ex_type_id:'1',Message:''[unixODBC]Could not connect to the server; Connection refused [172.16.254.36:5432]' while 'Connecting'', deprecated_codes = (0, 0), properties = { sqlcode: '08001',reason: '[unixODBC]Could not connect to the server; Connection refused [172.16.254.36:5432]',action: 'Connecting', }
Nov 17 10:41:59 ppa : INF [0:8140:f69eba30:2 1:8140:f56ffb90 Kernel]: [hub_impl::acquire_own_cred] system_for_scs: login failed (system exception)
Nov 17 10:41:59 ppa : DBG [0:8140:f69eba30:2 1:8140:f56ffb90 Kernel]: [hub_impl::acquire_own_cred] <=== EXIT (by exception) [0.060584]
Nov 17 10:41:59 ppa : DBG [SYSTEM 0:8116:f76736e0 pleskd]: [startNewProcess] stderr: [terminate called after throwing an instance of 'CORBA::NO_PERMISSION' ]
Nov 17 10:41:59 ppa : DBG [SYSTEM 0:8116:f76736e0 pleskd]: [UnixRunner::startNewProcess] <=== EXIT [0.243168]

The pem service cannot start because Postgres database engine is not running. On attempt to start Postgres it looks like it started, but in fact it crashes. The following entries are present in the end of the /var/lib/pgsql/9.1/pgstartup.log:

FATAL:  bogus data in lock file "postmaster.pid": "f2W"
FATAL:  bogus data in lock file "postmaster.pid": "f2W"
FATAL:  bogus data in lock file "postmaster.pid": "f2W"

Cause

postmaster.pid file with incorrect content prevents Postgres database engine from starting.

Resolution

  1. Remove the postmaster.pid file:

    # rm -f /var/lib/pgsql/9.1/data/postmaster.pid
    
  2. Start Posgres database engine:

    # service postgresql-9.1 start
    Starting postgresql-9.1 service:                           [  OK  ]
    
  3. Start pem service:

    # service pem start
    Starting pleskd:                                           [  OK  ]
    

Search Words

cannot login

terminate called after throwing an instance

looping redirect

Diagnostic info about SQL error

Could not connect to the server

When admin tries to login there is an infinite loop and cannot login

Connection refused

CORBA::NO_PERMISSION

login failed (system exception)

Failed to start sc Kernel

bogus data in lock file

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF