Plugin: SageAlert v2.x

[Slugger]

Was your license being accepted before?

It appears your email address isn't registered with the SageAlert db file. I'd actually like to confirm that. If you could email me your sagealert.sqlite file before attempting the fix below then that'd be appreciated.

The fix, assuming I'm right, is to simply to re-register your email address again from the GUI and restart SageAlert (load GUI, click Register > Register License, then enter your email address associated with the license file). I'm not sure why the email address was deleted, the only way that can be done, afaik, is to register a blank email address in the GUI.

Anyway, the fix should be as simple as re-registering the email. Please let me know if that fixes everything.

[kevine]

Already did that. Sorry. Still does not work though. Uninstall and reinstall plugin and now it is asking to restart Sage. I cannot do that at the moment.

SQLLite file attached just the same.

I thought it would be enough to restart jetty but apparently not.

No, it is first install of license.

[Slugger]

I need to update the instructions in the email. Restarting SageAlert and/or Jetty is no longer enough because of a recent change in how I package the jars. A full SageTV restart is required after registering the email address in the GUI. Your db file looks fine, once you restart Sage then the license file should be picked up fine. Let me know...

[kevine]

Restarted Sage server and still no good. Now the log stops at checking license file. I then tried to restart Jetty, and now Jetty won't start. I have not restarted the Sage server a 2nd time as this affects the WAF. Maybe later today but I do still believe a problem exists.

[Slugger]

Originally Posted by kevine

Restarted Sage server and still no good. Now the log stops at checking license file. I then tried to restart Jetty, and now Jetty won't start. I have not restarted the Sage server a 2nd time as this affects the WAF. Maybe later today but I do still believe a problem exists.

"Jetty won't start." What does that mean?

If the log stops at "Checking license" then SageAlert is crashing. Check your sagetv_0.txt log file. Search for the string "sagealert" (no quotes). Do you find any stack traces? If so, send them my way. If not, then you need to enable Jetty debug logging and reproduce the error. The only possibility I'm seeing right now for SageAlert to be crashing at that point is that it can't access the sqlite db file for some unknown reason. I need the stack trace from the JDBC driver (assuming that's what's causing it) in order to see just what the exact cause is.

[Slugger]

To enable Jetty debug logging, follow these directions.

[kevine]

Originally Posted by Slugger

To enable Jetty debug logging, follow these directions.

Attached. There is clearly a problem in the log file. Hope you can decipher. Thanks again.

[Slugger]

Apparently, SageAlert can't find the sagealert-common.jar, which is weird because it's a listed dependency of SageAlert.

In your C:/Program Files/SageTV/SageTV/JARs/ folder, look for files named sagealert-common*.*

Are there any? Is there at least one match named sagealert-common.jar? Is there more than one match? If there is then list them all. If there is no sagealert-common.jar in that folder then that's the problem. Force an install of the sagealert-common plugin from the STV (it's in the library section) and then restart SageTV. If that jar file is there then I need to see a directory listing of your JARs folder because then it seems there may be duplicate jars (this shouldn't be possible, but I'm not ruling it out).

Also, before restarting SageTV again, check C:\WINDOWS\TEMP\Jetty_0_0_0_0_8500_SageAlert.war__sagealert__.hljay4\webapp\WEB-INF\lib and C:\WINDOWS\TEMP\Jetty_0_0_0_0_8500_SageAlert.war__sagealert__.hljay4\webapp\WEB-INF\classes and make sure both of those directories are empty. If they aren't, what's in them?

[kevine]

sagealert-common.jar.318
sagealert-common.jar.342
sagealert-common.jar.370

Looks like the master is missing. Only the backups show. Things are recording right now. I will restart later this morning.

[Slugger]

What version of SageTV are you running? I know there were bugs with the plugin manager and updating jars in earlier betas, but I thought those were fixed long ago. If you're running anything recent then I'd probably bring this to the attention of the Sage devs via a bug report.

[kevine]

