We have 4 TM1 servers connected to single Pulse. Last couple of weeks we began to notice connectivity issues with one of the servers happening every day or two. The cause of that Pulse monitor, installed on TM1 server, which cease to respond (though indicates itself as running in Windows Services). Restarting Pulse monitor helps, but in day or two it happens again.
Application log doesn’t contain anything which could explain that behavior:
| 2023-07-09 23:12:48.937 | main | INFO | Pulse monitor version 1.0.9 |
|---|---|---|---|
| 2023-07-09 23:12:48.942 | main | INFO | Pulse server version 6.2.0 |
| 2023-07-09 23:12:48.943 | main | INFO | Settings from E:\Program Files\Pulse for TM1\conf\monitor.yml |
| 2023-07-09 23:12:48.948 | initialise | INFO | Server information: 16 cores, 262033 memory |
| 2023-07-09 23:12:50.427 | run | INFO | Refresh local state elapsed time 1479 ms |
| 2023-07-09 23:12:50.427 | run | INFO | Creating scheduled jobs |
| 2023-07-09 23:12:50.431 | run | INFO | Server name is: DEVDCWIN1316 |
| 2023-07-09 23:12:50.435 | run | INFO | Starting HTTPS server on port: 8094 |
| 2023-07-10 10:15:02.817 | main | INFO | Pulse monitor version 1.0.9 |
| 2023-07-10 10:15:02.817 | main | INFO | Pulse server version 6.2.0 |
| 2023-07-10 10:15:02.817 | main | INFO | Settings from E:\Program Files\Pulse for TM1\conf\monitor.yml |
| 2023-07-10 10:15:02.822 | initialise | INFO | Server information: 16 cores, 262033 memory |
| 2023-07-10 10:15:04.723 | run | INFO | Refresh local state elapsed time 1901 ms |
| 2023-07-10 10:15:04.723 | run | INFO | Creating scheduled jobs |
| 2023-07-10 10:15:04.724 | run | INFO | Server name is: DEVDCWIN1316 |
| 2023-07-10 10:15:04.738 | run | INFO | Starting HTTPS server on port: 8094 |
| Didn’t find anything in Event viewer either. |
Any suggestion where to look to investigate or how that could be fixed?