In our failover DMS, on the inactive DMA there is a constant error logging (in SLGSMGateway.txt) concerning the communication to the SMS Mobile Gateway:
2023/05/17 09:47:14.396|SLGSMGateway|1008|16688|Info|INF|-1|Going in failover, because no dataminer are registered anymore.
2023/05/17 09:47:14.852|SLGSMGateway|1008|16676|Info|INF|-1|Mobile Gateway is now initialized.
2023/05/17 09:47:24.402|SLGSMGateway|1008|16688|Info|INF|-1|Going in failover, because no dataminer are registered anymore.
2023/05/17 09:47:24.671|SLGSMGateway|1008|16676|Info|INF|-1|Mobile Gateway is now initialized.
2023/05/17 09:47:34.403|SLGSMGateway|1008|16688|Info|INF|-1|Going in failover, because no dataminer are registered anymore.
2023/05/17 09:47:34.482|SLGSMGateway|1008|16676|Info|INF|-1|Mobile Gateway is now initialized.
This seems to be related to the timeout settings in the mobile gateway configuration in our DMS, which is 10 seconds.
However, the mobile gateway is working properly and the communication from the active DMA is alright.
Is there any way to keep the inactive DMA from logging tons of messages that make no sense and have no purpose?
Thanks a lot!
Processes independently creating logging are often unaware of the failover state of a DMA. As you can see though, there is some protection for logging getting out of hand.
Hi Nils,
So you still need more information for this question? Based on the comments, I get the impression that this may already be resolved.
It seems as if the logging on the inactive DMA is somehow limited – only log entries from the last two days can be found, and the file size is smaller than 3 MB. So at least this does not lead to some kind of oversized logfile…