search

UniversalDevicesInc-PG3 / udi-poly-FlumeWater

MIT License
0 stars 1 forks source link

"Invalid Token" Data stopped being sent to ISY #6

Closed SteveHoyt closed 2 years ago

SteveHoyt commented 2 years ago

Good Morning

Around 6:50:54 this AM, the node server stopped returning values to the ISY. Looking at the log file I see the error "invalid Token"

Restarting it fixed the issue.

Can you take a look at the log file.

Also is there any value I can look at, that could trigger an alert, so I know this has happened....or even better initiate a restart.

Thanks Steve FlumeWater_2-26-2022_71932_AM.zip

Screen Shot 2022-02-26 at 8 00 23 AM
jimboca commented 2 years ago

Thanks for the log, that's what I needed to see. I'll look into what can be done.

jimboca commented 2 years ago

Try 3.0.8 and read all the README updates. Hopefully this resolves it, but I can't say for sure that automatically detecting that re-authorization is needed works since it never happens to me. Set up your monitoring programs as I described and let me know when it happens again.

SteveHoyt commented 2 years ago

Hi

The error happened again. Log file is attached. Not sure it is of value, as it is over a week ago it happened.

I left town last Thursday the 3rd. It stopped I suspect a day or 2 after I left, but not sure exactly when. Got the same invalid token error. Authorization status appears not to have changed, as I had a program tracking it, but not the other parameters and the authorization status did not change.

Thanks Steve FlumeWater_3-11-2022_62631_AM.zip

jimboca commented 2 years ago

Sorry, yes there is a bug in the code which tried to detect the authorization error, however it would have set the ST on the Flume2 Node. I'll try to get a fix out soon.

SteveHoyt commented 2 years ago

Not to worry about fixing the status part quickly.

Were you able to get any idea on what is causing the error.

Thanks

On Mar 11, 2022, at 12:41 PM, JimBoCA @.***> wrote:

Sorry, yes there is a bug in the code which tried to detect the authorization error, however it would have set the ST on the Flume2 Node. I'll try to get a fix out soon.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1065505526, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWP4SVLWD3AR3CMQPYDU7OVWNANCNFSM5PNDZ5IA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

jimboca commented 2 years ago

I'd like to see the log where the error first showed up to see what it says. But after I fix the bug it will recognize it's an auth error and attempt to reauthorize on the next short poll.

SteveHoyt commented 2 years ago

Sounds like a good bandade for the issue.

As I mentioned, I was out of town when it happened. The only way I know to get logs is via the PG3 interface and that appears to only go back to the last midnight.

Is there a command to get it somehow via an ssh session? If so let me know and I’ll give it a try.

On Mar 11, 2022, at 2:12 PM, JimBoCA @.***> wrote:

I'd like to see the log where the error first showed up to see what it says. But after I fix the bug it will recognize it's an auth error and attempt to reauthorize on the next short poll.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1065579376, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWIP2EPCVUA2INSWBHDU7PAL3ANCNFSM5PNDZ5IA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

jimboca commented 2 years ago

Yes, I could give the commands to look through the logs but I'm traveling now so won't have time to give details if your not unix proficient.

SteveHoyt commented 2 years ago

No urgency here…. I am sure the error will come back again, for now lets just wait for it again.

Steve

On Mar 11, 2022, at 2:12 PM, JimBoCA @.***> wrote:

I'd like to see the log where the error first showed up to see what it says. But after I fix the bug it will recognize it's an auth error and attempt to reauthorize on the next short poll.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1065579376, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWIP2EPCVUA2INSWBHDU7PAL3ANCNFSM5PNDZ5IA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

jimboca commented 2 years ago

Released 3.0.9 which should trap the authorization issue, and re-auth on next poll.
You must be on at least PG3 3.0.45 to see the new version. I'm upgrading my production box now to confirm.

SteveHoyt commented 2 years ago

I just upgraded to it.

I’ll let you know if I see anything of value.

Thanks Steve

On Mar 16, 2022, at 8:00 PM, JimBoCA @.***> wrote:

Released 3.0.9 which should trap the authorization issue, and re-auth on next poll. You must be on at least PG3 3.0.45 to see the new version. I'm upgrading my production box now to confirm.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1070036822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWONMGFII4HTUKG6VETVAKN57ANCNFSM5PNDZ5IA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

SteveHoyt commented 2 years ago

Just got the error again. I am not sure when it happened, as the status changed to "not started and I wasn't checking for that. It definitely was not today as you can see from the log file. Info attached. Not sure it is of any value. I have not upgraded lately due to all the problems I have been seeing reported. Thanks Steve

