Plugin: Sage Recording Extender (SREv3)

[Slugger]

Welcome to the support thread for SREv3. This version of SRE requires SageTV v7. There are many key changes introduced in SREv3. The highlights include:


Support for the new SageTV event model
Support for the new SageTV Plugin Manager
Configuration of SRE settings via STV
Migration to new web service for event data (http://www.livepvrdata.com)
Complete overhaul of web interface


I apologize in advance for the lack of documentation, but I've been busy porting all my plugins to SageTV v7. Those familiar with SRE should find that, new looks aside, everything is pretty much the same.

One key change in SREv3 is the need for a Google Account. The Live PVR Data web service requires Google Account authentication. You must provide your Google Account id and password in order to use SREv3.

SREv3 is currently in beta. The beta tag is mainly to do with incomplete features. The port is not done, but monitoring of supported events is functional. Things like editing the global override map have not been ported yet, but will be before too long.

Please feel free to provide feedback and post support questions in this thread.

[ohpleaseno]

What does livepvrdata.com scrape?

[Stuntman]

I just upgraded to Version 7 and installed your SRE plugin.. but the Sage web pages and the SRE pages no longer come up! They worked before upgrading, so I'm sure there is just something I've missed..

SRE shows as an installed plugin.. I have the webserver running on port 8500, at least that is what the GUI shows and it is where I had previously run it..

Has the directory structure changed? I used to use http://localhost:8500/sre

Is there some way to verify that the web service is running, other than NOT seeing the pages being served?

[Slugger]

What does livepvrdata.com scrape?

Whatever it needs to determine the status of the requested event. :D With the move to this web service, SRE is no longer concerned with web scrapers, XML/JSON parsers, etc. SRE simply makes an RPC call to livepvrdata.com and livepvrdata.com returns a status object, which SRE then acts on. If you look at the source code for SREv3 you'll notice it's significantly smaller and makes no reference to espn.com or any other web site. All those yucky details of figuring out where to go for event info and how to parse it is no longer SRE's concern! :)

[ohpleaseno]

Whatever it needs to determine the status of the requested event. :D With the move to this web service, SRE is no longer concerned with web scrapers, XML/JSON parsers, etc. SRE simply makes an RPC call to livepvrdata.com and livepvrdata.com returns a status object, which SRE then acts on. If you look at the source code for SREv3 you'll notice it's significantly smaller and makes no reference to espn.com or any other web site. All those yucky details of figuring out where to go for event info and how to parse it is no longer SRE's concern! :)

I guess what I'm getting at is the list of sports that SRE can monitor expanded with livepvrdata.com expanded? That site isn't all that helpful because there is nothing there.

Specifically, is NASCAR now supported?

[Slugger]

I just upgraded to Version 7 and installed your SRE plugin.. but the Sage web pages and the SRE pages no longer come up! They worked before upgrading, so I'm sure there is just something I've missed..

SRE shows as an installed plugin.. I have the webserver running on port 8500, at least that is what the GUI shows and it is where I had previously run it..

Has the directory structure changed? I used to use http://localhost:8500/sre

Is there some way to verify that the web service is running, other than NOT seeing the pages being served?

What do you get when you go to the url? Do you get a page not found (404) error or do you get a connection timed out error? If debug logging is enabled then you should be able to tell that Jetty started based on the output in the logs.

[Slugger]

I guess what I'm getting at is the list of sports that SRE can monitor expanded with livepvrdata.com expanded? That site isn't all that helpful because there is nothing there.

Specifically, is NASCAR now supported?

No, but it may eventually be added. Currently, it's just the big 6: MLB, NFL, NHL, NBA, NCAA hoops, NCAA pigskin.

As to livepvrdata.com, it's a closed beta (very closed). Eventually that site will come to life with content, but for now it's just the web service that's running.

[Stuntman]

What do you get when you go to the url? Do you get a page not found (404) error or do you get a connection timed out error? If debug logging is enabled then you should be able to tell that Jetty started based on the output in the logs.

I get the following.. which isn't a 404...

Internet Explorer cannot display the webpage

How do I turn on debug logging and where does it keep it's logs? I'll turn it on, if it isn't already..

Thanks!

[cat6man]

are you sure this is working? i went to livepvrdata.com (your link above) and got the message 'come back later'

[Slugger]

are you sure this is working? i went to livepvrdata.com (your link above) and got the message 'come back later'

Yes, it's working. :) The web service portion is up and running, there's just no public web site yet. Everything works though.

[Slugger]

I get the following.. which isn't a 404...

Internet Explorer cannot display the webpage

How do I turn on debug logging and where does it keep it's logs? I'll turn it on, if it isn't already..

Thanks!

Look for the plugins/sre directory under SageTV directory. In there should be an sre.log file. Is it being written to? Did you also install the web interface? Is it working? If not, disable and reenable the Jetty plugin; that may get you up and running as well.

[cat6man]

thanks so much for porting over SRE for us.
this is my one indispensable plugin.

however, since i have a game to record tonight, i won't get to play with v7
until tomorrow afternoon....i have to work in the morning, but i'll take a 1/2 day
vacation tomorrow to play with v7

cheers

[cat6man]

I just upgraded to Version 7 and installed your SRE plugin.. but the Sage web pages and the SRE pages no longer come up! They worked before upgrading, so I'm sure there is just something I've missed..


i'm probably being dumb here but after a flawless 8 minute upgrade which went so smooth i almost couldn't believe it, i find that i cannot find SRE or nielm's web interface in the plugins.

what am i doing wrong?

thanks in advance

edit: my dumb.............looked for "sre" not sage recording extender

[Slugger]

As in you've installed them, but they don't appear to be loading or you can't find them in the plugin manager to install them? If the latter then you'll find them under the Standard plugin type.

[cat6man]

found it and it installed itself beautifully.
i had to give my cat an email account on gmail, but SRE is now
working fine.........i'll have to give her a kitty snack as a reward.

i checked the log and it seems to be operating fine.

first test is red sox vs. phillies tonight.

thanks again slugger

digression
{
why the *&&!@ do we get the phillies when the yankees get
the mets?
}
end digression

[cat6man]

using

http://192.168.1.111:8500/sre/SREClient.html

using the old web interface address, i get 404 not found error.

nielm's web interface works ok.

is there something else i need for web interface in SRE?

[Slugger]

using

http://192.168.1.111:8500/sre/SREClient.html

using the old web interface address, i get 404 not found error.

nielm's web interface works ok.

is there something else i need for web interface in SRE?

Try /sre/SRE3.html

EDIT: /sre/ by itself should also work.

(I know, I know :) It's been kind of a mad scramble to get all the plugins ported to v7 so you'll have to bare with me on the outdated/missing docs).

[cat6man]

Try /sre/SRE3.html


that one works for me!
now that plugin options can be changed within sage7 or the hd200, the only reason (i think)
to use the web access is for overrides.........is that your thinking also?

thanks once again

do you still want to get rid of the 'slug'?

edit: how often does SRE go out to check? i don't see a variable /option for that and i also didn't see
tonight's phillies/sox game with a check mark (that would indicate it was found?)

[Slugger]

that one works for me!
now that plugin options can be changed within sage7 or the hd200, the only reason (i think)
to use the web access is for overrides.........is that your thinking also?

Yes.

do you still want to get rid of the 'slug'?

??


edit: how often does SRE go out to check? i don't see a variable /option for that and i also didn't see
tonight's phillies/sox game with a check mark (that would indicate it was found?)

Check frequency is no longer a configurable option - I'm limited by the web service constraints. Prior to the day of an event SRE will check the validity once a day. On the day of an event it will check approximately 30 mins before the scheduled start time of the recording (however, I don't think SRE is doing this permitted check [yet]). It will check again when the recording starts then it will sleep until 30 mins before the scheduled end of the recording at which time it will check every two minutes until the event is determined to have completed.

Do you have a warning symbol? Or just blank? When the recording starts it will definitely check again. Keep an eye on SageTV\plugins\sre\sre.log. Ensure there are no Google Account auth errors - that will prevent SRE from doing anything.

[cat6man]

Do you have a warning symbol? Or just blank? When the recording starts it will definitely check again. Keep an eye on SageTV\plugins\sre\sre.log. Ensure there are no Google Account auth errors - that will prevent SRE from doing anything.

i see only yellow triangles for all recordings.
i'll check log file shortly

p.s. vernon wells?

[Slugger]

i see only yellow triangles for all recordings.
i'll check log file shortly

I'm guessing there are Google authentication issues. You will get triangles for all future events, but for anything from today, it should be able to properly verify if your Google Account settings are correct.

p.s. vernon wells?

:rofl: Right... I forgot I called him a slug way back when! I've still been advocating a trade, especially because right now he actually has some trade value. Doubt there would be any takers - he still makes too much money. My thoughts: The Blue Jays aren't going to win the East. They'll likely finish 4th in the AL East assuming Boston picks it up. You can't rebuild the entire roster except Wells. If you're rebuilding then save the money and get some blue chip prospects for him (before his BA falls below .300). And based on the avg attendance in Toronto these days, they ought to be looking to save every penny they can.

[cat6man]

i see only yellow triangles for all recordings.


problem solved!! :goodjob:
it was my cat's fault. :confused:

as mentioned above in this thread, when i read that SRE required
a google account, i created an account for my cat that would be
used for this functionality.

now i know why they're called dumb animals.
:nono:

the dumb kitty entered her account as *@google.com
instead of *@gmail.com

i would expect it to work now

edit: as of saturday morning, the log no longer shows the error message about google account and passworkd, but i still have all yellow triangles

[cat6man]

hi,
are overrides implemented?
i was able to double click and type something in but it didn't stick

[Slugger]

hi,
are overrides implemented?
i was able to double click and type something in but it didn't stick

Yes, overrides are implemented. If an override doesn't stick then check the log file, it should tell you why. Also, the status message at the bottom right of the web UI will also give you a (basic) error message.

[cat6man]

still having problems here........have to check log file.

suggested feature: add access to log file from options page.
(i may be 2 or 3 floors away from my sage machine when i log in
so easy remote access to the log would be helpful)

[Slugger]

still having problems here........have to check log file.

suggested feature: add access to log file from options page.
(i may be 2 or 3 floors away from my sage machine when i log in
so easy remote access to the log would be helpful)

Yeah, the log viewer will be there before beta tag removed. If Google id/pwd is correct then everything should "just work." Keep me posted.

[cat6man]

this morning, i added the brewers-twins game, scheduled for 4pm but nothing happened in sage to indicate that it was tracking that game, and all my yellow triangles are still there.

here is a section of my sre log that captures some stuff before i fixed the email address problem yesterday and up to today.

let me know if you need anything more.

[Stuntman]

I too can't get SRE to work.. I see nothing in the recordings list and this in the sre.log file..


com.google.code.livepvrdata.rpc.AuthenticationException: com.google.gdata.client.GoogleService$CaptchaRequiredException: Captcha required

I deleted the entire JARs directory and did a clean install of this, Jetty Webserver and the web server interface (it isn't working either), though I do see the SRE webpages, so I know Jetty is working in some reduced manner..

Any idea what the Captcha required bit is about?

[Slugger]

If you see this error:


com.google.code.livepvrdata.rpc.AuthenticationException: com.google.gdata.client.GoogleService$CaptchaRequiredException: Captcha required


Go to this page:

https://www.google.com/accounts/DisplayUnlockCaptcha

And unlock your Google Account. After you unlock it then SRE should be able to authenticate and all should be good.

[Slugger]

I deleted the entire JARs directory and did a clean install of this, Jetty Webserver and the web server interface (it isn't working either), though I do see the SRE webpages, so I know Jetty is working in some reduced manner..

If SRE nor the web interface are working then something is wrong with Jetty. That's where you need to focus your attention. However, if SRE is writing captcha errors, etc. to the log file then SRE is running so it may be a firewall issue preventing access to the web sites?

Any idea what the Captcha required bit is about?

See post right above this one.

[cat6man]

was i supposed to upgrade jetty?
was this done for me automatically when i installed the SRE plugin?

i'm still getting all yellow triangles here.

[Slugger]

was i supposed to upgrade jetty?
was this done for me automatically when i installed the SRE plugin?

i'm still getting all yellow triangles here.

All dependencies are upgraded automatically. PM me your IP address and I'll have the web logs of livepvrdata.com looked at to see why you're not able to authenticate with the web service.

[cat6man]

info in PM

[cat6man]

more log info attached.

edit: when entering account info, should it be
1) name@gmail.com
or
2) name

[Slugger]

more log info attached.

edit: when entering account info, should it be
1) name@gmail.com
or
2) name

Full email address.

[bsquarewi]

Sorry if this is a bone-headed question.. But I went to install this plugin and the plug-in info screen there is a big warning in all caps saying: DO NOT INSTALL THIS ON A SAGE CLIENT, INSTALL DIRECTLY ON SAGE SERVER.

So that leaves a problem for me because I use the WHS version of Sage with a HD200 as my only means of connecting to the Sage UI. So can I install this from the HD200?

[Slugger]

Sorry if this is a bone-headed question.. But I went to install this plugin and the plug-in info screen there is a big warning in all caps saying: DO NOT INSTALL THIS ON A SAGE CLIENT, INSTALL DIRECTLY ON SAGE SERVER.

So that leaves a problem for me because I use the WHS version of Sage with a HD200 as my only means of connecting to the Sage UI. So can I install this from the HD200?

