Upstream closed this bug, probably with good reason. Haven't heard of
this happening in recent versions, and even if we did, it would need to
be reproduced and a backtrace caught on a 0.24, and preferrably 0.25
system. If this reoccurs, please open a new ticket.
** Changed in: mythtv (Ubuntu)
** Changed in: mythtv
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/330272
Title:
mythbackend silently fails with QSqlQuery::exec: empty query
To manage notifica
** Changed in: mythtv
Status: New => Confirmed
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Changed in: mythtv (Ubuntu)
Status: Confirmed => Triaged
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
This will require some modifications to the package to support trunk daily
packages in apport unfortunately.
On Thu, Oct 8, 2009 at 07:16, Kelvinelk wrote:
> Okay, apart from there not being an up-to-date and working minimyth for my
> diskless VIA frontend (WAF=gone through the floor), a desktop
Okay, apart from there not being an up-to-date and working minimyth for my
diskless VIA frontend (WAF=gone through the floor), a desktop frontend that
crashes on channel change (known, confirmed mythtv bug)
I am now running trunk with no issues and have gdb attached to the backend. ;)
Watch th
Apport doesn't want to catch this. It says "The problem cannot be
reported - This is not a genuine ubuntu package"
I will see if I can get the daily trunk builds going and attach gdb to
mythtv-backend. Please be aware that this means the WAF may go through
the floor as I iron out other issues I en
OK, so in theory if you turn on the daily trunk builds rather than the
karmic archive builds, you should get more debugging symbols built in.
So first thing i'd recommend is visit http://mythbuntu.org/auto-builds
and turn those on. Next if mythbackend isn't getting caught by apport,
run it through
Alternatively (and it might be easier), follow the directions on that
page to attach to the already running mythbackend process.
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ub
** Changed in: mythtv
Status: Unknown => New
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Bug watch added: mythtv.org bug tracker #7251
http://svn.mythtv.org/trac/ticket/7251
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/7251
Importance: Unknown
Status: Unknown
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.ne
Make that -v vbi,important,eit,siparser
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
I'll make another plea on the mailing lists for ideas on how to debug
this further. In the mean time:
1. Please enable apport if you can. don't know if it will help or not
2. The most important thing is to grab logs of the failure on 0.22 systems with
-v important,eit,siparser or if you can st
@MajorTom and FAO MarcRandolph
So, looks like this issue affects trunk as well as 0.21-fixes. Perhaps upstream
will pay attention to this bug now?
@Alistair
Yes it does coincide, but I rescanned on Thursday. Have you rescanned or seen
the bug occur before or after scanning?
--
mythbackend sile
Does this coincide with the changes to some of the ITV channels that may
require a channel re-scan?
I have been on holiday so the server has not been running but I read
about this while I was away.
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/33
Just a quick 'me too'. I'm also in the UK and use the DVB-S and DVB-T
EIT exclusively. I've started having this once or twice a day since
2009-10-02, presumably because of something in the current EIT data -
running mythbuntu with trunk 22179.
--
mythbackend silently fails with QSqlQuery::exec:
Well, just as I was starting to forget about this bug, it happened again
today! What a shame.
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Mine has now been running fine for 3 days with no errors (it would
previously fail within 12 hours of startup). I am NOT using the
--nohousekeeper flag.
I can only conclude at the moment that whatever wonky EIT data was being
received, which triggered the issue, is now no longer being broadcast?
@alistair
I think it depends on whether myth protocol has changed or not. I have a
minimyth frontend which ignores a change in myth protocol and attempts
to connect anyway. Other implementations will vary and will likely not
enable you to connect if there is a mismatch in the protocol.
@all
I hav
If I upgrade the backend, will existing front ends still work?
I have several front ends running on several distros and architectures
(but not on the back-end machine), and upgrading them all at once would
be a real pain. However, if they will still work, I can upgrade the
back end, and then do t
After compiling together information and posting to the mythtv-users
list, I have received no responses - so I'm afraid that the only course
forward is for one of you to either upgrade to alpha 0.22, or do a
parallel install (anyone have a spare drive or partition?) to see if the
problem is still o
This is a log file with -v important,eit,siparser
snippet just before sql error appears again:
QSqlQuery::exec: empty query
2009-08-31 17:11:02.522 PESPacket: Failed CRC check 0x22161100 != 0xc3bfa4b5
for StreamID = 0x70
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: e
It might or might not yield anything helpful, but someone might try
running with with -v eit,siparser (either one or both) logging turned
on overnight. Might produce some really large log files, so be sure to
turn it off in the morning!
--
mythbackend silently fails with QSqlQuery::exec: empty
I do not use mythfilldatabase - just the off-air schedules.
I have not had the problem recur since I changed to --nojobqueue - the
backend has been up for days, now. If upstream really is not fixing
this version, I am not keen to experiment by turning the option off
again to see if the problem re
Howdy all, I kinda doubt it is a problem with the database or the query
itself. The messed up date makes me think of something like a corrupted
pointer - most likely in the EIT code since that is the point in common
for you all. A corrupted pointer will result in lots things being
messed up in m
@Kelvinelk
I use EIT only, no mythfilldatabase.
I have a log from it falling over last night, with bind values
displayed, here is the first error message:
222-22MM-22dd 22hh:22mm:22ss.22zzz DB Error (Looking up chanID):
Query was:
SELECT chanid, useonairguide FROM channel, dtv_multiplex WHER
@MarcRandolph
No problem, and thanks for reopening.
@All with this bug
Do you all use EIT solely? Or do you use mythfilldatabase to get listings from
elsewhere also?
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug not
hey all, fyi I have rebuilt my mythtv from the 2.1 fixes branch with
the new DBError function from trunk to see if printing out the bind
values helps with diagnosing it.
I am still getting the problem every night so hopefully should have a
better error message tomorrow.
Roy
--
mythbackend sile
@Kevin,
Sorry, you are correct - I missed the mythcommflag angle somehow while I was
rushing around this morning. I'm more than happy to leave this open for a
while longer if you all can continue helping to debug it.
I did leave something out of my note earlier: MythContext:DBError() has been
@MarcRandolph
whoa - hang on a sec
you want to close a bug based on a guess? play fair!
the changeset you have linked to is for mythcommflag - I dont believe
this is a function associated with EIT.
@Roy Thomson
Thanks for letting us know - I am now running with --nohousekeeper -
will let yo
Thanks to all three of you for updates. Sounds like the common theme is
EIT. I may have found the offending code, and if that is indeed the
source of the problem you all are having, it has been changed in 0.22.
For those that are interested, you'll notice that the following
changeset describes fi
Just a note that --nojobqueue did NOT solve it for me.
It happened again last night.
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I get very similar error message, yes, that is how I found this bug too.
222-22MM-22dd 22hh:22mm:22ss.22zzz DB Error
(JobQueue::CleanupOldJobsInQueue: Error deleting old finished jobs.):
Query was:
DELETE FROM jobqueue WHERE (status in (:FINISHED, :ABORTED, :CANCELLED) AND
statustime <
As a follow-up:
> Do your error messages look very close to Kyle's (with the invalid
looking date 222-22MM-22dd 22hh:22mm:22ss.22zzz)?
Yes, indeed! Searching on 222 was how I found this thread. It also
seems to happen in the middle of the night.
> Do you all use remote frontends? If so
The error which i get are similar in format to Kyle's. It seems to
happen mostly in the middle of the night but it has been happening for
some time, around the time that it was first reported by Kyle. It is
only recently that it seems to be getting far more frequent.
Background to my mythtv setup:
ah - another question: Do you all use remote frontends? If so, do you have a
real IP address set for the backend rather than 127.0.0.1?
Or did you all happen to change a configuration? Do you use EIT? Random idea:
Perhaps the format of the EIT changed, and triggers a bug in MythTV.
--
myth
The fact that two of you have started seeing this within the past few
weeks would seem to indicate something changed in that time frame, or
soon before. Did you all do an update around that time? What versions
are you running? Have you run a database check? Do your error messages
look very clos
On Wednesday 26 August 2009 08:14:54 Roy Thompson wrote:
> I've started to get this issue in the last two weeks as well.
> mythbackend failing about every other day. Did you try .22?
Roy
Trying .22 looks to be more complex than I first thought.
However, I am now running the backend with options "
I've started to get this issue in the last two weeks as well.
mythbackend failing about every other day. Did you try .22?
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bu
I have just started to get this problem as well.
I notice that entries appear in the "programs" table of the database
with all-zero start and end times, which cannot be right! This started
out-of-the-blue just the other day.
I have a setup that uses the off-air programme guide from UK DVB-T.
I
Howdy, and thank you for helping to make Mythbuntu better.
Unfortunately, mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. Is
this bug still occurring for you? Could you please try to see if this
bug is reproducible on 0.22?
Hi,
I've just come home, and haven't used MythTV since last night. The
system has fallen over and mythbackend.log contains the following
info...
222-22MM-22dd 22hh:22mm:22ss.22zzz decodeLongLong() called with the
iterator too close to the end of the list.
222-22MM-22dd 22hh:22mm:22ss.22z
** Attachment added: "mythbackend.log"
http://launchpadlibrarian.net/22704530/mythbackend.log
--
mythbackend silently fails with QSqlQuery::exec: empty query
https://bugs.launchpad.net/bugs/330272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
43 matches
Mail list logo
