Ticket #10279 (closed Bug Report - General: fixed)
Opened 16 months ago
Last modified 11 months ago
spamming logs with shutdown messages
| Reported by: | brian@… | 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 danielk) (diff)
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
Change History
comment:1 Changed 11 months ago by beirdo
- Owner set to gigem
- Status changed from new to assigned
comment:2 Changed 11 months ago by beirdo
- Owner changed from gigem to beirdo
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 Changed 11 months ago by George Nassas <gnassas@…>
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 Changed 11 months ago by beirdo
Ahhh, very helpful. OK, that makes it easier to determine the actual issue.
comment:5 Changed 11 months ago by danielk
- Owner changed from beirdo to danielk
- Status changed from assigned to accepted
- Version changed from Unspecified to Master Head
- Milestone changed from unknown to 0.26
Changed 11 months ago by danielk
- Attachment 10279-v1.patch added
David's patch + comment ; this should fix the problem it just needs some testing before applying.
comment:7 Changed 11 months ago by David Engel <dengel@…>
- Status changed from accepted to closed
- Resolution set to fixed
comment:8 Changed 11 months ago by David Engel <dengel@…>
comment:9 Changed 11 months ago by kenni
- Owner changed from danielk to gigem
- Milestone changed from 0.26 to 0.25.2

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