Got it running and licensed. I had to rename the last jar .378 to .jar to get it to uninstall and reinstall the library manually. All seems to be working now. Bug report submitted as I am using the latest version of the beta. I am now on 7.0.17 as of this morning. Thank you for all your help. Great plugins you have. I use all of them.

[Slugger]

Snapshot 1065 is now available. I believe this build to be feature complete for v2.0.0. Now is the time to mention any issues or items you may want addressed before I remove the beta tag. Once the beta tag is removed I expect little activity with SageAlert for the immediate future (except for bug fixes) as I move on to other Sage projects.

Key addtions in 1065:

* Add support for remaining core events
* UI fixes

1065 adds support for ALL of the core's events. The significance of this will become clearer a few months (hopefully) from now.

[bialio]

Hey Slugger - I've got an issue where I'm not getting alerts - I suspect they are getting ignored because they look like duplicates.

I've got a QAM channel that frequently has errors when Sage initially tunes it - and it ends up with a recording error and then Sage restarts the tuner. I get an alert the first time this happens, but after that if it happens again, say the next day, I don't get an alert.

Does the 'ignore duplicate messages' just look at the text of the last message and ignore it based on that? Could you enhance it to check perhaps the timestamp of the last message also and maybe let the user configure a time that after which it will send the alert regardless of if it looks like a duplicate or not?

btl.

[Slugger]

The ignore duplicates option decides what's a duplicate based on what the core tells me. Before processing a system message, I call the GetSystemMessageRepeatCount() API call. If that call returns > 1 and you have that setting enabled in SageAlert then the system message is not processed. When that API call returns < 2 then the message is processed.

Unfortunately, if I change the way it works for your use case then I'll break it for someone else and vice versa. So I have to make a choice and I choose to go with the API's decision on what is and isn't a repeated sys msg. So if you want that logic to change you'll have to convince Narflex to change how the GetSystemMessageRepeatCount() API call works.

[bialio]

Unfortunately, if I change the way it works for your use case then I'll break it for someone else and vice versa.

We both know you can make it configurable so that it works more than one way. If you don't want to that's fine.

btl.

[Slugger]

Originally Posted by bialio

We both know you can make it configurable so that it works more than one way. If you don't want to that's fine.

btl.

Two words: feature creep. I think your situation is resolved by telling SageAlert not to ignore duplicate messages. You want SageAlert to consider a sys msg to be "not a duplicate" after x hours, even if the core tells me it is a repeat. The next guy says, "hey, I want it to be after y hours unless condition z is present then I want it to be t hours and hey, why not allow a day of week qualifier in there as well? And we both know you can do it."

If this were my full time job then I'd say, "hey, why not!?" Unfortunately, it isn't so I have to draw the line somewhere. In this case, I think you can have those extra sys msgs processed simply by telling SageAlert not to exclude messages marked as repeats by the core. If you don't like how the core decides what a repeat message is then I strongly encourage you to open a feature/bug report with Sage.

[Skirge01]

Slugger,

I just installed SageTV v7 (7.0.18) under WHS and on my client PC and am having issues with SageAlert. I'm seeing the following in the log:

2010-10-02 09:55:44,025 INFO  [e]: Event received: SageAlert_AppStarted :: {}
2010-10-02 09:55:44,025 INFO  [i]: SageAlert is now looking for custom events to register from other plugins...
2010-10-02 09:55:44,025 INFO  [i]: Invalid resource path defined for plugin, ignoring plugin!
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\gxt]
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\sagealert-common]
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\gwt-servlet]
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\libgrowl]
2010-10-02 09:55:44,025 INFO  [i]: No sagealert.properties file found in resource path, ignoring plugin!
2010-10-02 09:55:44,025 INFO  [i]: No sagealert.properties file found in resource path, ignoring plugin!

So, I uninstalled it and then I see that SageTV is telling me the plugin (2.0.0.1065) is not compatible, but there's no reason listed. That "not compatible" note may have been there when I first installed, but I may not have noticed. It's actually kind of scary that SageTV allows an incompatible plugin to be installed. I also noticed that the "common" dependency was still installed, so I uninstalled that, as well.

