Issue #9595 has been updated by Josh Cooper.
Daniel Pittman wrote: > ...this is nice, but isn't the root cause of the problem on Windows. Ruby > will flush internal buffers safely when it shuts down in the normal case, so > something on Windows is causing it to exit uncleanly, or without the normal > cleanup from triggering that flush. Yep. On Unix, the daemon.stop method gets called to cleanly shutdown, but the same is not true when running puppet agent via third-party service wrapper. I'll file a separate ticket for that. Likely we will need to register a console ctrl handler, SetConsoleCtrlHandler, and close the logs, etc. ---------------------------------------- Bug #9595: logs are not flushed completely https://projects.puppetlabs.com/issues/9595#change-54645 Author: Radosław Antoniuk Status: Accepted Priority: Normal Assignee: Josh Cooper Category: logging Target version: 2.7.x Affected Puppet version: 2.7.5 Keywords: Branch: the puppet and puppet master (v. 2.7.1) logs are not flushed properly to the files. when puppet/puppetmaster is logging through syslog, all is logged properly. if I switch to logging to the file /var/log/puppet/puppet.log, the file is often cut in the middle of the word, e.g.: <pre> [root@server2 manifests]# tail -2 /var/log/puppet/masterhttp.log [2011-09-19 09:12:32] - -> /production/file_metadata/files/config/jpackage50.repo? [2011-09-19 09:12:33] testsrv.domain.com - - [19/Sep/2011:09:12:33 PDT] "PUT /production/r[root@server2 manifests]# </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
