oVirt appliance does not work - httpd seems broken


#1

After spinning up the oVirt appliance for ManageIQ it seems broken from the start. It says to browse to the hostname/IP however, it seems httpd is not working.

`
Start ManageIQ? (Y/N): Y

Starting ManageIQ Server…
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/awesome_spawn-1.3.0/lib/awesome_spawn.rb:102:in run!': /bin/systemctl exit code: 1 (AwesomeSpawn::CommandResultError) from /opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/linux_admin-0.12.1/lib/linux_admin/common.rb:24:inrun!'
from /opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/linux_admin-0.12.1/lib/linux_admin/service/systemd_service.rb:21:in start' from /var/www/miq/vmdb/gems/pending/appliance_console.rb:348:inblock in module:ApplianceConsole
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:114:in loop' from /var/www/miq/vmdb/gems/pending/appliance_console.rb:114:inmodule:ApplianceConsole
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:98:in <main>'

`systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2016-06-02 11:08:52 EDT; 9s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 12238 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 12237 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 12237 (code=exited, status=1/FAILURE)

Jun 02 11:08:52 manageiq.veerotech.local systemd[1]: Starting The Apache HTTP Server…
Jun 02 11:08:52 manageiq.veerotech.local httpd[12237]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 11 of /etc/httpd/conf.d/cfme-https-applicat…or directory
Jun 02 11:08:52 manageiq.veerotech.local systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jun 02 11:08:52 manageiq.veerotech.local kill[12238]: kill: cannot find process ""
Jun 02 11:08:52 manageiq.veerotech.local systemd[1]: httpd.service: control process exited, code=exited status=1
Jun 02 11:08:52 manageiq.veerotech.local systemd[1]: Failed to start The Apache HTTP Server.
Jun 02 11:08:52 manageiq.veerotech.local systemd[1]: Unit httpd.service entered failed state.
Jun 02 11:08:52 manageiq.veerotech.local systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
`


#2

Hi @BillBill, which build was it that you used?


#3

Hello - it was the one on the manageiq site via oVirt. Capablanca-2


#4

Thanks @BillBill I will download and test myself.


#5

Thanks for the replay back - I had actually redeployed a new VM using the appliance and it seems to have worked now. I am wondering though, if it had something to do with the Hostname not being set correctly from the beginning, as that’s really the only difference.


#6

@iheim This sounds like maybe the ovirt team should look at it? Not sure who…can you help?