[mythtv] mythfilldatabase loops (was: mythbackend random segmentation fault)

Thu Jun 28 13:26:58 UTC 2007

I have a remaining problem with mythfilldatabase: I use tv_grab_be to 
gather program information and use this xml information to feed 
mythfilldatabase. The TV guide is updated, but mythfilldatabase loops;

$ /usr/bin/mythfilldatabase --file 1 -1 /home/mythtv/.mythtv/tvblad -v all
--- snip ---
===============================================================
| Attempting to contact the master backend for rescheduling.  |
| If the master is not running, rescheduling will happen when |
| the master backend is restarted.                            |
===============================================================
2007-06-28 15:07:32.636 MSqlQuery: SELECT data FROM settings WHERE value 
= 'MasterServerIP' AND hostname = 'primus' ;
2007-06-28 15:07:32.637 MSqlQuery: SELECT data FROM settings WHERE value 
= 'MasterServerIP' AND hostname IS NULL;
2007-06-28 15:07:32.637 MSqlQuery: SELECT data FROM settings WHERE value 
= 'MasterServerPort' AND hostname = 'primus' ;
2007-06-28 15:07:32.638 MSqlQuery: SELECT data FROM settings WHERE value 
= 'MasterServerPort' AND hostname IS NULL;
2007-06-28 15:07:32.639 MythSocket(840fa80:7): new socket
2007-06-28 15:07:32.640 MSqlQuery: SELECT data FROM settings WHERE value 
= 'WOLbackendReconnectWaitTime' AND hostname = 'primus' ;
2007-06-28 15:07:32.641 MSqlQuery: SELECT data FROM settings WHERE value 
= 'WOLbackendReconnectWaitTime' AND hostname IS NULL;
2007-06-28 15:07:32.642 MSqlQuery: SELECT data FROM settings WHERE value 
= 'WOLbackendConnectRetry' AND hostname = 'primus' ;
2007-06-28 15:07:32.643 MSqlQuery: SELECT data FROM settings WHERE value 
= 'WOLbackendConnectRetry' AND hostname IS NULL;
2007-06-28 15:07:32.643 Connecting to backend server: 192.168.1.250:6543 
(try 1 of 5)
2007-06-28 15:07:32.643 MythSocket(839ed10:8): new socket
2007-06-28 15:07:32.643 MythSocket(839ed10:8): attempting connect() to 
(192.168.1.250:6543)
2007-06-28 15:07:32.643 MythSocket(839ed10:8): state change Idle -> 
Connected
2007-06-28 15:07:32.644 write ->  8 21      MYTH_PROTO_VERSION 31
2007-06-28 15:07:32.645 read  <-  8 13      ACCEPT[]:[]31
2007-06-28 15:07:32.669 Using protocol version 31
2007-06-28 15:07:32.669 write ->  8 20      ANN Monitor primus 0
2007-06-28 15:07:32.976 read  <-  8 2       OK
2007-06-28 15:07:32.977 MythSocket(840fa80:7): attempting connect() to 
(192.168.1.250:6543)
2007-06-28 15:07:32.977 MythSocket(840fa80:7): state change Idle -> 
Connected
2007-06-28 15:07:32.977 write ->  7 20      ANN Monitor primus 1
2007-06-28 15:07:32.982 read  <-  7 2       OK
2007-06-28 15:07:32.982 MythSocket(840fa80:7): UpRef: 1
2007-06-28 15:07:32.983 write ->  8 24      RESCHEDULE_RECORDINGS -1
2007-06-28 15:07:32.983 read  <-  8 1       1
2007-06-28 15:07:32.983 write ->  8 32      MESSAGE[]:[]CLEAR_SETTINGS_CACHE
2007-06-28 15:07:32.984 read  <-  8 2       OK
2007-06-28 15:07:32.984 MythSocket(839ed10:8): DownRef: -1
2007-06-28 15:07:32.984 MythSocket(839ed10:8): state change Connected -> 
Idle
2007-06-28 15:07:32.984 MythSocket(839ed10:-1): delete socket
2007-06-28 15:07:32.984 MythSocket(840fa80:7): DownRef: 0
2007-06-28 15:07:32.986 MythSocket: readyread thread start
2007-06-28 15:07:32.986 MythSocket(840fa80:7): socket is readable
2007-06-28 15:07:32.986 MythSocket(840fa80:7): socket is readable
2007-06-28 15:07:32.986 MythSocket(840fa80:7): socket is readable
2007-06-28 15:07:32.987 MythSocket(840fa80:7): socket is readable

The last four lines are repeated endlessly (it seems to hang if I'm not 
running in debug mode), so I have to kill mythfilldatabase each time. 
It's again related to mysql, but I don't find similar problems on the 
internet.

Kind regards,
Jan

PS: note for belgian users: perhaps we should schedule one xml file that 
everyone can download?

Jan Tiri wrote:
> Paul,
>
> Thanks for the hint! I recompiled qt3 with mysqlclient_r and it seems to
> run stable now. Let's hope all other applications keep doing so and
> there will be a separate USE flag for that in Gentoo one day.
>
> primus / # ldd /usr/qt/3/plugins/sqldrivers/libqsqlmysql.so
>         libmysqlclient_r.so.15 => /usr/lib/libmysqlclient_r.so.15
> (0xb7dd1000)
>
> Kind regards,
> Jan
>
> Paul Andreassen wrote:
>   
>> On Tuesday 19 June 2007 07:53, Jan Tiri wrote:
>>   
>>     
>>> I experience segmentation faults when I start mythbackend. If it does
>>> start (sometimes directly, mostly after the third time) it crashes after
>>> doing some manipulations, but rarely during watching life tv.
>>>
>>> mythtv at primus ~ $ uname -a
>>> Linux primus 2.6.20-gentoo-r8 #2 PREEMPT Wed Jun 13 21:21:00 CEST 2007
>>> i686 AMD Athlon(TM) XP 2000+ AuthenticAMD GNU/Linux
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> [Switching to Thread -1247500608 (LWP 15597)]
>>> 0xb57eb218 in _db_return_ () from /usr/lib/libmysqlclient.so.15
>>>
>>>     
>>>       
>> Going to http://www.gossamer-threads.com/lists/mythtv/ and searching 
>> for "libmysqlclient gentoo" suggests a buggy QT using libmysqlclient instead 
>> of libmysqlclient_r.
>>
>> http://www.gossamer-threads.com/lists/mythtv/dev/202250#202250
>>
>> Paul
>>
>>   
>>     
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>   