Re: Issue with Accessing oVirt Manager Console
Hi Alex, After conducting a thorough check, we have confirmed that all virtual machines are operating smoothly, and the network is functioning without any issues (we can successfully SSH into both the VMs and the manager). Additionally, there is available storage on both the node and the manager. However, we are encountering difficulty accessing the oVirt manager console, as we are consistently receiving a "503 Service Unavailable" error. Thanks, Sachendra On Fri, Mar 29, 2024 at 2:11 PM Alex K <rightkicktech@gmail.com> wrote:
On Fri, Mar 29, 2024 at 8:26 AM Sachendra Shukla < sachendra.shukla@yagnaiq.com> wrote:
Hi Team,
We are currently experiencing difficulties accessing the oVirt Manager console. Please find attached a screenshot of the error for your reference.
[image: image.png]
You need to check what is causing it. There could be many causes. I would start to check the engine VM status, storage, network, logs, etc.
Please help me if you have any resolution. --
Regards,
*Sachendra Shukla*
IT Administrator
Yagna iQ, Inc. and subsidiaries
Email: Sachendra.shukla@yagnaiq.com <dnyanesh.tisge@yagnaiq.com>
Website: https://yagnaiq.com
Privacy Policy: https://www.yagnaiq.com/privacy-policy/
<https://www.linkedin.com/company/yagnaiq/mycompany/> <https://www.youtube.com/channel/UCeHXOpcUxWvOJO0aegD99Jg>
This communication and any attachments may contain confidential information and/or Yagna iQ, Inc. copyright material.
All unauthorized use, disclosure, or distribution is prohibited. If you are not the intended recipient, please notify Yagna iQ immediately by replying to the email and destroy all copies of this communication.
This email has been scanned for all known viruses. The sender does not accept liability for any damage inflicted by viewing the content of this email.
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2W3MRMOOSPB5X2...
-- Regards, *Sachendra Shukla* IT Administrator Yagna iQ, Inc. and subsidiaries Email: Sachendra.shukla@yagnaiq.com <dnyanesh.tisge@yagnaiq.com> Website: https://yagnaiq.com Privacy Policy: https://www.yagnaiq.com/privacy-policy/ <https://www.linkedin.com/company/yagnaiq/mycompany/> <https://www.youtube.com/channel/UCeHXOpcUxWvOJO0aegD99Jg> This communication and any attachments may contain confidential information and/or Yagna iQ, Inc. copyright material. All unauthorized use, disclosure, or distribution is prohibited. If you are not the intended recipient, please notify Yagna iQ immediately by replying to the email and destroy all copies of this communication. This email has been scanned for all known viruses. The sender does not accept liability for any damage inflicted by viewing the content of this email.
On the engine host . check contents of /var/log/ovirt-engine/engine.log . check the output of the commands: systemctl status ovirt-engine systemctl status httpd . check contents of JBoss instance related logs /var/log/ovirt-engine/server.log In 4.5.x you should see something like this (see the deployed engine.ear and ovirt-web-ui.war lines for example): 2024-03-26 17:26:29,515+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) WFLYUT0021: Registered web context: '/ovirt-engine/docs' for server 'default-server' 2024-03-26 17:26:29,530+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 46) WFLYUT0021: Registered web context: '/' for server 'default-server' 2024-03-26 17:26:29,575+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 46) WFLYUT0021: Registered web context: '/ovirt-engine/services' for server 'default-server' 2024-03-26 17:26:29,588+01 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 46) IJ000407: No lazy enlistment available for ENGINEDataSource 2024-03-26 17:26:29,633+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) WFLYUT0021: Registered web context: '/ovirt-engine' for server 'default-server' 2024-03-26 17:26:29,648+01 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 46) IJ000407: No lazy enlistment available for DWHDataSource 2024-03-26 17:26:29,666+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 46) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' 2024-03-26 17:26:29,843+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2024-03-26 17:26:30,097+01 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50) WFLYCLINF0002: Started timeout-base cache from ovirt-engine container 2024-03-26 17:26:31,880+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2024-03-26 17:26:31,880+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2024-03-26 17:26:31,880+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2024-03-26 17:26:31,880+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2024-03-26 17:26:31,930+01 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2024-03-26 17:26:31,933+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started in 16651ms - Started 1676 of 1890 services (393 services are lazy, passive or on-demand) 2024-03-26 17:26:31,940+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2024-03-26 17:26:31,940+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 2024-03-26 17:41:31,872+01 INFO [org.apache.sshd.common.util.security.eddsa.EdDSASecurityProviderRegistrar] (EE-ManagedExecutorService-hostUpdatesChecker-Thread-1) getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProvider eventually if in error try to restart ovirt-engine service systemctl restart ovirt-engine HIH, Gianluca On Fri, Mar 29, 2024 at 9:59 AM Sachendra Shukla < sachendra.shukla@yagnaiq.com> wrote:
Hi Alex,
After conducting a thorough check, we have confirmed that all virtual machines are operating smoothly, and the network is functioning without any issues (we can successfully SSH into both the VMs and the manager). Additionally, there is available storage on both the node and the manager. However, we are encountering difficulty accessing the oVirt manager console, as we are consistently receiving a "503 Service Unavailable" error.
Thanks, Sachendra
participants (2)
-
Gianluca Cecchi -
Sachendra Shukla