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

Suite log, out, err rotation should be synchronized #1446

Closed
hjoliver opened this issue May 6, 2015 · 6 comments
Closed

Suite log, out, err rotation should be synchronized #1446

hjoliver opened this issue May 6, 2015 · 6 comments
Assignees
Milestone

Comments

@hjoliver
Copy link
Member

hjoliver commented May 6, 2015

Currently these are rotated independently according to file size. It would be better to rotate all files with the log (which is biggest), so that the content matches across them all.

@hjoliver hjoliver added this to the soon milestone May 6, 2015
@arjclark
Copy link
Contributor

arjclark commented May 7, 2015

+1 - Very much agreed.

@matthewrmshin
Copy link
Contributor

See also #386.

@matthewrmshin
Copy link
Contributor

I must admit I am a bit confused by the current setting with these multiple modules:

  • cylc.suite_logging, which deals with log and err.
  • cylc.suite_log_interface, which provides a Pyro interface to err via cylc.suite_logging.
  • cylc.suite_output, which deals with out and err.

We need to do something to rationalise these.

@hjoliver
Copy link
Member Author

(a late-night look-in here)

We need to do something to rationalise these.

Yes, hence #386 (2 yrs old, gack).

In historical context it's not completely insane, however: cylc.suite_logging just configures the standard python logging facility (log message format etc.), which (as configured) happens to write WARNING and CRITICAL messages to stderr as well as the event log; cylc.suite_output redirects sys.std(out|err) to the suite log directory (this was added when the server became daemonizable?); and cylc.suite_log_interface is the new(ish) Pyro interface to the err log (this is used only by the gcylc info bar to highlight warnings and errors).

@matthewrmshin
Copy link
Contributor

See also #846.

@hjoliver
Copy link
Member Author

hjoliver commented Jun 19, 2016

We agreed this should still be done.

@hjoliver hjoliver modified the milestones: later, soon Jun 23, 2016
@oliver-sanders oliver-sanders self-assigned this Jul 13, 2016
@matthewrmshin matthewrmshin modified the milestones: next release, later Sep 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants