Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

service-status-ea.sh shows wrong status in Jamf #59

Open
mallej opened this issue Nov 28, 2024 · 0 comments
Open

service-status-ea.sh shows wrong status in Jamf #59

mallej opened this issue Nov 28, 2024 · 0 comments

Comments

@mallej
Copy link

mallej commented Nov 28, 2024

Describe the bug
When using service-status-ea.sh as an Extension Attribute the output is shown as "Not Healthy"
Running the script locally as root shows the correct status "Healthy"

Testing with
/usr/local/outset/outset --service-status
shows

INFO: getting Services status
INFO: LaunchDaemon(io.macadmins.Outset.boot.plist) status: Enabled
INFO: LaunchDaemon(io.macadmins.Outset.login-privileged.plist) status: Enabled
INFO: LaunchDaemon(io.macadmins.Outset.cleanup.plist) status: Enabled
INFO: LaunchAgent(io.macadmins.Outset.login.plist) status: Enabled
INFO: LaunchAgent(io.macadmins.Outset.on-demand.plist) status: Enabled
INFO: LaunchAgent(io.macadmins.Outset.login-window.plist) status: Enabled

Expected behavior
The Extension Attribute shows "Healthy" in Jamf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant