[ovirt-users] ovirt do not start postgresql
Yedidyah Bar David
didi at redhat.com
Thu Mar 22 08:40:15 UTC 2018
Hi all,
It's very hard to debug this without getting a full picture of the state
of the machine, including logs, versions, flow, etc. Some comments inside.
On Thu, Mar 22, 2018 at 10:12 AM, Sandro Bonazzola <sbonazzo at redhat.com> wrote:
>
>>
>> As Didi mentioned, we are looking for errors in the below files/dir.
>> Do you mind to take a look and share the error message?
>>
>> /var/log/ovirt-engine/setup/*
>> /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_log
>> /var/log/messages
>>
>>
>
> Didi, Eli, can you please have a look?
>
>
>
> Looking at the logs Marcos shared with me I see:
>
> 2018-03-21 15:02:30,373-0400 DEBUG
> otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema
> plugin.executeRaw:863 execute-result:
> ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p',
> '5432', '
> -u', 'engine_20180321150206', '-d', 'engine_20180321150206', '-l',
The fact that your database name is 'engine_20180321150206' most likely means
you have/had some problem, see also:
https://bugzilla.redhat.com/show_bug.cgi?id=1259782
Please check if you have other databases on your machine, why this one was
created, etc.
Some information to understand this can be found in the setup logs.
> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20180321150115-jjxbh3.log',
> '-c', 'apply'], rc=1
> 2018-03-21 15:02:30,374-0400 DEBUG
> otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:921
> execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s',
> 'localhost', '-p', '5432', '-u'
> , 'engine_20180321150206', '-d', 'engine_20180321150206', '-l',
> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20180321150115-jjxbh3.log',
> '-c', 'apply'] stdout:
> Creating schema engine_20180321150206 at localhost:5432/engine_20180321150206
> Creating fresh schema
> Creating tables...
> Creating functions...
>
> 2018-03-21 15:02:30,374-0400 DEBUG
> otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926
> execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s',
> 'localhost', '-p', '5432', '-u'
> , 'engine_20180321150206', '-d', 'engine_20180321150206', '-l',
> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20180321150115-jjxbh3.log',
> '-c', 'apply'] stderr:
> psql:/usr/share/ovirt-engine/dbscripts/create_functions.sql:1095: ERROR:
> must be owner of function uuid_generate_v1
> FATAL: Cannot execute sql command:
> --file=/usr/share/ovirt-engine/dbscripts/create_functions.sql
>
> 2018-03-21 15:02:30,374-0400 ERROR
> otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:428
> schema.sh: FATAL: Cannot execute sql command:
> --file=/usr/share/ovirt-engine/dbscripts/create_functions
> .sql
> 2018-03-21 15:02:30,375-0400 DEBUG otopi.context context._executeMethod:143
> method exception
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in
> _executeMethod
> method['method']()
> File
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py",
> line 430, in _misc
> raise RuntimeError(_('Engine schema refresh failed'))
> RuntimeError: Engine schema refresh failed
> 2018-03-21 15:02:30,376-0400 ERROR otopi.context context._executeMethod:152
> Failed to execute stage 'Misc configuration': Engine schema refresh failed
> 2018-03-21 15:02:30,377-0400 DEBUG otopi.transaction transaction.abort:119
> aborting 'DWH Engine database Transaction'
> 2018-03-21 15:02:30,377-0400 DEBUG otopi.transaction transaction.abort:119
> aborting 'Database Transaction'
>
>
> A few lines above in the log I see:
>
> ********* QUERY **********
> CREATE OR REPLACE FUNCTION uuid_generate_v1()
> RETURNS uuid STABLE
> AS $PROCEDURE$
> DECLARE
> v_val BIGINT;
> v_4_1_part CHAR(4);
> v_4_2_part CHAR(4);
> v_4_3_part CHAR(4);
> v_8_part CHAR(8);
> v_12_part CHAR(12);
> v_4_part_max INT;
> BEGIN
> PERFORM setseed(random());
>
> -- The only part we should use modulo is the 4 digit part, all the
> -- rest are really big numbers (i.e 16^8 - 1 and 16^12 - 1)
> -- The use of round(random() * 1000 is for getting a different id
> -- for DC/Cluster in different installations
> v_4_part_max = 65535;-- this is 16^4 -1
>
> v_val := nextval('uuid_sequence');
> v_4_1_part := lpad(to_hex((v_val + (round(random() * 1000))::BIGINT)),
> 4, '0');
> v_4_2_part := lpad(to_hex((v_val + (round(random() * 1000))::BIGINT)),
> 4, '0');
> v_4_3_part := lpad(to_hex((v_val + (round(random() * 1000))::BIGINT)),
> 4, '0');
>
> -- generate this part using the clock timestamp
> v_8_part := lpad(to_hex(cast(FLOOR(EXTRACT(EPOCH FROM
> clock_timestamp())) as bigint)), 8 , '0');
>
> v_12_part := lpad(to_hex((v_val + (round(random() * 1000))::BIGINT)),
> 12, '0');
>
> RETURN v_8_part || v_4_1_part || v_4_2_part || v_4_3_part || v_12_part;
> END;$PROCEDURE$
> LANGUAGE plpgsql;
> **************************
This function was removed by:
https://gerrit.ovirt.org/#/c/84832/
which should be included in 4.2.1 :
https://bugzilla.redhat.com/show_bug.cgi?id=1515635
>
> The log is OVESETUP_CORE/generatedByVersion=str:'4.2.1.7'
So not sure how you still have it.
I suggest to open a bug in bugzilla and attach a sosreport of the machine.
You can use this link:
https://bugzilla.redhat.com/enter_bug.cgi?alias=&assigned_to=sbonazzo%40redhat.com&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=unspecified&bug_status=NEW&cf_build_id=&cf_category=---&cf_clone_of=&cf_cloudforms_team=---&cf_compliance_control_group=---&cf_compliance_level=---&cf_crm=&cf_cust_facing=---&cf_devel_whiteboard=&cf_docs_score=&cf_documentation_action=---&cf_environment=&cf_internal_whiteboard=&cf_mount_type=---&cf_ovirt_team=Integration&cf_pm_score=&cf_regression_status=---&cf_story_points=---&cf_subsystem_team=---&cf_type=Bug&comment=Description%20of%20problem%3A%0D%0A%0D%0A%0D%0AVersion-Release%20number%20of%20selected%20component%20%28if%20applicable%29%3A%0D%0A%0D%0A%0D%0AHow%20reproducible%3A%0D%0A%0D%0A%0D%0ASteps%20to%20Reproduce%3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A%0D%0A&component=Setup.Engine&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&deadline=&defined_cf_layered_products=&defined_cf_partner=&defined_groups=1&defined_rh_sub_component=0&dependson=&description=&docs_contact=&estimated_time=&external_bug_id_1=&external_id_1=0&flag_type-155=X&flag_type-16=X&flag_type-415=X&flag_type-817=X&flag_type-818=X&flag_type-819=X&flag_type-820=X&flag_type-821=X&flag_type-823=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=unspecified&product=ovirt-engine&qa_contact=pstehlik%40redhat.com&rep_platform=Unspecified&requestee_type-155=&requestee_type-16=&rh_sub_component=&short_desc=&status_whiteboard=&target_milestone=---&target_release=---&version=4.2.0
My guess for the reason of the failure:
You updated the setup packages to 4.2.1.7, but the engine itself
failed to update - either because you ran engine-setup with
'--offline' or because you removed the repos, they were unavailable,
something like that.
Even if I am right, I'd still try to understand why it tries to use
database engine_20180321150206, as there might be some other problems.
Best regards,
--
Didi
More information about the Users
mailing list