PM upgrade 12.4 to 13 now can't access localhost PM

Aspirant

PM upgrade 12.4 to 13 now can't access localhost PM

this is a single purpose server.  Windows 2012. nothing on it has changed other than upgrading it from 12.4 to 13. Now I can't loginto PM locally. I get the "cannot connect to localhost:8080...."  checked the registry to make sure nothing changed. admin port is at 8080. https port is at 443 and httpportnum is 80. suggestion? thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
F-Secure

Re: PM upgrade 12.4 to 13 now can't access localhost PM

According to fsdiag I received via support from customer with similar symptoms, C:\Program Files (x86)\F-Secure\Management Server 5\lib folder contains multiple versions of fspms-webapp-1-SNAPSHOT.jar with different names (probably left after fspm-12.40-windows-hotfix-1 installation).

Please remove old version of the fspms-webapp-1-SNAPSHOT.jar from the lib folder. If you are not sure which of them should be dropped, you can stop Policy Manager Server service, remove the whole directory C:\Program Files (x86)\F-Secure\Management Server 5\lib\ and reinstall Policy Manager.

And for the future, do not keep “old” versions of jars if you are replacing them in the lib folder, because PM loads all jars from the folder 😉

View solution in original post

12 REPLIES 12
Scholar

Re: PM upgrade 12.4 to 13 now can't access localhost PM

I have the same problem. I had to revert back to 12.4 and it works fine.

Superuser

Re: PM upgrade 12.4 to 13 now can't access localhost PM

The first logon to the PM13 can take some time until PM has finished converting the databases.


What does Status Monitor say?

Check from "netstat -an" that port 8080 is listening on localhost.


After the PM Login pops up go to options and choose "Edit"

make sure the URL displayed reads https://localhost (not just http://)

What exactly is the Error-MSG that you get?

 

Try to access the port using a standard browser ("No Proxy")
Try http://localhost:80  :443 and :8080

Matthias
----------
perComp is a Platinum Partner of F-Secure since 1994. Any advice or help given by me in this forum is voluntarily and to my best knowledge based on working with the products since 1997. Direct contact for customers please check our homepage http://www.percomp.de

Aspirant

Re: PM upgrade 12.4 to 13 now can't access localhost PM

dusring conversion everything went fine all green check marks. both windows services are running. trying via URL all three (:80,:8080,:443) gets page cannot be displayed. the error message is "cannot connect to the server: localhost:8080. check that the host name and port are correct. Port number 8080 is used by default." IN the connections box I am trying to connect to https://localhost.  Below is the output of netstat -an it does not look like I have anything listening on 80, 8080.

 

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\morpheus>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49180 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49187 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49193 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2380 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6789 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49217 127.0.0.1:49218 ESTABLISHED
TCP 127.0.0.1:49218 127.0.0.1:49217 ESTABLISHED
TCP 127.0.0.1:49520 127.0.0.1:49521 ESTABLISHED
TCP 127.0.0.1:49521 127.0.0.1:49520 ESTABLISHED
TCP 127.0.0.1:49527 127.0.0.1:49528 ESTABLISHED
TCP 127.0.0.1:49528 127.0.0.1:49527 ESTABLISHED
TCP 127.0.0.1:49534 127.0.0.1:49535 ESTABLISHED
TCP 127.0.0.1:49535 127.0.0.1:49534 ESTABLISHED
TCP 127.0.0.1:49538 127.0.0.1:49539 ESTABLISHED
TCP 127.0.0.1:49539 127.0.0.1:49538 ESTABLISHED
TCP 127.0.0.1:49542 127.0.0.1:49543 ESTABLISHED
TCP 127.0.0.1:49543 127.0.0.1:49542 ESTABLISHED
TCP 127.0.0.1:49945 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49946 127.0.0.1:49947 ESTABLISHED
TCP 127.0.0.1:49947 127.0.0.1:49946 ESTABLISHED
TCP 192.168.1.19:139 0.0.0.0:0 LISTENING
TCP 192.168.1.19:3389 10.21.5.25:58744 ESTABLISHED
TCP 192.168.1.19:49892 5.9.225.163:443 CLOSE_WAIT
TCP 192.168.1.19:49896 5.9.225.163:443 CLOSE_WAIT
TCP 192.168.1.19:49917 5.9.225.163:443 ESTABLISHED
TCP 192.168.1.19:49924 5.9.225.163:443 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:5985 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49180 [::]:0 LISTENING
TCP [::]:49187 [::]:0 LISTENING
TCP [::]:49193 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:161 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3389 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:50917 *:*
UDP 127.0.0.1:52868 *:*
UDP 127.0.0.1:55231 *:*
UDP 127.0.0.1:60168 *:*
UDP 192.168.1.19:137 *:*
UDP 192.168.1.19:138 *:*
UDP [::]:123 *:*
UDP [::]:161 *:*
UDP [::]:500 *:*
UDP [::]:3389 *:*
UDP [::]:4500 *:*

 

 

 

 

