Without knowing the X, it's hard to know what's going on for sure. But to me, it looks like you missed one of the manual steps to be applied to upgrade from 2020.X to 2021.05. Have a look at the release notes and make sure you follow all the instructions between your 2020.X and 2021.05. My main suspect is one of the libraries that now must come from Leap. Without that changed applied to the server, the WebUI is know to show 404. However if 2020.X is too old, it could be it was based on Leap 15.1, and needs to run the script to migrate to Leap 15.2. But should not be the case if 2020.X is from the end of last year. On miércoles, 2 de junio de 2021 19:58:20 (CEST) Haupt, Torsten wrote:
Hi,
I didn't made every uyuni update the last months, but now I did it and it failed. I think my installed version was from end oft he last year. I followed the instructions on the website and all patches and updates were installed. The schema update with the first service start last several hours, but it fineshed. But the Uyuni site is not available; only the tomcat error "HTTP Status 404 - nicht gefunden Type Status Report Beschreibung The origin server did not find a current representation for the target resource or is not willing to disclose that one exists." appears. I restarted the services and the whole server without success.
Every time I do a "spacewalk-service start" the message "Starting spacewalk services... Running DB schema upgrade. This may take a while. Call the following command to see progress: journalctl -f -u uyuni-check-database.service Done." appears.
journalctl -f -u uyuni-check-database.service -- Logs begin at Thu 2019-02-07 15:13:46 CET. -- Jun 02 11:56:41 smduyuni systemd[1]: Stopped Uyuni check database. Jun 02 11:56:44 smduyuni systemd[1]: Starting Uyuni check database... Jun 02 11:56:44 smduyuni spacewalk-startup-helper[22859]: Your database schema already matches the schema package version [susemanager-schema-4.2.14-1.1.uyuni]. Jun 02 11:56:44 smduyuni spacewalk-startup-helper[22859]: Schema upgrade: [susemanager-schema-4.2.14-1.1.uyuni] -> [susemanager-schema-4.2.14-1.1.uyuni] Jun 02 11:56:44 smduyuni systemd[1]: Started Uyuni check database. Jun 02 19:42:08 smduyuni systemd[1]: Stopped Uyuni check database. Jun 02 19:42:11 smduyuni systemd[1]: Starting Uyuni check database... Jun 02 19:42:11 smduyuni spacewalk-startup-helper[24088]: Your database schema already matches the schema package version [susemanager-schema-4.2.14-1.1.uyuni]. Jun 02 19:42:11 smduyuni spacewalk-startup-helper[24088]: Schema upgrade: [susemanager-schema-4.2.14-1.1.uyuni] -> [susemanager-schema-4.2.14-1.1.uyuni] Jun 02 19:42:12 smduyuni systemd[1]: Started Uyuni check database.
It is always the same schema upgrade.
less /var/log/tomcat/catalina.2021-06-02.log 02-Jun-2021 19:42:14.398 SEVERE [main] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory [/srv/tomcat/webapps/rhn] java.lang.IllegalStateException: Error starting child at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java: 720) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1132 ) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java: 1865) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.jav a:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutor Service.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecu torService.java:118) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:10 44) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1575) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.jav a:123) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java: 423) at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936 ) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1 384) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1 374) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutor Service.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecu torService.java:140) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909 ) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:2 62) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardService.startInternal(StandardService.java :421) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:9 30) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Catalina.start(Catalina.java:633) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethod AccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Delegati ngMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rhn]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBas e.java:440) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java: 717) ... 37 more Caused by: java.lang.NullPointerException at org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.j ava:382) at org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java :195) at org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(Contex tConfig.java:1971) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1129 ) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java :775) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java :301) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.jav a:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java :5044) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 38 more 02-Jun-2021 19:42:14.400 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/srv/tomcat/webapps/rhn] has finished in [982] ms 02-Jun-2021 19:42:14.421 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-8080"] 02-Jun-2021 19:42:14.601 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-127.0.0.1-8009"] 02-Jun-2021 19:42:14.749 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 02-Jun-2021 19:42:14.881 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [1,660] milliseconds
Further logs and infos I would provide.
Greets Torsten
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com