jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

[dataloss bug] Log file truncated on disk #52

New Issue
Closed
opened 2026-01-19 18:31:22 +00:00 by michael · 2 comments
michael commented 2026-01-19 18:31:22 +00:00
Owner
Copy Link

Originally created by @fraserhess on GitHub.

I'm not sure if this is new in 1.3 or because of a finishedTrigger in 1.3, but let me explain.

Reproducibly, I have an incomplete log file at /Library/Logs/Setup Manager.log. It's around 12Kb in size and stops in the middle of a log message. (I am happy to provide an example file privately.)

Perhaps relevant to 1.3, I am testing a finishedTrigger that installs Jamf Connect and restarts. It's possible that either the Jamf Connect install kills the loginwidow and Setup Manager processes is doing so before the log file is written to disk or the shutdown command is cancelling a deferred write.

Originally created by @fraserhess on GitHub. I'm not sure if this is new in 1.3 or because of a `finishedTrigger` in 1.3, but let me explain. Reproducibly, I have an incomplete log file at `/Library/Logs/Setup Manager.log`. It's around 12Kb in size and stops in the middle of a log message. (I am happy to provide an example file privately.) Perhaps relevant to 1.3, I am testing a `finishedTrigger` that installs Jamf Connect and restarts. It's possible that either the Jamf Connect install kills the loginwidow and Setup Manager processes is doing so before the log file is written to disk or the `shutdown` command is cancelling a deferred write.
michael added the bug label 2026-01-19 18:31:22 +00:00
michael commented 2026-01-19 18:31:22 +00:00
Author
Owner
Copy Link

@fraserhess commented on GitHub:

12458 bytes seems to be the important limit.

Testing results:
1.3 beta with 1.3 configuration (finalAction: none; finishedTrigger): log truncated at 12458 bytes
1.3 beta with 1.2 configuration (finalAction: restart; no finishedTrigger): log is still truncated at 12458 bytes
1.2.2 with 1.2 configuration: log is 65652 bytes

@fraserhess commented on GitHub: 12458 bytes seems to be the important limit. Testing results: 1.3 beta with 1.3 configuration (finalAction: none; finishedTrigger): log truncated at 12458 bytes 1.3 beta with 1.2 configuration (finalAction: restart; no finishedTrigger): log is still truncated at 12458 bytes 1.2.2 with 1.2 configuration: log is 65652 bytes
michael commented 2026-01-19 18:31:22 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

fixed in 1.3

@scriptingosx commented on GitHub: fixed in 1.3
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#52
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?