Tweet
Here is an FYI and a potential feature request.
We use an Environment Variable to define where the vrlclient.xml lives. The problem is apparently installers can overwrite this file and will overwrite this file based on the environment variable path.
So what we had happening was that every time a slave detected it was out-of-date and updated it would run a vray or phoenix installer whose XML defined the chaos group license information. As soon as another installer would execute which had the correct settings it too would then load the vrlclient.xml and overwrite it again.
What we were seeing was that the licenses were spontaneously succeeding and then failing and then succeeding at random times on our farm with no obvious cause even on the same machine. Checking the xml would result in it being correct, but it would be random when it would be right and when it would be wrong so troubleshooting missed the temporal nature of the file constantly changing.
I recommend changing the installer logic if possible to *not* write to an xml file if it's not-local or the path is defined by an environment variable. We solved the issue for "good" by setting the file properties to read-only. Hopefully that will prevent it from happening to us again but if you are getting super random -7 server denied access errors... make sure you don't have installers triggering on the farm which include license settings.
We use an Environment Variable to define where the vrlclient.xml lives. The problem is apparently installers can overwrite this file and will overwrite this file based on the environment variable path.
So what we had happening was that every time a slave detected it was out-of-date and updated it would run a vray or phoenix installer whose XML defined the chaos group license information. As soon as another installer would execute which had the correct settings it too would then load the vrlclient.xml and overwrite it again.
What we were seeing was that the licenses were spontaneously succeeding and then failing and then succeeding at random times on our farm with no obvious cause even on the same machine. Checking the xml would result in it being correct, but it would be random when it would be right and when it would be wrong so troubleshooting missed the temporal nature of the file constantly changing.
I recommend changing the installer logic if possible to *not* write to an xml file if it's not-local or the path is defined by an environment variable. We solved the issue for "good" by setting the file properties to read-only. Hopefully that will prevent it from happening to us again but if you are getting super random -7 server denied access errors... make sure you don't have installers triggering on the farm which include license settings.
Comment