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

autopkgserver: autopkgserver should report /Library ownership issues to a file, rather than console only output. #830

Open
rslowe opened this issue Oct 13, 2022 · 0 comments · May be fixed by #831

Comments

@rslowe
Copy link

rslowe commented Oct 13, 2022

Describe the problem
AutopkgServer assumes that /Library is owned by root:wheel, and will immediately crash out if it isn't. This is presumably done to ensure that nothing else on the box can modify what AutopkgServer is doing. AutoPkgServer will enter a launchd crash loop (where launchctl will continuously attempt to restart the autopkgserver, and autopkgserver will kill itself due to the ownership problem) and not obviously report this problem to any external logs. (Only sign is a generic "1" exit code)

AutoPkgServer output
This output can only be obtained by running AutoPkgServer Interactively (not via the LaunchCTL kickstart command)

[root@buildbot ~]# /Library/AutoPkg/autopkgserver/autopkgserver
/Library/AutoPkg/autopkgserver must have group wheel or admin.
/Library/AutoPkg must have group wheel or admin.
/Library must be owned by root.
/Library must have group wheel or admin.

Expected behavior
This error information should be logged to a file on disk, similar to the regular autopkgserver logs at /var/log/autopkgserver. This allows easier troubleshooting of the autopkgserver in its intended environment.

Version

  • OS version: 12.5
  • AutoPkg Version: 2.7
@rslowe rslowe changed the title AutopkgServer should report /Library ownership issues to a file, rather than console only output. autopkgserver: autopkgserver should report /Library ownership issues to a file, rather than console only output. Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant