Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Commodore
Commodore
845 views

Server is not reporting

Hi,

I am using NAM 4.4 Appliance . it was working fine till yesterday but today Access gateway and identity server is showing Health Server is not reporting. I have restarting it but didn't work . Also i have pasted logs for Access gateway.

Please guys help me out.

Access gateway

Mar 05, 2019 5:26:11 PM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter OAuthApplicationJspMvcFilter
MultiException stack 1 of 3
java.lang.NullPointerException
at com.novell.nam.nidp.oauth.nidp.NIDPClientConfig.init(NIDPClientConfig.java:41)
at com.novell.nam.nidp.oauth.nidp.NIDPClientConfig.<init>(NIDPClientConfig.java:37)
at com.novell.nam.nidp.oauth.nidp.wrapper.NIDPConfigServiceWrapper.<init>(NIDPConfigServiceWrapper.java:36)


MultiException stack 2 of 3
java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.novell.nam.nidp.oauth.core.filters.OAuth2
ProxyFilter errors were found
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:249)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:360)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:114)
0 Likes
6 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

On 05-03-2019 6:34 PM, frankabhinav wrote:
>
> Hi,
>
> I am using NAM 4.4 Appliance . it was working fine till yesterday but
> today Access gateway and identity server is showing Health *Server is
> not reporting*. I have restarting it but didn't work . Also i have
> pasted logs for Access gateway.
>
> Please guys help me out.
>
> *Access gateway*
>
>
> Code:
> --------------------
> Mar 05, 2019 5:26:11 PM org.apache.catalina.core.StandardContext filterStart
> SEVERE: Exception starting filter OAuthApplicationJspMvcFilter
> MultiException stack 1 of 3
> java.lang.NullPointerException
> at com.novell.nam.nidp.oauth.nidp.NIDPClientConfig.init(NIDPClientConfig.java:41)
> at com.novell.nam.nidp.oauth.nidp.NIDPClientConfig.<init>(NIDPClientConfig.java:37)
> at com.novell.nam.nidp.oauth.nidp.wrapper.NIDPConfigServiceWrapper.<init>(NIDPConfigServiceWrapper.java:36)
>
> --------------------
>
>
>
> Code:
> --------------------
> MultiException stack 2 of 3
> java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.novell.nam.nidp.oauth.core.filters.OAuth2
> ProxyFilter errors were found
> at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:249)
> at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:360)
> at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
> at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:114)
>
> --------------------
>
>


Is that all you see in the catalina.out?

--
Cheers,
Edward
0 Likes
Commodore
Commodore

Yes ,

They were no error were inside idp log. I did some search and found error in the following file

/opt/volera/roma/logs/app_sc.0.log


Device Name : idp-C6E57CF03F1F9214
757(D)2019-03-05T18:55:00Z(L)application.sc.bgProcess(T)20(C)com.volera.vcdn.application.sc.alert.AlertCleanupWork(M)execute(Msg)
Device Name : ag-B7204FFDD1E044FA
758(D)2019-03-05T18:55:00Z(L)application.sc.bgProcess(T)20(E)java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:851)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:848)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at com.volera.vcdn.application.sc.alert.AlertCleanupWork.deleteAlerts(AlertCleanupWork.java:104)
at com.volera.vcdn.application.sc.alert.AlertCleanupWork.cleanup(AlertCleanupWork.java:142)
at com.volera.vcdn.application.sc.alert.AlertCleanupWork.execute(AlertCleanupWork.java:42)
at com.volera.vcdn.platform.executor.DefaultExecutor$ExecutionThread.run(DefaultExecutor.java:541)
(Msg)THROW


2337(D)2019-03-05T18:28:44Z(L)application.sc.command(T)21(C)com.volera.vcdn.application.sc.command.work.IDPCommandWork(M)sendComm
and(E)Error in sending request to Device.<!-- VConnection.java:951 java.net.ConnectException: Connection refused (Connection refu
sed) -->
at com.volera.vcdn.platform.communication.VConnection.sendData(VConnection.java:951)
at com.volera.vcdn.platform.communication.VConnection.sendInternal(VConnection.java:375)
at com.volera.vcdn.platform.communication.VConnection.send(VConnection.java:334)
at com.volera.vcdn.application.sc.command.work.IDPCommandWork.sendCommand(IDPCommandWork.java:149)
at com.volera.vcdn.application.sc.command.work.IDPCommandWork.execute(IDPCommandWork.java:95)
at com.volera.vcdn.platform.executor.DefaultExecutor$ExecutionThread.run(DefaultExecutor.java:541)
Caused by: 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 com.volera.vcdn.platform.communication.VConnection.sendData(VConnection.java:845)
... 5 more
(Msg)<amLogEntry> 2019-03-05T23:58:44Z SEVERE DeviceManager: AM#100902059: Error - VCDNException thrown in the sendCommand method
of com.volera.vcdn.application.sc.command.work.IDPCommandWork </amLogEntry>

2338(D)2019-03-05T18:28:44Z(L)application.sc.command(T)21(C)com.volera.vcdn.application.sc.command.work.IDPCommandWork(M)execute(
E)Error sending the commands to the device.<!-- IDPCommandWork.java:163 Error in sending request to Device.<!-- VConnection.java:
951 java.net.ConnectException: Connection refused (Connection refused) --> -->
at com.volera.vcdn.application.sc.command.work.IDPCommandWork.sendCommand(IDPCommandWork.java:163)
at com.volera.vcdn.application.sc.command.work.IDPCommandWork.execute(IDPCommandWork.java:95)
at com.volera.vcdn.platform.executor.DefaultExecutor$ExecutionThread.run(DefaultExecutor.java:541)
Caused by: Error in sending request to Device.<!-- VConnection.java:951 java.net.ConnectException: Connection refused (Connection
refused) -->
at com.volera.vcdn.platform.communication.VConnection.sendData(VConnection.java:951)
at com.volera.vcdn.platform.communication.VConnection.sendInternal(VConnection.java:375)
at com.volera.vcdn.platform.communication.VConnection.send(VConnection.java:334)
at com.volera.vcdn.application.sc.command.work.IDPCommandWork.sendCommand(IDPCommandWork.java:149)
... 2 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
0 Likes
Commodore
Commodore

Any Update guys??
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 06-03-2019 12:34 AM, frankabhinav wrote:
>
> Yes ,
>
> They were no error were inside idp log. I did some search and found
> error in the following file
>
> */opt/volera/roma/logs/app_sc.0.log*
>>
>>
>> Device Name : idp-C6E57CF03F1F9214
>> 757(D)2019-03-05T18:55:00Z(L)application.sc.bgProcess(T)20(C)com.volera.vcdn.application.sc.alert.AlertCleanupWork(M)execute(Msg)
>> Device Name : ag-B7204FFDD1E044FA
>> 758(D)2019-03-05T18:55:00Z(L)application.sc.bgProcess(T)20(E)java.net.SocketException:
>> Unexpected end of file from server
>> at
>> sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:851)
>> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)
>> at
>> sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:848)
>> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569)
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
>> at
>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
>> at
>> com.volera.vcdn.application.sc.alert.AlertCleanupWork.deleteAlerts(AlertCleanupWork.java:104)
>> at
>> com.volera.vcdn.application.sc.alert.AlertCleanupWork.cleanup(AlertCleanupWork.java:142)
>> at
>> com.volera.vcdn.application.sc.alert.AlertCleanupWork.execute(AlertCleanupWork.java:42)
>> at
>> com.volera.vcdn.platform.executor.DefaultExecutor$ExecutionThread.run(DefaultExecutor.java:541)
>> (Msg)THROW
>>

>
>> 2337(D)2019-03-05T18:28:44Z(L)application.sc.command(T)21(C)com.volera.vcdn.application.sc.command.work.IDPCommandWork(M)sendComm
>> and(E)Error in sending request to Device.<!-- VConnection.java:951
>> java.net.ConnectException: Connection refused (Connection refu
>> sed) -->
>> at
>> com.volera.vcdn.platform.communication.VConnection.sendData(VConnection.java:951)
>> at
>> com.volera.vcdn.platform.communication.VConnection.sendInternal(VConnection.java:375)
>> at
>> com.volera.vcdn.platform.communication.VConnection.send(VConnection.java:334)
>> at
>> com.volera.vcdn.application.sc.command.work.IDPCommandWork.sendCommand(IDPCommandWork.java:149)
>> at
>> com.volera.vcdn.application.sc.command.work.IDPCommandWork.execute(IDPCommandWork.java:95)
>> at
>> com.volera.vcdn.platform.executor.DefaultExecutor$ExecutionThread.run(DefaultExecutor.java:541)
>> Caused by: 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
>> com.volera.vcdn.platform.communication.VConnection.sendData(VConnection.java:845)
>> ... 5 more
>> (Msg)<amLogEntry> 2019-03-05T23:58:44Z SEVERE DeviceManager:
>> AM#100902059: Error - VCDNException thrown in the sendCommand method
>> of com.volera.vcdn.application.sc.command.work.IDPCommandWork
>> </amLogEntry>
>>
>> 2338(D)2019-03-05T18:28:44Z(L)application.sc.command(T)21(C)com.volera.vcdn.application.sc.command.work.IDPCommandWork(M)execute(
>> E)Error sending the commands to the device.<!-- IDPCommandWork.java:163
>> Error in sending request to Device.<!-- VConnection.java:
>> 951 java.net.ConnectException: Connection refused (Connection refused)
>> --> -->
>> at
>> com.volera.vcdn.application.sc.command.work.IDPCommandWork.sendCommand(IDPCommandWork.java:163)
>> at
>> com.volera.vcdn.application.sc.command.work.IDPCommandWork.execute(IDPCommandWork.java:95)
>> at
>> com.volera.vcdn.platform.executor.DefaultExecutor$ExecutionThread.run(DefaultExecutor.java:541)
>> Caused by: Error in sending request to Device.<!-- VConnection.java:951
>> java.net.ConnectException: Connection refused (Connection
>> refused) -->
>> at
>> com.volera.vcdn.platform.communication.VConnection.sendData(VConnection.java:951)
>> at
>> com.volera.vcdn.platform.communication.VConnection.sendInternal(VConnection.java:375)
>> at
>> com.volera.vcdn.platform.communication.VConnection.send(VConnection.java:334)
>> at
>> com.volera.vcdn.application.sc.command.work.IDPCommandWork.sendCommand(IDPCommandWork.java:149)
>> ... 2 more
>> Caused by: java.net.ConnectException: Connection refused (Connection
>> refused)
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at
>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>>

>
>


the app_sc.log shows all the logging for the device manager. Going by this it seems it can't communicate with the JCC service. Can you check if that
is running? rcnovell-jcc status. It would probably also help the logs for that. /opt/novell/devman/jcc/logs/jcc***.log

--
Cheers,
Edward
0 Likes
Absent Member.
Absent Member.

Perhaps if you can post a start up from catalina.out to see if we find more clues there.

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 07-03-2019 2:56 AM, EricVeysey wrote:
>
> Perhaps if you can post a start up from catalina.out to see if we find
> more clues there.
>
>

To be honest, i dont think this is a tomcat issue. I think this is jcc being hosed

--
Cheers,
Edward
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.