F-Secure

Re: PM upgrade 12.4 to 13 now can't access localhost PM

Hello,
Anvarij, PMS service in started state does not guarantee that PMS has loaded successfully. It just starts and stops java, which does all the business logic.
To make sure that PMS is up and running, please check c:\Program Files (x86)\F-Secure\Management Server 5\logs\fspms-stderrout.log, it should have entry "Server:main: Started @36108ms" or similar in the end.
Anvarij, happoman, if Policy Manager Server did not reach the “Started” state in timely fashion, please send me all logs from this folder in private message or even gather full fsdiag. You can forward it via F-Secure support as well, but it might take more time :)
Matthias, Maintenance Tool that is run during setup, upgrades DB schema so now first PMS start after the upgrade should be fast as usual service start.

Superuser

Re: PM upgrade 12.4 to 13 now can't access localhost PM

a look at the logfiles then.

Matthias
----------
perComp is a Platinum Partner of F-Secure since 1994. Any advice or help given by me in this forum is voluntarily and to my best knowledge based on working with the products since 1997. Direct contact for customers please check our homepage http://www.percomp.de

Aspirant

Re: PM upgrade 12.4 to 13 now can't access localhost PM

Thanks for the response. Below is a constant message that is most likely the problem. I would be happy to send you the log files via private message but I am unsure of the process. I did create an fsdiag. it's 160mb. I also created a ticket but as you indicated that can take a little time and thier 100mb limit did not allow me to upload the fsdiag with it so thats going to delay it even more. below is the error in the log that repeats itself.

 

2017-11-01 10:05:47.508:WARNSmiley Surprisedejs.ServletHandler:qtp2034688500-33619: /aus/8/MRQ
java.net.BindException: Address already in use: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:357)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1546)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at com.fsecure.fspms.proxy.TransparentHttpProxy.copyResponseHeaders(TransparentHttpProxy.java:218)
at com.fsecure.fspms.proxy.TransparentHttpProxy.handleRequest(TransparentHttpProxy.java:92)
at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:51)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:964)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:867)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:841)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
at com.fsecure.fspms.jetty.RewriteHandlerWithAsyncSupport.handle(RewriteHandlerWithAsyncSupport.java:30)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at com.fsecure.fspms.jetty.SingleConnectorHandler.handle(SingleConnectorHandler.java:33)
at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:169)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:534)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Thread.java:748)
2017-11-01 10:05:47.508:WARNSmiley Surprisedejs.ServletHandler:qtp2034688500-33627: /aus/8/MRQ
java.net.BindException: Address already in use: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:357)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1546)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at com.fsecure.fspms.proxy.TransparentHttpProxy.copyResponseHeaders(TransparentHttpProxy.java:218)
at com.fsecure.fspms.proxy.TransparentHttpProxy.handleRequest(TransparentHttpProxy.java:92)
at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:51)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:964)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:867)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:841)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
at com.fsecure.fspms.jetty.RewriteHandlerWithAsyncSupport.handle(RewriteHandlerWithAsyncSupport.java:30)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at com.fsecure.fspms.jetty.SingleConnectorHandler.handle(SingleConnectorHandler.java:33)
at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:169)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:534)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Thread.java:748)

F-Secure

Re: PM upgrade 12.4 to 13 now can't access localhost PM

According to fsdiag I received via support from customer with similar symptoms, C:\Program Files (x86)\F-Secure\Management Server 5\lib folder contains multiple versions of fspms-webapp-1-SNAPSHOT.jar with different names (probably left after fspm-12.40-windows-hotfix-1 installation).

Please remove old version of the fspms-webapp-1-SNAPSHOT.jar from the lib folder. If you are not sure which of them should be dropped, you can stop Policy Manager Server service, remove the whole directory C:\Program Files (x86)\F-Secure\Management Server 5\lib\ and reinstall Policy Manager.

And for the future, do not keep “old” versions of jars if you are replacing them in the lib folder, because PM loads all jars from the folder 😉

View solution in original post

Aspirant

Re: PM upgrade 12.4 to 13 now can't access localhost PM

That did the trick.  thanks so much.

Regular Member

Re: PM upgrade 12.4 to 13 now can't access localhost PM

hello, i've this problem to. FSPMS 12.40, windows server 2012r2. after upgrade to fspms13 "cannot connect to localhost" at any ports
:-((