Skip to content

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

@mallej

Description

@mallej

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions