I think this has been discussed before, but when Blue Iris server is auto updated and restarted, the Node Server stops working. A restart of the node server for Blue Iris fixes this. There was a solution to add code to possibly make it fix itself on a disconnect on a previous thread. I tried it, didn't seem to work (adding the suggested line makes the node server stay in disconnected state and won't connect). It appears this node server isn't actively being maintained. @bpwwer - I have seen you comment on others who would like the functionality of being able to restart a single node server either by a schedule or command line. I do understand your comments that it's just a band aid, but it would be nice to either have a real fix here, or this ability. You also indicated you are willing to help when the author might not be responsive or can't help (I believe the author here indicated they don't use Blue Iris anymore and can't test). Bottom line, any help here would be appreciated. I do code alot, I just don't use python, so I don't think I can easily figure out a solution . . . Thanks!

First off, my comments and reasons for not wanting to allow for automated restarts of node servers/PG3 are really because that tends to be used as a band-aid to handle poorly behaving node servers. The right way to do things is to get the node servers to not behave badly. In this case, the node server isn't really behaving badly, it's behaving mostly as intended. When it can't communicate with Blue Iris, it goes into a disconnected state and waits for someone to take action to resolve the issue. Now it could and should handle this better. It should try to re-connect, the code is mostly there, just not the logic to attempt that. In cases like this, where the author has pretty much abandoned the node server, I'll typically take a look if I have time. Unfortunately, I don't always have time to dig into someone else code to figure out how it works and what can be done to resolve any issues. You happened to ask at a time when I'm not real busy so I'm going to try and make some changes. Version 2.0.3 should try to re-connect when it fails to query the Blue Iris server. I have no way to test this.

oops...I spoke too soon. I had not disabled by program that does a rediscover when a disconnect occurs. Just did test again and this time no automatic reconnect occurred. Still need to do a rediscover

Blue Iris Node Server Disconnected after Software update

By pkauf
November 7 in BlueIris

Followers 2

Go to solution Solved by bpwwer, November 7

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

× Pasted as rich text. Paste as plain text instead

Only 75 emoji are allowed.

× Your link has been automatically embedded. Display as a link instead

× Your previous content has been restored. Clear editor

× You cannot paste images directly. Upload or insert images from URL.

Insert image from URL

Followers 2

Go to topic listing

Recently Browsing
- No registered users viewing this page.
Who's Online (See full list)
- tlightne
- Bumbershoot
- gdavis
- hart2hart
- hec
Forum Statistics
- Total Topics
  
  37.1k
- Total Posts
  
  371.6k

Sign In

Blue Iris Node Server Disconnected after Software update

Recommended Posts

GTench

Join the conversation

Recently Browsing

Who's Online (See full list)

Forum Statistics

Browse

Activity