Plugin: Sage Recording Extender (SREv3)

[Slugger]

Originally Posted by 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?

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/show...15&postcount=1

[Slugger]

Originally Posted by cat6man

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


http://forums.sagetv.com/forums/show...15&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]

Originally Posted by cat6man

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.

[Slugger]

Originally Posted by 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.

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]

Originally Posted by Slugger

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]

Originally Posted by Sparhawk6

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]

Originally Posted by Peter_h

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]

Originally Posted by Slugger

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