Yes, installing from HD200 is fine (because that'll install it on the SageTV server). The warning refers only to installation from a SageTVClient (i.e. PC client). Do not install it on a SageTVClient instance, it will not work.

[cat6man]

here is error message i got with your command line

[Slugger]

here is error message i got with your command line

That's a firewall issue. Java is unable to connect to the remote host (livepvrdata.com in this case). Since it's timing out then that tells me there's a firewall silently dropping packets.

The client will only ever attempt to connect to the following URLs:

https://livepvrdata.appspot.com/auth (port 443)
http://livepvrdata.appspot.com/rpc (port 80)

[cat6man]

so does installing the plugin take care of the firewall or do i need to manually do this? (at home..........obviously i can't modify corporate firewall)

i'll redo the test at home tonight and check firewall. what is the name of the program(s) that need firewall access? is it just SRE or something else?

[Slugger]

so does installing the plugin take care of the firewall or do i need to manually do this? (at home..........obviously i can't modify corporate firewall)

i'll redo the test at home tonight and check firewall. what is the name of the program(s) that need firewall access? is it just SRE or something else?

Nope, the plugin does nothing to configure firewalls. Since plugins run inside of SageTV, it's the SageTV process that needs outgoing access to ports 80 and 443. When running that command line tool I sent you, it's java.exe that would need the same access.

[cat6man]

latest

[Slugger]

So you're able to connect to the web service. Now we can conclude that something is wrong in SRE specifically. We're going to need a custom build to get more debug info...

[cat6man]

don' see much activity in log file

[cat6man]

slugger,
have you seen this?
possible issues for sage6 to sage7 upgrade


http://forums.sagetv.com/forums/showthread.php?p=425915&postcount=1

[Slugger]

slugger,
have you seen this?
possible issues for sage6 to sage7 upgrade


http://forums.sagetv.com/forums/showthread.php?p=425915&postcount=1

Doesn't apply to our ongoing investigation.

[cat6man]

i put jetty into verbose mode, sent you short log file before leaving for work,
more later when i get home.

[Slugger]

i put jetty into verbose mode, sent you short log file before leaving for work,
more later when i get home.

Yeah, we need to make some more changes to the Jetty logging. If you're home by 4:30ish (EDT) we can do it before I head out for the evening, otherwise it'll have to wait until tomorrow night.

[Sparhawk6]

I'm having no luck installing version 3.0 on Sage7. I keep getting the message "failed" when I try to install. I also don't see where I need to input my google account info. Apparently I'm totally lost without documentation. :D

[Slugger]

I'm having no luck installing version 3.0 on Sage7. I keep getting the message "failed" when I try to install. I also don't see where I need to input my google account info. Apparently I'm totally lost without documentation. :D

You can't configure the plugin until it installs successfully. The configuration is all in the STV. If you keep getting failed for the install then you'll have to go looking in the Sage logs for error messages. Is the plugin install creating the SageTV\plugins\sre directory? Is there anything in that dir?

There isn't much documentation for me to add as far as installation goes.

* Find it in the plugin manager
* Click Install

If it's failing then I need to see error messages, but failure at this stage would either be inability to download the zip files or Sage has failed to extract the zip files. Do you get any error message on the GUI from Sage when the installation fails?

[Sparhawk6]

You can't configure the plugin until it installs successfully. The configuration is all in the STV. If you keep getting failed for the install then you'll have to go looking in the Sage logs for error messages. Is the plugin install creating the SageTV\plugins\sre directory? Is there anything in that dir?

There isn't much documentation for me to add as far as installation goes.

* Find it in the plugin manager
* Click Install

If it's failing then I need to see error messages, but failure at this stage would either be inability to download the zip files or Sage has failed to extract the zip files. Do you get any error message on the GUI from Sage when the installation fails?

I don't get any error messages.

A few things:
I first tried to install this via the extender. I don't know if that makes a difference.
I have not uninstalled SRE 2.x. Is this necessary?

[Slugger]

I don't get any error messages.

A few things:
I first tried to install this via the extender. I don't know if that makes a difference.
I have not uninstalled SRE 2.x. Is this necessary?

Installing from the extender is fine.

Not removing SRE 2.x... not a problem. The plugin deals with that situation just fine. Did the plugin create the plugins/sre/ directory? You're going to have to enable debug logging and try to look for some output. The only thing we seem to know right now is that the plugin is failing to install and that's more a Sage issue than an SRE issue. Hopefully the debug logs will have something to say about that.

[Slugger]

A new version is available in the repository. It fixes one major bug and another key issue. All users are encouraged to upgrade asap.


Upgrade to latest livepvrdata library
Fix dependency issues; some users may have been missing required jars for SRE to work properly because the httpclient3 plugin did not list all its dependencies properly; new httpclient3 plugin fixes the issue so this version of SRE now depends on that updated version of the plugin
Stop repeatedly trying to authenticate a user's Google Account with livepvrdata.com if it fails (at their request); instead if it fails then post a system message and stop hammering livepvrdata.com until the user has corrected the issue


Users can upgrade via the plugin manager.

[cat6man]

SRE is working great here with the latest version of the plugin.
great stuff slugger...........many thanks

[Sparhawk6]

Getting this error upon install:

2010-05-29 03:58:09,685 FATAL [PooledThread] com.google.code.sagetvaddons.sre3.server.SageTVPluginSRE (SageTVPluginSRE.java:172) - DB copy failed
java.io.IOException: Failed to delete original file 'sre.sqlite' after copy to 'plugins\sre\sre.sqlite'
at org.apache.commons.io.FileUtils.moveFile(FileUtils.java:1821)
at org.apache.commons.io.FileUtils.moveFileToDirectory(FileUtils.java:1856)
at com.google.code.sagetvaddons.sre3.server.SageTVPluginSRE.start(SageTVPluginSRE.java:169)
at sage.plugin.a.a(Unknown Source)
at sage.e.u$38.null(Unknown Source)
at sage.ay.a(Unknown Source)
at sage.e.a(Unknown Source)
at sage.x.f(Unknown Source)
at sage.x.e(Unknown Source)
at sage.x.access$100(Unknown Source)
at sage.x$3.run(Unknown Source)
at sage.cu$a.run(Unknown Source)

[Peter_h]

I am experiencing the same issue as SparHawk6. The plugin is failing to install. I also previously had SRE 2.xx installed. My log is almost identical to his.

10-05-29 01:16:33,710 INFO [AppEnv]: Registered for recording schedule change events!
2010-05-29 01:16:33,710 INFO [SageTVPluginSRE]: Running plugin start() method!
2010-05-29 01:16:33,756 FATAL [SageTVPluginSRE]: DB copy failed
java.io.IOException: Failed to delete original file 'sre.sqlite' after copy to 'plugins\sre\sre.sqlite'
at org.apache.commons.io.FileUtils.moveFile(FileUtils.java:1821)
at org.apache.commons.io.FileUtils.moveFileToDirectory(FileUtils.java:1856)
at com.google.code.sagetvaddons.sre3.server.SageTVPluginSRE.start(SageTVPluginSRE.java:169)
at sage.plugin.a.a(Unknown Source)
at sage.e.u$38.null(Unknown Source)
at sage.ay.a(Unknown Source)
at sage.a.m$b.a(Unknown Source)
at sage.a.m.a(Unknown Source)
at sage.e.a(Unknown Source)
at sage.bc.a(Unknown Source)
at sage.bc.a(Unknown Source)
at sage.e.a(Unknown Source)
at sage.e.a(Unknown Source)
at sage.e$2.run(Unknown Source)
at sage.cu$a.run(Unknown Source)

[Slugger]

Which OS are you guys running?

For whatever reason, SRE doesn't have permission to or is unable to delete the sre.sqlite file in SageTV\ after it copies it to the new location. If you're running Vista or Win7 then this is probably a UAC problem of some sort, so please let me know what version of Windows you're running.

The easiest way to work around this in the mean time is to stop Sage, go to SageTV\plugins\sre and ensure that sre.sqlite has already been copied there. If it hasn't then copy the file from SageTV\ to that location then delete (or rename) the original in SageTV\ then restart Sage. Renaming or deleting the sre.sqlite file in SageTV\ will allow the SRE startup to skip that step and move on.

[Peter_h]

I am running WHS.

Edit: Tried exactly what you said and doesn't look like it worked. I can get to SRE web interface fine. However, version number is still showing as 2.X.X

[Slugger]

I am running WHS.

Interesting. I run on XP and that's it so I can't test it on all flavours of Windows. My guess is maybe you're running Sage 7 as a different user than Sage 6? Not sure, just a guess. In any case, you'll have to go with the work around because the current code assumes that it can delete the old db file at startup. I've fixed it for a future build such that it'll just copy the file then try to delete it separately. If the delete fails then it'll just ignore that and move on.

[Peter_h]

Interesting. I run on XP and that's it so I can't test it on all flavours of Windows. My guess is maybe you're running Sage 7 as a different user than Sage 6? Not sure, just a guess. In any case, you'll have to go with the work around because the current code assumes that it can delete the old db file at startup. I've fixed it for a future build such that it'll just copy the file then try to delete it separately. If the delete fails then it'll just ignore that and move on.


Hey Slugger, install was done using the admin user in both instances. I'm certain it's not a user problem.

Is this version supposed to display version 3 in the web interface? I did as you said and it's displaying version 2 still in the web interface

[Slugger]

Hey Slugger, install was done using the admin user in both instances. I'm certain it's not a user problem.

Is this version supposed to display version 3 in the web interface? I did as you said and it's displaying version 2 still in the web interface

You should be getting a v3 web interface and it should look drastically different. It should look like the screen shot that's available via the plugin manager. You may have to clear your browser cache in order to see it load properly.

[Peter_h]

I still don't think it's installing properly. It's still pulling up the old version.

When I go to <server>:<jettyport>/sre it redirects to sre/sreClient.html. It does not redirect to the new sre/sre3.html. If I try to go directly to sre/sre3.html I get

HTTP ERROR 404

Problem accessing /sre/SRE3.html. Reason:

NOT_FOUND

The plugin is still showing failed in the plugin manager.

The exact steps to manually move the sjqsqlite file were as follows.\
I shut down the sagetv service, moved sjq.sqlite to the plugins/sre folder, and then restarted the service.

[Sparhawk6]

Which OS are you guys running?

For whatever reason, SRE doesn't have permission to or is unable to delete the sre.sqlite file in SageTV\ after it copies it to the new location. If you're running Vista or Win7 then this is probably a UAC problem of some sort, so please let me know what version of Windows you're running.

The easiest way to work around this in the mean time is to stop Sage, go to SageTV\plugins\sre and ensure that sre.sqlite has already been copied there. If it hasn't then copy the file from SageTV\ to that location then delete (or rename) the original in SageTV\ then restart Sage. Renaming or deleting the sre.sqlite file in SageTV\ will allow the SRE startup to skip that step and move on.

I'm running WinXP.

[Slugger]

Ok... it seems like maybe what's happening is that SREv2 is being loaded by Jetty before SREv3 can replace it and upgrade. Follow these steps:

* Stop Sage
* Ensure that SageTV\plugins\sre\ contains sre.war and sre.context.xml
* If necessary, copy SageTV\sre.sqlite to SageTV\plugins\sre\sre.sqlite
* Delete SageTV\sre.sqlite
* Delete SageTV\jetty\webapps\sre.war
* Delete SageTV\jetty\contexts\sre.context.xml

If the last two files don't exist for some reason then you'll have to enable Sage debug logging and look for why the plugin startup is failing. If they do exist then my theory seems correct and these steps should allow SREv3 to startup properly.

[Peter_h]

That worked, thanks!

[Sparhawk6]

Worked for me as well. Thanks.

[cat6man]

not a biggie.

i see yellow triangles (look like caution signs) on all the MLB baseball games currently in my schedule, and presumably to be monitored by SRE.
is that the meaning you intended (to be monitored by SRE)?

if so, the yellow caution sign sort of gives more of a warning look to things than a 'SRE will do your bidding' in the future.

[Slugger]

not a biggie.

i see yellow triangles (look like caution signs) on all the MLB baseball games currently in my schedule, and presumably to be monitored by SRE.
is that the meaning you intended (to be monitored by SRE)?

if so, the yellow caution sign sort of gives more of a warning look to things than a 'SRE will do your bidding' in the future.

I assume we're talking about games scheduled into the future (i.e. not today)? In this case, SRE is unable to verify that the game can actually be monitored so you get a warning symbol. The issue: livepvrdata is currently using espn.com Bottom Line feed, which only serves the current day so when SRE asks livepvrdata about those future games it gets an error in return. It's a warning because it's unknown. On the day of the game, it'll change to a check or an error.

I expect livepvrdata.com to move to a different feed in the future that will support future date lookups and if/when they do then SRE will automatically handle it as expected.

[Slugger]

Ok... it seems like maybe what's happening is that SREv2 is being loaded by Jetty before SREv3 can replace it and upgrade. Follow these steps:

* Stop Sage
* Ensure that SageTV\plugins\sre\ contains sre.war and sre.context.xml
* If necessary, copy SageTV\sre.sqlite to SageTV\plugins\sre\sre.sqlite
* Delete SageTV\sre.sqlite
* Delete SageTV\jetty\webapps\sre.war
* Delete SageTV\jetty\contexts\sre.context.xml

If the last two files don't exist for some reason then you'll have to enable Sage debug logging and look for why the plugin startup is failing. If they do exist then my theory seems correct and these steps should allow SREv3 to startup properly.

That worked, thanks!

Worked for me as well. Thanks.

Ok, so the requirement is that SREv2 (or older) must be uninstalled before installing SREv3. I'll be sure to add that to the docs when I get to them.

[cat6man]

Ok, so the requirement is that SREv2 (or older) must be uninstalled before installing SREv3. I'll be sure to add that to the docs when I get to them.

wasn't needed for me though...........wonder why?

[Slugger]

wasn't needed for me though...........wonder why?

The thought of even trying to figure that out is hurting my head! :D Consider yourself lucky. ;)

[cat6man]

one more question, in the same category of 'not a biggie'

is there any reason to keep non-sports events monitored?
any reasons pro or con?

[Slugger]

one more question, in the same category of 'not a biggie'

is there any reason to keep non-sports events monitored?
any reasons pro or con?

For support of future feature(s). Please don't ask what they are. :D

[cat6man]

i think i can guess.............any games where the yankees are beating up on either the red sox or blue jays, you can have SRE eliminate those innings from the game!

very cool :thumb:

[gopher]

Note: I had problems initially with getting SRE to install on v7 on WHS. I had to uninstall v7, manually remove all plugins, re-install v7, remove plugins, re-install plugs. I can get to the web interface, but all monitored airings have yellow triangles, even on the date of airings. Below is a snippet of log when one of the airings occurs. Any ideas or help?

2010-06-02 21:04:07,990 ERROR [AiringMonitor]: 'NHL Hockey: Chicago Blackhawks at Philadelphia Flyers': Error reading status; will try again on next check! [247985ms]
com.google.code.livepvrdata.rpc.RpcException: org.apache.xmlrpc.client.XmlRpcClientException: Failed to read server's response: Protocol violation: Unexpected single newline character in chunk size
at com.google.code.livepvrdata.rpc.Client.fire(Client.java:207)
at com.google.code.livepvrdata.rpc.Client.getEventStatus(Client.java:257)
at com.google.code.sagetvaddons.sre3.server.AiringMonitor.run(AiringMonitor.java:131)
Caused by: org.apache.xmlrpc.client.XmlRpcClientException: Failed to read server's response: Protocol violation: Unexpected single newline character in chunk size
at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:190)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:156)
at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143)
at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:137)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:126)
at com.google.code.livepvrdata.rpc.Client.fire(Client.java:205)
... 2 more
Caused by: java.io.IOException: Protocol violation: Unexpected single newline character in chunk size
at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputStream(ChunkedInputStream.java:273)
at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputStream.java:221)
at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream.java:146)
at java.io.FilterInputStream.read(Unknown Source)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:88)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:186)
... 9 more

[Slugger]

Please update to the latest version. I suspect those kinds of problems have been fixed. If not, then send me logs after you've upgrade and reproduced.

[gopher]

That worked. I updated other components, but must have missed the SRE update. Thanks.

[spacecadet]

Hi Slugger,

Just upgraded to the new v3 tonight. I'm a bit confused on the "status" column in the Web UI. It's currently showing a yellow triangle for tonight's Red Sox game (which I am guessing would mean there was some kind of error/warning while trying to monitor the event). However, SRE appears to be extending the event with no trouble. The broadcast ended at 10PM, but SRE is extended the recording as we speak.

So, everything appears to be working great (:clap:), but I'm a bit confused on the yellow triangle in the status.

Am I missing something?

Thanks as always for all of your hard work!

[Slugger]

Have a look in SageTV/plugins/sre/sre.log for details on what's going on. If it's a warning symbol then it means it's probably not able to monitor the game and so it just applied the default padding to the recording. Most likely cause is a Google auth problem, but that log file will tell you more.

[spacecadet]

Have a look in SageTV/plugins/sre/sre.log for details on what's going on. If it's a warning symbol then it means it's probably not able to monitor the game and so it just applied the default padding to the recording. Most likely cause is a Google auth problem, but that log file will tell you more.

Sorry should've mentioned that in my earlier post... the log looks just fine (and the recording just automatically ended about 1-2 minutes after the end of the game)

2010-06-05 22:04:23,909 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [407ms]
2010-06-05 22:06:24,034 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [125ms]
2010-06-05 22:08:26,971 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [2937ms]
2010-06-05 22:10:27,565 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [594ms]
2010-06-05 22:12:30,643 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [3078ms]
2010-06-05 22:14:30,955 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [312ms]
2010-06-05 22:16:34,299 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [3344ms]
2010-06-05 22:18:35,002 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [703ms]
2010-06-05 22:20:35,690 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event not over; recording extended! [688ms]
2010-06-05 22:22:39,002 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Event is over; recording will end at Sat Jun 05 22:24:00 EDT 2010 [3312ms]
2010-06-05 22:24:08,268 INFO [AiringMonitor]: 'Extra Innings: ': Unmonitored event; ending monitor [63ms]
2010-06-05 22:24:35,018 INFO [AiringMonitor]: 'ESPNEWS: ': Unmonitored event; ending monitor [78ms]
2010-06-05 22:24:39,002 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Airing is not recording; stopping monitor thread! [0ms]
2010-06-05 22:24:39,002 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Baltimore Orioles': Removed manual record flag.

