----- Original Message -----
From: "Hans-Joachim" <rni(a)chef.net>
To: "Yedidyah Bar David" <didi(a)redhat.com>, users(a)ovirt.org
Sent: Friday, November 21, 2014 2:24:02 PM
Subject: Re: [ovirt-users] oVIRT 3.5/CentOS 6.5 Reports are not working anymore
> Sent: Thursday, November 20, 2014 at 1:22 PM
> From: "Yedidyah Bar David" <didi(a)redhat.com>
> To: Hans-Joachim <rni(a)chef.net>
> Subject: Re: [ovirt-users] oVIRT 3.5/CentOS 6.5 Reports are not working
> anymore
>
> ----- Original Message -----
> > From: "Hans-Joachim" <rni(a)chef.net>
> > To: "Yedidyah Bar David" <didi(a)redhat.com>
> > Sent: Thursday, November 20, 2014 1:30:10 PM
> > Subject: Re: [ovirt-users] oVIRT 3.5/CentOS 6.5 Reports are not working
> > anymore
> >
> OK. Please run:
>
> service ovirt-engine restart
> service ovirt-engine-reports restart
> service httpd restart
done
>
> Try to connect to:
>
http://myserver.domain
> And from there, the link "Reports Portal"
will puts me to
http://myserver.domain/ovirt-engine/services/reports-redirect
and afterwards redirect me to
https://myserver.domain/ovirt-engine-reports with a 404 ERROR
>
> Which URL were you redirected to? If it does not work, please post:
>
> /etc/ovirt-engine*
> /etc/httpd
> /var/log/ovirt-engine*
> /var/log/httpd
>
> Please reply to the list, so that others can try to help and also
> find in the future (especially after it's solved :-) )
>
Best
Hans-Joachim
Seems to me that the problem is in /etc/httpd/conf.d/ovirt-engine.conf,
which seems like a left-over from 3.2. This should have been deleted by
the upgrade from 3.2 to 3.3. Couldn't see in your attachments a log of
this upgrade (done probably 1+ years ago). Such a log should have been
in /var/log/ovirt-engine/setup. If you can't find such a log, and/or if
you suspect other problems you encountered due to problems in this
upgrade, I suggest that you install another engine (e.g. in a temp VM)
with configuration as similar as possible to your existing one, and compare
all relevant files (/etc/httpd, /etc/ovirt-engine*) between them and try
to understand what needs fixing.
This specific file can (and should) safely be deleted.
Best,
--
Didi