question-mark
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.

Log full of "Daemon running." messages

See original GitHub issue

Expected behaviour:

log be useful 😃 Perhaps change this specific message to debug level output?

Actual behaviour:

At some point, the log began to be flooded with this message, but I am not sure why as I have not seen this behaviour in the past. I note the line of code generating it (manager.py line 502) has not changed recently. I would expect this to be perhaps shown at the debug level?

Log Snippet:

(click to expand)
2020-09-12 10:51:59 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:52:30 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:53:00 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:53:31 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:53:38 INFO     task          search-tv       Plugin next_series_episodes has requested task to be ran again after execution has completed. Reason: Look for next season
2020-09-12 10:54:02 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:54:18 INFO     task          search-tv       Rerunning the task in case better resolution can be achieved.
2020-09-12 10:54:32 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:54:34 ERROR    api_bluray    search-movies   Error refreshing movie details for Mulan from blu-ray.com, cached info being used. No search results found for Mulan (2020) on blu-ray.com
2020-09-12 10:54:41 ERROR    api_bluray    search-movies   Error refreshing movie details for Ava from blu-ray.com, cached info being used. No search results found for Ava (2020) on blu-ray.com
2020-09-12 10:55:03 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:55:34 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:56:04 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:56:35 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:57:05 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:57:36 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:58:07 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:58:37 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:59:08 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 10:59:39 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:00:09 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:00:40 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:01:11 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:01:41 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:02:12 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:02:43 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:03:14 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:03:44 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:04:15 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:04:46 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:05:16 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:05:47 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:06:18 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:06:48 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:07:19 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:07:50 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:08:20 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:08:51 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:09:22 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:09:52 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:10:23 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:10:53 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:11:24 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:11:55 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:12:26 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:12:56 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:13:27 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:13:57 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:14:28 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:14:59 INFO     manager                       Daemon running. (PID: 269)
2020-09-12 11:15:30 INFO     manager                       Daemon running. (PID: 269)

Additional information:

  • FlexGet version: 3.1.71
  • Python version: 3.8.5
  • Installation method: docker
  • Using daemon (yes/no): yes
  • OS and version: ubuntu
  • Link to crash log:

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
ksurlcommented, Oct 10, 2020

@AspenScythe we have a pull request pending review for an official image. however, frankyw is probably talking about wiserain’s image (the one who commented here).

0reactions
gazpachokingcommented, May 4, 2021

I’ve moved this message to debug log, and changed the flexget daemon status command to output it directly to the console. https://github.com/Flexget/Flexget/commit/93715a77a3813a63d9bc441bd2252af8b5cd1edc

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to see full log from systemctl status service?
Just use the journalctl command, as in: journalctl -u service-name.service. Or, to see only log messages for the current boot:
Read more >
Set daemon message log to debug level - IBM
The message log level for LSF daemons is set in lsf.conf with the parameter LSF_LOG_MASK. ... The root RES is the RES that...
Read more >
How to get the logs for a daemon process on Linux
I tried to look for logs and couldn't find it... I tried to check under /var/log/messages/ there is no folder called messages ....
Read more >
How To Use Journalctl to View and Manipulate Systemd Logs
Basic Log Viewing. To see the logs that the journald daemon has collected, use the journalctl command. When used alone, every journal entry ......
Read more >
Logging in New-Style Daemons with systemd - Loggly
The protocol for this log emission is as simple as it could be: Every line is one log message. The process manager is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found