[Slugger]

Can you zip up your complete log file and email it to me? PM me if you don't have my email address. Also include the game and start time you were monitoring (so I don't have to come back here looking for it when I get a chance to debug this). I think it's just that I'm not flipping that symbol at the start of a game, but I'll take a look at it some evening next week.

Bottom line (especially while SREv3 is still in beta): when it doubt, the logs are the definitive answer. If the logs say a game is being monitored, rest assured it is. Then if something on the GUI isn't matching what the logs are telling you then (preferably), open an issue ticket (http://code.google.com/p/sagetv-addons/issues/list) or else post a message here.

[cat6man]

same here slugger............it has been working great all week, but even today's game against the orioles in a couple of hours still shows the yellow warning triangle (which i expect for games on future days)

sounds like a flag isn't being flipped somewhere, but it works great :thumb:

fyi: for sports fans, i just discovered the 'anti-favorite' or 'favorite-delete' plugin which is great for creating Boolean NOT functions to be ANDed with favorites.

since red sox games on mlb-ei are blacked out when playing the yankees since i live in yankee broadcast territory, i set an anti-favorite for 'yankees' associated with the favorite 'boston red sox'.............

3 cheers for user accessible boolean logic :jump:

[sic0048]

I've just started using this plugin. In fact, the first two truely monitored sporting event will happen tonight (NHL hockey & NBA basketball). Both have the yellow triangle in the web server. After reading the threads, I would expect this on days before the event, but not on the event day itself.

I've attached the sre log file in case someone wants to look over it. Keep in mind that there are a couple of errors in the beginning of the file where I had my google ID incorrect (I added @google.com to the ID originally). However, there have been a couple more errors after that point, but nothing that I take as too serious.

Still, I guess I'd like some assurance that everything is going to work as expected! After all, I'm a little nervous before getting my SRE cherry popped tonight ;)

Thanks!

[cat6man]

sic
you should be fine..........relax...........yellow triangles work fine in sre3.

[sic0048]

sic
you should be fine..........relax...........yellow triangles work fine in sre3.

Good to know. I appreciate the vote of confidence.

EDIT - Just an FYI - my NBA game now shows a green check mark as well. I guess I was just too impatient.

[Slugger]

Yeah, it all looks good. Here's what I can say:

Barring any unforseen bugs, at the very least SRE will always apply the default padding to a monitored event if it can't somehow monitor it. The default value of the padding is 1 hour (60 mins).

If you're worried, then check the sre.log file shortly after a recording starts. A monitored recording is always checked against the data source at the start of a recording then sleeps until 30 mins before its scheduled end. For example, a hockey game listed in the EPG from 8pm - 11pm will check the data source and log at 8pm then, assuming it was successful, will sleep until 10:30pm and then monitor the event every 2 mins until it's over.

As for the warning triangles, there's some logic errors in the GUI only as far as I can tell. The sre.log file trumps whatever the GUI is telling you. When in doubt, refer to the log files for the definitive answer as to what SRE is thinking and doing.

