Opened 14 years ago
Closed 13 years ago
Last modified 13 years ago
#10279 closed Bug Report - General (fixed)
spamming logs with shutdown messages
| Reported by: | Owned by: | gigem | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.25.2 |
| Component: | MythTV - General | Version: | Master Head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description (last modified by )
I have noticed recently on v0.25pre-3930-g074d3e2 when the backend is logging shutdown events it spams the log with the same message hundreds of times over the span of a second or two such as:
2012-01-23 07:29:53.423755 N [1595/2013] Scheduler scheduler.cpp:2624 (HandleIdleShutdown) - I'm idle now... shutdown will occur in 300 seconds. 2012-01-23 07:29:53.425268 N [1595/2013] Scheduler scheduler.cpp:2624 (HandleIdleShutdown) - I'm idle now... shutdown will occur in 300 seconds. <<<snip>>>
This seems unnecessary.
Attachments (1)
Change History (10)
comment:1 by , 13 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
| Owner: | changed from to |
|---|
Could you run the backend with -v schedule please? This will turn on some more logging right where the timeouts are happening, and I'd like to see what code path it's following when in this state.
Thanks.
comment:3 by , 13 years ago
Here are two logs which have -v schedule and exhibit the problem. The first is >4MB and the second ~ 600K. Search for "(run) - sleeping for 0 ms".
http://files.nassas.com/mythbackend.20120707095825.2687.log.bz2 http://files.nassas.com/mythbackend.20120708075339.2420.log.bz2
comment:4 by , 13 years ago
Ahhh, very helpful. OK, that makes it easier to determine the actual issue.
comment:5 by , 13 years ago
| Milestone: | unknown → 0.26 |
|---|---|
| Owner: | changed from to |
| Status: | assigned → accepted |
| Version: | Unspecified → Master Head |
by , 13 years ago
| Attachment: | 10279-v1.patch added |
|---|
David's patch + comment ; this should fix the problem it just needs some testing before applying.
comment:7 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
comment:9 by , 13 years ago
| Milestone: | 0.26 → 0.25.2 |
|---|---|
| Owner: | changed from to |

It wouldn't surprise me if this were fixed now, but let's hand it to the person who knows the scheduler best.