I can similarly confirm that there is no interaction from any third party software when this truncation/corruption/loss happens.
And the 10% damage is roughly what I saw when using versions of hub and controller from the pre-hub-7.72 era. I have seen a significant reduction in the number of occurrences using the 7.95 controller and 7.93 hub but not to the point of eliminating the problem - probably 1 in a 100 occurence instead of 1 in 10.
It feels like there's a race condition that occurs when package updates are applied. Mainly because I can add to this cfg file corruption behavior an additional failure to successfully complete the installation of all package files. Typically files will get staged in robot/pkg/temp and then the new files get copied to the destination with a .new extension, then existing files get renamed with a .old extension, then the .new files get renamed to the actual final name and the .old files will be removed.
It is very common to find the .old files still in place. less common to find the .new, and pretty common to find the files still in the temp directory with the existing file renamed.
Usually one can fix this by copying the .new files manually to the correct names or removing the .old extension from the existing files.
Happens pretty frequently with hub and controller updates. I've never sen it happen with probes like CDM where there's no robot restart involved.
So my suspicion with this behavior is that the controller is getting restarted too soon - essentially while it is processing the cfx file or moving the install files around.
Just a guess at this point - would love to have confirmation but then if I knew which system was going to be broken ahead of time to grab the logs before and after it happened I'd have started playing the lottery a long time ago and be living on a nicely supplied tropical island far from the concerns of modern day IT.
Original Message:
Sent: 07-12-2019 05:06 AM
From: Christian McHugh
Subject: robot.cfg disappeared from RHEL 7 servers
Hey all,
I've confirmed with our linux teams that we do not run antivirus or backup services on our hosts. So unfortunately, the root case for this behavior is still unknown. We do run uim as a service account (not root). This is a mandate by our infosec team, so we have no ability to change it, but I wonder if that might be related.
Original Message:
Sent: 07-11-2019 12:04 PM
From: Alex Yasuda
Subject: robot.cfg disappeared from RHEL 7 servers
Adding more details about David Michael comments, basically you need to execute this steps:
-> Anti-Virus Protection and Nimsoft
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=47887
------------------------------
Senior Support Engineer
Broadcom
Original Message:
Sent: 05-16-2018 09:24 AM
From: Imran Khan
Subject: robot.cfg disappeared from RHEL 7 servers
Hi Guys,
I received robot inactive alert and when checked, I found that robot.cfg does not exist in the system.
Did anyone faced this issue in their environment?
Kindly Suggest.
Regards,
ImranK