[Users] Installation problem
Hi all, I was working through the installation of ovirt-engine today (after spending more time than I care to admit struggling with networking & DNS issues - VPNs, dnsmasq, "classic" network start-up and iptables/firewall rules can interract with each other in strange and surprising ways). Anyway - I went through the engine set-up successfully, and got the expected message at the end: "**** Installation completed successfully ******" with a message to visit the engine web application to finish set-up. Unfortunately, when I connected (after resolving networking issues) to the server in question, I got a "Service temporarily unavailable" error (503) from Apache. in httpd's error.log, I have:
[Fri Sep 21 13:37:03 2012] [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (localhost) failed [Fri Sep 21 13:37:03 2012] [error] ap_proxy_connect_backend disabling worker for (localhost) [Fri Sep 21 13:37:03 2012] [error] proxy: AJP: failed to make connection to backend: localhost
When I try to restart the ovirt-engine service, I get the following in journalctl:
Sep 21 13:34:44 clare.neary.home engine-service.py[5172]: The engine PID file "/var/run/ovirt-engine.pid" already exists. Sep 21 13:34:44 clare.neary.home systemd[1]: PID 1264 read from file /var/run/ovirt-engine.pid does not exist. Sep 21 13:34:44 clare.neary.home systemd[1]: Unit ovirt-engine.service entered failed state.
I tried to clean up and restart, but engine-cleanup failed:
[root@clare ovirt-engine]# engine-cleanup -u
Stopping JBoss service... [ DONE ]
Error: Couldn't connect to the database server.Check that connection is working and rerun the cleanup utility Error: Cleanup failed. please check log at /var/log/ovirt-engine/engine-cleanup_2012_09_21_14_02_37.log
It turns out, in /var/log/messages, that I have these error messages:
Sep 21 14:00:59 clare pg_ctl[5298]: FATAL: could not create shared memory segment: Invalid argument Sep 21 14:00:59 clare pg_ctl[5298]: DETAIL: Failed system call was shmget(key=5432001, size=36519936, 03600). Sep 21 14:00:59 clare pg_ctl[5298]: HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 36519936 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections. Sep 21 14:00:59 clare pg_ctl[5298]: If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for. Sep 21 14:00:59 clare pg_ctl[5298]: The PostgreSQL documentation contains more information about shared memory configuration. Sep 21 14:01:03 clare pg_ctl[5298]: pg_ctl: could not start server Sep 21 14:01:03 clare pg_ctl[5298]: Examine the log output. Sep 21 14:01:03 clare systemd[1]: postgresql.service: control process exited, code=exited status=1 Sep 21 14:01:03 clare systemd[1]: Unit postgresql.service entered failed state.
I increased the kernel's SHMMAX, and engine-cleanup worked correctly. Has anyone else experienced this issue? When I re-run engine-setup, I also got stuck when reconfiguring NFS - when engine-setup asked me if I wanted to configure the NFS domain, I said "yes", but then it refused to accept my input of "/mnt/iso" since it was already in /etc/exports - perhaps engine-cleanup should also remove ISO shares managed by ovirt-engine, or else handle more gracefully when someone enters an existing export? The only fix I found was to interrupt and restart the engine set-up. Also, I have no idea whether allowing oVirt to manage iptables will keep any extra rules I have added (specifically for DNS services on port 53 UDP) which I added to the iptables config. I didn't take the risk of allowing it to reconfigure iptables the second time. After all that, I got an error when starting the JBoss service:
Starting JBoss Service... [ ERROR ] Error: Can't start the ovirt-engine service Please check log file /var/log/ovirt-engine/engine-setup_2012_09_21_14_28_11.log for more information
And when I checked that log file:
2012-09-21 14:30:02::DEBUG::common_utils::790::root:: starting ovirt-engine 2012-09-21 14:30:02::DEBUG::common_utils::835::root:: executing action ovirt-engine on service start 2012-09-21 14:30:02::DEBUG::common_utils::309::root:: Executing command --> '/sbin/service ovirt-engine start' 2012-09-21 14:30:02::DEBUG::common_utils::335::root:: output = 2012-09-21 14:30:02::DEBUG::common_utils::336::root:: stderr = Redirecting to /bin/systemctl start ovirt-engine.service Job failed. See system journal and 'systemctl status' for details.
2012-09-21 14:30:02::DEBUG::common_utils::337::root:: retcode = 1 2012-09-21 14:30:02::DEBUG::setup_sequences::62::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run function() File "/bin/engine-setup", line 1535, in _startJboss srv.start(True) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 795, in start raise Exception(output_messages.ERR_FAILED_START_SERVICE % self.name) Exception: Error: Can't start the ovirt-engine service
And when I check the system journal, we're back to the service starts, but the PID mentioned in the PID file does not exist. Any pointers into how I might debug this issue? I haven't found anything similar in a troubleshooting page, so perhaps it's not a common error? Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
Dave Neary wrote:
It turns out, in /var/log/messages, that I have these error messages:
Sep 21 14:00:59 clare pg_ctl[5298]: FATAL: could not create shared memory segment: Invalid argument Sep 21 14:00:59 clare pg_ctl[5298]: DETAIL: Failed system call was shmget(key=5432001, size=36519936, 03600). Sep 21 14:00:59 clare pg_ctl[5298]: HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 36519936 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections. Sep 21 14:00:59 clare pg_ctl[5298]: If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for. Sep 21 14:00:59 clare pg_ctl[5298]: The PostgreSQL documentation contains more information about shared memory configuration. Sep 21 14:01:03 clare pg_ctl[5298]: pg_ctl: could not start server Sep 21 14:01:03 clare pg_ctl[5298]: Examine the log output. Sep 21 14:01:03 clare systemd[1]: postgresql.service: control process exited, code=exited status=1 Sep 21 14:01:03 clare systemd[1]: Unit postgresql.service entered failed state.
I increased the kernel's SHMMAX, and engine-cleanup worked correctly.
Has anyone else experienced this issue?
Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on?
When I re-run engine-setup, I also got stuck when reconfiguring NFS - when engine-setup asked me if I wanted to configure the NFS domain, I said "yes", but then it refused to accept my input of "/mnt/iso" since it was already in /etc/exports - perhaps engine-cleanup should also remove ISO shares managed by ovirt-engine, or else handle more gracefully when someone enters an existing export? The only fix I found was to interrupt and restart the engine set-up.
Just switch to a different terminal and edit /etc/exports and continue engine-setup.
Also, I have no idea whether allowing oVirt to manage iptables will keep any extra rules I have added (specifically for DNS services on port 53 UDP) which I added to the iptables config. I didn't take the risk of allowing it to reconfigure iptables the second time.
After all that, I got an error when starting the JBoss service:
Starting JBoss Service... [ ERROR ] Error: Can't start the ovirt-engine service Please check log file /var/log/ovirt-engine/engine-setup_2012_09_21_14_28_11.log for more information
And when I checked that log file:
2012-09-21 14:30:02::DEBUG::common_utils::790::root:: starting ovirt-engine 2012-09-21 14:30:02::DEBUG::common_utils::835::root:: executing action ovirt-engine on service start 2012-09-21 14:30:02::DEBUG::common_utils::309::root:: Executing command --> '/sbin/service ovirt-engine start' 2012-09-21 14:30:02::DEBUG::common_utils::335::root:: output = 2012-09-21 14:30:02::DEBUG::common_utils::336::root:: stderr = Redirecting to /bin/systemctl start ovirt-engine.service Job failed. See system journal and 'systemctl status' for details.
2012-09-21 14:30:02::DEBUG::common_utils::337::root:: retcode = 1 2012-09-21 14:30:02::DEBUG::setup_sequences::62::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run function() File "/bin/engine-setup", line 1535, in _startJboss srv.start(True) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 795, in start raise Exception(output_messages.ERR_FAILED_START_SERVICE % self.name) Exception: Error: Can't start the ovirt-engine service
And when I check the system journal, we're back to the service starts, but the PID mentioned in the PID file does not exist.
Any pointers into how I might debug this issue? I haven't found anything similar in a troubleshooting page, so perhaps it's not a common error?
Cheers, Dave.
Are you following the setup instructions from the Wiki? I have done that a couple of times now and haven't had problems sofar. Had lots of problems with the pre-3.1 releases though. Joop
Hi, On 09/21/2012 03:57 PM, Joop wrote:
Are you following the setup instructions from the Wiki? I have done that a couple of times now and haven't had problems sofar. Had lots of problems with the pre-3.1 releases though.
I am installing RPMs on Fedora 17 through the http://ovirt.org/releases/stable/rpm/Fedora/$releasever/ repository. I've been following the quick start guide: http://wiki.ovirt.org/wiki/Quick_Start_Guide and have been noting my various difficulties for a "Troubleshooting" page. Is there a better document to follow? Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
----- Original Message -----
From: "Joop" <jvdwege@xs4all.nl> To: "Dave Neary" <dneary@redhat.com> Cc: "users" <users@ovirt.org> Sent: Friday, September 21, 2012 9:57:02 AM Subject: Re: [Users] Installation problem
Dave Neary wrote:
It turns out, in /var/log/messages, that I have these error messages:
Sep 21 14:00:59 clare pg_ctl[5298]: FATAL: could not create shared memory segment: Invalid argument Sep 21 14:00:59 clare pg_ctl[5298]: DETAIL: Failed system call was shmget(key=5432001, size=36519936, 03600). Sep 21 14:00:59 clare pg_ctl[5298]: HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 36519936 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections. Sep 21 14:00:59 clare pg_ctl[5298]: If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for. Sep 21 14:00:59 clare pg_ctl[5298]: The PostgreSQL documentation contains more information about shared memory configuration. Sep 21 14:01:03 clare pg_ctl[5298]: pg_ctl: could not start server Sep 21 14:01:03 clare pg_ctl[5298]: Examine the log output. Sep 21 14:01:03 clare systemd[1]: postgresql.service: control process exited, code=exited status=1 Sep 21 14:01:03 clare systemd[1]: Unit postgresql.service entered failed state.
I increased the kernel's SHMMAX, and engine-cleanup worked correctly.
Has anyone else experienced this issue?
Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on?
I'm going to take a stab and guess Fedora. This came up for an unrelated reason in #fedora-devel the other day, because Fedora (and I suspect Debian as well) has a policy of sticking as close to upstream as possible it uses the shmmax of the upstream kernel - which is as you note quite low. In RHEL and other EL6 derivatives this value is modified and set much higher. Steve
This is a multi-part message in MIME format. --------------000800040702030209080207 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Steve Gordon wrote:
Has anyone else experienced this issue?
Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on?
I'm going to take a stab and guess Fedora. This came up for an unrelated reason in #fedora-devel the other day, because Fedora (and I suspect Debian as well) has a policy of sticking as close to upstream as possible it uses the shmmax of the upstream kernel - which is as you note quite low. In RHEL and other EL6 derivatives this value is modified and set much higher.
Steve
OK, learned something because I didn't suspect that Fedora would be so low because its set higher in RHEL en for example CentOS that I use on a db production platform. Thought that Fedora and RHEL were much closer. Joop --------------000800040702030209080207 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Steve Gordon wrote: <blockquote cite="mid:500936754.2964558.1348241174744.JavaMail.root@redhat.com" type="cite"> <blockquote type="cite"> <blockquote type="cite"> <pre wrap=""> Has anyone else experienced this issue? </pre> </blockquote> <pre wrap="">Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on? </pre> </blockquote> <pre wrap=""><!----> I'm going to take a stab and guess Fedora. This came up for an unrelated reason in #fedora-devel the other day, because Fedora (and I suspect Debian as well) has a policy of sticking as close to upstream as possible it uses the shmmax of the upstream kernel - which is as you note quite low. In RHEL and other EL6 derivatives this value is modified and set much higher. Steve </pre> </blockquote> OK, learned something because I didn't suspect that Fedora would be so low because its set higher in RHEL en for example CentOS that I use on a db production platform.<br> Thought that Fedora and RHEL were much closer.<br> <br> Joop<br> <br> <br> </body> </html> --------------000800040702030209080207--
Hi, Additional information: After removing and re-running engine-setup, I try once again to run ovirt-engine. I get the following error in the logs: ==> /var/log/ovirt-engine/console.log <== Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. Nothing else, unfortunately, and I have no idea how to debug JBoss AS to figure out what's going wrong. Are there any requirements in terms of the JRE which aren't specified in the quick start guide? Thanks, Dave. On 09/21/2012 03:57 PM, Joop wrote:
Dave Neary wrote:
It turns out, in /var/log/messages, that I have these error messages:
Sep 21 14:00:59 clare pg_ctl[5298]: FATAL: could not create shared memory segment: Invalid argument Sep 21 14:00:59 clare pg_ctl[5298]: DETAIL: Failed system call was shmget(key=5432001, size=36519936, 03600). Sep 21 14:00:59 clare pg_ctl[5298]: HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 36519936 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections. Sep 21 14:00:59 clare pg_ctl[5298]: If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for. Sep 21 14:00:59 clare pg_ctl[5298]: The PostgreSQL documentation contains more information about shared memory configuration. Sep 21 14:01:03 clare pg_ctl[5298]: pg_ctl: could not start server Sep 21 14:01:03 clare pg_ctl[5298]: Examine the log output. Sep 21 14:01:03 clare systemd[1]: postgresql.service: control process exited, code=exited status=1 Sep 21 14:01:03 clare systemd[1]: Unit postgresql.service entered failed state.
I increased the kernel's SHMMAX, and engine-cleanup worked correctly.
Has anyone else experienced this issue?
Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on?
When I re-run engine-setup, I also got stuck when reconfiguring NFS - when engine-setup asked me if I wanted to configure the NFS domain, I said "yes", but then it refused to accept my input of "/mnt/iso" since it was already in /etc/exports - perhaps engine-cleanup should also remove ISO shares managed by ovirt-engine, or else handle more gracefully when someone enters an existing export? The only fix I found was to interrupt and restart the engine set-up.
Just switch to a different terminal and edit /etc/exports and continue engine-setup.
Also, I have no idea whether allowing oVirt to manage iptables will keep any extra rules I have added (specifically for DNS services on port 53 UDP) which I added to the iptables config. I didn't take the risk of allowing it to reconfigure iptables the second time.
After all that, I got an error when starting the JBoss service:
Starting JBoss Service... [ ERROR ] Error: Can't start the ovirt-engine service Please check log file /var/log/ovirt-engine/engine-setup_2012_09_21_14_28_11.log for more information
And when I checked that log file:
2012-09-21 14:30:02::DEBUG::common_utils::790::root:: starting ovirt-engine 2012-09-21 14:30:02::DEBUG::common_utils::835::root:: executing action ovirt-engine on service start 2012-09-21 14:30:02::DEBUG::common_utils::309::root:: Executing command --> '/sbin/service ovirt-engine start' 2012-09-21 14:30:02::DEBUG::common_utils::335::root:: output = 2012-09-21 14:30:02::DEBUG::common_utils::336::root:: stderr = Redirecting to /bin/systemctl start ovirt-engine.service Job failed. See system journal and 'systemctl status' for details.
2012-09-21 14:30:02::DEBUG::common_utils::337::root:: retcode = 1 2012-09-21 14:30:02::DEBUG::setup_sequences::62::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run function() File "/bin/engine-setup", line 1535, in _startJboss srv.start(True) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 795, in start raise Exception(output_messages.ERR_FAILED_START_SERVICE % self.name) Exception: Error: Can't start the ovirt-engine service
And when I check the system journal, we're back to the service starts, but the PID mentioned in the PID file does not exist.
Any pointers into how I might debug this issue? I haven't found anything similar in a troubleshooting page, so perhaps it's not a common error?
Cheers, Dave.
Are you following the setup instructions from the Wiki? I have done that a couple of times now and haven't had problems sofar. Had lots of problems with the pre-3.1 releases though.
Joop
-- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
This is a multi-part message in MIME format. --------------070305040201090202010603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dave Neary wrote:
Hi,
Additional information:
After removing and re-running engine-setup, I try once again to run ovirt-engine. I get the following error in the logs: ==> /var/log/ovirt-engine/console.log <== Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
Nothing else, unfortunately, and I have no idea how to debug JBoss AS to figure out what's going wrong.
Are there any requirements in terms of the JRE which aren't specified in the quick start guide?
@Dave, Don't know if you have the luxury of starting from scratch but to be honest I have had problem with multple engin-setup/cleanup cycles and had to start from scratch which was faster than figuring out what went wrong. Those problems where with the pre-3.1 release. This is my ovirt.repo which I guess will be same for you: [ovirt-stable] name=Stable builds of the oVirt project baseurl=http://ovirt.org/releases/stable/rpm/Fedora/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 [ovirt-beta] name=Beta builds of the oVirt project baseurl=http://ovirt.org/releases/beta/rpm/Fedora/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 [ovirt-nightly] name=Nightly builds of the oVirt project baseurl=http://ovirt.org/releases/nightly/rpm/Fedora/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0 And the following is the first part of my history of my managment server 1 chkconfig sshd on 2 service sshd start 3 ifconfig 4 yum update --exclude=kernel* 5 uname -a 6 yum install -y firefox 7 yum install -y wget 8 yum install -y mc 9 yum install -y spice-xpi 10 init 6 11 system-config-network 12 cd /etc/sysconfig/networking/ 13 ls 14 ls -l devices/ 15 cat devices/ifcfg-em1 16 nano devices/ifcfg-em1 17 nano devices/ifcfg-p2p1 18 nano devices/ifcfg-p2p2 19 ls 20 ls devices/ 21 chkconfig NetworkManager off 22 service NetworkManager stop 23 chkconfig network on 24 service network start 25 ifconfig 26 init 6 27 exit 28 ifconfig 29 ifconfig 30 yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm 31 nano /etc/yum.repos.d/ovirt.repo 32 yum install engine-setup -y 33 ifconfig 34 ifconfig 35 pwd 36 system-config-network 37 ifconfig 38 service network restart 39 ifconfig 40 init 6 41 exit 42 cat /proc/cpuinfo 43 dmesg | grep CZ100 44 yum install dmidecode 45 cat /proc/meminfo 46 dmidecode | less 47 dmidecode | grep CZ 48 ps 49 ps -ef 50 top 51 cat /etc/exports 52 nano /etc/exports So all I did was follow the quick install and started of by getting some things installed I like, stop NetworkManager en setup the network, installed the ovirt.repo, entered my server in RT ;-) (dmidecode stuff) and not shown because I probably did it in another console engine-setup. Both my engine server and the two hosts I run for testing are HP Proliant ML110 and one DL3xx host. I had one migration problem because the uuid in the ML110's is the same and then you can't migrate, error is: migrating to same host, or something close to it. Base install is from Fedora 17 KDE live CD. Joop --------------070305040201090202010603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Dave Neary wrote: <blockquote cite="mid:505CADA4.6080303@redhat.com" type="cite">Hi, <br> <br> Additional information: <br> <br> After removing and re-running engine-setup, I try once again to run ovirt-engine. I get the following error in the logs: <br> ==> /var/log/ovirt-engine/console.log <== <br> Error: Could not create the Java Virtual Machine. <br> Error: A fatal exception has occurred. Program will exit. <br> <br> Nothing else, unfortunately, and I have no idea how to debug JBoss AS to figure out what's going wrong. <br> <br> Are there any requirements in terms of the JRE which aren't specified in the quick start guide? <br> </blockquote> <br> @Dave,<br> Don't know if you have the luxury of starting from scratch but to be honest I have had problem with multple engin-setup/cleanup cycles and had to start from scratch which was faster than figuring out what went wrong. Those problems where with the pre-3.1 release. This is my ovirt.repo which I guess will be same for you:<br> <br> <div class="moz-text-flowed" style="font-family: -moz-fixed; font-size: 13px;" lang="x-western">[ovirt-stable] <br> name=Stable builds of the oVirt project <br> baseurl=<a class="moz-txt-link-freetext" href="http://ovirt.org/releases/stable/rpm/Fedora/$releasever/">http://ovirt.org/releases/stable/rpm/Fedora/$releasever/</a> <br> enabled=1 <br> skip_if_unavailable=1 <br> gpgcheck=0 <br> <br> [ovirt-beta] <br> name=Beta builds of the oVirt project <br> baseurl=<a class="moz-txt-link-freetext" href="http://ovirt.org/releases/beta/rpm/Fedora/$releasever/">http://ovirt.org/releases/beta/rpm/Fedora/$releasever/</a> <br> enabled=1 <br> skip_if_unavailable=1 <br> gpgcheck=0 <br> <br> [ovirt-nightly] <br> name=Nightly builds of the oVirt project <br> baseurl=<a class="moz-txt-link-freetext" href="http://ovirt.org/releases/nightly/rpm/Fedora/$releasever/">http://ovirt.org/releases/nightly/rpm/Fedora/$releasever/</a> <br> enabled=0 <br> skip_if_unavailable=1 <br> gpgcheck=0 <br> <br> <br> </div> And the following is the first part of my history of my managment server<br> <br> <div class="moz-text-flowed" style="font-family: -moz-fixed; font-size: 13px;" lang="x-western"> 1 chkconfig sshd on <br> 2 service sshd start <br> 3 ifconfig <br> 4 yum update --exclude=kernel* <br> 5 uname -a <br> 6 yum install -y firefox <br> 7 yum install -y wget <br> 8 yum install -y mc <br> 9 yum install -y spice-xpi <br> 10 init 6 <br> 11 system-config-network <br> 12 cd <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>etc/sysconfig/networking<span class="moz-txt-tag">/</span></i> <br> 13 ls <br> 14 ls -l devices/ <br> 15 cat devices/ifcfg-em1 <br> 16 nano devices/ifcfg-em1 <br> 17 nano devices/ifcfg-p2p1 <br> 18 nano devices/ifcfg-p2p2 <br> 19 ls <br> 20 ls devices/ <br> 21 chkconfig NetworkManager off <br> 22 service NetworkManager stop <br> 23 chkconfig network on <br> 24 service network start <br> 25 ifconfig <br> 26 init 6 <br> 27 exit <br> 28 ifconfig <br> 29 ifconfig <br> 30 yum localinstall <a class="moz-txt-link-freetext" href="http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm">http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm</a> <br> 31 nano /etc/yum.repos.d/ovirt.repo <br> 32 yum install engine-setup -y <br> 33 ifconfig <br> 34 ifconfig <br> 35 pwd <br> 36 system-config-network <br> 37 ifconfig <br> 38 service network restart <br> 39 ifconfig <br> 40 init 6 <br> 41 exit <br> 42 cat /proc/cpuinfo <br> 43 dmesg | grep CZ100 <br> 44 yum install dmidecode <br> 45 cat /proc/meminfo <br> 46 dmidecode | less <br> 47 dmidecode | grep CZ <br> 48 ps <br> 49 ps -ef <br> 50 top <br> 51 cat /etc/exports <br> 52 nano /etc/exports <br> <br> <br> So all I did was follow the quick install and started of by getting some things installed I like, stop NetworkManager en setup the network, installed the ovirt.repo, entered my server in RT ;-) (dmidecode stuff) and not shown because I probably did it in another console engine-setup.<br> Both my engine server and the two hosts I run for testing are HP Proliant ML110 and one DL3xx host. I had one migration problem because the uuid in the ML110's is the same and then you can't migrate, error is: migrating to same host, or something close to it.<br> Base install is from Fedora 17 KDE live CD.<br> <br> Joop<br> <br> </div> <br> </body> </html> --------------070305040201090202010603--
Hi, On 09/21/2012 08:10 PM, Dave Neary wrote:
After removing and re-running engine-setup, I try once again to run ovirt-engine. I get the following error in the logs: ==> /var/log/ovirt-engine/console.log <== Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
I traced this to two unrecognised options being passed to the Java process by /usr/share/ovirt-engine/scripts/engine-service.py: -XX:+UseCompressedOops and -XX:+TieredCompilation By removing these from the command line, I make progress. I now have an oVirt web application displaying in my browser! I also noticed this typo in the same file: engineArgs.extend([ # Virtual machine options: "-server", "-XX:+UseCompressedOops", "-XX:+TieredCompilation", "-Xms%s" % engineHeapMin, "-Xms%s" % engineHeapMax, // This should be "-Xmx%s" to set the max heap size "-XX:PermSize=%s" % enginePermMin, "-XX:MaxPermSize=%s" % enginePermMax, "-Djava.net.preferIPv4Stack=true", "-Dsun.rmi.dgc.client.gcInterval=3600000", "-Dsun.rmi.dgc.server.gcInterval=3600000", "-Djava.awt.headless=true", ]) Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On 09/24/2012 04:34 PM, Dave Neary wrote:
Hi,
On 09/21/2012 08:10 PM, Dave Neary wrote:
After removing and re-running engine-setup, I try once again to run ovirt-engine. I get the following error in the logs: ==> /var/log/ovirt-engine/console.log <== Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
I traced this to two unrecognised options being passed to the Java process by /usr/share/ovirt-engine/scripts/engine-service.py: -XX:+UseCompressedOops and -XX:+TieredCompilation
Are you running in 32 bits environment? If you are in a 64 bits environment it is probably better to use a 64 bits Java virtual machine. The problem is that the -XX:+UseCompressedOops is only available in 32 bits Java virtual machines. There is a bug for that and it has already been fixed: https://bugzilla.redhat.com/852037
By removing these from the command line, I make progress. I now have an oVirt web application displaying in my browser!
I also noticed this typo in the same file:
engineArgs.extend([ # Virtual machine options: "-server", "-XX:+UseCompressedOops", "-XX:+TieredCompilation", "-Xms%s" % engineHeapMin, "-Xms%s" % engineHeapMax, // This should be "-Xmx%s" to set the max heap size "-XX:PermSize=%s" % enginePermMin, "-XX:MaxPermSize=%s" % enginePermMax, "-Djava.net.preferIPv4Stack=true", "-Dsun.rmi.dgc.client.gcInterval=3600000", "-Dsun.rmi.dgc.server.gcInterval=3600000", "-Djava.awt.headless=true", ])
That has been fixed as well: https://bugzilla.redhat.com/856564 -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
Hi, On 09/24/2012 05:28 PM, Juan Hernandez wrote:
Are you running in 32 bits environment? If you are in a 64 bits environment it is probably better to use a 64 bits Java virtual machine. The problem is that the -XX:+UseCompressedOops is only available in 32 bits Java virtual machines. There is a bug for that and it has already been fixed:
Honestly, I don't know. This suggests that I am: When I try to add clare (the same host the engine is running on) as a host in the management interface, I see the following error: 2012-Sep-24, 17:39:59 Failed to install Host clare. Step: REQ PACKAGES; Details: Loaded plugins: langpacks, presto, refresh-packagekit, versionlock No package rsync.x86_64 available. Error: Nothing to do (rsync.x86_64). My yum repository is all 32 bit - I have installed rsync.i686 with no problems. Is oVirt confused about whether the host is 32 bit or 64 bit? How could that happen?
That has been fixed as well:
Great! Thanks. Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On 09/24/2012 05:43 PM, Dave Neary wrote:
Hi,
On 09/24/2012 05:28 PM, Juan Hernandez wrote:
Are you running in 32 bits environment? If you are in a 64 bits environment it is probably better to use a 64 bits Java virtual machine. The problem is that the -XX:+UseCompressedOops is only available in 32 bits Java virtual machines. There is a bug for that and it has already been fixed:
Honestly, I don't know.
This suggests that I am:
When I try to add clare (the same host the engine is running on) as a host in the management interface, I see the following error:
2012-Sep-24, 17:39:59
Failed to install Host clare. Step: REQ PACKAGES; Details: Loaded plugins: langpacks, presto, refresh-packagekit, versionlock No package rsync.x86_64 available. Error: Nothing to do (rsync.x86_64).
My yum repository is all 32 bit - I have installed rsync.i686 with no problems.
Is oVirt confused about whether the host is 32 bit or 64 bit? How could that happen?
I don't think anyone ever tested with 32bit hosts, and the bootstrap code obviously looks for x86_64 packages (not that i think there is a special reason for that). may i ask why use a 32bit host (almost any virt capable host is 64bit). thanks, Itamar
Hi, On 09/24/2012 05:43 PM, Dave Neary wrote: <snip>
Failed to install Host clare. Step: REQ PACKAGES; Details: Loaded plugins: langpacks, presto, refresh-packagekit, versionlock No package rsync.x86_64 available. Error: Nothing to do (rsync.x86_64).
My yum repository is all 32 bit - I have installed rsync.i686 with no problems.
Is oVirt confused about whether the host is 32 bit or 64 bit? How could that happen?
I should have read http://wiki.ovirt.org/wiki/Quick_Start_Guide#Prerequisites more closely: "For each Host (oVirt Node or Fedora Host) <snip> The breakdown of the server requirements are as below: For each host: AMD-V or Intel VT enabled, AMD64 or Intel 64 extensions, minimum 1 GB RAM, 3 GB free storage and 1 Gbps network interface." So you can't run an oVirt node without a 64 bit processor and virt extensions. I should have read the instructions more closely. Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
participants (5)
-
Dave Neary -
Itamar Heim -
Joop -
Juan Hernandez -
Steve Gordon