With that said, when the GUI and the logs don't agree then I'd like to know about it - preferrably with an issue ticket (http://code.google.com/p/sagetv-addons/issues/list). I'm aware of warning for current day events on the GUI and will dig into it asap. However, this week is looking rather busy so asap may not be until later in the week.

[cat6man]

hey man, SRE3 *works* so there is no rush to dig into yellow triangles...........they can stay there forever as long as SRE3 works
like it does today.

life is too short to sweat the little stuff...........

hope next week isn't too rough that you don't get to enjoy the jays!

[spacecadet]

Yeah, it all looks good. Here's what I can say:

Barring any unforseen bugs, at the very least SRE will always apply the default padding to a monitored event if it can't somehow monitor it. The default value of the padding is 1 hour (60 mins).

If you're worried, then check the sre.log file shortly after a recording starts. A monitored recording is always checked against the data source at the start of a recording then sleeps until 30 mins before its scheduled end. For example, a hockey game listed in the EPG from 8pm - 11pm will check the data source and log at 8pm then, assuming it was successful, will sleep until 10:30pm and then monitor the event every 2 mins until it's over.

As for the warning triangles, there's some logic errors in the GUI only as far as I can tell. The sre.log file trumps whatever the GUI is telling you. When in doubt, refer to the log files for the definitive answer as to what SRE is thinking and doing.

With that said, when the GUI and the logs don't agree then I'd like to know about it - preferrably with an issue ticket (http://code.google.com/p/sagetv-addons/issues/list). I'm aware of warning for current day events on the GUI and will dig into it asap. However, this week is looking rather busy so asap may not be until later in the week.

Yup. I had the yellow triangles today as well. However, the Red Sox game extended with no trouble. Shortly before game time, the 1:30 Red Sox game showed a green check mark. Sometime after the start of the game, the green check mark turned into a yellow triangle. Towards the end of the scheduled event, I noticed some errors in the log file AND SRE had applied the default padding to the recording (1 hour). However, the game went into extra innings and ended a full 90 minutes after the end of the scheduled event. It looks like SRE had trouble communicating with the server, extended the recording to the default padding, but on the next check the server was up and all was well.

I'm expecting the Celtics game tonight to be fine as well (also showing a green check mark right now), but I set the default padding to 180 minutes to be safe :)

No hurry on a fix Slugger, take your time and I'm confident the kinks will be worked out. I'll PM you my latest log file, so you can see the errors.

[Slugger]

The next beta build will be delivered to the plugin repository some time today (hopefully before tonight's ball games start, but no promises; busy day ahead). Here's what's fixed in the build:


Fix issue 122: Always ensure the event being monitored is completed according to the EPG before unsetting the manual recording flag
Fix issue 125: Avoid possible early end of monitor in case of transient errors with livepvrdata.com web source
Fix bug where monitor could end early in the case where multiple slow responses are received from livepvrdata.com causing the poller to sleep beyond the extended recording time
Fix sync issues with the status column on the GUI
Post system message (warning) if the "pre-game" status check (happens sometime during the 30 minutes prior to the scheduled start of the recording) does not produce a valid monitor (i.e. an override might be needed).


Some extra info worth mentioning about the GUI status column...

The status of a specific recording monitor is only checked once a day (at the request of livepvrdata.com) until the day of the event, but in SRE the thread that checks status runs every 30 minutes and checks the timestamp of the last check for each scheduled recording and if it's never been checked or the last check was more than 24 hours ago then it will check again. So when you schedule a new recording, it may take up to 30 minutes before the status column properly reflects the status as expected.

On the day of the event, the status is checked as follows:


The status is checked between 12:15-12:45 EST(GMT-500)/EDT(GMT-400); this is done because most sports (currently) use ESPN Bottom Line feed and it does not switch over until 12:00 ET each day. This check is done to change the warnings to check marks as early as possible each day
Status is then checked again sometime during the 30 minutes prior to the scheduled start of the recording; if this check does not find a valid monitor then a system message is posted warning you that a monitor may need an override. There are cases where this may produce false positives and those should just be ignored. An example of this is if livepvrdata.com were down at 19:30 and SRE checked status for a recording of The Simpsons starting at 20:00 well SRE will tell you an override might be needed for The Simpsons, obviously that's not true. It's the price you pay for the ability to receive system messages about actual events that might need an override (because the game is listed as "Teams TBA" or something, which definitely will need an override). A future build may provide the ability to disable system messages to avoid false positive messages, though I personally think the false positives are worth it given that they should be few and far between. Combined with SageAlert, one could receive these notices via email/SMS such that they'd know when a game will need an override without the need to constantly monitor the SRE log file.

[cat6man]

here is a tricky one, probably not in sre's scope, but since we sports folks hang on every byte slugger writes, this may be the audience:

on thursday, the red sox play the indians on game13 (mlb-ei)
also, on mlb-hd i see 'regional coverage' which is marlins at phillies or
red sox at indians

any idea if sage can tell which is going to be shown where i am?
does mlb or any other web site explain which games will be shown in which market?

[spacecadet]

here is a tricky one, probably not in sre's scope, but since we sports folks hang on every byte slugger writes, this may be the audience:

on thursday, the red sox play the indians on game13 (mlb-ei)
also, on mlb-hd i see 'regional coverage' which is marlins at phillies or
red sox at indians

any idea if sage can tell which is going to be shown where i am?
does mlb or any other web site explain which games will be shown in which market?

No thoughts on how to resolve that one. This happens to me a couple times every football season where ABC and ESPN will show opposing games depending on what part of the country you are in:

For example, ABC shows: A vs. B or C vs. D and ESPN shows C vs. D or A vs. B

In which case, I usually have to go look at the coverage maps on ESPN's site and then manually record the correct game. Oftentimes, Zap2it will update the guide with the specific game as the date gets closer, but not always.

Not sure how you'd check this for the Extra Innings package.

[cat6man]

i understand also that i need to do an override, but it is very annoying of MLB to
not have a simple way for us to figure out which game we are going to get.

p.s. sre3 will have informational messages when faced with this (when there is no override)
and it can't figure out which game is which............i recorded mlb-hd tonight to catch
stausberg's 1st start for washington but sre3 of course didn't know which game mlb was
broadcasting here.

[Slugger]

Yeah, there's nothing SRE (or anything) can do except hope that the EPG data is updated with the actual game being shown prior to the scheduled start of the recording. With the addition of the system messages, at least you should be notified that an override is required prior to the start of the recording.

[Slugger]

Nasty deadlock bug in 856. Fixed (hopefully) in 858. I'll do more testing when I have time tomorrow, but even if this fix doesn't work it's better than 856, which will deadlock SRE after a successful airing monitor stops a recording. Worst case scenario is that 858 doesn't fix it, but it should. I will confirm the fix once I test it more thoroughly tomorrow or post details on the next build that will fix it.

I apologize in advance for those who chose to monitor more than one recording tonight with 856 - it's a guarantee that the second recording was not monitored nor would it have had the default padding applied, etc. (b/c SRE would have deadlocked after the first monitor finished).

EDIT: After looking at the code closer, there is a couple of scenarios where the deadlock may have been avoided, but most likely not. You definitely want to move off of 856 ASAP.

[Slugger]

If nothing else, 858 is a major improvement over 856. I'm actually quite confident in saying that it completely fixes the deadlock issues in 856, but don't have time to give it the full testing needed tonight. However, my quick, informal testing shows I can't reproduce the deadlocks that were easily reproducible in 856 so I highly recommend everyone on 856 moves to 858 asap.

[sic0048]

Thanks for the bug update. While I hadn't worried about it, I think I experienced this exact scenerio a couple of days ago (when I used SRE for the first time). I recorded both NHL and NBA games that night and while the first game seemed to end correctly, the 2nd was defaulting to the 1 hr padding.

Since it was my first time using SRE, I thought maybe it was normal to do that (ie the server couldn't connect or some other reason it might default to the default padding).

Knowing that it was a bug definitely increases my confidence (and acceptance level) of SRE. Because truth be known, I was a little disappointed. :blush:

[Slugger]

Thanks for the bug update. While I hadn't worried about it, I think I experienced this exact scenerio a couple of days ago (when I used SRE for the first time). I recorded both NHL and NBA games that night and while the first game seemed to end correctly, the 2nd was defaulting to the 1 hr padding.

Since it was my first time using SRE, I thought maybe it was normal to do that (ie the server couldn't connect or some other reason it might default to the default padding).

Knowing that it was a bug definitely increases my confidence (and acceptance level) of SRE. Because truth be known, I was a little disappointed. :blush:

This bug was introduced only in build 856, which was released only yesterday. Older versions did not contain the bug. If you experienced this with something more than a day old then this is not the bug you're seeing. In that case, I'd like to see your sre.log file for further analysis.

I will say that the final kinks are just about worked out... I'm running full tests on 858 today (should be completed by the time I'm done work), but the informal tests I did last night suggest all is good. Assuming that to be the case, I highly recommend upgrading to 858 and then report anything that doesn't seem right. I really would like to see that log file. If you do send it to me, please tell me which games you were monitoring and the date. Even better, would be to prune the logs so they start at the time of the first monitored recording. :)

[kmp14]

Dumb question time. When looking at the Recording Schedule in the web ui for SRE, why does everything, including non-sports regular programming, have the Monitor? checkbox checked? Seems to me that this indicates that all recordings will be extended, at lest with the default padding, is this true?

[Slugger]

Dumb question time. When looking at the Recording Schedule in the web ui for SRE, why does everything, including non-sports regular programming, have the Monitor? checkbox checked? Seems to me that this indicates that all recordings will be extended, at lest with the default padding, is this true?

All recordings are monitored in SREv3, this is done for future enhancements - enhancements I will not be discussing at this time. ;)

Shows that will not be monitored (i.e. non-sports events) will NOT have the default padding applied. They simply query the web service, the web service replies that it is not a monitored event and then SRE immediately stops monitoring it (with no padding, extension, etc. applied).

[Slugger]

My testing on 858 has proven successful. I'm giving 858 the thumbs up! :thumb:

Everyone should be moving to 858 asap. This is especially true if you're running 856. 856 is bad, very bad!

[kmp14]

All recordings are monitored in SREv3, this is done for future enhancements - enhancements I will not be discussing at this time. ;)

Shows that will not be monitored (i.e. non-sports events) will NOT have the default padding applied. They simply query the web service, the web service replies that it is not a monitored event and then SRE immediately stops monitoring it (with no padding, extension, etc. applied).

I knew it was a dumb question. Thanks Slugger, excellent work!

[spacecadet]

All recordings are monitored in SREv3, this is done for future enhancements - enhancements I will not be discussing at this time. ;)

Shows that will not be monitored (i.e. non-sports events) will NOT have the default padding applied. They simply query the web service, the web service replies that it is not a monitored event and then SRE immediately stops monitoring it (with no padding, extension, etc. applied).

What happens if the web service is down? Is the default padding then applied to all recordings?

[Slugger]

What happens if the web service is down? Is the default padding then applied to all recordings?

Yes, but only if the web service was available at some point then went down at the time the recording started. If your server is never able to talk to the web service then default padding will never be applied.

livepvrdata.com runs on the Google cloud so the odds of it being down/unresponsive are low (definitely not 0%, but low). However, there are times when you will get errors (heavy load on the server handling your request, etc.), which will cause 500 errors from the cloud. These types of errors will cause default padding to be applied sometimes. I have yet to experience it (and I've been running against this web service a lot longer than anyone else), but with that said, it's definitely possible.

I may add a whitelist setting in SRE to restrict what program titles will be monitored against the web service, for those who are worried about this scenario. I'd like to hear about it if this actually happens to someone. SRE will log a message anytime it applies default padding to any recording so you will know if/when it happens to you. Alternatively, I may change the algorithm in SRE that determines when default padding is applied. A single check with the web service could fail, but 30 consecutive checks are just completely unlikely to fail (unless your internet connection is down). I'd like to avoid whitelisting, etc. because of planned enhancements, but I do understand the concerns here.

[spacecadet]

Yes, but only if the web service was available at some point then went down at the time the recording started. If your server is never able to talk to the web service then default padding will never be applied.

livepvrdata.com runs on the Google cloud so the odds of it being down/unresponsive are low (definitely not 0%, but low). However, there are times when you will get errors (heavy load on the server handling your request, etc.), which will cause 500 errors from the cloud. These types of errors will cause default padding to be applied sometimes. I have yet to experience it (and I've been running against this web service a lot longer than anyone else), but with that said, it's definitely possible.

I may add a whitelist setting in SRE to restrict what program titles will be monitored against the web service, for those who are worried about this scenario. I'd like to hear about it if this actually happens to someone. SRE will log a message anytime it applies default padding to any recording so you will know if/when it happens to you. Alternatively, I may change the algorithm in SRE that determines when default padding is applied. A single check with the web service could fail, but 30 consecutive checks are just completely unlikely to fail (unless your internet connection is down). I'd like to avoid whitelisting, etc. because of planned enhancements, but I do understand the concerns here.

The flip side of this is that the same result could occur if *my* internet connection is down (or any node between me and livepvrdata.com) - which I guess you mentioned above. Both of these are probably also unlikely, but aren't out of the realm of possibility.

I would say it's not a problem until it happens to someone and then it's probably a *huge* annoyance (possible missed recordings, etc).

I'm not advocating for doing anything about - just putting it out there as food for thought. I'll ponder this and let you know if any other solutions come to mind.

[Slugger]

Another new beta, 3.0.0.865, is ready, with a few key fixes:


Fix issue 127: Remove default padding if it was applied and then the event was successfully monitored (handle transient errors with livepvrdata)
Do not mark a recording's status as unknown if it was previously known (handle transient errors with livepvrdata)
Do not apply default padding to recordings if the status of the recording was previously determined to be NO_MONITOR (handle transient errors with livepvrdata)


These fixes should better address the concerns discussed last night. As was discussed, any recording would have default padding applied if livepvrdata was unavailable at the time the recording started (either livepvrdata was down/non-responsive or your internet was down, etc). These fixes address the issue, though it's not 100% bulletproof. However, now default padding would only be applied under this specific scenario:

Every single check with livepvrdata failed to receive a valid response up to the day of the recording.

AND

The check 30 mins prior to the start of the recording and the check at the start of the recording also failed.

With these fixes, now only ONE of these checks needs to succeed in order for the default padding not to be applied. Since most people's favs will appear on their recording schedule at least 3 days in advance then in order for default padding to be applied to a recording, your internet and/or livepvrdata.com must be down/non-responsive for at least 72 consecutive hours. Again, this is not impossible, but I think I've reduced the probability of this event occurring sufficiently to satisfy everyone's concerns. :) If I haven't, I'd like to hear why.

[cat6man]

hi slugger,

i've updated to your last 2 updates but think there is an "updating" problem inside SRE (no pun intended).
again tonight, i got an informational error that SRE could not identify the game for an MLB-HD game listed as 'regional game'. i know that won't work unless overridden, but i deleted those games from my schedule days ago and the informational errors are still appearing.

thx man

[Slugger]

hi slugger,

i've updated to your last 2 updates but think there is an "updating" problem inside SRE (no pun intended).
again tonight, i got an informational error that SRE could not identify the game for an MLB-HD game listed as 'regional game'. i know that won't work unless overridden, but i deleted those games from my schedule days ago and the informational errors are still appearing.

thx man

Good catch! ;) Once a recording's status is checked, it's always going to be validated daily, even if you cancel the recording. It also means system messages will be posted for these cancelled recordings (as you experienced). This has now been fixed. The fix will be in the next build.

[cat6man]

thank you muchly!

[ScubaMedic]

All recordings are monitored in SREv3, this is done for future enhancements - enhancements I will not be discussing at this time. ;)

Shows that will not be monitored (i.e. non-sports events) will NOT have the default padding applied. They simply query the web service, the web service replies that it is not a monitored event and then SRE immediately stops monitoring it (with no padding, extension, etc. applied).

So do these shows have to generate a system message? Is there a way to turn off SRE generating system messages? It sounds like SRE will be able to monitor these shows in the future so no system message will be generated but until then there are a lot of SRE system messages to go through.

Thanks for all the work. We really do appreciate it.

[Slugger]

So do these shows have to generate a system message? Is there a way to turn off SRE generating system messages?

Not currently, might add an option to disable them, but...

It sounds like SRE will be able to monitor these shows in the future so no system message will be generated but until then there are a lot of SRE system messages to go through.

If you're running 865 or newer then you should only be receiving "a lot" of system messages from SRE if your internet is constantly down or livepvrdata.com is constantly down. I can say that the latter is rarely, if ever, down (livepvrdata.com runs on the Google cloud, which is rarely, if ever, down). If you are on 865 or newer and are still receiving lots of system messages for non-monitored events then I'd like to see your sre.log file for analysis. I don't think you really want to disable system messages because they will alert you to recordings that actually do need an override and with the improvements that were made in 865, the number of false positive sys messages should be minimal. Again, if that's not the case then I'd like to see the sre.log file.

[panteragstk]

I've looked around this thread and can't find an answer to my question. Could you please point me to where it says what I need to do to enter my user id and password. I've gone into the cconfig in the plugin manager, but it says my password is incorrect. I made sure that it was correct and I am able to log into my google account. Where is a config file I can manually change to make sure my userid and password are correct?

[Slugger]

I've looked around this thread and can't find an answer to my question. Could you please point me to where it says what I need to do to enter my user id and password. I've gone into the cconfig in the plugin manager, but it says my password is incorrect. I made sure that it was correct and I am able to log into my google account. Where is a config file I can manually change to make sure my userid and password are correct?

What are the errors you're getting in the sre.log file? The settings are stored in Sage.properties, but for security, the Google password is not stored in plain text so you won't be able to edit the value directly in Sage.properties.

[sic0048]

I've looked around this thread and can't find an answer to my question. Could you please point me to where it says what I need to do to enter my user id and password. I've gone into the cconfig in the plugin manager, but it says my password is incorrect. I made sure that it was correct and I am able to log into my google account. Where is a config file I can manually change to make sure my userid and password are correct?

Log into the SRE web page (http://yourjettyhost:8080/sre) and at the bottom of the page there is a "Options" button. Pressing that will bring up a page that shows some options including the google account ID and password.

[ScubaMedic]

Again, if that's not the case then I'd like to see the sre.log file.

Ok I think this is the file.

It may be a connection problem. I'm on satellite internet so it takes things a while to make the trip and some programs don't like that and time out. The internet connection is usually not down though.

[Slugger]

Ok I think this is the file.

It may be a connection problem. I'm on satellite internet so it takes things a while to make the trip and some programs don't like that and time out. The internet connection is usually not down though.

It's not so much the connection is slow, it's that it's being reset (maybe by Google, on their end, but most likely on your end). Either way, I'll add an option to disable all system messages. It'll be in the next build. Of course, the trade off with disabling system messages is that legit override alerts won't be generated (via sys msgs, they'll still be logged in sre.log).

[ScubaMedic]

So how do you trace a connection being reset? Would that be a router problem or a WildBlue problem?

I would like to try and fix it so I can get the legit system messages.

It did work though when I recorded the hockey game. It may have just added the default and I didn't know the difference.

[Slugger]

My guess is that it's an issue with your link to the satellite, but that's only a guess and is backed by no evidence what so ever. In the best of situations, I'm not what'd you call a networking expert (especially WAN/ISP issues), but my knowledge is even less when considering I have absolutely no knowledge about your ISP setup.

All I can tell you about is the errors you've showed me. Your attempt to connect to the livepvrdata.com app (hosted on the Google cloud) is encountering connection reset errors - and lots of them; probably too many. If everyone were reporting the errors I'd say it's a Google problem, since no one else is (nor have I ever experienced them) then my guess is that it's a problem on your end. The fact that you're with a satellite ISP makes the argument stronger, but, again, I have no real evidence to back my guess up.

A new build that provides the ability to disable system messages is now in the repository. (This build also contains a few other fixes.)

[cat6man]

hi slugger,

i had my first failure with SRE when it didn't extend the sox-dodgers game today on Fox............so i missed the red sox bottom of the 9th rally to win the game.................i saw a green check on the game earlier in the day, but i'll have to check the log file and see if there is a clue there.

it has run flawlessly until the game today, so i'm inclined, a la Fox/Beck, to blame a conspiracy but i have a hard time figuring out how it would work.........left wing hollywood vs. people's socialistic republic of cambridge would both be on the right's * list, so maybe they wanted to annoy both bastions of liberalism and saw a 2 for 1 opportunity :confused:

or it could be just software or the internet, but that wouldn't be as much fun

edit: adding log..........game start at 4:00, note that it checked at 6:30 and set next check time for 6:30

[Slugger]

Based on the log, it seems you have a padding setup for the fav? The recording started at 15:59, but I assume it was actually in the EPG to start at 16:00? Is there also a 1 min (or more) padding at the end for the fav? I think I found the bug (don't account for padding, which triggers the wrong code path and tried to schedule an already scheduled task), but just want to confirm before adding the fix.

[cat6man]

yes, all my favorites have 1 minutes pads at both ends.......thanks

[Slugger]

Yeah, ok, the bug is fixed, but Google Code is having some problems preventing me from committing the changes. Once I can, a new build will be in the repository that contains the fix.

[cat6man]

got the latest update this morning, but won't have a test until tomorrow (sox are travelling to arizona on a day off)..............i did note that the download was brutally slow, like where you can count 1-2-3 (or more) in between % changes in download............something was slowing down this am......but it did seem to install ok

[Slugger]

This is a heads up that livepvrdata.com will be doing some testing on the cloud over the next couple weeks. They will be testing OAuth authentication with the web app and to do all of the required testing requires them to switch the production version of the app from the current one to the test version. SRE currently does not support this new version of livepvrdata.com so when they switch the web app, SRE will be broken.

I've been guaranteed that they will only switch during the day time and will switch it back by 6pm EDT daily, which means this should not affect most SRE users. The only side effect will be that pre game checks of events may fail during the day, but should recover by the start of recordings. With that said, anything could happen and SRE may be broken on some evenings. Should that happen, your recordings may not be extended. This is the price of volunteering my user base as test subjects. :)

Depending on their test results, they may upgrade to OAuth sooner rather than later, which means SRE will be immediately broken until I get OAuth support in. I'm pushing for them to hold off on the upgrades until the MLB All Star break, but I don't think they want to wait that long. Time will tell.

The move to OAuth is actually a good thing - it means I will no longer have to ask for nor store your Google Account id/pwd in SRE. You will simply authorize Live PVR Data to use your Google Account and SRE only has to store and maintain the authorization token received from Google. It also removes a lot of the hacked authentication mechanisms currently in use. So this change is actually welcomed, but it will require a new version of SRE to support it. Changes aren't huge, but will take some time so if they upgrade before the All Star break then I'm afraid SRE will be useless for a few days+.

livepvrdata.com will start testing OAuth on the cloud this week (as early as tomorrow afternoon).

I'll provide updates in this thread as they become available.

[cat6man]

This is the price of volunteering my user base as test subjects. :)


we are all lab rats :rofl:

[skiingwiz]

The manual flag is not being unset for me. I've tracked it down to the log section below. Two weird things are happening. (Which may or may not be related.)

1) The AiringMonitor seems to be kicking off twice. Every 2 minutes there are 2 runs (16 seconds apart in my log) of the AiringMonitor.
2) Somehow, the recording is ending before SRE thinks that it should.

Looking at the AiringMonitor code, it seems that the flag isn't unset because the next to last check determines that the event it over and sets isMonitored to false. The last check then determines that the airing is not recording, but doesn't change isMonitored. So in the finally block, the unsetManualFlag method is never called.

Any help figuring out how to fix this would be appreciated.


2010-06-24 23:10:04,912 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event not over; recording extended! [312ms]
2010-06-24 23:10:04,912 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:10:20,850 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event not over; nothing to be done! [172ms]
2010-06-24 23:10:20,850 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:12:04,897 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event not over; recording extended! [297ms]
2010-06-24 23:12:04,897 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:12:20,850 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event not over; nothing to be done! [172ms]
2010-06-24 23:12:20,850 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:14:04,787 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event not over; recording extended! [187ms]
2010-06-24 23:14:04,787 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:14:20,881 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event not over; nothing to be done! [203ms]
2010-06-24 23:14:20,881 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:16:04,803 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Event is over; recording will end at Thu Jun 24 23:18:00 EDT 2010 [203ms]
2010-06-24 23:16:04,803 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Next check in 2 minutes...
2010-06-24 23:16:20,678 INFO [AiringMonitor]: 'MLB Baseball: Pittsburgh Pirates at Texas Rangers': Airing is not recording; stopping monitor thread! [0ms]

[Slugger]

Are you running 3.0.0.872?

[skiingwiz]

Are you running 3.0.0.872?

Yes, I am. I have been for a few days prior to the log that I posted.

[Slugger]

Now that I'm actually awake and alert this morning, I studied this a little closer. ;)

The manual flag is not being unset for me. I've tracked it down to the log section below. Two weird things are happening. (Which may or may not be related.)

1) The AiringMonitor seems to be kicking off twice. Every 2 minutes there are 2 runs (16 seconds apart in my log) of the AiringMonitor.

This was a regression bug introduced. It's been fixed. Now, only one airing monitor can ever be invoked for the same airing id.

2) Somehow, the recording is ending before SRE thinks that it should.

Fixed - I think. You'll have to let me know. I believe there is a delay between me (SRE) resetting the end time of the recording and the Sage airing object actually reflecting that time on subsequent calls to read it. Should be fixed. It was just a display bug, the recording should have ended when it was ending - no logic problems, but it should obviously print when it actually is going to stop the recording.

Looking at the AiringMonitor code, it seems that the flag isn't unset because the next to last check determines that the event it over and sets isMonitored to false. The last check then determines that the airing is not recording, but doesn't change isMonitored. So in the finally block, the unsetManualFlag method is never called.

