You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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)
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
The text was updated successfully, but these errors were encountered: