Opened 9 years ago

Closed 8 years ago

#9583 closed Bug Report - Hang/Deadlock (Upstream Bug)

[HANG] Deadlock in backend on starting a new recording?

Reported by: mythtv@… Owned by: stuartm
Priority: critical Milestone: 0.25
Component: MythTV - EIT Version: 0.24-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Not sure about this, but maybe a deadlock in some threads? Sometimes scheduled recordings are not recorded and the frontend goes very slow when this happens. Also the recordings screen on the frontend is empty until I restart the backend. I waited about 15-20 minutes here before I restarted.

2011-02-13 15:11:55.225 Reschedule requested for id 0.
2011-02-13 15:11:55.348 Scheduled 17 items in 0.1 = 0.04 match + 0.08 place
2011-02-13 15:12:03.695 Reschedule requested for id -1.
2011-02-13 15:12:03.880 Scheduled 17 items in 0.2 = 0.10 match + 0.08 place
2011-02-13 15:12:24.165 TVRec(1): ASK_RECORDING 1 29 0 0
2011-02-13 15:12:24.805 TVRec(2): ASK_RECORDING 2 29 0 0
2011-02-13 15:21:17.457 AutoExpire: CalcParams(): Max required Free Space: 5.0 GB w/freq: 15 min

As you can see, the "Changing from None to RecordingOnly?" line never showed up.

Any debug-level flags you want me to enable until next time it happens? I've had "important,general" until now, but added "record,channel".

Attachments (3)

backend.gdb (28.2 KB) - added by mythtv@… 9 years ago.
Backtrace on runnig process
myth_bug.log.gz (31.6 KB) - added by mythtv@… 9 years ago.
Log with more verbose flags
version_info (536 bytes) - added by Raymond Wagner 9 years ago.

Download all attachments as: .zip

Change History (10)

Changed 9 years ago by mythtv@…

Attachment: backend.gdb added

Backtrace on runnig process

comment:1 Changed 9 years ago by beirdo

Summary: Deadlock in backend on starting a new recording?[HANG] Deadlock in backend on starting a new recording?

Please attach the version of mythbackend you are running (mythbackend --version)

comment:2 Changed 9 years ago by beirdo

Component: MythTV - GeneralMythTV - EIT
Owner: set to Stuart Auchterlonie

Seems to be EIT related. Possibly a dupe of #9261

comment:3 Changed 9 years ago by mythtv@…

I used v0.24-158-g48d554e-dirty the last time this happened. This time is v0.24-177-g316718a-dirty as per the attached version_info.

And some other info from the backend server, I use separate frontend/backend system.

# snippet from /proc/cpuinfo
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 95
model name      : AMD Athlon(tm) Processor LE-1600
stepping        : 3
cpu MHz         : 2209.887

# grep -i dvb /var/log/dmesg
DVB: registering new adapter (Satelco EasyWatch DVB-C MK3)
DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...
DVB: registering new adapter (Satelco EasyWatch DVB-C MK3)
DVB: registering adapter 1 frontend 0 (Philips TDA10023 DVB-C)...

# uname -a
Linux vdr-be 2.6.34-gentoo-r1 #1 SMP Tue Jul 27 10:26:21 EEST 2010 i686 AMD Athlon(tm) Processor LE-1600 AuthenticAMD GNU/Linux
Last edited 9 years ago by Raymond Wagner (previous) (diff)

comment:4 Changed 9 years ago by mythtv@…

Got some more logs now with more verbose flags.

Happened again yesterday while watching LiveTV and a recording was about to start. LiveTV show froze and the recording did not start so I restarted backend so the recording could start as seen around 2011-02-18 22:02 in the log.

Still on v0.24-177-g316718a-dirty

Changed 9 years ago by mythtv@…

Attachment: myth_bug.log.gz added

Log with more verbose flags

Changed 9 years ago by Raymond Wagner

Attachment: version_info added

comment:5 Changed 8 years ago by stuartm

Milestone: unknown0.25
Priority: minorcritical
Type: Bug ReportBug Report - Hang/Deadlock

This should at least get looked at once before 0.25 is out

comment:6 Changed 8 years ago by Stuart Auchterlonie

Owner: changed from Stuart Auchterlonie to stuartm
Status: newassigned

Unfortunately i'm not going to get a chance to look at it.

comment:7 Changed 8 years ago by danielk

Resolution: Upstream Bug
Status: assignedclosed

The problem here appears to be the mysql server going out to lunch.

Note: See TracTickets for help on using tickets.