CSP CLI closes after login

[David Draper]

Tried to update to CSP 2.7 and when I logged in I was required to change my password.  Now when I log back into the CLI I see this message:

java.net.ConnectException: Connection refused (Connection refused)
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 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.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:589)
 at java.net.Socket.connect(Socket.java:538)
 at java.net.Socket.<init>(Socket.java:434)
 at java.net.Socket.<init>(Socket.java:244)
 at com.cisco.ca.ss.lcm.adminshell.client.ShellClient.main(ShellClient.java:51)
Error occured: could not connect to the database server.
Please make sure mysql database server is up and running.

[christopher.oelke1]

I have the same issue, I literally just upgraded (or attempted to) to 2.7. I used the CLI to do the install and it never gives any output on the status of it. I come back and attempt to log back in and it will quickly show those Java errors.

Funny you posted this only a few hours ago haha.

[antchris]

Hello David,

This generally happens when attempting to login to as the CSPC is still spinning up - although you may be able to ping and have ssh connection, the admin shell is one of the last services to start. 

Best practice is to allow a few moments post restart/reboot before logging into the admin shell - you should not receive the java/db connection error.

Regards

[taywelch · Accepted solution]

Hello David, 

It looks like the admin shell never came back up after the upgrade. Can you reboot the collector and see if admin shell restores?

Thanks, 

Taylor

[David Draper]

I ended up just rebuilding the collector on 2.7.  I tried rebooting the collector multiple times without success.  Thanks for help!

-Dave

[christopher.oelke1]

Dave,

I did the same thing as well, just rebuilt it. I think that something happened going directly from 2.6 to 2.7 and corrupted the build. It works fine now, I just wish I could narrow it down to what exactly caused that hassle.

Thanks!