Skip to content
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.

Scripts not running although logs show they ran successfully #90

Open
conner-lotus opened this issue Dec 29, 2021 · 3 comments
Open

Scripts not running although logs show they ran successfully #90

conner-lotus opened this issue Dec 29, 2021 · 3 comments

Comments

@conner-lotus
Copy link

I am new to Outset. The test scripts I have setup are not executing the results. Not sure what I am missing.

  • fresh Monterrey Mac

  • installed Python3 (using link on Outset page)

  • installed Outset-3.0.3 .pkg

  • created simple test scripts (lo.sh) for each scenario (such as login-once).
    Sleep 10
    touch /Users/Shared/lo.txt

  • Permissions and ownership for the script show this:
    -rwxr-xr-x 1 root wheel 36 Dec 29 14:53 /usr/local/outset/login-once/lo.sh

  • outset logs show this:
    2021-12-29 03:10:52 PM - INFO: Processing /usr/local/outset/login-once/lo.sh

For this instance, there was only one line in the log.

Does this indicate success? the lo.txt file was not created automatically. However when I run this script through terminal the lo.txt file is successfully created.

What am I missing?

Thanks in advance.

@kkordisch
Copy link

I am seeing similar issues on 12.1.

@arubdesu
Copy link
Contributor

Hey there, "Installed python3" is unfortunately not enough info in 2021, as there are several versions depending on the source. Do you see an entry for your script when you run this command:

defaults read ~/Library/Preferences/com.github.outset.once.plist

? I can tell you it does work in my environment using munki-python and scripts using either that python in the shebang or /bin/bash.

@conner-lotus
Copy link
Author

I installed Python 3.10.1 from the Python website, https://www.python.org/downloads/ .

@arubdesu This is the output I got running the command you suggested:
2021-12-30 10:19:16.203 defaults[798:25814]
Domain /Users//Library/Preferences/com.github.outset.once.plist does not exist

However, I updated the shebang in each script and added an exit statement, and it seems to have resolved the issue.

Thanks for the assistance!

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

No branches or pull requests

3 participants