daHostname:8581/typecatalog/certifications/snmp is inaccessible
search cancel

daHostname:8581/typecatalog/certifications/snmp is inaccessible

book

Article ID: 193963

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

We are receiving a 404 error when trying to access http://daHostname:8581/typecatalog

Environment

All supported releases

Cause

Potential Cause: Data Aggregator cache corruption due to excessive security scans

1. Check to make sure that the following directories exist and contain files.  If something has gone awry with them it is likely that an entire directory is missing:

$InstallDIR/IMDataAggregator/data/certifications/CA_$currentVersion/components
$InstallDIR/IMDataAggregator/data/certifications/CA_$currentVersion/device_manager
$InstallDIR/IMDataAggregator/data/certifications/CA_$currentVersion/metric_families
$InstallDIR/IMDataAggregator/data/certifications/CA_$currentVersion/vendor_certs

2. Check to see how typecatalog is being advertised in a browser window:

http://daHostname:8581

This is correct:

Endpoint address: http://daHostname:8581/typecatalog
WADL : http://daHostname:8581/typecatalog?_wadl

This is incorrect:

Endpoint address: http://daHostname:8581/odata/typecatalog
WADL : http://daHostname:8581/odata/typecatalog?_wadl

Resolution

1. Stop the Data Aggregator:

systemctl stop dadaemon activemq

2. Rename the /opt/IMDataAggregator/apache*/data directory to reset the cache

mv /opt/IMDataAggregator/apache*/data /opt/IMDataAggregator/apache*/data.old

3. Start the Data Aggregator

systemctl start dadaemon

4. After the Data Aggregator is back online and synchronized with Performance Center, check to ensure you can access the following URL in a web browser:

http://daHostname:8581/typecatalog/certifications/snmp/IfXTableMib

Additional Information

The Performance Management environment should be "whitelisted" from security scans due to the negative and overwhelming effect they can have on the environment. 

 

Error messages indicating a Security Scan can be seen in the /opt/IMDataAggregator/apache*/data/log/karaf.log and may look something like:

WARN  | p353115687-59585 | 2020-01-14 18:53:52,627 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname:8581/mgmt/login's Observer 
WARN  | p353115687-59751 | 2020-01-14 18:53:52,635 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname:8581/dms2/Login.jsp's Observer 
WARN  | p353115687-59585 | 2020-01-14 18:53:52,644 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname:8581/login's Observer 
WARN  | p353115687-59585 | 2020-01-14 18:53:52,664 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname:8581/sws/data/sws_data.js's Observer 
WARN  | p353115687-59751 | 2020-01-14 18:53:52,673 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname:8581/wcd/system.xml's Observer 
WARN  | p353115687-59585 | 2020-01-14 18:53:52,681 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname:8581/js/Device.js's Observer 
WARN  | p353115687-59532 | 2020-01-14 18:53:52,800 | ServletController | nsport.servlet.ServletController  175 | f.cxf-rt-transports-http |       | Can't find the the request for http://daHostname8581/properties/configuration.php's Observer

or

WARN  | p353115687-59532 | 2020-01-14 18:54:50,074 | AbstractHttpConnection | ty.server.AbstractHttpConnection  552 | gregate.jetty-all-server |       | %.
java.lang.IllegalArgumentException: Bad % encoding: %.
    at org.eclipse.jetty.http.HttpURI.getDecodedPath(HttpURI.java:634)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:471)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)[58:org.eclipse.jetty.aggregate.jetty-all-server:8.1.17.v20150415]
    at java.lang.Thread.run(Thread.java:748)[:1.8.0_222]

or

WARN  | RMI TCP Accept-0 | 2020-06-14 18:29:50,327 | tcp | sun.rmi.runtime.Log$LoggerLog  237 |  |       | RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=43391] throws
java.io.IOException: The server sockets created using the LocalRMIServerSocketFactory only accept connections from clients running on the host where the RMI remote objects have been exported.
    at sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(LocalRMIServerSocketFactory.java:114)[:1.8.0_222]
    at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:405)[:1.8.0_222]
    at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:377)[:1.8.0_222]
    at java.lang.Thread.run(Thread.java:748)[:1.8.0_222]

 

 

Powered by Wolken Software