Reset Search
 

 

Article

Cannot access XMC with "Error 404" after upgrade to 8.4.2

« Go Back

Information

 
TitleCannot access XMC with "Error 404" after upgrade to 8.4.2
Symptoms
  • XMC displays "Error 404" after upgrade
  • Following exception is seen during startup in the server.log
2020-04-17 15:26:39,664 ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Address already in use /10.0.0.65:80
at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:151)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
  • Apache2 is seen to be bound to port 80 running a netstat -anp command within the SSH shell
    tcp6 0 0 :::80 :::* LISTEN
    2381/apache2
Environment
XMC 8.4.2
Cause
apache2 package has been installed and is binding to port 80 before XMC can start up
Resolution
Disable apache2 and reboot the server:
systemctl stop apache2
systemctl disable apache2
Additional notes
Once the issue is resolved the server would become functional, however it's highly recommended to redeploy and transfer the data to the new server as the installed packages do not match what has been tested in our QA. Future operation/upgrades may encounter further issues. 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255