I have the same setup on CentOS7.4, with same packages as you mentioned. I suppose your Tomcat is tomcat-7.0.76, right? One more thing - dwr is storing DWRSESSIONID into browser cache, could you try cleaning your browser cache/force reloading the Overview page?

Thank you,
Jiri

Dne 24.4.2018 v 11:14 Ree, Jan-Albert van napsal(a):

Hello,


Our instance is running Scientific Linux 7.4 , PostgreSQL 9.2 local


root@spacewalk ~ # rpm -qa | grep spacewalk-java
spacewalk-java-config-2.8.78-1.el7.centos.noarch
spacewalk-java-lib-2.8.78-1.el7.centos.noarch
spacewalk-java-2.8.78-1.el7.centos.noarch
spacewalk-java-postgresql-2.8.78-1.el7.centos.noarch
root@spacewalk ~ # rpm -qa | grep dwr
dwr-3.0.2-1.el7.centos.noarch

The upgrade was done yesterday afternoon, exactly according to the documentation. With spacewalk 2.7 we used dwr-3.0rc2-8.el7.noarch, I can't find the dwr-3.0rc2-9in the old yum logs anywhere so it was never installed on this system.

I'm only seeing one error in the catalina log, related to the AJP connector :

Apr 24, 2018 11:06:55 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler ["ajp-bio-0:0:0:0:0:0:0:1-8009"]
java.net.SocketException: Protocol family unavailable
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:55)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:403)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:715)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:642)
at org.apache.catalina.startup.Catalina.load(Catalina.java:667)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:253)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)

Apr 24, 2018 11:06:55 AM org.apache.catalina.core.StandardService initInternal
SEVERE: Failed to initialize connector [Connector[AJP/1.3-8009]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[AJP/1.3-8009]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:642)
at org.apache.catalina.startup.Catalina.load(Catalina.java:667)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:253)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed at org.apache.catalina.connector.Connector.initInternal(Connector.java:980)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 12 more
Caused by: java.net.SocketException: Protocol family unavailable
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:55)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:403)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:715)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
... 13 more

Apr 24, 2018 11:06:55 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 900 ms

Other than that the catalina.out log is clear.

Regards,
--
Jan-Albert



Jan-Albertvan Ree| Linux System Administrator| MARIN Support Group
MARIN| T +31 317 49 35 48| [email protected] <mailto:[email protected]> | www.marin.nl <http://www.marin.nl>

LinkedIn <https://www.linkedin.com/company/marin> YouTube <http://www.youtube.com/marinmultimedia> Twitter <https://twitter.com/MARIN_nieuws> Facebook <https://www.facebook.com/marin.wageningen> MARIN news: MARIN at Maritime Industry, May 29-31, Gorinchem <http://www.marin.nl/web/News/News-items/MARIN-at-Maritime-Industry-May-2931-Gorinchem.htm>
------------------------------------------------------------------------
*From:* [email protected] <[email protected]> on behalf of Jiří Dostál <[email protected]>
*Sent:* Tuesday, April 24, 2018 10:56
*To:* [email protected]
*Subject:* Re: [Spacewalk-list] Empty "Overview" page after upgrading from 2.7 to 2.8

Hello,

could you please provide information on which system you have tried? I've just tested the scenario on different systems and didn't bump at the issue - I can see Overview page after upgrade. However, the behavior you described is the same as having spacewalk-java-2.8 and dwr-3.0rc2-9. This combination causes blank main page (BUT traceback in catalina.out as well) but it should not happen as there's a dependency on it. So far it really looks as some sort of caching issue.

Thank you for your info

Jiri


Dne 23.4.2018 v 19:23 Angelo Lisco napsal(a):
Hi all,
after upgrading my Spacewalk server from 2.7 to 2.8 I'm experiencing a weird bug: the "Overview" page that Spacewalk shows after the login is empty. I can see the page header and the left-side menu but It doesn't display all the nice summaries of the Spacewalk infra.

The weird thing is that nothing strange appears on the log files (both catalina.out and rhn_server_xmlrpc.log). No stacktraces, no errors at all.

Maybe I'm wrong but I suppose that something got broken in this commit:
https://github.com/spacewalkproject/spacewalk/commit/ace6add83252e33c776e5803947fff9ef361885a <https://github.com/spacewalkproject/spacewalk/commit/ace6add83252e33c776e5803947fff9ef361885a>

For now, my workaround was to downgrade the drw package from the 3.0.2-1 to the 3.0rc2-9 version. I also needed to downgrade the spacewalk-java package to spacewalk-java-2.8.73-1 since it's a tightly-coupled dependency of dwr.

After the downgrade, I'm able to see the "Overview" page again.
I've also tried to clean the tomcat cache and restart my spacewalk setup but the issue was still present.

Thanks for your help.
Angelo Lisco


_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

--
Jiří Dostál | Associate Software Engineer
Red Hat Satellite


_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

--
Jiří Dostál | Associate Software Engineer
Red Hat Satellite

_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to