Unable to login to DLP console - java.net.ConnectException: Connection refused: connect
search cancel

Unable to login to DLP console - java.net.ConnectException: Connection refused: connect

book

Article ID: 159821

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

Unable to login to DLP console. The Tomcat log files contain the following error which occurs every time the Enforce services are restarted:

24 Mar 2010 18:26:17,255- Catalina.stop:
java.net.ConnectException: Connection refused: connect
                at java.net.PlainSocketImpl.socketConnect(Native Method)
                at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
                at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
                at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
                at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                at java.net.Socket.connect(Socket.java:520)
                at java.net.Socket.connect(Socket.java:470)
                at java.net.Socket.<init>(Socket.java:367)
                at java.net.Socket.<init>(Socket.java:180)
                at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:394)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:585)
                at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:343)
                at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:434)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:585)
                at org.tanukisoftware.wrapper.WrapperStartStopApp.stop(WrapperStartStopApp.java:420)
                at org.tanukisoftware.wrapper.WrapperManager$13.run(WrapperManager.java:3134)
24 Mar 2010 18:26:26,504- Initializing Coyote HTTP/1.1 on http-443
24 Mar 2010 18:26:26,504- Initialization processed in 734 ms
24 Mar 2010 18:26:26,520- Starting service Catalina
24 Mar 2010 18:26:26,535- Starting Servlet Engine: Apache Tomcat/5.5
24 Mar 2010 18:26:26,535- XML validation disabled

Environment

DLP 15.x, 16.x

Resolution

The Enforce server initialization is delayed due to a tomcat error. Check the following:

- Recycle the Oracle services, then recycle the Enforce services and attempt to login to the console again.
- Check if there is an IIS server running on the Enforce server, if so, stop it.
- Check if there are any lock files (*.lck) under DLP directories. If so, delete them and recycle the Enforce services.
- Try stopping all non-essential services on the the Enforce Windows server and restart the Symantec DLP Manager service.
- Look at the system event logs and see if there are system errors that are causing tomcat to behave badly.
- Check whether there are recent Java updates on the Enforce box.
- Make sure AV exclusions are in place.