Excellent... a Java programmer! :D You found the cause of issue 132 (http://code.google.com/p/sagetv-addons/issues/detail?id=132). Don't be shy about submitting patches because I'm more than willing to apply them. ;)

Anyway, this has been fixed. A new build will appear in the repository shortly.

[skiingwiz]

Excellent... a Java programmer! :D You found the cause of issue 132 (http://code.google.com/p/sagetv-addons/issues/detail?id=132). Don't be shy about submitting patches because I'm more than willing to apply them. ;)

Guilty ;) Glad I could help. Next time, I'll look to submit a patch and save you some work.

Anyway, this has been fixed. A new build will appear in the repository shortly.
Awesome. Thanks for the quick turn around. I'll upgrade today and check out the changes.

[cat6man]

discussion of manual flag made me wonder:

what is the purpose of the config option regarding manual flag and favorites?
can you explain why i would turn it either on or off?

tx

p.s. it was so cool to have SRE record the entire 4:30 hour game in arizona the other
night............i appreciate SRE even more when night games are on the left coast and time
zones away!

[skiingwiz]

discussion of manual flag made me wonder:

what is the purpose of the config option regarding manual flag and favorites?
can you explain why i would turn it either on or off?

When SRE extends a recording that is a favorite, it has to convert it to a manual recording. (That's just the way Sage works.) If the config option is on, it will remove the manual recording flag once the recording is over. (Basically, setting it back to a favorite.)

I recommend turning it on. I don't see any disadvantage to having it on. If it is turned off and you have your favorite set to "Keep at most x recordings" (like I do), the recordings marked as manual won't count against that total, so they won't be automatically deleted.

[cat6man]

thanks..........sounds like a non-issue for me, so i'll just leave it on
(i archive all recordings each night from Sage's PC hard drive to an NAS)

[Slugger]

The Live PVR Data team has went ahead with its latest update, which moves the entire service to OAuth authentication. This change immediately breaks all versions of SRE. :(

Good news: I have an initial update for SRE that adds OAuth support. It is very, very rough around the edges, but is functional.

Basically, after upgrading you will get a system message telling you that SRE needs a google access token and will tell you to visit /sre/ in Jetty. Load the SRE web GUI and it will immediately present the Google authorization window. You have to click the first button (I know it's ugly/cut off, but I have to head out for the day by 1pm :)) to bring up the Google site. Login to Google as directed and grant livepvrdata.com access to your Google account. Google will respond with a verification code. Feed that code back into SRE and click the second button. All goes well and SRE will proceed. That's it, everything else is the same except SRE no longer (directly) asks for nor stores your Google credentials.

Undoubtedly there will be some problems, I've only been able to do some basic initial testing. But without this update, SRE has a 0% chance of working. Hopefully just a few minor patches to address any issues that arise. Please report any problems and I'll get them addressed ASAP.

The updated SRE will appear in the repository shortly.

[cat6man]

that explains the sre message yesterday and today.........since the sox
play at 1pm today, the game has already started and since sre update requires a re-start, i'll wait until tonight to start testing it out.

let me know if there is anything other than the above you want me/us to check out

[cat6man]

update procedure went fine here (note: needed to close and reopen browser since cached SRE page was old one)

testing with ray/twins game now to see if it gets monitored

pretty quick turn around there slugger!

[Slugger]

pretty quick turn around there slugger!

I was given plenty of warning about this change and have been working on this here and there for a couple of weeks. Admittedly, the changes shouldn't be as rough as they are, but then again, it's way too nice to be sitting in front of a laptop at this time of the year hashing out UI issues. ;) Hell, it's too nice out right now to be doing any kind of coding that doesn't pay the bills! :D (Now back to the bbq to finish up dinner... ;))

[cat6man]

didn't seem rough around the edges at all............and i can report that sre.log
shows it worked correctly on the rays/twins game i picked as a test recording

looks fine from here (just back from the family bbq)

[Slugger]

I disabled monitoring via an override b/c I knew that it can't be monitored via livepvrdata.com, but I wish I hadn't b/c now I want to know how SRE handles it. Can someone fill me in on how SRE handles this? Is the default padding applied? My review of the source code suggests that it won't apply default padding because it is a valid event type ("MLB Baseball"), but SRE will be told the event details are invalid (i.e. SRE is asking livepvrdata for details on an invalid event for a valid event type so it's a client error). What do you think SRE should do in this case? The current logic (assuming default padding isn't applied) is that since the event is not valid and was never valid then SRE should just do nothing with the recording. Now I'm wondering if default padding should be applied in this case? Either way, I wouldn't expect any kind of padding to be applied to recordings of the derby tonight.

Either way, if someone could fill me in on what happens I'd appreciated it. Appropriate portions of your sre.log file will also be helpful.

FYI: livepvrdata.com won't be changing data sources for MLB anytime soon (though they eventually will be moving to mlb.com) so we won't know if the all star game can be monitored until espn.com updates their feed tomorrow afternoon. If espn.com is not providing the feed for the all star game then SRE will not be able to monitor the all star game either. The last few all star events (NBA, Pro Bowl) were not carried in the espn.com feed so I'm not too hopeful at this point. Since livepvrdata.com is still in closed beta, they aren't rushing to change the data sources just yet so we're stuck with whatever espn.com decides to do. I'll add another post once I know tomorrow.

EDIT: Today's SRE update (884) claimed to fix a bug with handling overrides that disable the monitor for the recording. The fix isn't quite right and doesn't work. I've since fixed it and checked in the fix, but won't be rushing to post a new build.

[skiingwiz]

You are correct, no default padding was applied. I've attached a portion of my log, though I'm not sure it will tell you anything that you don't know.

As for what SRE should do, I am not sure where I fall on this. I can understand the logic that is currently being used. At the same time, I'd hate to miss something because it couldn't be monitored. I guess I'd rather the default padding be applied. Of course, that could get you into the situation where that causes conflicts with other recordings... It's a complicated issue.

[Slugger]

Unfortunately, the all star game is not in the ESPN Bottom Line feed for today so therefore livepvrdata.com will not be able to monitor tonight's game. After last night's results, it is clear that the current version of SRE will not apply default padding in this scenario so you may wish to add padding manually. I'm still not sure whether or not SRE should be applying default padding in this case, but either way I will not have time to make such a change and properly test it before tonight so you'll have to manually pad the recording, if desired.

Eventually, livepvrdata.com will be moving to the mlb.com feed for baseball, but there is no eta for that change at this time.

[cat6man]

well, there is no rush since there won't be another all star game until a year from now :D

[spacecadet]

I've noticed that over the last week or so most (all?) of my sports recordings are being extended with the default padding.

Not sure what to make of this except the Red Sox are on the West Coast this week and the games are ending after midnight. Anyone else who records the Red Sox having this issue? All I know is that lately, I've been seeing about 2 dozen system messages a week related to SRE.

Let me know how I can help to debug.

Errors in the log look like this:

2010-07-24 01:34:00,401 INFO [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Seattle Mariners': Next check in 2 minutes...
2010-07-24 01:34:27,667 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:148)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:63)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

[Slugger]

I need the entire sre.log file starting at 10pm (when the game started). It does appear to be a bug with either my code or the livepvrdata lib when the date changes over at midnight. I'll have to do some more testing, but the complete log for the game is a good place for me to start.

[cat6man]

I've noticed that over the last week or so most (all?) of my sports recordings are being extended with the default padding.

Not sure what to make of this except the Red Sox are on the West Coast this week and the games are ending after midnight. Anyone else who records the Red Sox having this issue? All I know is that lately, I've been seeing about 2 dozen system messages a week related to SRE.



i was going to post the same thing here about the sox games on the west coast getting the default padding and an error message saying it couldn't be monitored.

let me know if you need a 2nd log.

[Slugger]

i was going to post the same thing here about the sox games on the west coast getting the default padding and an error message saying it couldn't be monitored.

let me know if you need a 2nd log.

More logs are never a bad thing... send it my way, please. Just prune it so it starts when the game started.

[spacecadet]

I need the entire sre.log file starting at 10pm (when the game started). It does appear to be a bug with either my code or the livepvrdata lib when the date changes over at midnight. I'll have to do some more testing, but the complete log for the game is a good place for me to start.

Check your PM for a copy of my log file.

Thanks!

[cat6man]

another log for overnite recording with the same problem (same angels/sox going
past midnight local time)

[Slugger]

another log for overnite recording with the same problem (same angels/sox going
past midnight local time)

Can you PM me your IP address? Assuming it's the one I see in the livepvrdata.com logs sent to me then I can clearly see that there's a bug. When the game starts it correctly used the date '20100727' but then at the 12:30am status check it queried the event using the date '20100728', which is obviously the problem. I just haven't had time to investigate whether it's an SRE bug or a bug with the livepvrdata library.

Trust me, this is my #1 priority once I have a few spare cycles, but there's just lots of "life" things going on right now that are chewing up all of those free cycles that are coming my way. Rest assured, however, that I will get to this asap. I've created a ticket (http://code.google.com/p/sagetv-addons/issues/detail?id=137&colspec=ID%20Stars%20Type%20Plugin%20Status%20Priority%20Milestone%20Owner%20Summary) for this issue and interested users may want to star that ticket at the project site to receive email updates as progress is made.

[cat6man]

hi slugger,

please, there is really no rush to get this fixed..........when you have time to get to it is cool (plus the sox are done with the west coast now :D).......real life takes precedence, plus it is summer vacation time

as for my IP address, do you mean the ip address for the fios WAN side?

cheers

[Slugger]

as for my IP address, do you mean the ip address for the fios WAN side?

cheers

Yes, please.

[Slugger]

Snapshot 901 is now in the repository. This build contains the fix for the "airing monitor fails after midnight" bug (issue 137). It also contains the fix for issue 136 (unable to create overrides for future events).

These fixes are bundled with various GUI fixes, which are functional, but not complete. After playing with both SmartGWT and GXT, I've decided I like GXT better and have begun converting SRE from SmartGWT to GXT. These changes aren't complete, but are at a stage that everything that needs to be functional is and in order to deliver the "midnight" fix in a timely fashion, I also had to deliver the GXT fixes.

Please report back your results, especially if you find any bugs.

[Slugger]

Please report back your results, especially if you find any bugs.

I don't record many late games and only did a couple to test the "midnight" fix. If anyone else is recording late games please let me know how it goes with 901.

[Sparhawk6]

Slugger, when I click "get auth code," I get a "HTTP ERROR 404" error with a very long URL and "NOT_FOUND" at the bottom. How do I fix that?

[Slugger]

Slugger, when I click "get auth code," I get a "HTTP ERROR 404" error with a very long URL and "NOT_FOUND" at the bottom. How do I fix that?

Fixed in snapshot 903.

[Slugger]

The livepvrdata.com team had released their latest (closed) beta, which is an API breaker from previous releases. I'm testing the updates required in SRE and will get an update in the repository asap. SRE is broken until you upgrade. (Hopefully it's no more than a couple hours before the update is in the repository.)

[Slugger]

A little ahead of schedule and ready in time for tonight's games! :)

No actual code changes required to support the latest livepvrdata4j lib, I just had to change the dependencies in sre to require the latest lib. As an added bonus, this snapshot includes an early preview of the ported global override editor. It's functional, but a little buggy still. Should be ready in plenty of the time for the start of NCAA football (where it's needed most).

[kchase56]

I'm running the latest 906 build of SRE and my log file has the following types of errors =>

2010-08-05 21:41:50,290 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-05 21:41:50,627 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-05 21:41:50,915 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-05 21:41:50,944 INFO [MonitorStatusChecker]: Done monitor status check. [2406ms]


Any light you could shed on this problem would be greatly appreciated.

Thanks

[Slugger]

Those errors are normal. They mean that SRE is trying to validate games on future days, but livepvrdata.com is not able to. This is because livepvrdata.com is using the ESPN.com Bottom Line feed as its source for MLB scores and that feed only supports the current day's games so when SRE asks livepvrdata to verify a future game, livepvrdata fires an error saying it can't verify the event. Even though it's an expected error, SRE still logs it as an error with the stack trace b/c SRE does not know what's an "expected" error and what isn't. This extra logging is necessary to ensure that "unexpected" errors are fully logged as well.

Once a game starts recording then you should see log entries from "[AiringMonitor]" describing that it's properly monitoring the game or you should get a system message in sagetv saying that there is a problem monitoring the active recording. If you get the latter, then I definitely want to see those logs.

[kchase56]

Basically SRE has stopped monitoring events all together. What can I send you to help debug this issue? The SRE.log file contains nothing but items like what I previously posted, so I don't think that it would be of any use to you.

Here is what was logged during the recording of the Red Sox vs. Cleveland game yesterday =>

2010-08-04 19:08:46,922 INFO [AiringMonitor]: 'MLB Baseball: Cleveland Indians at Boston Red Sox': Next check at Wed Aug 04 21:30:00 EDT 2010
2010-08-04 19:09:07,750 WARN [OverrideValidator]: OverrideValidator error
java.io.IOException: <html>
<head>
<title>Status page</title>
</head>
<body style="font-family: sans-serif;">
<h3>Method Not Allowed</h3><p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.6">here</a>.<br>
Please continue your visit at our <a href="/">home page</a>.
</p>
</body>
</html>

at com.google.code.livepvrdata4j.Client.submit(Client.java:99)
at com.google.code.livepvrdata4j.Client.submit(Client.java:90)
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:161)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2



Thanks

[Slugger]

You were still running 903 after the livepvrdata.com upgrade, which required 906 to operate. Show me [AiringMonitor] logs from last night (Aug 5) where a game was not being properly monitored (assuming you had also upgraded to 906 by then).

[kchase56]

I'm currently recording the Red Sox vs Yankees game and I'm seeing the following in the log =>

2010-08-06 19:11:25,574 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-06 19:11:25,846 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-06 19:11:26,133 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-06 19:11:26,415 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)


The game started at 7:00 PM and it's currently 8:54 PM and I'm still getting these errors in the log. Any ideas what might be going on?

Thanks

[Slugger]

[OverrideValidator] errors are nomal, they have nothing to do with a game that is currently being recorded. SRE checks the status of future events every 30 minutes and in the case of MLB, you will get those errors, as explained above.

For the game that's currently recording, look for an entry in the sre.log from [AiringMonitor] at 7:00pm (or whatever time the game started recording). That check should tell you the game is not over and that it'll check again at (about) 9:30pm (or 30 mins before the scheduled end of the recording). It's at that time when the game will actually start monitoring.

[kchase56]

I'm only seeing [AiringMonitorManager] messages and not any [AiringMonitor] messages in my SRE.log. These messages are as follows =>

2010-08-06 00:09:24,915 INFO [AiringMonitorManager]: Unsubscribed from recording started events!
2010-08-06 00:10:58,351 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-06 00:10:59,390 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-06 00:11:10,215 INFO [AiringMonitorManager]: Subscribed to recording started events!
2010-08-06 00:11:10,229 INFO [AiringMonitorManager]: Initializing monitors for 0 active recording(s).
2010-08-06 00:11:10,230 INFO [AppEnv]: Registered for recording schedule change events!
2010-08-06 00:11:25,275 INFO [DataStore]: Reading data store from 'C:\SageTV\SageTV\plugins\sre\sre.sqlite'
2010-08-06 00:11:25,680 WARN [OverrideValidator]: OverrideValidator error

Any ideas? I love this app and I hate to miss the end of these marathon Red Sox vs Yankee games. Tonight's recording stopped at 10:00 PM, yet the game continued beyond this time.

Thanks

[freewheeling]

