Problem: The Stats Manager jobs are not running after the customer relocated the DBS nodes. The IP address associated with the DBS environment was changed correctly on the Viewpoint Monitored Systems section. None of the other portlets are having problems or reporting issues. Environment/Conditions/Configuration TDBMS 14.10.05.09 Viewpoint 15.11.00.05
Cause: Viewpoint has not updated the IP address information for the Stats Manager collector after changing it on the Monitored Systems screen. You will see such error in dcs.log (/opt/teradata/viewpoint/dcs/logs/ dcs.log) 2017-12-11 01:00:20,387 ERROR [Resynchronizer-AWSDev] {} resync.Resynchronizer.run(140) - Unable to resynchronize stats data for system AWSDev org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC 15.10.00.09] [Error 1277] [SQLState 08S01] Login timeout for Connection to XXX.XX.XXX.XX Mon Dec 11 01:00:20 CET 2017 socket orig=XXX.XX.XXX.XX cid=2aed57ce sess=0 java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImp l.doConnect(AbstractPlainSocketImpl.java:344) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocket Impl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:1217)
Solution: Restart Viewpoint services.
Example: TERADATADB-1-17:~ # /opt/teradata/viewpoint/bin/vp-control.sh status Mon Dec 11 10:54:34 CET 2017 Checking the status of all Teradata Viewpoint services. Checking for Teradata ActiveMQ: running Checking for Teradata Alert Service: running Checking for TMSMonitor: running Checking for DCS: running Checking for Viewpoint: running Checking for PostgreSQL 9.1.20: running Restart the viewpoint service using the command below
TERADATADB-1-17:~ # /opt/teradata/viewpoint/bin/vp-control.sh restart Mon Dec 11 10:54:45 CET 2017 Stopping all Teradata Viewpoint services. Mon Dec 11 10:54:45 CET 2017 viewpoint: stopping... Shutting down Viewpoint done Mon Dec 11 10:55:17 CET 2017 viewpoint: stopped Mon Dec 11 10:55:17 CET 2017 dcs: stopping... Shutting down DCS done Mon Dec 11 10:55:21 CET 2017 dcs: stopped Mon Dec 11 10:55:21 CET 2017 tmsmonitor: stopping... Shutting down TMSMonitor done Mon Dec 11 10:55:54 CET 2017 tmsmonitor: stopped Mon Dec 11 10:55:54 CET 2017 camalert: stopping... Shutting down Teradata Alert Service done Mon Dec 11 10:55:55 CET 2017 camalert: stopped Mon Dec 11 10:55:55 CET 2017 tdactivemq: stopping... Shutting down Teradata ActiveMQ done Mon Dec 11 10:55:57 CET 2017 tdactivemq: stopped Mon Dec 11 10:55:57 CET 2017 All Teradata Viewpoint services stopped. Mon Dec 11 10:55:57 CET 2017 Starting all Teradata Viewpoint services. Mon Dec 11 10:55:57 CET 2017 tdactivemq: starting... Starting Teradata ActiveMQ done Mon Dec 11 10:55:59 CET 2017 tdactivemq: started Mon Dec 11 10:55:59 CET 2017 camalert: starting... Starting Teradata Alert Service done Mon Dec 11 10:56:01 CET 2017 camalert: started Mon Dec 11 10:56:01 CET 2017 tmsmonitor: starting... Starting TMSMonitor done Mon Dec 11 10:56:03 CET 2017 tmsmonitor: started Mon Dec 11 10:56:03 CET 2017 dcs: starting... Starting DCS done Mon Dec 11 10:56:09 CET 2017 dcs: started Mon Dec 11 10:56:09 CET 2017 viewpoint: starting... Starting Viewpoint done Mon Dec 11 10:56:11 CET 2017 viewpoint: started Mon Dec 11 10:56:11 CET 2017 All Teradata Viewpoint services started.
TERADATADB-1-17:~ # /opt/teradata/viewpoint/bin/vp-control.sh status Checking for Teradata ActiveMQ: running Checking for Teradata Alert Service: running Checking for TMSMonitor: running Checking for DCS: running Checking for Viewpoint: running Checking for PostgreSQL 9.1.20: running |