Re: [Users] canot disable ssl on database
2012/6/29 Doron Fediuck <dfediuck@redhat.com>:
Looks like your db is down. Please try service postgresql status If it's not running, start it.
apparently starting postgres service was failed also, perhaps there's a package missing? is this a known issue on fedora 16? [root@ovirt01 ~]# service postgres status Redirecting to /bin/systemctl status postgres.service postgres.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) [root@ovirt01 ~]# service postgres stop Redirecting to /bin/systemctl stop postgres.service [root@ovirt01 ~]# service postgres start Redirecting to /bin/systemctl start postgres.service Failed to issue method call: Unit postgres.service failed to load: No such file or directory. See system logs and 'systemctl status postgres.service' for details. -- Regards, Umarzuki Mochlis http://debmal.my
On 06/29/2012 06:59 AM, Umarzuki Mochlis wrote:
2012/6/29 Doron Fediuck<dfediuck@redhat.com>:
Looks like your db is down. Please try service postgresql status If it's not running, start it.
apparently starting postgres service was failed also, perhaps there's a package missing? is this a known issue on fedora 16?
please use fedora 17 for 3.1. and its postgresql
[root@ovirt01 ~]# service postgres status Redirecting to /bin/systemctl status postgres.service postgres.service Loaded: error (Reason: No such file or directory) Active: inactive (dead)
[root@ovirt01 ~]# service postgres stop Redirecting to /bin/systemctl stop postgres.service
[root@ovirt01 ~]# service postgres start Redirecting to /bin/systemctl start postgres.service Failed to issue method call: Unit postgres.service failed to load: No such file or directory. See system logs and 'systemctl status postgres.service' for details.
2012/6/29 Itamar Heim <iheim@redhat.com>:
On 06/29/2012 06:59 AM, Umarzuki Mochlis wrote:
2012/6/29 Doron Fediuck<dfediuck@redhat.com>:
Looks like your db is down. Please try service postgresql status If it's not running, start it.
apparently starting postgres service was failed also, perhaps there's a package missing? is this a known issue on fedora 16?
please use fedora 17 for 3.1. and its postgresql
my bad but it seemed that postgresql failed to start anyway. would upgrading to fedora 17 solve this? [root@ovirt01 ~]# service postgresql status Redirecting to /bin/systemctl status postgresql.service postgresql.service - PostgreSQL database server Loaded: loaded (/lib/systemd/system/postgresql.service; disabled) Active: failed since Fri, 29 Jun 2012 20:05:25 +0800; 6s ago Process: 4265 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/postgresql.service -- Regards, Umarzuki Mochlis http://debmal.my
On 06/29/2012 02:09 PM, Umarzuki Mochlis wrote:
2012/6/29 Itamar Heim <iheim@redhat.com>:
On 06/29/2012 06:59 AM, Umarzuki Mochlis wrote:
2012/6/29 Doron Fediuck<dfediuck@redhat.com>:
Looks like your db is down. Please try service postgresql status If it's not running, start it.
apparently starting postgres service was failed also, perhaps there's a package missing? is this a known issue on fedora 16?
please use fedora 17 for 3.1. and its postgresql
my bad but it seemed that postgresql failed to start anyway. would upgrading to fedora 17 solve this?
[root@ovirt01 ~]# service postgresql status Redirecting to /bin/systemctl status postgresql.service postgresql.service - PostgreSQL database server Loaded: loaded (/lib/systemd/system/postgresql.service; disabled) Active: failed since Fri, 29 Jun 2012 20:05:25 +0800; 6s ago Process: 4265 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/postgresql.service
It looks like you never started that database before. You need to run "postgresql-setup" before being able to start it.
2012/6/29 Juan Hernandez <juan.hernandez@redhat.com>:
It looks like you never started that database before. You need to run "postgresql-setup" before being able to start it.
thanks but something might had been missed on my part -bash-4.2$ psql engine -U postgres -c "UPDATE vdc_options set option_value = 'false' where option_name = 'SSLEnabled'" psql: FATAL: database "engine" does not exist -- Regards, Umarzuki Mochlis http://debmal.my
2012/6/29 Umarzuki Mochlis <umarzuki@gmail.com>:
2012/6/29 Juan Hernandez <juan.hernandez@redhat.com>:
It looks like you never started that database before. You need to run "postgresql-setup" before being able to start it.
thanks but something might had been missed on my part
-bash-4.2$ psql engine -U postgres -c "UPDATE vdc_options set option_value = 'false' where option_name = 'SSLEnabled'" psql: FATAL: database "engine" does not exist
indeed i had skipped "engine-setup" and now i the setup was a success -- Regards, Umarzuki Mochlis http://debmal.my
On 29/06/12 15:09, Umarzuki Mochlis wrote:
2012/6/29 Itamar Heim <iheim@redhat.com>:
On 06/29/2012 06:59 AM, Umarzuki Mochlis wrote:
2012/6/29 Doron Fediuck<dfediuck@redhat.com>:
Looks like your db is down. Please try service postgresql status If it's not running, start it.
apparently starting postgres service was failed also, perhaps there's a package missing? is this a known issue on fedora 16?
please use fedora 17 for 3.1. and its postgresql
my bad but it seemed that postgresql failed to start anyway. would upgrading to fedora 17 solve this?
[root@ovirt01 ~]# service postgresql status Redirecting to /bin/systemctl status postgresql.service postgresql.service - PostgreSQL database server Loaded: loaded (/lib/systemd/system/postgresql.service; disabled) Active: failed since Fri, 29 Jun 2012 20:05:25 +0800; 6s ago Process: 4265 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/postgresql.service
Hi Umarzuki, These are 2 separate issues; 1. You have a problem in your DB installation. 2. As Itamar suggested, oVirt 3.1 should be installed in Fedora 17, and not 16. Unsure if the upgrade process will fix your DB installation error, so I suggest you start a clean environment if possible. ie- get a new Fedora 17 setup, and install oVirt 3.1 on it. -- /d "Air conditioned environment - Do NOT open Windows!"
2012/7/1 Doron Fediuck <dfediuck@redhat.com>:
Unsure if the upgrade process will fix your DB installation error, so I suggest you start a clean environment if possible. ie- get a new Fedora 17 setup, and install oVirt 3.1 on it.
is it possible for me to just: - purge ovirt and all installed dependencies - upgrade fedora 16 -> 17 - install ovirt 3.1? -- Regards, Umarzuki Mochlis http://debmal.my
On 07/02/2012 07:27 AM, Umarzuki Mochlis wrote:
2012/7/1 Doron Fediuck <dfediuck@redhat.com>:
Unsure if the upgrade process will fix your DB installation error, so I suggest you start a clean environment if possible. ie- get a new Fedora 17 setup, and install oVirt 3.1 on it.
is it possible for me to just: - purge ovirt and all installed dependencies - upgrade fedora 16 -> 17 - install ovirt 3.1?
yes. run engine-cleanup script to help the purging...
participants (4)
-
Doron Fediuck -
Itamar Heim -
Juan Hernandez -
Umarzuki Mochlis