DX Unified Infrastructure Management

I have a situation where the controller keeps 'going down' every few minutes. In USM, the alert count does not increase, it seems to come in as a new alarm / event every time, which in turn causes multiple duplicate event tickets in our CRM due to integration

Under what conditions does a 'going down' event get triggered? I've checked connectivity via tcpdump, and NTP all seems to be ok, don't really see any issues - has anyone else seen similar issues before, and anything additional I can check?

Apr 17 10:11:47:098 [140337017726720] Controller: --------------------------------------------------------------------------------------------------------
Apr 17 10:11:47:099 [140337017726720] Controller: ----- Robot controller 7.90 [Build 7.90.7621, Feb 22 2017] started -----
Apr 17 10:11:47:099 [140337017726720] Controller: Name = , Port = 48000
Apr 17 10:11:47:099 [140337017726720] Controller: OS = UNIX / Linux / Linux 2.6.32-642.4.2.el6.x86_64 #1 SMP Mon Aug 15 02:06:41 EDT 2016 x86_64
Apr 17 10:11:47:099 [140337017726720] Controller: Domain = 
Apr 17 10:11:47:099 [140337017726720] Controller: Primary HUB = /
Apr 17 10:11:47:099 [140337017726720] Controller: Secondary HUB = 
Apr 17 10:11:47:099 [140337017726720] Controller: Loglevel = 0, Logfile = controller.log
Apr 17 10:11:47:103 [140337017726720] Controller: Running as user root (0)
Apr 17 10:11:47:103 [140337017726720] Controller: -----
Apr 17 10:11:47:103 [140337017726720] Controller: Controller on  port 48000 started
Apr 17 10:11:48:112 [140337017726720] Controller: Hub  contact established
Apr 17 10:43:16:570 [140337017726720] Controller: Going down...
Apr 17 10:43:24:582 [140337017726720] Controller: Down
Apr 17 10:43:35:637 [139988764989184] Controller: --------------------------------------------------------------------------------------------------------
Apr 17 10:43:35:637 [139988764989184] Controller: ----- Robot controller 7.90 [Build 7.90.7621, Feb 22 2017] started -----
Apr 17 10:43:35:637 [139988764989184] Controller: Name = , Port = 48000
Apr 17 10:43:35:637 [139988764989184] Controller: OS = UNIX / Linux / Linux 2.6.32-642.4.2.el6.x86_64 #1 SMP Mon Aug 15 02:06:41 EDT 2016 x86_64
Apr 17 10:43:35:637 [139988764989184] Controller: Domain = 
Apr 17 10:43:35:637 [139988764989184] Controller: Primary HUB = /
Apr 17 10:43:35:637 [139988764989184] Controller: Secondary HUB = /
Apr 17 10:43:35:637 [139988764989184] Controller: Loglevel = 0, Logfile = controller.log
Apr 17 10:43:35:642 [139988764989184] Controller: Running as user root (0)
Apr 17 10:43:35:642 [139988764989184] Controller: -----
Apr 17 10:43:35:642 [139988764989184] Controller: Controller on  port 48000 started
Apr 17 10:43:36:651 [139988764989184] Controller: Hub  contact established
Apr 17 11:18:50:111 [139988764989184] Controller: Going down...
Apr 17 11:18:58:127 [139988764989184] Controller: Down
Apr 17 11:19:05:161 [140290132383488] Controller: --------------------------------------------------------------------------------------------------------

A manual restart or an internal restart of the controller.

Set the controller loglevel to 3 or higher and logsize to 5000

you should get more details.

There used to be an issue with date and time stamp on the OS being off so check the data an time is not off more than 5  minutes.

Hello Shaun, you may open a support case for this request and attach the logfiles as explained by Gene to it for further investigation.

Kind regards,

Britta Hoffner