Screen Shot 2022-03-28 at 8 18 36 AM Screen Shot 2022-03-28 at 8 29 35 AM

debug.log pg3-current.log

jimboca commented 2 years ago

That's odd that uptime is 8minutes? I'll try to review the logs today.

SteveHoyt commented 2 years ago

I had done a restart…after capturing the log

On Mar 28, 2022, at 9:22 AM, JimBoCA @.***> wrote:

That's odd that uptime is 8minutes? I'll try to review the logs today.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1080854464, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWLF6YGD5OSPORUKWILVCHMDHANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.

SteveHoyt commented 2 years ago

Looks like something funny going on around 9:33:35,043 that it seems to have recovered from. Message in log says to let developer know about this error..

Files attached

Screen Shot 2022-03-30 at 9 40 09 AM Screen Shot 2022-03-30 at 9 41 55 AM Screen Shot 2022-03-30 at 9 39 39 AM

<img width="1165" alt="Screen Shot 2022-03-30 at 9 FlumeWater_3-30-2022_94046_AM.zip 39 08 AM

Screen Shot 2022-03-30 at 9 39 24 AM

" src="https://user-images.githubusercontent.com/97555417/160888153-42550673-aa15-4f4b-8ee5-d61426bbbd9e.png">

Screen Shot 2022-03-30 at 9 39 08 AM
SteveHoyt commented 2 years ago

It looks like flume is really acting up 7 errors so far today.

The good news is your NodeServer seems to be handling the multiple errors just fine.

See errors at 2:13:46, 2:37:46, 4:01:46, 4:25:46, 6:49:46, 9:09:47, and 9:37:47. version info and log file attached

Screen Shot 2022-04-03 at 9 50 31 AM

