This question was originally posted on DCIM Support by Christopher Ramsay on 2019-11-13
Hello, I had a post back in March 2019 of the same question header where my ETL integrations would stop running and it had something to do with the job scheduler being stuck. We did some back and forth and ultimately a reboot caused the job scheduler to re-initialize and my ETL integrations would run again. Since then, I have a couple other instances where the same issue has happened (ETL jobs stop running), and when I saw this I did a reboot and it fixed the issue. I just noticed that this has happened again, but now multiple reboots have not solved the issue for me and my jobs are still stuck. What can I do to get these jobs to run again?
This comment was originally posted on DCIM Support by Jef Faridi on 2019-11-18
I will send you an invite to my =S= box shortly so the data safely can be shared with me. If you could provided the following data, then I will take a look and see what might be the issue/cause:
1. server logs
(in earlier 8.x such as 8.2.2, server logs can be collected from server Webmin interface, StruxureWare DC Operation > Download Log Files > Download log files)
2- latest backup file
(backup files usually located in the /data/backup folder)
3- short description of the ETL job, eg. what is expected from the ETL integration.
4- when (date/time) do you experience the issue and how do you see that? include screen captures illustrating your issue experience on screen.
5- Do you know if =S= has been involved with your ETL implementation?
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!