+1Hello there everyone,
I have come across a very weird issue lately.
Any policy that I add to Self Service+ fail to run, while if I open Terminal and run jamf policy -event TRIGGER it works like a charm.
The policy does not matter it if includes a package or a script. It has been driving me nuts.
Tried on different machines and re-installing Self Service+ app.
Thank you in advance,
Spyros
+2Hi
Is there anything showing in the jamf.log or in the policy logs on JAMF Pro ? Also forgot to add what do you have set as the Trigger for the policy to run ?
+1Hi,
Only thing available in jamf.log is
Thu Feb 12 10:52:43 SRB-L-RLWV3XR5J6 jamf[2002]: Removing existing launchd task /Library/LaunchAgents/com.jamfsoftware.jamfhelper.plist...
Thu Feb 12 10:52:43 SRB-L-RLWV3XR5J6 jamf[2002]: Checking for policy ID 42...
Thu Feb 12 10:53:07 SRB-L-RLWV3XR5J6 jamf[2067]: Removing existing launchd task /Library/LaunchDaemons/com.jamfsoftware.task.bgrecon.plist…
On Jamf Pro logs, looks like the policies are still pending.
+26Is this just on one device or is it on many? Also what happens if you run something like recon?
When you run sudo Jamf policy event -id, there should be a lot of text going on telling you what is happening. Are you getting any of that or is it just erroring out? I’m wondering if you have some network filtering going on.
+1Is this just on one device or is it on many? Also what happens if you run something like recon?
When you run sudo Jamf policy event -id, there should be a lot of text going on telling you what is happening. Are you getting any of that or is it just erroring out? I’m wondering if you have some network filtering going on.
Hi,
jamf policy -event works just fine. It only fails through Self Service.
I have also tried creating a policy with just the package an a trigger word.
Then a second policy which just had a command in it (jamf policy -event TRIGGER) and it fails as well.
When it fails I don’t see any error, neither on .log nor on Jamf Pro.
+26What do the self service logs say? May also be a good idea to run a log filter and watch what is being chattered about when policies are running.
+1Hello everyone,
I managed to narrow down the problem a bit. What it looks like is that Self Service+ is calling a policy using policy id and not event trigger.
So if I go to Terminal and type in
sudo jamf policy -id 47 it fails as well, saying
No policies were found for the ID 47
Meanwhile is the computer is in scope and ongoing frequency is on.
Same happens to other policies, but not all of them, without a specific pattern.
+27While I’d love to offer a brilliant solution, this really sounds like it’s time for a ticket with Support. It’s possible that there is some database corruption. Not saying I’ve experienced that, but that is a pretty weird failure.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.