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.

Sign up for GitHub

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

Jump to bottom

no logs on mainnet sentinel-a #114

Closed
troggy opened this issue Jun 18, 2019 · 2 comments
Closed

no logs on mainnet sentinel-a #114

troggy opened this issue Jun 18, 2019 · 2 comments
Labels
operations

Comments

@troggy
Copy link
Member

troggy commented Jun 18, 2019 •
edited
Loading

Make sure the sentinel is writing logs
@troggy
Copy link
Member Author

troggy commented Jun 18, 2019

logrotate + logging to a file = problem

While you appear to be logging to a file, you are really logging to a file descriptor. After log rotation by an external application, the application continues to log to a file descriptor, but now it is no longer connected with the file, which has been re-created through log rotation. While the log may be empty, your disk space may well be continuing to increase.

More details: foreversd/forever#106 (comment)

Simplest workaround is to add copytruncate, proper solution is to log to STDOUT and let systemd handle the logging

@troggy
Copy link
Member Author

troggy commented Jul 8, 2019

solved. Logging to STDOUT now. Applied on mainnet only

leapdao/leap-node#286

@troggy troggy closed this as completed Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
operations
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@troggy