6 Replies Latest reply on Sep 21, 2016 7:03 AM by Bill Robinson

Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Rohit Nayyar Dec 22, 2011 5:42 AM

Share This:

Hi,

I am facing this issue where in I am unable to connec to the Linux x64 appserver which is 8.1.03.312, from a solaris nsh client which is at 8.1.02.233.

When we try to do a blcred to connect to the appserver from the soalris box :-

blcred -p NSH/br/authenticationProfiles.xml cred -acquire -profile SRP

we get this error:

username: BLAdmin

password:

Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

The appserver.log has the following :

22 Dec 2011 11:26:43,370] [Authentication-Service-Thread-1] [WARN] [::CLIENT_IP_ADRESS] [Appserver] Received unexpected data from /CLIENT_IP_ADDRESS:57456. Connection will be aborted.

[22 Dec 2011 11:26:43,370] [Authentication-Service-Thread-1] [INFO] [::CLIENT_IP_ADDRESS] [Appserver] Authentication Connection closed

If i raise the logging in Appserver to Debug, i get the following exception:

com.bladelogic.om.infra.auth.service.ProtocolCompatibilityException: Received unexpected data from /10.81.43.109:56891. Connection will be aborted.

at com.bladelogic.om.infra.auth.service.AuthSvcConnection.receiveAuthMessage(AuthSvcConnection.java:294)

at com.bladelogic.om.infra.auth.service.AuthSvcConnection.handleAuthRequest(AuthSvcConnection.java:111)

at com.bladelogic.om.infra.auth.service.AuthSvcWorkerThread.execute(AuthSvcWorkerThread.java:63)

at com.bladelogic.om.infra.auth.service.AuthSvcWorkerThread.execute(AuthSvcWorkerThread.java:17)

at com.bladelogic.om.infra.app.service.thread.BlBlockingThread.run(BlBlockingThread.java:95)

Caused by: java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:129)

at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)

at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)

at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)

at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)

at java.io.BufferedInputStream.read(BufferedInputStream.java:317)

at com.bladelogic.sso.engine.StreamMessaging.receiveMessage(StreamMessaging.java:163)

at com.bladelogic.sso.engine.StreamMessaging.receiveToken(StreamMessaging.java:201)

at com.blad

Also,

here is the blasadmin config :

SocketConnectTimeout:60

SocketOperationTimeout:7200

SocketTimeout:60000 - This was default to 600, I tried increasing this to 60000 , but didnt help.

Any thing else ? Anyone seen this ? Usually, I have seen this with incompatible versions, but this is not the case here .

Can i blame the network ? Firewall ?

I can see that the connection is established with appserver via 9840, this is netstat -a | grep 9840 on the client

sol110.57456 appserver.9840 9088 0 49640 0 ESTABLISHED

ANy ideas ?

Thanks,

Rohit

1. Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Jim Wilson Dec 22, 2011 6:10 AM (in response to Rohit Nayyar)

https://docs.bmc.com/docs/display/BBSASPwiki/Known+issues+and+workarounds

"Please be aware, if you try to connect version 8.1.SP2 (or lower) of the console to a version 8.1 SP3 Application Server, you will receive the following message:
A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.
This issue is corrected by upgrading the BMC BladeLogic Server Automation Console to version 8.1 SP3."

NOTE: To use the BLCLI or the blcred utility, you must install the BMC BladeLogic console on the NSH client.

HTH
Jim
Like Show 0 Likes(0)

Actions
2. Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Rohit Nayyar Dec 22, 2011 6:13 AM (in response to Jim Wilson)

Thanks a lot.
I was doubting this to be a version compatiblity issue but haven't seen this before for a difference in SP levels .
Thanks a lot, it saved my time and also time of the BMC Support , if I was going to raise a support call.

Thanks,
Rohit
Like Show 0 Likes(0)

Actions
3. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Bill Robinson Dec 23, 2011 12:32 PM (in response to Rohit Nayyar)

There was a protocol change between 8.1 SP2 and 8.1 SP3 as the TB notes. We typically don’t do this, but there was a particular bug that needed this change to be resolved.
Like Show 0 Likes(0)

Actions
4. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Roger May Aug 15, 2012 6:31 AM (in response to Rohit Nayyar)

All,

Need some help here......
I'm facing a very simialr issue, but I believe I already have matching compnents in this case - From Windows 7 machine, connecting to an Appserver running 8.1.02, using Console version 8.1.02 and getting the error :-
A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.
In the Appserver logs, the error :-Received unexpected data from /146.105.143.123:44760. Connection will be aborted.

Also, a colleague is running the exact same version of the console and is connecting ok.

I have removed/reinstalled the console and cleared out as many references to bladelogic from registry, romaingdata etc that I can find

Any ideas?

Thanks

Roger
Like Show 0 Likes(0)

Actions
5. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Shubhi Johri Sep 21, 2016 4:40 AM (in response to Rohit Nayyar)

Hi All,

I am also facing same issue with version 8.2 SP4
Like Show 0 Likes(0)

Actions
6. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Bill Robinson Sep 21, 2016 7:03 AM (in response to Shubhi Johri)

appserver logs ? console version ? stack trace ?
Like Show 0 Likes(0)

Actions

Go to original post

Communities

Communities

Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

1. Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

2. Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

3. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

4. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

5. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

6. Re: Authentication failure: A network error has occurred. The authentication service may have closed the connection due to a long period of inactivity.

Actions

More Like This

Incoming Links