[FlumeWater_4-3-2022_94958_AM.zip](https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/files/8405077/FlumeWater_4-3-2022_94958_AM.zip

jimboca commented 2 years ago

Great news. Glad it's finally seeing the error and recovering. I'll review the log.

SteveHoyt commented 2 years ago

Good Morning

Looks like it died this morning and could not recover...see around 8:21 in attached log file

Thank FlumeWater_4-4-2022_111417_AM.zip s

jimboca commented 2 years ago

Sorry, another simple fix, code updated but I can't release until I'm at home. Will try to remember to do it tonight.

jimboca commented 2 years ago

Version 3.0.10 released

SteveHoyt commented 2 years ago

Hi again

Looks like another non recovered hang around 6:37 this am.

Log and version info included.

Screen Shot 2022-04-12 at 8 24 23 AM

FlumeWater_4-12-2022_82302_AM.zip

SteveHoyt commented 2 years ago

Just was checking status and it appears it can't restart correctly, after the error reported above yesterday. see attached log files. Let me know if I need to try anything. See restart attempt at 6:23 and 6:57 this morning

Thanks Steve

Screen Shot 2022-04-13 at 9 20 36 AM

FlumeWater_4-13-2022_91950_AM.zip

jimboca commented 2 years ago

Taking a look at the last one now, but the previous one didn't actually upload the FlumeWater_4-12-2022_82302_AM.zip file, can you resend it?

jimboca commented 2 years ago

3.0.11 should fix the issue with it not starting up, this was caused by changes to PG3. But if you still have the 4-12 zip file I would like to see that issue.

SteveHoyt commented 2 years ago

resending FlumeWater_4-12-2022_82302_AM.zip

FlumeWater_4-12-2022_82302_AM.zip

jimboca commented 2 years ago

Thanks, got it this time

jimboca commented 2 years ago

I see the error and think I have it fixed as well, very odd that I never see any errors. I will try and test soon and release again.

SteveHoyt commented 2 years ago

Great

When you say you never see any errors do you mean on your test system? Your sons house right.

I wonder what the difference could be between our 2 setups?

Are you running version 2 of the hardware…

On Apr 14, 2022, at 12:05 PM, JimBoCA @.***> wrote:

I see the error and think I have it fixed as well, very odd that I never see any errors. I will try and test soon and release again.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1099536849, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWPTE3PSLRPWC6VKDVDVFBT6XANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.

jimboca commented 2 years ago

No, I have a version 1 system at my place, but they changed out my meter to one that doesn't work with Flume so it doesn't monitor any water flow, but is still all working.

SteveHoyt commented 2 years ago

FYI

I have version 2 here.

On Apr 14, 2022, at 2:44 PM, JimBoCA @.***> wrote:

No, I have a version 1 system at my place, but they changed out my meter to one that doesn't work with Flume so it doesn't monitor any water flow, but is still all working.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1099654372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWJT22FFPBVT3DFHTRLVFCGS5ANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.

jimboca commented 2 years ago

Well, I actually looked at my logs and I am getting the same error on my dev box, just my programs where not actually working! I think I've fixed the programs so I should get notified if it fails. I can release this version or wait and see if it happens, whichever you prefer.

SteveHoyt commented 2 years ago

Thats good news you are seeing it too. I was wondering why it was only me.

I say go ahead and release it and we will have 2 systems testing rather than 1.

It is raining out here a bit so it is not critical that all is perfect yet.

Thanks Steve

On Apr 14, 2022, at 6:25 PM, JimBoCA @.***> wrote:

Well, I actually looked at my logs and I am getting the same error on my dev box, just my programs where not actually working! I think I've fixed the programs so I should get notified if it fails. I can release this version or wait and see if it happens, whichever you prefer.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1099769754, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWNPYRN4SOWLM7W2QCLVFDAPNANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.

jimboca commented 2 years ago

I've made some fixes, not totally happy with it but it's not crashing and I'm heading to the lake for a week so won't have much time to work on it. Released 3.0.12

SteveHoyt commented 2 years ago

looks like a startup problem. I know you are gone just documenting for when you get back..

Screen Shot 2022-04-18 at 11 13 35 AM

.

SteveHoyt commented 2 years ago

you can ignore above post. Upgraded to PG3 v59 and problem went away

SteveHoyt commented 2 years ago

Hi

It went crazy this AM around 11:00. Has been fine for over a week. It looks like it partially recovered, but would then fail again. I restarted it after about 20 minutes and all is well again. Log and version info attached. It would be interesting to see if yours failed around the same time too.

Stev

Screen Shot 2022-04-26 at 11 20 54 AM

FlumeWater_4-26-2022_112016_AM.zip e

jimboca commented 2 years ago

Yes, mine started failing last night and still failing today, flipping back and forth, but I'm not home so can't see the log file to figure out what is happening.

jimboca commented 2 years ago

I see a problem where short and long poll run at the same time which may be the cause of this conflict. I'll try to resolve that.

SteveHoyt commented 2 years ago

Interesting that yours is failing too. Perhaps something on their end triggers it.

Don’t worry about fixing it until you get back. I am ok here now it appears.

On Apr 26, 2022, at 11:54 AM, JimBoCA @.***> wrote:

I see a problem where short and long poll run at the same time which may be the cause of this conflict. I'll try to resolve that.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1110140715, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWMGIPZOUJ6G2L5N5GTVHA3WJANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.

Steve

jimboca commented 2 years ago

Released 3.0.13. I've not had an authorization issue with it for the last week, and it's properly trapping connection errors to flume servers which happen many times a day which you can monitor if desired with something like:

Flume Sensor - [ID 000D][Parent 0001]

If
        'FlumeWater / Flume Sensor 6607798382029348' Node Status is True
     Or 'FlumeWater / Flume Sensor 6607798382029348' Node Status is not True

Then
        Set 'Notification Controller / Service Pushover dev' Send Sys Short With Params To JimsPhone Priority=Normal

Which sends the content: ${sys.program.#.name}: ${sys.node.#.name}=${sys.node.#.ST}

SteveHoyt commented 2 years ago

It looks like the new version 14 stops updating values automatically. If I do a query they update. See attached log files, in particular after 15:11 today where I upgrade pg3 to the latest version. There are also a number of times I restarted earlier it seems to start fine but then does only shortfalls. The long poll don't return data

Screen Shot 2022-06-06 at 3 30 58 PM

FlumeWater_6-6-2022_32932_PM.zip .

jimboca commented 2 years ago

fixed in 3.0.15

SteveHoyt commented 1 year ago

Thanks

I would be interested to know what you find. It is still happening today after I sent the info to you.

I wonder if it is a server issue on their side and if you are seeing problems with your flume.

Steve

On Apr 3, 2022, at 11:03 AM, JimBoCA @.***> wrote:

Great news. Glad it's finally seeing the error and recovering. I'll review the log.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1086919132, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWMG3XRHJMYMJHHXVQTVDHMOLANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.

SteveHoyt commented 1 year ago

just resent it to you.

On Apr 13, 2022, at 8:26 PM, JimBoCA @.***> wrote:

3.0.11 should fix the issue with it not starting up, this was caused by changes to PG3. But if you still have the 4-12 zip file I would like to see that issue.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/6#issuecomment-1098672127, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWJFAU4MR4GDHBNSB4DVE6F7ZANCNFSM5PNDZ5IA. You are receiving this because you authored the thread.