On Mon, Mar 14, 2022 at 11:23 PM <louisb(a)ameritech.net> wrote:
I'm seeking help with my issue related to display the ovirt UI Web Admin Screen on my
server. I'm very puzzled by this because I can display the UI on a remote machine
with no issue. I install ovirt on my server remotely connected to the server via ssh, I
had no issues performing the install. As I said earlier I'm able to bring up the
Admin UI remotely on the same machine that was connected remotely.
What really puzzle me is that, I'm able to bring up the UI remotely but not on the
server console. They both are using the same release RHEL 8 and Firefox. When I try to
bring up the UI on the server console I get the following message:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is
temporarily unavailable.
I confirmed that all of the installed files are stored on the server, where should I
start looking?
My Server has four/4 network adapters installed with different IP addresses assigned. My
DNS has the domain entered for each network adapter all pointing to the same server. My
DNS entry for ovirt is "AAAABBBB.1234.net" specified four/4 time with a
different IP address for each network adapter.
Does the install of ovirt latch to a specific network adapter and IP Address?
httpd is configured (keeping its default) to listen on 0.0.0.0 (all
addresses) (and this is why it does manage to give you a 404 answer).
It still might be related to your specific networking configuration, though.
As a start (and IMO also always) I'd give each IP address its own
different name, and use the name provided to engine-setup for the
question about the machine's FQDN for the address you want to use the
web interface for. When connecting from a different machine, your
stack probably automatically connects to the correct address (perhaps
due to routing/firewalling/whatever?). When running locally, all can
work.
That said, I can't tell why it does not work - I think it should have,
as-is. Might be something else? E.g. we are quite picky about name
resolution, both forward and backward. Perhaps some of your PTR
records are wrong?
Did you change anything on the machine other than configuring
networking and running engine-setup? Perhaps changed apache httpd's
configuration?
Could this be a permission issue on the server? I'm using the same account and UID
on both server and workstation.
Unlikely.
What ever it might how do I start the debugging process to create a solution?
You can start by checking logs - both /var/log/httpd/* and
/var/log/ovirt-engine/* .
I'm very new to ovirt and Linux so I'm trying to learn.
Good luck!
May I note, that most experienced Linux/Unix sysadmins do not install
browsers on their servers, do not have GUIs there, etc., and so your
case is rather unique. If it's only for "ease of use", perhaps you
should give up and connect only from a remote browser. Running a
GUI/browser on a server is generally not recommended - it's a ton of
software that's often less security-scanned/audited, you risk
connecting to rogue websites, etc. If it's for a technical reason -
because you need some functionality and that's the only way - feel
free to ignore.
Best regards,
--
Didi