05-16-2019 02:10 PM
I am running into an issue on one PC where I get an error dialog on Systemlink saying "The changes failed to apply" when trying to add feeds to a PC.
Here is an excerpt from the salt minion log file:
2019-05-16 11:21:21,574 [salt.transport.tcp:1015][ERROR ][3904] Got response for message_id 1 that we are not tracking
2019-05-16 11:22:20,260 [salt.transport.tcp:1015][ERROR ][3100] Got response for message_id 1 that we are not tracking
2019-05-16 11:23:18,620 [salt.transport.tcp:1015][ERROR ][4364] Got response for message_id 1 that we are not tracking
2019-05-16 11:24:17,094 [salt.transport.tcp:1015][ERROR ][11548] Got response for message_id 1 that we are not tracking
2019-05-16 11:36:42,886 [salt.minion :1918][WARNING ][11920] The minion failed to return the job information for job 20190516083633196095_6680. This is often due to the master being shut down or overloaded. If the master is running, consider increasing the worker_threads value.
2019-05-16 11:38:18,997 [salt.minion :1918][WARNING ][11920] The minion failed to return the job information for job 20190516083813688330_8908. This is often due to the master being shut down or overloaded. If the master is running, consider increasing the worker_threads value.
The whole file is mostly that "Got response for message_id..." message, but right at the end, around when i tried to add the feed is where I see the "The minion failed..." error.
Does anyone have any ideas what might be going wrong?
Thanks
05-17-2019 10:21 AM
What version of the SystemLink Server are you running? Also, are there other feeds already installed on the target you are trying to deploy to?
05-24-2019 08:07 AM
Is there a way to see what version of SystemLink Server is being used through the SystemLink Web Application?
05-24-2019 12:18 PM
Not from the SystemLink Web App UI. You would need to open NIPM on the server to determine what version it's running.
05-31-2019 12:02 PM
We are running Systemlink server version 18.2
05-31-2019 02:52 PM
We’ve fixed a bunch of Systems Management Issues since 18.2. This sounds similar to others we saw. Are you able to upgrade to 19.0?