So, I'm back at the beginning with a plugin listing for SageAlert which says it's not compatible. I successfully installed several other plugins without any similar issues.

Any ideas?

[Slugger]

Originally Posted by Skirge01

Slugger,

I just installed SageTV v7 (7.0.18) under WHS and on my client PC and am having issues with SageAlert. I'm seeing the following in the log:

2010-10-02 09:55:44,025 INFO  [e]: Event received: SageAlert_AppStarted :: {}
2010-10-02 09:55:44,025 INFO  [i]: SageAlert is now looking for custom events to register from other plugins...
2010-10-02 09:55:44,025 INFO  [i]: Invalid resource path defined for plugin, ignoring plugin!
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\gxt]
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\sagealert-common]
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\gwt-servlet]
2010-10-02 09:55:44,025 INFO  [i]: Defined resource path does not exist, ignoring plugin! [C:\Program Files\SageTV\SageTV\plugins\libgrowl]
2010-10-02 09:55:44,025 INFO  [i]: No sagealert.properties file found in resource path, ignoring plugin!
2010-10-02 09:55:44,025 INFO  [i]: No sagealert.properties file found in resource path, ignoring plugin!

This is fine. It's just part of the plugin's initialization process. SageAlert goes looking at all the other plugins installed on your system and checks for (optional) SageAlert integration. If it finds it, it loads it, if it doesn't, it logs why (for debugging purposes). The only plugin I'm aware of that will actually succeed on that check is my custom events plugin, which provides additional events of interest to SageTV and it also provides the required SageAlert support so that you can configure notifications for them within SageAlert.

So, I uninstalled it and then I see that SageTV is telling me the plugin (2.0.0.1065) is not compatible, but there's no reason listed. That "not compatible" note may have been there when I first installed, but I may not have noticed. It's actually kind of scary that SageTV allows an incompatible plugin to be installed. I also noticed that the "common" dependency was still installed, so I uninstalled that, as well.

Which version did you upgrade to 7.0.18 from? If you were at 15 or lower then that explains it. 7.0.16 provided a new plugin constraint: <ServerOnly> that restricts installation of a plugin to the SageTV server JVM only. SageAlert uses that tag because running SageAlert on a client PC means that 95% (or more) of the alerts that SageAlert handles will never be generated and therefore never fired (because only the SageTV server can generate most of the events in the core). If you were running SageAlert on a client PC prior to 7.0.16 then you should have noticed most of the events never fired.

I encourage you to open a bug report against 7.0.18 with Sage describing the fact that it is not properly reporting the incompatibility reason when the reason is "Server Only plugin". That should definitely be fixed before GA.

So, I'm back at the beginning with a plugin listing for SageAlert which says it's not compatible. I successfully installed several other plugins without any similar issues.

Any ideas?

Remove the plugin from your PC client and install it on the Sage server.

[Skirge01]

Originally Posted by Slugger

Which version did you upgrade to 7.0.18 from? If you were at 15 or lower then that explains it. 7.0.16 provided a new plugin constraint: <ServerOnly> that restricts installation of a plugin to the SageTV server JVM only. SageAlert uses that tag because running SageAlert on a client PC means that 95% (or more) of the alerts that SageAlert handles will never be generated and therefore never fired (because only the SageTV server can generate most of the events in the core). If you were running SageAlert on a client PC prior to 7.0.16 then you should have noticed most of the events never fired.

I upgraded from SageTV v6, so would that still explain this? I went straight from v6 to v7 beta 18.

I encourage you to open a bug report against 7.0.18 with Sage describing the fact that it is not properly reporting the incompatibility reason when the reason is "Server Only plugin". That should definitely be fixed before GA.

Will do. Thanks.

Remove the plugin from your PC client and install it on the Sage server.

They really shouldn't allow you to install a plugin designed for the server onto a client, but--not being a developer--maybe I'm just not thinking this through enough.

[Skirge01]

UPDATE: Regarding the "not compatible" message, it looks like that message is only showing up on the client, not on the server.