What plug-in or API can identify when SageTV is recording?

[wayner]

One note for those of you using the unRAID version of SageTV. If you use the Docker backup process then your SageTV docker always gets restarted when you run that as it needs to shut down the dockers to do the backup.

[peternm22]

Originally Posted by timg11

Is the "SageTV Web Interface" plugin doing anything or should I remove it as a plugin?

The SageTV Web Interface plugin installs the Jetty plugin. SageTV plugins can use other plugins as dependencies.

For example, the Jetty plugin is required for the Web Interface, the Mobile Web Interface and BMT.

If you uninstall the the Web Interface, I believe those XML files will cease to work.

[wayner]

Originally Posted by peternm22

If you uninstall the the Web Interface, I believe those XML files will cease to work.

But the web interface is hugely useful - I can't envision not having it installed and accessible from the outside world. If you are out someplace and realize that you forgot to set a show to record you can easily log in and set it to record.

Not that you need that these days as no one ever leaves home

[timg11]

I'm in the process of building a new system with 64 bit Windows and SageTV.

I have installed the Jetty Web Server plugin, and used its configuration interface to set the user name and password.

When I access the URL: http://localhost:8080/sage/Home?xml=currrecording

I first get the browser prompt for credentials (Sign In). I enter the user/password I entered into in the plugin configuration. When I click the Sign In button, I get:

HTTP ERROR 403
Problem accessing /sage/Home. Reason:
    User not in required role
Powered by Jetty://

Since configuring the plugin, I have restarted the server, and also SageTV service.


What am I doing wrong? Everything is the same as the prior machine except it is now 64 bits.


Edit: here is the plugin configuration on both systems:

Old System                                                  New System  
                    
ant     1.8.2                                               ant     1.8.2
Apache Mina Core    1.1.7                                   Apache Mina Core    1.1.7
commons-lang    2.4                                         commons-lang    2.4
commons-net 1.4.1                                           commons-net 1.4.1
Darksky Forecast API    1.3.1                               Google Weather  2.0.3
groovy  2.0.5.1                                             groovy  2.0.5.1
InfoPopup / Caller ID   7.0.4                               InfoPopup / Caller ID   7.0.4
InfoPopup STVi  7.0.4                                       InfoPopup STVi  7.0.4
jackson-annotations Library                 
jackson-core Library                    
jackson-databind Library                    
jackson-datatype-jsr310 Library                 
Jetty Web Server    2.3.0.17                                Jetty Web Server    2.3.0.17
JSON.org    20140107.2                                      JSON.org    20140107.2
log4j   1.2.17                                              log4j   1.2.17
Nielm's Sage Utilities  1.4.4                               Nielm's Sage Utilities  1.4.4
Nielm's Sage XML Info   1.4.1                               Nielm's Sage XML Info   1.4.1
SageTV Groovy Tools 1.0.4                                   SageTV Groovy Tools 1.0.4
SageTV Web Interface    3.3.1                               SageTV Web Interface    3.3.1
sagex-api - SageTV API Extensions9.1.7.0                    sagex-api - SageTV API Extensions   9.1.7.0
Simple Logging Façade for Java API LIbrary (slf4j)  1.7.12  Simple Logging Façade for Java API LIbrary (slf4j)  1.7.12
Simple Logging Façade Log4j Implementation library  1.7.12  Simple Logging Façade Log4j Implementation library  1.7.12
Weather using NWS and Darksky   0.18 beta                   Weather using NWS API   0.13 beta

So the only difference (other than Weather-related plugins) is the jackson libraries, which are shown as dependency only.

[timg11]

As I inspect various files comparing the new system (not working) to the old (working) system, I found login.properties and login.conf.
They are identical.

I found logs - these are what is logged from running my script:

curl -u TV:***** "http://localhost:8080/sage/Home?xml=currrecording" > c:\batch\SageRecStatus.xml

From working system file 2020_12_24.request.log:

0:0:0:0:0:0:0:1 - TV [24/Dec/2020:17:27:40 +0000] "GET /sage/Home?xml=currrecording HTTP/1.1" 200 435 "-" "curl/7.62.0"

From non-working system file 2020_12_24.request.log:

0:0:0:0:0:0:0:1 - TV [24/Dec/2020:17:54:42 +0000] "GET /sage/Home?xml=currrecording HTTP/1.1" 403 1406 "-" "curl/7.62.0"

Unfortunately no clue as to why the 403 is occurring.

[timg11]

Update - I solved it.

By Searching on the phrase

sagetv jetty server 403 "User not in required role"

I was able to find this thread

where @skyeclad suggests "By going into the Jetty settings and changing the Username and password 2 times, I was able to correct whatever was a problem."

I did the same, using the plugin configuration, change the user/pw to something else, then back again to what is in my script, restarting the server each time.

Voila - now it works! Thanks @skyeclad!

[timg11]

I have improved my script to detect Jetty error conditions:

curl -u TV:***** "http://localhost:8080/sage/Home?xml=currrecording" > c:\batch\SageRecStatus.xml
grep ERROR c:\batch\SageRecStatus.xml
if not errorlevel==1 goto JettyError
grep channelId c:\batch\SageRecStatus.xml
if errorlevel==1 goto NotRec
echo Recording
goto end
:JettyError
echo Error Returned in XML
goto end
:NotRec
echo Not Recording
:end