Basically, after upgrading you will get a system message telling you that SRE needs a google access token and will tell you to visit /sre/ in Jetty. Load the SRE web GUI and it will immediately present the Google authorization window. You have to click the first button (I know it's ugly/cut off, but I have to head out for the day by 1pm :)) to bring up the Google site. Login to Google as directed and grant livepvrdata.com access to your Google account. Google will respond with a verification code. Feed that code back into SRE and click the second button. All goes well and SRE will proceed. That's it, everything else is the same except SRE no longer (directly) asks for nor stores your Google credentials.

Undoubtedly there will be some problems, I've only been able to do some basic initial testing. But without this update, SRE has a 0% chance of working. Hopefully just a few minor patches to address any issues that arise. Please report any problems and I'll get them addressed ASAP.

The updated SRE will appear in the repository shortly.

I don't understand what any of this means. What does "in Jetty" mean? How do you visit a site "in Jetty"? Is /SRE/ a website? Load the GUI into what? I just don't understand any of it. I've really never understood what I'm supposed to do with this plugin.

I know that Jetty is like a browser, but how do you start it or use it? How would you "visit/SRE" in it? This thread is so jargon-heavy that I just can't make any sense of it, and the same goes for the stuff on the internet about it. I've tried changing the username and password in the Jetty plugin but it tells me I have the wrong password or user name, and all I did was inter my google account name and password. Also entered the entire gmail address, and that didn't work either.

"load the SRE Web GUI" What's the SRE web GUI and what do I load it in? The plugin manager? Is the GUI one of those icons to the right? The jargon is getting me really frustrated.

[Slugger]

I'm only seeing [AiringMonitorManager] messages and not any [AiringMonitor] messages in my SRE.log. These messages are as follows =>

2010-08-06 00:09:24,915 INFO [AiringMonitorManager]: Unsubscribed from recording started events!
2010-08-06 00:10:58,351 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-06 00:10:59,390 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-06 00:11:10,215 INFO [AiringMonitorManager]: Subscribed to recording started events!
2010-08-06 00:11:10,229 INFO [AiringMonitorManager]: Initializing monitors for 0 active recording(s).
2010-08-06 00:11:10,230 INFO [AppEnv]: Registered for recording schedule change events!
2010-08-06 00:11:25,275 INFO [DataStore]: Reading data store from 'C:\SageTV\SageTV\plugins\sre\sre.sqlite'
2010-08-06 00:11:25,680 WARN [OverrideValidator]: OverrideValidator error

Any ideas? I love this app and I hate to miss the end of these marathon Red Sox vs Yankee games. Tonight's recording stopped at 10:00 PM, yet the game continued beyond this time.

Thanks

If there's nothing in the log from AiringMonitor then


SRE has crashed and therefore is not monitoring any recordings
The Sage core event dispatcher thread has crashed and is therefore no longer firing events for SRE to receive and act upon
Some other thread/plugin is hogging the event dispatcher thread such that SRE cannot receive the recording started events
Monitoring is disabled in the SRE settings


If it's #1 then you should enable debug logging in Sage and look for exception dumps from SRE. If it's #2 or #3 then there is a debug option for adding output from the dispatcher thread to the Sage debug logs; the details slip my mind at the moment. #4 seems unlikely because there would be log messages in sre.log saying that was the case.

Either way, if the problems persist a lot of debugging will be necessary. PM me if you want to head down this road. I'm out of town until Sunday or Monday so it'll be at least a couple days before I'm even at home again to be able to start debugging this.

[Slugger]

I don't understand what any of this means. What does "in Jetty" mean? How do you visit a site "in Jetty"?

Jetty is a web application server plugin for SageTV. People, such as me, write plugins that run as web apps. Jetty hosts and serves these apps, which are typically viewed in a web browser. I assume one has some understanding of the software they install on their systems and therefore take a few liberties when describing things.

Is /SRE/ a website?

Yes, well, technically it's the context of a web application (yeah, lots more jargon in this sentence) served by Jetty, but that's really just semantics. For simplicity's sake, let's just say, "sure it's a URI to a web site hosted by Jetty."

Load the GUI into what?

A web browser. The URL is http://your_sage_server_ip:jetty_port/sre/

The default port is 8080 (I believe, but that's configurable). An example of where you might visit would be http://192.168.0.1:8080/sre/ - assuming your SageTV server is located at IP address 192.168.0.1 and your installation of the Jetty plugin is configured to run on port 8080, adjust accordingly.

I just don't understand any of it. I've really never understood what I'm supposed to do with this plugin.

If you want to monitor and extend live sporting event recordings then install this plugin, if you don't then don't install it.

I know that Jetty is like a browser, but how do you start it or use it?

No, Jetty is not a web browser. It is a J2EE application container. It runs applications. Typically one accesses the applications it hosts via a web browser.

When you install SRE (in Sage v7) it automatically installs and starts Jetty because SRE is dependent on Jetty.

How would you "visit/SRE" in it?

See above (re: http://192.168.0.1:8080/sre/)

This thread is so jargon-heavy that I just can't make any sense of it, and the same goes for the stuff on the internet about it. I've tried changing the username and password in the Jetty plugin but it tells me I have the wrong password or user name, and all I did was inter my google account name and password. Also entered the entire gmail address, and that didn't work either.

Jetty's default id and password have nothing to do with your Google Account. The default id is "sage" and the password is "frey". I believe this is documented in the Jetty wiki. Furthermore, the only place you should be entering your Google id and password is on the Google web site when redirected by SRE. SRE never directly prompts you or asks for your Google credentials.


"load the SRE Web GUI" What's the SRE web GUI and what do I load it in? The plugin manager? Is the GUI one of those icons to the right? The jargon is getting me really frustrated.

Deep breath... the web GUI in SRE refers to the SRE web site located at http://your_server_ip:your_port/sre/

I can't help you learn all the terminology, you'll either pick it up as you go or you'll uninstall the plugin. I'll eventually rewrite the user guide for SREv3, but it's just going to contain a lot of the same terminology used above. If it's not user friendly enough then I challenge you to learn it and contribute a "Jetty apps for the less technical" type documentation. Keep in mind these plugins aren't written by a large team - it's a one man show. I write it, I document it, I support it. The problem with that is I'm so familiar with the inner workings of everything that I tend to take some things for granted when it may not be as obvious to others. I know this happens, I try to avoid it, but it's inevitable. It's the price one pays for free software. You want a 100 page "easy to understand" manual for a plugin that's but a couple thousand lines of Java code (if that) then I'd have to quit my job and make this my full time job. Needless to say, this hobby doesn't pay the mortgage.

Familiar with the saying, "no such thing as a free lunch"? Well, the plugin is free, the source code is free and open source, the support I provide is free, but there is a price. Namely, if you don't know how this all works then you're going to have to do some homework and try to learn. On that front, I'm more than willing to help and answer questions, but you've got to meet me half way. Just telling me your frustrated isn't going to get you using this plugin any faster. It sounds like you might want to start learning about Jetty and what it does. Once you understand that then hopefully it's more clear how SRE fits into the picutre. Then you study in more detail what SRE is doing and then hopefully the full picture is clear.

Now I'm down from the adrenaline rush I got at the poker tables tonight and will have no problems falling asleep now... good night.

[voorhees]

Well it has been since last football season since I recorded anything that SRE needed to potentially extend. Also since then the web interface has changed, and my guess is that is where I am a little stumped and probably missing something easy.

I have a manual recording set for the NFL Hall Of Fame game tonight. I do not see any indication in the SRE web GUI that it is going to be monitored any differently than my other upcoming recordings, as I used to in the previous version. The SRE web GUi shows:

4145224 NFL Football Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys 8/8/10 6:00 PM - 9:00 PM

I checked the EPG Maps web page and it says:

Current day's events for 'nfl' unless it's before noon ET then this will be yesterday's events.
Dallas at Cincinnati (8:00 PM ET)


I have tried changing the episode name from "Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys" to many things:

Cincinnati Bengals vs. Dallas Cowboys
Cincinnati vs. Dallas
Dallas at Cincinnati
Dallas vs. Cincinnati
Bengals vs. Cowboys
Dallas vs. Cincinnati

And, for everyone of them I get a message "The override you created is invalid and was deleted!" I looked on the SRE Google code web site but did not see anything covering the latest version of SRE and use of overrides and monitoring. I am assuming the game should be monitored since it is on the EPG Maps feed. Is there any indication that the game will be monitored somewhere? Why am I unable to create an override for the game tonight (assuming I am doing it right)?

Any help would me greatly appreciated. Thanks.

P.S. - I am using SRE 3.0.0.906 according SageTV. I am unable to check the version on the web GUI using the help button anymore though.

[Slugger]

Well it has been since last football season since I recorded anything that SRE needed to potentially extend. Also since then the web interface has changed, and my guess is that is where I am a little stumped and probably missing something easy.

I have a manual recording set for the NFL Hall Of Fame game tonight. I do not see any indication in the SRE web GUI that it is going to be monitored any differently than my other upcoming recordings, as I used to in the previous version. The SRE web GUi shows:

4145224 NFL Football Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys 8/8/10 6:00 PM - 9:00 PM

I checked the EPG Maps web page and it says:

Current day's events for 'nfl' unless it's before noon ET then this will be yesterday's events.
Dallas at Cincinnati (8:00 PM ET)


I have tried changing the episode name from "Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys" to many things:

Cincinnati Bengals vs. Dallas Cowboys
Cincinnati vs. Dallas
Dallas at Cincinnati
Dallas vs. Cincinnati
Bengals vs. Cowboys
Dallas vs. Cincinnati

And, for everyone of them I get a message "The override you created is invalid and was deleted!" I looked on the SRE Google code web site but did not see anything covering the latest version of SRE and use of overrides and monitoring. I am assuming the game should be monitored since it is on the EPG Maps feed. Is there any indication that the game will be monitored somewhere? Why am I unable to create an override for the game tonight (assuming I am doing it right)?

Any help would me greatly appreciated. Thanks.

P.S. - I am using SRE 3.0.0.906 according SageTV. I am unable to check the version on the web GUI using the help button anymore though.

A few things to point out here...

First, monitoring of the game should succeed (now - as of 19:00 EDT). The problem was that livepvrdata.com did not have support for NFL monitoring turned on. It's since been turned on. I've verified myself that it appears to be working now. You might have to delete any overrides you've created, depending on which one you currently have in there.

Second, sre-maps.appspot.com is no longer used by SRE. SREv3 exclusively uses the livepvrdata.com web service for all its monitoring data. Eventually, you'll be able to go to livepvrdata.com and view/modify the override maps, etc., but since they're still in a closed beta that's not available yet. However, SRE 3.0.0.906 does have it's own global override editor linked to livepvrdata.com so you can edit the map that way - it's a little buggy, but it's getting there.

Finally, the Help menu, etc. are still missing. Slowly but surely it'll reappear. :)

Let me know if the game doesn't monitor after removing overrides. If it doesn't then I would like to see your sre.log file. I've set up the game to record (after 19:00 EDT) and SRE was able to get the proper response from livepvrdata.com so I expect it to be able to monitor fine.

[voorhees]

Slugger thanks for the response. That clears up a few things. I did not have an override since it always gave me the "Invalid Override" message. However, now when I go to the SRE web GUI I still do not see anything different. There is no indication that the game is being monitored other than there is a check mark in the Monitored box like every other scheduled recording. What indicator do you have that it is being monitored by SRE? It will now allow me to create an override, do I need to create an override to have SRE monitor the game? A few things cleared up but I am still unclear as to how to I get SRE to extend the game (if needed) or even check if SRE is monitoring the game. :confused:

Thanks.

[Slugger]

Slugger thanks for the response. That clears up a few things. I did not have an override since it always gave me the "Invalid Override" message. However, now when I go to the SRE web GUI I still do not see anything different. There is no indication that the game is being monitored other than there is a check mark in the Monitored box like every other scheduled recording. What indicator do you have that it is being monitored by SRE? It will now allow me to create an override, do I need to create an override to have SRE monitor the game? A few things cleared up but I am still unclear as to how to I get SRE to extend the game (if needed) or even check if SRE is monitoring the game. :confused:

Thanks.

No override necessary. Have a look in SageTV/plugins/sre/sre.log - it will tell you what's going on. This port to Sage v7 is still in beta - the GUI is still being worked on. The log file will tell you exactly what the plugin is up to. There should be an entry for 8pm in that log saying that it's monitoring the game.

[Slugger]

However, now when I go to the SRE web GUI I still do not see anything different. There is no indication that the game is being monitored other than there is a check mark in the Monitored box like every other scheduled recording. What indicator do you have that it is being monitored by SRE?

There are status icons that will be shown on the next update - the code's already checked in, I'm just working on a few other things that I want to clean up before uploading a new build to the Sage plugin repository.

It will now allow me to create an override, do I need to create an override to have SRE monitor the game?

No. As a matter of fact, SRE will generate a system message in SageTV when it believes you may need to create an override. No system message, no override needed.

A few things cleared up but I am still unclear as to how to I get SRE to extend the game (if needed) or even check if SRE is monitoring the game.

The sre.log file is the definitive place to go to see what the plugin is doing. Eventually a lot of the key data in that log file will be portrayed within the GUI, but I'm still not quite there yet.

You don't need to create overrides unless you get a system message from SRE telling you that it thinks you need one. Typically, that should only really be necessary for NCAA events. All the pro sports (that are supported) have the maps setup properly already so if SRE generates a system message for a pro sport then it's likely that a software update will be needed. NCAA is a different beast because there are just too many schools and abbreviations used in the EPG data to try and pre-fill the maps - that's why the global override editor is available so that the user community can help get the maps for NCAA filled in.

[voorhees]

There are status icons that will be shown on the next update - the code's already checked in, I'm just working on a few other things that I want to clean up before uploading a new build to the Sage plugin repository.

No. As a matter of fact, SRE will generate a system message in SageTV when it believes you may need to create an override. No system message, no override needed.

The sre.log file is the definitive place to go to see what the plugin is doing. Eventually a lot of the key data in that log file will be portrayed within the GUI, but I'm still not quite there yet.

You don't need to create overrides unless you get a system message from SRE telling you that it thinks you need one. Typically, that should only really be necessary for NCAA events. All the pro sports (that are supported) have the maps setup properly already so if SRE generates a system message for a pro sport then it's likely that a software update will be needed. NCAA is a different beast because there are just too many schools and abbreviations used in the EPG data to try and pre-fill the maps - that's why the global override editor is available so that the user community can help get the maps for NCAA filled in.

Thanks so very much for the info. That clears up all my questions. I did create an override right after posting just to see if the GUI changed if I created one. No change, but now I know why. I checked the log and it looks like it is working great.

2010-08-08 20:31:05,296 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Event not over; nothing to be done! [312ms]
2010-08-08 20:31:05,296 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Next check at Sun Aug 08 20:33:05 MDT 2010
2010-08-08 20:33:05,578 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Event not over; nothing to be done! [282ms]
2010-08-08 20:33:05,578 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Next check in 2 minutes...
2010-08-08 20:35:05,562 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Event not over; nothing to be done! [266ms]
2010-08-08 20:35:05,562 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Next check in 2 minutes...
2010-08-08 20:37:05,562 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Event not over; nothing to be done! [266ms]
2010-08-08 20:37:05,562 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Next check in 2 minutes...
2010-08-08 20:39:05,578 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Event not over; nothing to be done! [282ms]
2010-08-08 20:39:05,578 INFO [AiringMonitor]: 'NFL Football: Hall of Fame Game: Cincinnati Bengals vs. Dallas Cowboys': Next check in 2 minutes...

Thanks so much again for your help and the great info on the current behavior. I know you guys have been using SRE a good bit with the baseball season, but my SRE season is just starting up. This has been one of my most valuable plugins for a couple of years and thank you very much for all of your hard work.

[Slugger]

Snapshot 3.0.0.915 is now available in the repository. Other than a couple minor touchups on the GUI, I believe this to be feature complete for v3.0.0. I ask everyone to upgrade and provide any feedback at all. If there's something missing/not working/doesn't look right/etc. then this is the time to bring it up. If I hear nothing then I'll probably tag this as official and SRE will be going on the back burner for a little while (except for reported bugs and any required changes to maintain support with livepvrdata.com).

[vividweb]

Slugger

How does LivePVRdata affect what can be monitored? Is it now easier to add new sports/events to be monitored? I know I have asked about CFL previously, but wonder if anything has changed now with the monitoring service.

[Slugger]

Slugger

How does LivePVRdata affect what can be monitored? Is it now easier to add new sports/events to be monitored? I know I have asked about CFL previously, but wonder if anything has changed now with the monitoring service.

Eventually, more sports/event types should be added, but it's out of my control - sort of. SRE now supports monitoring for whatever livepvrdata.com supports. The nice thing for me is that I got to remove all of the code that used to be in SRE for downloading, parsing, and interpreting web pages of scores. Now I just include the livepvrdata.com jar file and use their API. This is a life saver. It also means that broken parsers, etc. are no longer an SRE issue. Once a parser is fixed (at livepvrdata.com) then SRE is immediately and automatically fixed (with no updates required for SRE).

I say what's supported is "sort of" out of my control. That's because I'm in close contact with the livepvrdata.com team and am helping some with their (sports) monitors. So if something could be added, I can talk to them directly and perhaps make it happen - no promises though. With that said, livepvrdata.com is still in a closed beta and during the closed beta they are not focusing on adding all kinds of event monitors, but are focused on developing their app. Therefore I suspect what's supported now is not going to change any time soon and what's supported now are the 4 big pro sports (NFL, MLB, NBA, NHL) and NCAA football and basketball. These will probably be the only sports supported for the near future.

I'm more than willing to suggest CFL support (or any other event type), but the first thing they'll ask me is "where's the data source, is it near real time, and can it be easily consumed and interpreted?" And so that's my first question to you. If you can find the data source, I'll send it to them. Of course, this was always the same deal with older versions of SRE, except I was the one left to write the ugly piece in the middle that "consumed and interpreted" the data source. My deal has always been, you find the data source and I'll do the rest. Well, now the deal is, you find the data source and I'll do my best to have livepvrdata.com support it. Some events are going to be tougher than others. I suspect CFL football will be tougher, but at the end of the day I believe their goal is to support as many events as possible so, again, find the data source and I'll contact them about it.

[vividweb]

There should be something close to real time for CFL, especially with the new app that is out for BB and soon for iPhone. But whether that data is public or not will be the question.

I'll see if I can catch a game live. So used to just letting sage grab it, and watching later that never think to look when a game is actually on. If I find something I'll pass it on.

Glad you were able to find some way to get some help with your projects. You need to take some time and just watch TV. :)

[larryf]

Tried a test game tonight (wanted to be sure I have this working before the 'real' NFL season starts)... Got the following message:

2010-08-12 20:00:02,358 INFO [AiringMonitor]: 'NFL Preseason Football: Carolina Panthers at Baltimore Ravens': Unmonitored event; ending monitor

I'm assuming the pre-season NFL is not monitored? If that's the case, it looks like I have everything set up correctly with no other errors in the logs.

Thanks,
Larry

[Slugger]

Tried a test game tonight (wanted to be sure I have this working before the 'real' NFL season starts)... Got the following message:

2010-08-12 20:00:02,358 INFO [AiringMonitor]: 'NFL Preseason Football: Carolina Panthers at Baltimore Ravens': Unmonitored event; ending monitor

I'm assuming the pre-season NFL is not monitored? If that's the case, it looks like I have everything set up correctly with no other errors in the logs.

Thanks,
Larry

Yes, "NFL Preseason Football" isn't supported, however, you can override the title to "NFL Football" and then SRE will attempt to monitor it. Be sure the game isn't a replay or tape delay otherwise SRE may be told the game is over way too early and then just stop the recording (if end early setting is enabled). This is the main reason why preseason NFL isn't supported by default (too many games are replayed/tape delayed and fool SRE when it tries to monitor them).

[Sparhawk6]

I can't seem to log in to SRE at all. Going to http://192.168.1.8:7650/sre/ (my server's address and the jetty port), gives me HTTP ERROR: 404

Problem accessing /sre/. Reason:

NOT_FOUND

The log file says that SRE is being loaded into Jetty:

2010-08-05 15:06:05,130 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-05 15:06:05,958 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-06 11:48:07,849 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-06 11:48:09,786 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-14 16:54:24,535 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-14 16:54:28,019 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-14 17:04:31,175 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-14 17:04:31,238 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-14 17:06:06,035 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-14 17:06:06,082 INFO [SrePlugin]: Deployment into Jetty completed!
2010-08-14 17:11:20,800 INFO [SrePlugin]: Deploying SRE app within Jetty plugin...
2010-08-14 17:11:20,863 INFO [SrePlugin]: Deployment into Jetty completed!

Running the latest version. What's the deal?

EDIT: I also just tried http://localhost:7650/sre/ on the server machine, but I still get the same error.

[Slugger]

Typically that means SRE encountered an error during its initialization. To determine this, we need Jetty logging turned up and then look for exception dumps in the sagetv and/or jetty log files. Disabling SRE then reenabling it may get you started up again. If the same symptoms occur then there is likely an error at startup causing it to not load properly. Good news is, with a stack trace the problem is usually easily fixed; bad news is, without proper jetty logging enabled then the stack trace may never be logged.

If you continue to have problems, grab me on msn messenger (my id is my email, pm me if you don't have my email) and we can track it down (might take awhile, depending on the issue).

[cat6man]

hi slugger,

i may be having a new issue here........what do you think?

i set up a favorite to record all red sox games on a set of mlb extra innings channels.

in addition, i manually set up a recording for MLB-HD, which may or may not carry the sox game (e.g. it may say red sox vs. rangers OR brewers at somewhere, so i can't tell in advance if the MLB-HD will carry the sox or not........if it doesn't overtax my 2 hd-pvr boxes with conflicts, i just record them both)

now, since the MLB-HD game doesn't actually list 'red sox vs. rangers', i have to set an override manually, which yesterday immediately gave me a green check mark to show that both broadcasts of the game were to be monitored.

however, i got an error message at 10:30 (2:30 into the nominal 3:00 game) saying the game could not be monitored..........since the override went fine, and the original favorite recording went fine (and was monitored and extended, while the override one stopped at 3 hours), i wonder if there is an issue in SRE about monitoring 2 recordings of the same game?

i'll dig up a log if that would help, but superficially from here it seems it might be a logic issue monitoring 2 recordings of the same game.
let me know if a log would help.

[Slugger]

Are you running 915 or later? There was a bug that would delete the override details too early, causing the recording to no longer be monitored starting at that first check 30 mins before the end of the recording. It was fixed in 915. If you are running 915 or later then I'll need some logs.

[cat6man]

running the latest (919), so i'll dig you up some logs later today

[Slugger]

running the latest (919), so i'll dig you up some logs later today

I'll take the logs to look at, but I'll also need you to reproduce it and then let me know as soon as you do. livepvrdata.com only retains (debug) logs for 24 hours so I won't be able to match up the sre logs with the debug info at livepvrdata.com. So if you can reproduce this then that'll be great.

[cat6man]

here's the log.

game starts at 20:00, and both reg fave and override appear ok.
at 22:30, both are checked (look ok) and scheduled for 2 minutes on.
at 22:32, the override game (with *) has disappeared and is replaced by 'regional game' which of course cannot be checked.
so it looks like the override disappeared at SRE side.

if this is insufficient, i'll try to capture again for you.

[Slugger]

I guess I'm going to change all that code to the way I should have done it in the first place. :) If a situation comes up and you can reproduce it then I'd love to see you reproduce it again so that I can look at the livepvrdata.com debug logs with it to match some things up, but as you said, it's definitely SRE losing the override data on its end - I'm just not sure why. Anyway, I'm going to fix that up, hopefully some time this week, but may be the weekend before I do.

[Slugger]

Bah... I think I found the issue, but before I go fixing up that code, I've added some logging to it. Can you upgrade to 925 and try to reproduce it? Either way I think I'm going to rip it all apart a little and do it the way I should have done it the first time, but if I'm right I should be able to at least get a temp fix in the repository rather quickly and give myself a little more time for the full cleanup and fix.

Give it 5-10 mins for 925 to show up in the plugin repository.

[cat6man]

hi slugger,

i upgraded to 925, but i can't reproduce the problem until tomorrow night.
i'll record sox-angels game and pretend mld-hd 'regional game is the same game with an override, so we should get data tomorrow evening.............game at 7:00 so problem should manifest itself around 9:32

i'll check back here tomorrow afternoon in case there are other suggestions to try

[Slugger]

Sounds good, let me know as soon as you get some results, please.

[cat6man]

report, part 1:

this afternoon, both the fave game and the override game showed in SRE with green check marks.

game started at 7:00

just checked SRE at 8:07 and the override is already gone (back to 'regional coverage' for episode).
neither game is showing a green check mark any more.

apparently it is not waiting for the 3:00 - 30minute point to check before losing the override.

i'll go down to the basement and get you the log in a couple of minutes.

edit: file attached, should be 925 not 995 in filename........i'll check log again at 9:30 or so and see how it
proceeds with extending

[Slugger]

2010-08-17 19:12:06,323 INFO [MonitorStatusChecker]: Deleted monitor status and override data for Airing: 'MLB Baseball' on channel 586/'MLBHD'
2010-08-17 19:12:06,417 INFO [MonitorStatusChecker]: Deleted monitor status and override data for Airing: 'MLB Baseball' on channel 1473/'GAMEHD2'


Got exactly what I was expecting to see. Thanks. That confirms the bug, I know what it is and how to fix it, but I'm going to fix it "right" instead of just hacking in a fix. It'll be a few days before I can get a few solid hours to clean it up.

Basically, overrides are next to useless until I fix this. :( I will do my best to get to it over the next week, definitely before NCAA football kicks off because NCAA is really where overrides are especially needed.

[cat6man]

great..........no rush here for me as i can get all the games without mlb-hd or just make mlb-hd games another favorite and record both, so i have acceptable work arounds.

cheers

[Slugger]

Snapshot 933 now in the repository. This build should fix all the override issues reported earlier in the week. If cat6man can try to reproduce again and report back his findings that'd be great.

[cat6man]

will schedule a test for tonight

thanks for the quick fix slugger

[cat6man]

mlb-hd 'regional game' starts at 8 tonight, not 7 when the sox game i'm already recording starts.............so, i put an override on the 7pm yankees game on yes.

i guess this will tell us if the override sticks or not, but won't exactly duplicate the override changing back to 'regional game' which can't be SRE'd........if the override fails, it would revert to the yankee game which could be SRE'd

so assuming there is nothing unique in the code that would make the 'regional game' override behave differently than the yes ntwk override, i guess this would
serve your purposes for testing, right slugger?

[Slugger]

Yeah, the test is to just make sure the override isn't lost - so as long as it doesn't revert back to the Yankees game then all is good. If it does, then I need logs and it's back to the drawing board, so to speak.

[cat6man]

7:15 and SRE shows both fave and override status with green check..........so far so good..........i'll check log later

7:45 and SRE shows both fave and override but no green check (override still there)
[lester gives up 5 runs in top of first to Jays, must resist urge to cancel both recording and get data for blue jay fan slugger........] ;)

[Slugger]

7:15 and SRE shows both fave and override status with green check..........so far so good..........i'll check log later

7:45 and SRE shows both fave and override but no green check (override still there)
[lester gives up 5 runs in top of first to Jays, must resist urge to cancel both recording and get data for blue jay fan slugger........] ;)

Final score aside :D, did you get some final results as far as the SRE testing goes?

[cat6man]

yes, both recordings observed the extender rules and finished about +18 minutes beyond the 3 hour nominal game length.

good work!

by the way, should the green status check go away while game is still going on (per comment above)?

[Slugger]

yes, both recordings observed the extender rules and finished about +18 minutes beyond the 3 hour nominal game length.

good work!

by the way, should the green status check go away while game is still going on (per comment above)?

The check should disappear because that's how I coded it, but my code doesn't reflect my intention there so it's a bug. However, it's a minor one as it only really affects the GUI display of that green check. A future build will fix that.

Did I mention that Toronto beat Boston 16-2 last night? :D

[cat6man]

if you are going to change it anyway, perhaps the green check for things that can be SRE'd and another mark/color for ones that are currently active (i.e. started but not yet finished).........or vice versa

[cat6man]

something wrong tonight............no override, just normal fave recording, game going into extra innings but SRE killed job at 10:00 (said not recording?)

[Slugger]

For some reason SRE was told the game stopped recording at 21:58. You're going to have to look at your sagetv logs to see if the recording stopped for some reason. That check simply asks the Sage API if the recording is still active and if the core tells SRE it's not then it cancels the monitor right there. That's what happened. If anything, there was an issue with the Sage API either reporting that the recording had stopped when it hadn't or the query of the MediaFile object from the core returned null unexpectedly.

[cat6man]

tonight's game was rained out........how does SRE handled postponed games?
if the game is postponed at start time, will it kill the recording?
if not, will it not look until 30 minutes before scheduled end?
if the latter, would it make sense to perhaps do a PPD check every 20 or 30 minutes? not sure any other sporting event has this issue..........not a biggie either, since it doesn't happen all that many times each year

[Slugger]

tonight's game was rained out........how does SRE handled postponed games?
if the game is postponed at start time, will it kill the recording?
if not, will it not look until 30 minutes before scheduled end?
if the latter, would it make sense to perhaps do a PPD check every 20 or 30 minutes? not sure any other sporting event has this issue..........not a biggie either, since it doesn't happen all that many times each year

I'll be curious to know the answer... here's what I expect to happen:

1) If the game is marked as postponed before the recording is scheduled to start, then SRE should kill it right when the recording starts, but only if you've enabled the "end recording early" setting in SRE.

