Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"tail -F" sometime fail to follow new log file
See original GitHub issueOn Linux it looks like tail -F may not reliably follow new log files. When this happens, chiadog will report “Your harvester appears to be offline”, and inspecting the /proc file system shows that the tail process is still opening the old log file, eg. .chia/mainnet/log/debug.log.11.
Environment:
- OS: Ubuntu 20.04
- Python version: 3.8.5
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (1 by maintainers)
Top Results From Across the Web
`tail -f` sometimes stops updating - and the file hasn't moved
Doing a Ctrl> - C and restarting the tail works fine, though. And I checked to make sure the logfile isn't being rotated...
Read more >tail" fail to produce any output? - Unix & Linux Stack Exchange
tail -f 's tail is actually something unknown in the present, ... X lines of the file, then using some OS magic (like...
Read more >Following log files with tail -f - David Winterbottom
Today's was the 'follow' option of the tail command. It's commonplace to use tail for viewing the recent entries to a log file:....
Read more >'tail -f' does not follow when file updated using 'tee'
The file is closed and reopened when tail detects that the filename being read from has a new inode number. The -F option...
Read more >tail -f doesn't work properly · Issue #3942 · microsoft/WSL
run tail -f testsrv.log. not follow when file growing.then ls testsrv.log in another wsl console. it output new contents.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Official release is out. This is hopefully resolved, please reopen issue if not.
This bug is what prevent me to use this software for production monitoring. Overall, very good job. Concerning the issue, I have a couple ideas on how it ccould be at least be dirty fixed before making better code for the long run. The simpliest drity fix for now could be:
When ‘Your harvester appears to be offline! No events for the past X seconds.’ is detected, the code could just try to reload log consumer first before sending warning.