Posted on 10-22-2018 05:56 AM
I had setup the whole set of tools to get patch management from an external source:
- PatchServer set up and running
- Patch definitions created with PatchStarter and uploaded to the server
- JSS configured to pull definitions from the PatchServer
- Patch policies relying on all these pieces
Then, I tried to upload new updated definitions and all the apps that I'm tracking went to 0 machines on the latest version, 0 machines on other versions, 0 completed and 0 pending on the policies…
In a way, it seems as if the definition is broken or sending information that does not work on the JSS side, so I have tried from manually editing the json files to deleting everything and configuring it all again with no luck.
Has anybody here had similar issues? Any ideas to get this back up and running?
Posted on 10-22-2018 07:01 AM
Had this once, along with it not updating the latest known version number for a patch.
A restart of the Tomcat service brought it back to life for me.
Posted on 10-23-2018 12:49 AM
So, today when I arrived at the office the numbers where there…
Tomcat wasn't restarted so it seems to me that the JSS pulls this info and updates the queries only a few times a day instead of doing it "live".