2) Otherwise, it'll record until at least the check at 30 mins before the end of the recording.

I don't think a PPD check is necessary because you expected to use a tuner to record the game anyway so it's not like you're missing anything unexpectedly because of the partial recording of a rain out.

[Slugger]

@cat6man Anymore info on the other issue you reported the other day?

[cat6man]

@cat6man Anymore info on the other issue you reported the other day?

hasn't happened again, so i assume it was some sort of anomaly

[cat6man]

I'll be curious to know the answer... here's what I expect to happen:

1) If the game is marked as postponed before the recording is scheduled to start, then SRE should kill it right when the recording starts, but only if you've enabled the "end recording early" setting in SRE.

2) Otherwise, it'll record until at least the check at 30 mins before the end of the recording.

I don't think a PPD check is necessary because you expected to use a tuner to record the game anyway so it's not like you're missing anything unexpectedly because of the partial recording of a rain out.

well, tonight the game is still being recorded, so i guess the PPD wasn't out there early enough (i do have 'end recording early' set)

however, to test further, i'm recording a show on PBS at 9pm-10pm, and overriding it as the rained out red sox game..........so that way it should definitely test case 1)

[cat6man]

log looks good.

game at 7pm was recorded, as PPD was not announced until sometime after 7:15pm or so.....game eventually stopped early, 30 minutes before normal end, by SRE

test override scheduled to start at 9pm ended recording very quickly (1.9MB file) when SRE found game had ended early

so, everything looks good slugger

[Sparhawk6]

Thanks Slugger for the personal customer support over MSN Messenger! I got my issued fixed!

[Slugger]

As NCAA football begins, users will need to create overrides in order to map the school names used by Zap2It to the school names used by livepvrdata.com, which is using espn.com for NCAA football monitoring at this time.

