I tried the suggestion of deleting the postmaster.pid file after verifying that 
it was not locked by any process.  

Then I restarted postgres which succeeded and then restarted the engine VM.

The vm came up normally and passed the liveliness test.


Gary


------------------------------------------------------------------------
Gary Pedretty                                        g...@ravnalaska.net 
<mailto:g...@eraalaska.net>
Systems Manager                                          www.flyravn.com 
<http://www.flyravn.com/>
Ravn Alaska                           /\                    907-450-7251
5245 Airport Industrial Road         /  \/\             907-450-7238 fax
Fairbanks, Alaska  99709        /\  /    \ \ Second greatest commandment
Serving All of Alaska          /  \/  /\  \ \/\   “Love your neighbor as
Really loving the record green up date! Summmer!!   yourself” Matt 22:39
------------------------------------------------------------------------












> On Jan 7, 2017, at 12:01 PM, Gary Pedretty <g...@ravnalaska.net> wrote:
> 
> After more testing, I can get the engine vm to run manually with ha-agent 
> stopped.  It still fails the liveliness check.  Here is the repeating error 
> in the engine.log from the engine vm
> 
> ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool — 46) [] 
> Error in getting DB connection, database is inaccessible: Error retrieving 
> database metadata; nested exception is 
> org.springframework.jdbc.support.MetaDataAccessException: Could not get 
> Connection for extracting meta data; nested exception is 
> org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC 
> Connection; nested exception is java.sql.SQLException: 
> javax.resource.ResourceException: IJ000453: Unable to get managed connection 
> for java:/ENGINEDataSource
> 
> 
> Found a suggestion about trying a test connection to the database and get the 
> following.
> 
> [root@fai-kvm-engine ~]# psql --host localhost --port 5432 --user engine 
> --password engine
> Password for user engine:
> psql: could not connect to server: Connection refused
>         Is the server running on host "localhost" (::1) and accepting
>         TCP/IP connections on port 5432?
> could not connect to server: Connection refused
>         Is the server running on host "localhost" (127.0.0.1) and accepting
>         TCP/IP connections on port 5432?
> [root@fai-kvm-engine ~]#
> 
> and checking that postgresql is running shows 
> 
> [root@fai-kvm-engine ~]# systemctl status postgresql
> â— postgresql.service - PostgreSQL database server
>    Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; 
> vendor preset: disabled)
>    Active: failed (Result: exit-code) since Sat 2017-01-07 20:58:04 UTC; 2s 
> ago
>   Process: 23867 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p 
> ${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
>   Process: 23860 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} 
> (code=exited, status=0/SUCCESS)
> 
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> systemd[1]: Starting PostgreSQL 
> database server...
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> pg_ctl[23867]: pg_ctl: another server 
> might be running; trying to start server anyway
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> pg_ctl[23867]: FATAL:  pre-existing 
> shared memory block (key 5432001, ID 0) is still in use
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> pg_ctl[23867]: HINT:  If you're sure 
> there are no old server processes still running, remove the shared memory 
> block or just delete the file "postmaster.pid".
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> pg_ctl[23867]: pg_ctl: could not 
> start server
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> pg_ctl[23867]: Examine the log output.
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> systemd[1]: postgresql.service: 
> control process exited, code=exited status=1
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> systemd[1]: Failed to start 
> PostgreSQL database server.
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> systemd[1]: Unit postgresql.service 
> entered failed state.
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
> <http://fai-kvm-engine.ravnalaska.net/> systemd[1]: postgresql.service failed.
> 
> 
> ------------------------------------------------------------------------
> Gary Pedretty                                        g...@ravnalaska.net 
> <mailto:g...@eraalaska.net>
> Systems Manager                                          www.flyravn.com 
> <http://www.flyravn.com/>
> Ravn Alaska                           /\                    907-450-7251
> 5245 Airport Industrial Road         /  \/\             907-450-7238 fax
> Fairbanks, Alaska  99709        /\  /    \ \ Second greatest commandment
> Serving All of Alaska          /  \/  /\  \ \/\   “Love your neighbor as
> Really loving the record green up date! Summmer!!   yourself” Matt 22:39
> ------------------------------------------------------------------------
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> On Jan 6, 2017, at 10:05 PM, Gary Pedretty <g...@ravnalaska.net 
>> <mailto:g...@ravnalaska.net>> wrote:
>> 
>> I just tried running the most recent update that came out for Ovirt Hosted 
>> Engine setup.  This is a glusterized setup with 4 hosts setup as per the 
>> Documentation.   Each host had the icon showing upgrades available so I 
>> started clicking upgrade for each host doing them one at time. 3 of them 
>> went into maintenance fine, migrated their VMs and then activated when done. 
>>  The last one to do was the one actually running the hosted-engine VM.  This 
>> host also had one other VM.  It migrated the other VM just fine, but stalled 
>> trying to migrate the hosted-engine.  Eventually the web interface became 
>> non-responsive and I moved to command line.  I have tried everything to get 
>> the engine to start up.  I have tried putting all the hosts in maintenance 
>> so that I could selectively tell it to start the hosted-engine VM on one 
>> host specifically, but each fails with the “Failed Liveliness error.  I have 
>> tried restarting the ha agents, re-initializing the lockspace all with no 
>> success.  All my VMs are still running fine, I just cannot get the 
>> hosted-engine to run.   I can if necessary shutdown all the VMs and restart 
>> all the hosts, but was trying to avoid that unless I have to.
>> 
>> Ideas.
>> 
>> Gary
>> 
>> 
>> ------------------------------------------------------------------------
>> Gary Pedretty                                        g...@ravnalaska.net 
>> <mailto:g...@eraalaska.net>
>> Systems Manager                                          www.flyravn.com 
>> <http://www.flyravn.com/>
>> Ravn Alaska                           /\                    907-450-7251
>> 5245 Airport Industrial Road         /  \/\             907-450-7238 fax
>> Fairbanks, Alaska  99709        /\  /    \ \ Second greatest commandment
>> Serving All of Alaska          /  \/  /\  \ \/\   “Love your neighbor as
>> Really loving the record green up date! Summmer!!   yourself” Matt 22:39
>> ------------------------------------------------------------------------
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users@ovirt.org <mailto:Users@ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
> 
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to