hi team,
SLDataminer service was automatically stoping and starting, need help on this.
thanks,
s.j.v.praveen
hi @Arunkrishna,
startup type is automatic (Delayed start)
below are the SLDataMIner.txt logs
2023/07/03 05:15:08.554|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 0; Error: 0; Debug: 0 (from LogSettings.xml)
2023/07/03 05:15:08.569|SLDataMiner|8532|9924|CDataMiner::CreateLog|CRU|-1|Launching SLDataMiner
2023/07/03 05:15:08.569|SLDataMiner|8532|9924|CServiceModule::LaunchDataMiner|CRU|-1|Starting dependencies…
2023/07/03 05:15:10.549|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::CreateConnection|DBG|0|– SLNetCom object successfully created.
2023/07/03 05:15:10.559|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::AddLocalInfo|DBG|-1|– Added local SLNetCom info: VT_BSTR :
2023/07/03 05:15:10.559|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::AddLocalInfo|DBG|-1|– Added local SLNetCom info: VT_BSTR : localhost
2023/07/03 05:15:10.559|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::AddLocalInfo|DBG|-1|– Added local SLNetCom info: VT_BSTR : 127.0.0.1
2023/07/03 05:15:10.559|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::Init|DBG|0|** Initializing SLNetCom
2023/07/03 05:15:12.655|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::Init|DBG|0|** Initializing SLNetCom succeeded
2023/07/03 05:15:12.714|SLDataMiner|8532|9924|CDataMiner::DataMinerBatch|DBG|-1|** Executing actions from StartupDataMiner.bat …
2023/07/03 05:15:12.764|SLDataMiner|8532|9924|CDataMiner::CreateModules|DBG|-1|** Starting Creation DataMiner Modules …
2023/07/03 05:15:14.920|SLDataMiner|8532|9924|Version|INF|-1|Running DataMiner v10.3.7.0
2023/07/03 05:15:14.920|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Create request.lic …
2023/07/03 05:15:14.928|SLDataMiner|8532|9924|CDataMiner::DataMinerBatch|DBG|-1|** Executing actions from StartupDataMinerLic.bat …
2023/07/03 05:15:14.929|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Checking License …
2023/07/03 05:15:16.423|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|INF|-1|No licenses for MAC: 0A-5E-36-EC-3B-13
2023/07/03 05:15:16.423|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** DMA file version is 10.3
2023/07/03 05:15:16.423|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Licensed version is 10.3
2023/07/03 05:15:16.423|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|INF|-1|No licenses for MAC: 0A-5E-36-EC-3B-13
2023/07/03 05:15:16.424|SLDataMiner|8532|9924|CDataMiner::Init|CRU|-1|** Performing Demo-license check
2023/07/03 05:15:16.467|SLDataMiner|8532|9924|CDataMiner::Init|CRU|-1|** Successful offline verification as Demo DataMiner
2023/07/03 05:15:16.467|SLDataMiner|8532|9924|CDataMiner::Init|CRU|-1|********************************************************************
2023/07/03 05:15:16.467|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 20 elements. (Default – Demo)
2023/07/03 05:15:16.467|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 real elements. (Default – Demo)
2023/07/03 05:15:16.467|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 virtual elements. (Default – Demo)
2023/07/03 05:15:16.467|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 concurrent reservations. (Default – Demo)
2023/07/03 05:15:16.467|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 spectrum elements. (Default – Demo)
2023/07/03 05:15:16.468|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 20 elements. (Default – Demo)
2023/07/03 05:15:16.468|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 spectrum elements. (Default – Demo)
2023/07/03 05:15:16.468|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 real elements. (Default – Demo)
2023/07/03 05:15:16.468|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 virtual elements. (Default – Demo)
2023/07/03 05:15:16.468|SLDataMiner.exe 10.3.2321.1738|8532|9924|L::IsLicensed|CRU|-1|Licensed for 4294967295 concurrent reservations. (Default – Demo)
2023/07/03 05:15:16.469|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Getting hardware information …
2023/07/03 05:15:16.474|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::Init|INF|0|– 8 processor(s) ~ Intel ~ revision 0x4F01
2023/07/03 05:15:16.474|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeSerialPorts|INF|0|– Available serial ports : COM1
2023/07/03 05:15:16.474|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::Init()|INF|0|– Joining WorkGroup (2) ‘WORKGROUP’
2023/07/03 05:15:16.480|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeNetwork|CRU|-1|Interface 15 has name Ethernet 2
2023/07/03 05:15:16.480|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeNetwork|CRU|-1|Interface 1 has name Loopback Pseudo-Interface 1
2023/07/03 05:15:16.486|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0|– 6 Adapter {D7F2A7DC-EA23-44EF-8EBE-84BAD862A9D8} (Ethernet 2) context 15
2023/07/03 05:15:16.486|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| DHCP = Enabled
2023/07/03 05:15:16.486|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| IPAddress: 10.0.4.56
2023/07/03 05:15:16.486|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| SubnetMask: 255.255.240.0
2023/07/03 05:15:16.486|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| Default Gateway: 10.0.0.1
2023/07/03 05:15:16.486|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| MAC: 0A-5E-36-EC-3B-13
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| Interface default GW = 10.0.0.1
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0|– 10.0.4.56 (255.255.240.0) context 939786250 on Ethernet 2 (0A-5E-36-EC-3B-13)
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::InitializeIP|INF|0| Interface address = 10.0.4.56
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::CAdapterOrder::LogAdaptersList|CRU|-1|No tag configured. Using observed adapters order.
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::CAdapterOrder::LogAdaptersList|CRU|-1|NIC 1 Ethernet 2
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::CAdapterOrder::LogAdaptersList|CRU|-1| IP 1 10.0.4.56
2023/07/03 05:15:16.487|SLDataMiner.exe 10.3.2321.1738|8532|9924|CHardware::SetSkipAsSourceIP|INF|-1|SkipAsSource Flag for ip (10.0.4.56) is set to FALSE
2023/07/03 05:15:16.495|SLDataMiner.exe 10.3.2321.1738|8532|9924|CRequest::AddLocalInfo|DBG|-1|– Added local SLNetCom info: VT_BSTR : 10.0.4.56
2023/07/03 05:15:16.496|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Amount Action Threads: 16
2023/07/03 05:15:16.498|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Initializing XML …
2023/07/03 05:15:16.517|SLDataMiner|8532|9924|CDataMiner::InitializeXML|INF|0|Bigdata active
2023/07/03 05:15:16.572|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Setting DMA-Name (EC2AMAZ-DSHABII)
2023/07/03 05:15:16.581|SLDataMiner|8532|9924|CDataMiner::Init|DBG|-1|** Initializing Maintenance …
issue resolved
its because of dataminer 10.3 upgrade.
https://docs.dataminer.services/user-guide/Troubleshooting/Known_issues/KI_Restart_loop_when_Elasticsearch_unavailable.html
Hello Praveen,
the log files you shared show Dataminer starting up 03/07 at 05:15:08
as far as it restarted, you can find out what triggered the restart looking into the log file SLWatchdog2_BAL.txt
hi Danielle Falcone,
it is SLWatchdog2_BAL.txt or SLWatchdog2_BAK.txt?
below logs for SLWatchdog2_BAK.txt
2023-07-03 07:42:50 3176|SLDataMiner active …
2023-07-03 07:42:50 3176|Run Count: 105
2023-07-03 07:42:50 3176|Restored connection with SLNet…
2023-07-03 07:42:50 3176|- Email notification active
2023-07-03 07:42:50 3176|- Email destination dataminer.minidump@skyline.be
2023-07-03 07:42:50 3176|- Email CC destination
2023-07-03 07:42:50 3176|- Email BCC destination
2023-07-03 07:42:50 3176|- Email max in hour
2023-07-03 07:42:50 3176|- Email process count
2023-07-03 07:42:50 3176|- Email timeout time
2023-07-03 07:42:50 3176|- Email max attachement size
2023-07-03 07:42:50 3176|- Email password option
2023-07-03 07:42:50 3176|Stopping restart timer (reset)
2023-07-03 07:42:50 3176|DMA is active…
2023-07-03 07:42:51 17852|DMA manual start…
2023-07-03 07:42:52 14816|Setting version to 10.3.7.0-13107-20230614-release
2023-07-03 07:42:56 14816|Add Thread (1) SLDMS – DATAMINER_NOTIFICATION_QUEUE Thread [pid 9660 – thread 13656] (time = 00:45:00)
2023-07-03 07:42:56 14816|–> Added process watch for PID 15668 process SLSNMPAgent.exe (Critical)
2023-07-03 07:42:56 9568|–> Process 15668 SLSNMPAgent.exe registered
2023-07-03 07:42:56 14816|–> Added process watch for PID 16100 process SLASPConnection.exe (Reset allowed)
2023-07-03 07:42:56 10024|–> Process 16100 SLASPConnection.exe registered
2023-07-03 07:42:58 14816|Add Thread (2) SLDataMiner.exe – License timer [pid 4632] (time = 01:30:00)
2023-07-03 07:43:06 3176|Sending notification e-mail failed. Notification Problem: Mail server (localhost) is unavailable (No connection could be made because the target machine actively refused it. = 0x8007274dh; last response: )
2023-07-03 07:43:08 17852|Sending notification e-mail failed. Notification Problem: Mail server (localhost) is unavailable (No connection could be made because the target machine actively refused it. = 0x8007274dh; last response: )
2023-07-03 07:43:08 17852|DataMiner restarted
2023-07-03 07:43:17 17852|Add Thread (3) SLDataMiner.exe – ActionThread [pid 4632 – thread 5936] (time = 00:07:30)
2023-07-03 07:43:17 17852|Add Thread (4) SLDataMiner – DATAMINER_NOTIFICATION_QUEUE Thread [pid 4632 – thread 12072] (time = 00:45:00)
2023-07-03 07:43:19 17852|Add Thread (5) SLElement – DATAMINER_NOTIFICATION_QUEUE Thread [pid 15368 – thread 18756] (time = 00:45:00)
2023-07-03 07:43:19 17852|Add Thread (6) SLElement.exe – ClientNotificationsthread [pid 15368 – thread 14556] (time = 00:07:30)
2023-07-03 07:43:19 14816|Add Thread (7) SLElement.exe – Database thread [pid 15368 – thread 3392] (time = 00:07:30)
2023-07-03 07:43:19 17504|Add Thread (8) SLElement.exe – AlarmLevelLink thread [pid 15368 – thread 18124] (time = 00:07:30)
2023-07-03 07:43:20 18288|Restart (with SLNet) is called by The connection with the database has been restored.
2023-07-03 07:43:20 18288|Stopping: 1 time
2023-07-03 07:43:20 16056|Add Thread (40) SLElement.exe – Parameter thread [pid 15368 – thread 19352] (time = 00:07:30)
2023-07-03 07:43:20 16056|Add Thread (41) SLElement.exe – DataGateway::ScheduleDataThread [pid 15368 – thread 12272] (time = 00:07:30)
2023-07-03 07:43:21 16056|Add Thread (42) SLElement.exe – PublishDataThread [pid 15368 – thread 12400] (time = 00:07:30)
2023-07-03 07:43:21 11560|–> Added process watch for PID 19452 process SLProtocol.exe (Critical)
2023-07-03 07:43:21 7724|–> Process 19452 SLProtocol.exe registered
2023-07-03 07:43:22 11560|–> Added process watch for PID 18504 process SLProtocol.exe (Critical)
2023-07-03 07:43:22 6292|–> Process 18504 SLProtocol.exe registered
2023-07-03 07:43:22 11560|–> Added process watch for PID 17256 process SLProtocol.exe (Critical)
2023-07-03 07:43:22 12640|–> Process 17256 SLProtocol.exe registered
2023-07-03 07:43:22 11560|–> Added process watch for PID 17524 process SLProtocol.exe (Critical)
2023-07-03 07:43:22 5304|–> Process 17524 SLProtocol.exe registered
2023-07-03 07:43:22 11560|–> Added process watch for PID 13288 process SLProtocol.exe (Critical)
2023-07-03 07:43:22 13704|–> Process 13288 SLProtocol.exe registered
2023-07-03 07:43:22 11560|Add Thread (49) SLProtocol.exe – GetProtocolObjectThread [pid 19452 – thread 7116] (time = 00:07:30)
2023-07-03 07:43:22 14816|Add Thread (50) SLProtocol.exe – DataMiner notifications thread [pid 19452 – thread 16300] (time = 00:07:30)
2023-07-03 07:43:22 12040|Add Thread (51) SLProtocol.exe – CleanAsyncResponses [pid 19452 – thread 15040] (time = 00:07:30)
2023-07-03 07:43:22 16056|Add Thread (52) SLProtocol.exe – Query thread [pid 19452 – thread 16476] (time = 00:45:00)
2023-07-03 07:43:22 17504|Add Thread (53) SLProtocol.exe – Bitrate thread [pid 19452 – thread 7132] (time = 00:07:30)
2023-07-03 07:43:22 17504|Add Thread (54) SLProtocol.exe – GetProtocolObjectThread [pid 18504 – thread 2952] (time = 00:07:30)
2023-07-03 07:43:22 14816|Add Thread (55) SLProtocol.exe – Bitrate thread [pid 18504 – thread 16820] (time = 00:07:30)
2023-07-03 07:43:22 12040|Add Thread (56) SLProtocol.exe – Query thread [pid 18504 – thread 14012] (time = 00:45:00)
2023-07-03 07:43:22 11560|Add Thread (57) SLProtocol.exe – CleanAsyncResponses [pid 18504 – thread 872] (time = 00:07:30)
2023-07-03 07:43:22 16056|Add Thread (58) SLProtocol.exe – DataMiner notifications thread [pid 18504 – thread 11040] (time = 00:07:30)
2023-07-03 07:43:22 11560|Add Thread (59) SLProtocol.exe – GetProtocolObjectThread [pid 17256 – thread 16960] (time = 00:07:30)
2023-07-03 07:43:22 12040|Add Thread (60) SLProtocol.exe – Query thread [pid 17256 – thread 6240] (time = 00:45:00)
2023-07-03 07:43:22 14816|Add Thread (62) SLProtocol.exe – Bitrate thread [pid 17256 – thread 9456] (time = 00:07:30)
2023-07-03 07:43:22 17504|Add Thread (63) SLProtocol.exe – CleanAsyncResponses [pid 17256 – thread 5176] (time = 00:07:30)
2023-07-03 07:43:22 16056|Add Thread (61) SLProtocol.exe – DataMiner notifications thread [pid 17256 – thread 3720] (time = 00:07:30)
2023-07-03 07:43:22 16056|–> Added process watch for PID 3140 process SLScripting.exe (Reset allowed)
2023-07-03 07:43:22 17504|Add Thread (64) SLProtocol.exe – GetProtocolObjectThread [pid 17524 – thread 9380] (time = 00:07:30)
2023-07-03 07:43:22 16456|–> Process 3140 SLScripting.exe registered
2023-07-03 07:43:22 11560|Add Thread (65) SLProtocol.exe – Bitrate thread [pid 17524 – thread 7928] (time = 00:07:30)
2023-07-03 07:43:22 14816|Add Thread (66) SLProtocol.exe – DataMiner notifications thread [pid 17524 – thread 10124] (time = 00:07:30)
2023-07-03 07:43:22 12040|Add Thread (67) SLProtocol.exe – Query thread [pid 17524 – thread 16220] (time = 00:45:00)
2023-07-03 07:43:22 16496|Add Thread (68) SLProtocol.exe – CleanAsyncResponses [pid 17524 – thread 18568] (time = 00:07:30)
2023-07-03 07:43:22 16496|Add Thread (69) SLProtocol.exe – GetProtocolObjectThread [pid 13288 – thread 8508] (time = 00:07:30)
2023-07-03 07:43:22 12040|Add Thread (70) SLProtocol.exe – DataMiner notifications thread [pid 13288 – thread 12896] (time = 00:07:30)
2023-07-03 07:43:22 11560|Add Thread (71) SLProtocol.exe – Bitrate thread [pid 13288 – thread 932] (time = 00:07:30)
2023-07-03 07:43:22 17504|Add Thread (72) SLProtocol.exe – CleanAsyncResponses [pid 13288 – thread 19020] (time = 00:07:30)
2023-07-03 07:43:22 14816|Add Thread (73) SLProtocol.exe – Query thread [pid 13288 – thread 10260] (time = 00:45:00)
2023-07-03 07:43:22 14816|Add Thread (74) SLDataMiner.exe – AlarmLevelRegistrationThread [pid 4632 – thread 13756] (time = 00:07:30)
2023-07-03 07:43:22 17504|Add Thread (75) SLDataMiner.exe – AlarmLevelUpdateThread [pid 4632 – thread 19240] (time = 00:07:30)
2023-07-03 07:43:22 17504|Add Thread (76) SLDataMiner.exe – AlarmStackThread [pid 4632 – thread 7376] (time = 00:07:30)
2023-07-03 07:43:22 14816|Add Thread (77) SLDataMiner.exe – Database Offload Thread [local] [pid 4632 – thread 1704] (time = 00:07:30)
2023-07-03 07:43:22 11560|Add Thread (78) SLDataMiner.exe – ReplicationDBThread [pid 4632 – thread 9416] (time = 00:07:30)
2023-07-03 07:43:22 16496|Add Thread (79) SLDataMiner.exe – Database cleaning [pid 4632 – thread 2264] (time = 00:30:00)
2023-07-03 07:43:22 12040|Add Thread (80) SLDataMiner.exe – DBThread [pid 4632 – thread 15036] (time = 00:07:30)
2023-07-03 07:43:22 12040|Add Thread (81) SLDataMiner.exe – Notify time [pid 4632] (time = 00:07:30)
2023-07-03 07:43:23 12040|–> Added process watch for PID 5884 process SLAutomation.exe (Reset allowed)
2023-07-03 07:43:23 18912|–> Process 5884 SLAutomation.exe registered
2023-07-03 07:43:23 12040|–> Added process watch for PID 9472 process SLScheduler.exe (Reset allowed)
2023-07-03 07:43:23 16916|–> Process 9472 SLScheduler.exe registered
2023-07-03 07:43:23 12040|Add Thread (85) SLAutomation.exe – Handle Notifications Thread [pid 5884 – thread 15280] (time = 00:07:30)
2023-07-03 07:43:23 12040|Add Thread (86) SLSpectrum.exe – HeartBeat Thread [pid 1584 – thread 7084] (time = 00:07:30)
2023-07-03 07:43:25 12040|Add Thread (87) SLDMS.exe – NotificationThread for 10.0.4.56 [pid 9660 – thread 13400] (time = 00:07:30)
2023-07-03 07:43:25 12040|Add Thread (88) SLDMS.exe – NotificationThread [pid 9660 – thread 12136] (time = 00:07:30)
2023-07-03 07:43:26 12040|Add Thread (89) SLSNMPAgent.exe – DelayedNotificationsThread started for Element [pid 15668 – thread 11028] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (90) SLSNMPAgent.exe – Polling thread for element: EC2AMAZ-DSHABII [pid 15668 – thread 12200] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (91) SLSNMPAgent.exe – PopThread: Email and sms notifications [pid 15668 – thread 12664] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (92) SLSNMPAgent.exe – IncomingAlarmsThread [pid 15668 – thread 18036] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (93) SLSNMPAgent.exe – SNMP_PP_InformThread [pid 15668 – thread 16136] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (94) SLDMS.exe – SNMP Notifications thread [pid 9660 – thread 17944] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (95) SLBrain.exe – Action Launching Thread [pid 3664 – thread 14848] (time = 00:07:30)
2023-07-03 07:43:26 12040|Add Thread (96) SLBrain.exe – Alarm Handling Thread [pid 3664 – thread 1164] (time = 00:07:30)
2023-07-03 07:43:26 12040|Add Thread (97) SLBrain.exe – Handle Notifications Thread [pid 3664 – thread 4112] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (98) SLDMS.exe – Notify other objects thread [pid 9660 – thread 11712] (time = 00:07:30)
2023-07-03 07:43:26 12040|Add Thread (99) SLSpectrum.exe – Measurement Point Service Updates [pid 1584 – thread 18840] (time = 00:07:30)
2023-07-03 07:43:26 12040|–> Added process watch for PID 19380 process SLLog.exe (Critical)
2023-07-03 07:43:26 17472|–> Process 19380 SLLog.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 18316 process SLXml.exe (Critical)
2023-07-03 07:43:26 19328|–> Process 18316 SLXml.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 4632 process SLDataMiner.exe (Critical)
2023-07-03 07:43:26 14096|–> Process 4632 SLDataMiner.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 3528 process SLNetCOMService.exe (Critical)
2023-07-03 07:43:26 14240|–> Process 3528 SLNetCOMService.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 2184 process SLNet.exe (Critical)
2023-07-03 07:43:26 14912|–> Process 2184 SLNet.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 13024 process SLSpiHost.exe (Reset allowed) (RTEs enabled)
2023-07-03 07:43:26 11580|–> Process 13024 SLSpiHost.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 12812 process SLAnalytics.exe (Reset allowed)
2023-07-03 07:43:26 2948|–> Process 12812 SLAnalytics.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 9660 process SLDMS.exe (Critical)
2023-07-03 07:43:26 5760|–> Process 9660 SLDMS.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 11628 process SLSNMPManager.exe (Critical)
2023-07-03 07:43:26 19160|–> Process 11628 SLSNMPManager.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 10592 process SLSNMPManager.exe (Critical)
2023-07-03 07:43:26 18324|–> Process 10592 SLSNMPManager.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 3480 process SLSNMPManager.exe (Critical)
2023-07-03 07:43:26 19216|–> Process 3480 SLSNMPManager.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 18016 process SLDataGateway.exe (Critical)
2023-07-03 07:43:26 6740|–> Process 18016 SLDataGateway.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 13948 process SLPort.exe (Critical)
2023-07-03 07:43:26 8288|–> Process 13948 SLPort.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 2892 process SLPort.exe (Critical)
2023-07-03 07:43:26 11068|–> Process 2892 SLPort.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 14608 process SLPort.exe (Critical)
2023-07-03 07:43:26 8832|–> Process 14608 SLPort.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 12124 process SLPort.exe (Critical)
2023-07-03 07:43:26 17568|–> Process 12124 SLPort.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 3696 process SLPort.exe (Critical)
2023-07-03 07:43:26 14368|–> Process 3696 SLPort.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 15368 process SLElement.exe (Critical)
2023-07-03 07:43:26 11608|–> Process 15368 SLElement.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 3664 process SLBrain.exe (Critical)
2023-07-03 07:43:26 11700|–> Process 3664 SLBrain.exe registered
2023-07-03 07:43:26 12040|–> Added process watch for PID 1584 process SLSpectrum.exe (Critical)
2023-07-03 07:43:26 7852|–> Process 1584 SLSpectrum.exe registered
2023-07-03 07:43:26 12040|Add Thread (100) SLDataMiner.exe – Mobile Notification Thread [pid 4632 – thread 11972] (time = 00:07:30)
2023-07-03 07:43:26 16496|Add Thread (101) SLDataMiner.exe – Mobile Thread [pid 4632 – thread 18396] (time = 00:07:30)
2023-07-03 07:43:26 12040|Add Thread (102) SLDMS.exe – ConnectionThread [pid 9660 – thread 19276] (time = 00:07:30)
2023-07-03 07:43:26 11560|Add Thread (103) SLDataMiner.exe – ServiceThread [pid 4632 – thread 11080] (time = 00:07:30)
2023-07-03 07:43:26 14816|Add Thread (104) SLDataMiner.exe – ServiceReplicationThread [pid 4632 – thread 18688] (time = 00:07:30)
2023-07-03 07:43:26 12040|(100) Stopped Mobile Notification Thread from SLDataMiner.exe
2023-07-03 07:43:26 12040|Remove Thread (100) succeeded.
2023-07-03 07:43:26 16496|(101) Stopped Mobile Thread from SLDataMiner.exe
2023-07-03 07:43:26 16496|Remove Thread (101) succeeded.
2023-07-03 07:43:26 16496|Add Thread (105) SLDataMiner.exe – RedundancyThread [pid 4632 – thread 16440] (time = 00:07:30)
2023-07-03 07:43:26 12040|Report values initialized…
2023-07-03 07:43:26 12040|Startuptime sent…
2023-07-03 07:43:28 16496|Add Thread (106) SLASPConnection.exe – Handle Notifications Thread [pid 16100 – thread 16180] (time = 00:07:30)
2023-07-03 07:43:40 6740|-> Process with PID 18016 (SLDataGateway.exe) stopped.
2023-07-03 07:43:40 6740|Queueing FULL DataMiner Restart in 2 minutes (SLDataGateway.exe)
2023-07-03 07:43:40 3176|Mutex of SLDataMiner released …
2023-07-03 07:43:40 3176|Cleared list of monitored processes/threads
2023-07-03 07:43:40 14096|-> Process with PID 4632 (SLDataMiner.exe) stopped.
2023-07-03 07:43:40 17568|-> Process with PID 12124 (SLPort.exe) stopped.
2023-07-03 07:43:40 11068|-> Process with PID 2892 (SLPort.exe) stopped.
2023-07-03 07:43:40 14368|-> Process with PID 3696 (SLPort.exe) stopped.
2023-07-03 07:43:40 8288|-> Process with PID 13948 (SLPort.exe) stopped.
2023-07-03 07:43:40 8832|-> Process with PID 14608 (SLPort.exe) stopped.
2023-07-03 07:43:40 5760|-> Process with PID 9660 (SLDMS.exe) stopped.
2023-07-03 07:43:40 19328|-> Process with PID 18316 (SLXml.exe) stopped.
2023-07-03 07:43:40 19160|-> Process with PID 11628 (SLSNMPManager.exe) stopped.
2023-07-03 07:43:40 18324|-> Process with PID 10592 (SLSNMPManager.exe) stopped.
2023-07-03 07:43:40 9568|-> Process with PID 15668 (SLSNMPAgent.exe) stopped.
2023-07-03 07:43:40 19216|-> Process with PID 3480 (SLSNMPManager.exe) stopped.
2023-07-03 07:43:41 13704|-> Process with PID 13288 (SLProtocol.exe) stopped.
2023-07-03 07:43:41 6292|-> Process with PID 18504 (SLProtocol.exe) stopped.
2023-07-03 07:43:41 5304|-> Process with PID 17524 (SLProtocol.exe) stopped.
2023-07-03 07:43:41 12640|-> Process with PID 17256 (SLProtocol.exe) stopped.
2023-07-03 07:43:41 7724|-> Process with PID 19452 (SLProtocol.exe) stopped.
2023-07-03 07:43:41 17472|-> Process with PID 19380 (SLLog.exe) stopped.
2023-07-03 07:43:41 11608|-> Process with PID 15368 (SLElement.exe) stopped.
2023-07-03 07:43:41 10024|-> Process with PID 16100 (SLASPConnection.exe) stopped.
2023-07-03 07:43:41 10024|Remove Threads(0) (SLASPConnection.exe) succeeded.
2023-07-03 07:43:41 11700|-> Process with PID 3664 (SLBrain.exe) stopped.
2023-07-03 07:43:41 18912|-> Process with PID 5884 (SLAutomation.exe) stopped.
2023-07-03 07:43:41 18912|Remove Threads(0) (SLAutomation.exe) succeeded.
2023-07-03 07:43:41 16916|-> Process with PID 9472 (SLScheduler.exe) stopped.
2023-07-03 07:43:41 16916|Remove Threads(0) (SLScheduler.exe) succeeded.
2023-07-03 07:43:42 7852|-> Process with PID 1584 (SLSpectrum.exe) stopped.
2023-07-03 07:43:42 16456|-> Process with PID 3140 (SLScripting.exe) stopped.
2023-07-03 07:43:42 16456|Remove Threads(0) (SLScripting.exe) succeeded.
2023-07-03 07:43:42 2948|-> Process with PID 12812 (SLAnalytics.exe) stopped.
2023-07-03 07:43:42 2948|Remove Threads(0) (SLAnalytics.exe) succeeded.
2023-07-03 07:43:42 11580|-> Process with PID 13024 (SLSpiHost.exe) stopped.
2023-07-03 07:43:42 11580|Remove Threads(0) (SLSpiHost.exe) succeeded.
2023-07-03 07:43:42 11580|Send alarm for process disappearance SLSpiHost.exe (bDoClear = FALSE)
2023-07-03 07:43:42 11580|Send alarm for process disappearance SLSpiHost.exe FAILED: The RPC server is unavailable. (0x800706bah)
2023-07-03 07:43:42 14240|-> Process with PID 3528 (SLNetCOMService.exe) stopped.
2023-07-03 07:43:42 14912|-> Process with PID 2184 (SLNet.exe) stopped.
2023-07-03 07:43:43 12040|Sending notification e-mail failed. Notification Problem: Mail server (localhost) is unavailable (No connection could be made because the target machine actively refused it. = 0x8007274dh; last response: )
2023-07-03 07:43:43 18288|Restarting
2023-07-03 07:43:50 6740|NOT Resetting IP addresses (no DRS configuration active)
issue resolved
its because of dataminer 10.3 upgrade.
https://docs.dataminer.services/user-guide/Troubleshooting/Known_issues/KI_Restart_loop_when_Elasticsearch_unavailable.html
If you go to Services and find SLDataMiner, what is the startup type you see there ?
Also, what does the last few lines of SLDataMiner.txt log file in C: –> Skyline DataMiner –> Logging folder say ?