Check your recording schedule after 12:30 EDT on game day (you can actually check ahead of time usually for football, for example this week's games are already showing up in the espn feed and so they show up in the link below). If any NCAA game needs an override then go here:

http://www.livepvrdata.com/events.jsp

This web page (I'm told it'll be prettied up some time down the road) shows a live view of every event livepvrdata.com is capable of monitoring for the given day. Find the game you're trying to monitor and create an override in SRE to match the school name(s) used. When SRE asks if you want to create a global override say "yes" and setup the override as appropriate. Once you save a global override then you will not need to create an override for the same school again (unless espn.com changes the way it displays the school). A global override is also immediately made available to all SRE users. Eventually we should get a map of most NCAA schools, which should eliminate the need for worrying about overrides. However, it will take awhile and some community effort.

Also, livepvrdata.com support for monitoring NCAA football was enabled earlier today (no SRE update required).

[tmiranda]

Slugger,

Thanks for the update on NCAA football. With pro football season approaching are there any special notes or updates we need to be aware of?

Tom

PS. Feature request:

- Brett Favre Job Queue (BFJQ). Schedules or deschedules games depending on if Brett plays or doesn't play. User configurable option if play=schedule or play=deschedule.

[Slugger]

Slugger,

Thanks for the update on NCAA football. With pro football season approaching are there any special notes or updates we need to be aware of?

Tom

PS. Feature request:

- Brett Favre Job Queue (BFJQ). Schedules or deschedules games depending on if Brett plays or doesn't play. User configurable option if play=schedule or play=deschedule.

NFL is good to go. No map updates, SRE updates, etc. req'd. It should "just work." Mind you, I'm about ready to deliver a sweeping update to SRE (pretty big, possible I haven't found all the bugs in it, but I've got to go with it at some point). This update might interrupt NFL (all) monitoring, but I've been pretty diligent in my testing so I'm fairly confident it won't break anything too horribly. :blush:

This update will set me up for a series of other changes coming down the pipe that I'll discuss at the time of this delivery.

[Slugger]

Snapshot 977 is now in the repository. There is only one change, but it's a big one:

Migrate data store to H2 database engine; prep for future changes

I've migrated the app's data store from SQLite to H2. The reason for this is so that clients can easily access the SRE database as needed. And the reason for that, is to support my on going effort to introduce SRE into the STV.

977 only provides the migration from SQLite to H2. The STVi is not included at this time because I'm still working on it, but here's a small little example of what I'm up to:

http://gateway.battams.ca/sre3_in_stv.gif

As you can see, I'm adding SRE details to the STV. The first iteration will be a read only type of thing where it will display details about overrides, possibly what's being monitored, etc. Either way it'll just be informational display. A future iteration will hopefully add write capabilities from the STV (i.e. setup overrides, etc. directly from the STV).

Mind you, I may not like the end result and could scrap the whole idea all together. If you think this will be useful then the time to speak up is now. Ideas are also welcome.

Either way the migration to H2 is staying and this is really what I need people to test asap. My testing has proven successful, but I need more confirmation. This upgrade will drop any defined overrides you have setup in your recording schedule (it does not delete global overrides, but will require you to set them up in the rec schedule again). This is a one time only thing.

[Peter_h]

Wow, I'm really liking the information in the STV. Can't wait to try this when I get home.

[Slugger]

Wow, I'm really liking the information in the STV. Can't wait to try this when I get home.

There is no STVi yet. Only the db migration to H2 is in the repository right now. It's going to be a week or two probably before I have the STVi ready.

[cat6man]

the main thing i can think of is the ability to do overrides in the STV......today i have to be at some pc to do the override..........would be a killer addition

[Slugger]

A few key bug fixes in this build. Still no STVi and I'm not so sure I'll end up finishing it. I was quickly reminded why I don't do STVi work in the first place today as things just didn't go smoothly at all while I was working on it. Perhaps I'll sit down and try again in a week or two, but I just don't think I have the patience nor desire to work in Studio so I may have spoke too soon when discussing a possible STVi for SRE.

[cat6man]

is the latest version broken?
i see nothing in my SRE recording schedule at all

edit: sox rained out tonight due to approaching hurricane earl, so i don't need SRE today, but i've never seen it blank before

let me know if you want to see anything else like a log or test something

[Slugger]

Is the sre.log file still being written to? Are other jetty apps still working? I'm running 981 with no issues. Did you install and run the last build (977)?

If the log is still being written to (MonitorStatusChecker is still running periodically, etc.) then there's something wrong with the web app portion. Have a look at the sagetv_0.txt file, but more than likely you'll have to enable jetty debug logging completely to get all the details I'll need to see. Maybe we'll get lucky and the sre.log file contains exception dumps (unlikely for this scenario, but you never know)?

Is anyone else seeing this problem?

[spacecadet]

Is the sre.log file still being written to? Are other jetty apps still working? I'm running 981 with no issues. Did you install and run the last build (977)?

If the log is still being written to (MonitorStatusChecker is still running periodically, etc.) then there's something wrong with the web app portion. Have a look at the sagetv_0.txt file, but more than likely you'll have to enable jetty debug logging completely to get all the details I'll need to see. Maybe we'll get lucky and the sre.log file contains exception dumps (unlikely for this scenario, but you never know)?

Is anyone else seeing this problem?

I am seeing content in the Recording Monitor, but I did notice that the Ohio State/Marshall game was not monitor correctly last night (recording cut off before the game ended). I'm running build 975.

Here's the log:

2010-09-02 19:30:00,735 INFO [AiringMonitor]: 'College Football: Marshall at Ohio State': Event not over; nothing to be done! [375ms]
2010-09-02 19:30:00,876 WARN [AiringMonitor]: Unable to schedule monitor
java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Unknown Source)
at java.util.Timer.schedule(Unknown Source)
at com.google.code.sagetvaddons.sre3.server.AiringMonitor.run(AiringMonitor.java:231)
at java.lang.Thread.run(Unknown Source)
2010-09-02 19:30:00,876 INFO [AiringMonitor]: 'College Football: Marshall at Ohio State': Next check at Thu Sep 02 22:00:00 EDT 2010
2010-09-02 20:18:56,376 INFO [AiringMonitor]: 'College Football: Marshall at Ohio State': Event not over; nothing to be done! [1625ms]
2010-09-02 20:18:56,532 WARN [AiringMonitor]: Unable to schedule monitor
java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Unknown Source)
at java.util.Timer.schedule(Unknown Source)
at com.google.code.sagetvaddons.sre3.server.AiringMonitor.run(AiringMonitor.java:231)
at java.lang.Thread.run(Unknown Source)
2010-09-02 20:18:56,532 INFO [AiringMonitor]: 'College Football: Marshall at Ohio State': Next check at Thu Sep 02 22:00:00 EDT 2010
2010-09-02 20:19:15,251 INFO [AiringMonitor]: 'No Data': Unmonitored event; ending monitor [187ms]
2010-09-02 23:00:05,923 INFO [AiringMonitor]: 'American Chopper: Senior vs. Junior: Meteorite Men Bike': Unmonitored event; ending monitor [203ms]

[rlvogel322]

I'm running 981 and things are showing up. Let me know if you guys need me to check anything else.

[Slugger]

@Spacecadet Please move to 982 and see what happens

[cat6man]

just loaded today's version of SRE (981), and still nothing listed in recording schedule.
note: i also upgraded to 7.0.16 this morning, another simultaneously changed variable

edit: just saw reference to 982

[cat6man]

anyone else running 7.0.16?

[Slugger]

I'm on 7.0.16 with no issues. Is it just the rec schedule that's empty (and rest of the UI loads) or is it the entire web page is blank?

[spacecadet]

@Spacecadet Please move to 982 and see what happens

Upgraded just now. Will keep you posted.

Thanks!

[cat6man]

upgraded to 982 (with sage 7.0.16)........still nothing in sre recording schedule

edit: i'm going to try a complete new re-install and see what happens

re-installed SRE but still nothing at all in recording schedule..........so error messages within SRE, so let me see
what logs i have

[cat6man]

here is a log file............lots of errors and failures in there.

[tmiranda]

I'm getting the same thing. Slugger is busy drinking beer right now so I'm not expecting a fix any time soon. (Not a good fix anyway.)

[cat6man]

it may not be related, but there is a sage service bug in 7.0.16 and a sage.jar file has been posted by narflex elsewhere

http://forums.sagetv.com/forums/showthread.php?t=50618

[Slugger]

it may not be related, but there is a sage service bug in 7.0.16 and a sage.jar file has been posted by narflex elsewhere

http://forums.sagetv.com/forums/showthread.php?t=50618

Did that fix your issue with the blank recording schedule? If not, we're going to have to debug together, but as tmiranda said, it won't be tonight. I'm coherent still, but that's slowly fading as well. :D We just won our quarterfinal game to go to 4-0 and the celebrating is continuing! :) Probably best to msg me Monday morning for a debug session (well, maybe Mon afternoon :D)

[cat6man]

haven't tried it (yet)..........will get to it tomorrow morning.

congrats on your victory!

[Slugger]

haven't tried it (yet)..........will get to it tomorrow morning.

congrats on your victory!


2010-09-03 03:49:54,057 INFO [DataStore]: Using DB: jdbc:h2:tcp://m-btv:9092/plugins/sre/sre.db
2010-09-03 03:50:13,838 FATAL [DataStore]: org.h2.jdbc.JdbcSQLException: Connection is broken: "Connection refused: connect" [90067-139]
2010-09-03 03:50:13,838 FATAL [DataStore]: Exception during data store init
java.io.IOException: Error opening data store


That's your problem with SRE... check your H2 plugin settings on host 'm-btv'. Is the TCP port set to 9092? Is TCP access enabled? Get that working and SRE should start working as well.

Ok, I've been told if I don't start on another drink they're going to throw my laptop out the window so I'm out of here for the night...

[cat6man]

2010-09-03 03:49:54,057 INFO [DataStore]: Using DB: jdbc:h2:tcp://m-btv:9092/plugins/sre/sre.db
2010-09-03 03:50:13,838 FATAL [DataStore]: org.h2.jdbc.JdbcSQLException: Connection is broken: "Connection refused: connect" [90067-139]
2010-09-03 03:50:13,838 FATAL [DataStore]: Exception during data store init
java.io.IOException: Error opening data store


That's your problem with SRE... check your H2 plugin settings on host 'm-btv'. Is the TCP port set to 9092? Is TCP access enabled? Get that working and SRE should start working as well.

Ok, I've been told if I don't start on another drink they're going to throw my laptop out the window so I'm out of here for the night...

my H2 plugin in v7 says tcp is permitted and set to 9092.......do i need to do something to the firewall or should the plugin have managed this? (nothing H2 related shows up in windows firewall)

well, i'm going to need help working through this as i have no idea what an H2 plugin is...........no rush, see you monday

[cat6man]

I'm getting the same thing. Slugger is busy drinking beer right now so I'm not expecting a fix any time soon. (Not a good fix anyway.)

per slugger, do you have any idea what to do with H2?

[Slugger]

per slugger, do you have any idea what to do with H2?

TCP port 9092 needs to be opened if you're running a firewall. Highly unlikely the H2 plugin itself will config the firewall. Best thing to try would be to disable your firewall and then restart Sage and see if those H2 errors go away/the recording schedule populates in SRE.

Try connecting to http://<ip>:8082 as the H2 plugin also provides web access via port 8082 as well.

[tmiranda]

per slugger, do you have any idea what to do with H2?

Other than checking the port, no. For me it's always worked well but I have no firewall software behind the router.

[cat6man]

i have nothing beyond the router either.........just windows firewall (windows xp) on the sage pc..........but i'll try disabling the firewall to see if that makes a difference.

what OS are the rest of you running? (i'm on XPpro)

[cat6man]

no problem connecting to H2 via port 8082, but still no recordings at all populated in SRE

weren't we using H2 previously? and wouldn't it have been working before?
what would have changed this past week?

[Slugger]

I've got a Linux server and a WinXP Home SP3 server (core 7.0.16 on both). No firewall on either and both are running H2 server + SRE fine. Something is wrong with the TCP server port for H2 (port 9092) on your system. All of those H2 errors in the SRE log are "connection refused" meaning that the H2 TCP server isn't running, has crashed, or something is blocking access to it.


weren't we using H2 previously? and wouldn't it have been working before?
what would have changed this past week?


SRE was migrated to H2 (from SQLite) in build 976. The first release to the repository would have been 3.0.0.977. If you upgraded to 977 and that worked for you then something happened to your H2 plugin in the meantime, if you never moved to 977 and went from 975 to 98x then it seems your H2 plugin was never working properly. It all comes down to the "connection refused" errors. You need to determine if it's something blocking access to port 9092 (tcp) or if the H2 server is crashing for some reason. My guess is it's the former.

[robogeek]

Are you guys with the H2 problems running Slimserver software on your SageTV server machines? If so, that's the problem...Slimserver uses the same port as H2 and will prevent H2 from binding to port 9092.

If you think you might have some other software preventing H2 from binding to port 9092, you can try changing the H2 port in the plugin configuration...a restart of SageTV may be required for H2 to move to the new port.

[rlvogel322]

Are you guys with the H2 problems running Slimserver software on your SageTV server machines? If so, that's the problem...Slimserver uses the same port as H2 and will prevent H2 from binding to port 9092.

If you think you might have some other software preventing H2 from binding to port 9092, you can try changing the H2 port in the plugin configuration...a restart of SageTV may be required for H2 to move to the new port.

I have Squeezecenter and had to move H2 to 9093 and the latest of SRE is working for me.

[cat6man]

Are you guys with the H2 problems running Slimserver software on your SageTV server machines? If so, that's the problem...Slimserver uses the same port as H2 and will prevent H2 from binding to port 9092.

If you think you might have some other software preventing H2 from binding to port 9092, you can try changing the H2 port in the plugin configuration...a restart of SageTV may be required for H2 to move to the new port.

bingo! yes i do have slimserver running! will move H2 to 9093..........thanks folks!

edit: changed port to 9093 for H2 and my scheduled recordings in SRE are back!

many thanks to robogeek and rlvogel322 for solving this.

edit2: since slimserver is pretty widespread, perhaps the default for H2 should be moved to 9093?

[Slugger]

bingo! yes i do have slimserver running! will move H2 to 9093..........thanks folks!

edit: changed port to 9093 for H2 and my scheduled recordings in SRE are back!

many thanks to robogeek and rlvogel322 for solving this.

edit2: since slimserver is pretty widespread, perhaps the default for H2 should be moved to 9093?

Probably not a bad idea. jphipps is the owner of the H2 plugin so you may want to drop him a PM and mention this?

[cat6man]

PMd him..........he plans to update default to 9093

[larryf]

Not sure if this was discussed before, would there be any problems with recording two games back to back on the same station? (ie, game one is from 1-4, game two is from 4-7 on the same channel).

I have enough tuners that can record the station, just not sure what would happen when the game is 'extended' at the last minute. Before SRE Sage would simply take the highest priority tuner and record both.

Edited to say: Now that I think of it, there is one station that I may tape two games back to back and it's only one one tuner... Would both games record and be extended?


Thanks,
Larry

[spacecadet]

Not sure if this was discussed before, would there be any problems with recording two games back to back on the same station? (ie, game one is from 1-4, game two is from 4-7 on the same channel).

I have enough tuners that can record the station, just not sure what would happen when the game is 'extended' at the last minute. Before SRE Sage would simply take the highest priority tuner and record both.

Larry

There's a configuration setting to "Ignore Back to Back Recordings".

If enabled, the 1st recording will end promptly at 4 and the 2nd recording will begin on the same tuner

If disabled, the 1st recording will be extended as needed and the 2nd recording will begin on a different tuner.

I choose to leave it enabled, since I record all of the Sunday football games and know that the end of the 1pm game will show up at the beginning of the 4pm game's recording.

[larryf]

There's a configuration setting to "Ignore Back to Back Recordings".

If enabled, the 1st recording will end promptly at 4 and the 2nd recording will begin on the same tuner

If disabled, the 1st recording will be extended as needed and the 2nd recording will begin on a different tuner.

I choose to leave it enabled, since I record all of the Sunday football games and know that the end of the 1pm game will show up at the beginning of the 4pm game's recording.

Thanks, I see it now in the settings, 'ignore front end of back to back recordings'. I just set it to true, that should work well for me too.

Larry

[Slugger]

Not sure if this was discussed before, would there be any problems with recording two games back to back on the same station? (ie, game one is from 1-4, game two is from 4-7 on the same channel).

I have enough tuners that can record the station, just not sure what would happen when the game is 'extended' at the last minute. Before SRE Sage would simply take the highest priority tuner and record both.

Larry

There is a setting on the web UI or in the plugin config screen in the STV called "ignore back to back recordings". If true then SRE will simply ignore the first recording and not monitor it meaning if the first game runs long then the rest of it will be in the second recording, which will be monitored.

If that option is false (default) then SRE would extend the first recording, forcing the second to move to another tuner. If another tuner isn't available to record the second game then that recording becomes a conflict and will not be recorded.

SRE only considers recordings to be back to back if, and only if, they follow each other and both recordings are scheduled to record on the exact same channel and the second recording is NOT an intelligent recording and the second recording in NOT live tv (i.e. the second recording must be a manually scheduled recording or a scheduled favourite recording).

EDIT: I see spacecadet and I were replying at the same time. :)