Jump to content

Restart not working in new version


johnnyt

Recommended Posts

Neither the "Restart Nodelink" button on System Config page of UI, nor the restart command sent from ISY to Nodelink work for me in the new 0.10.5 version. Worked fine for years using 0.9.x. Both kill Nodelink but don't restart it.

Am running it on Windows 10. What do I need to do for this to work, especially the command sent from ISY so I can automatically restart if/when something goes wrong. 

Any info would be appreciated.

Link to comment
Share on other sites

  • 6 months later...

How do I restart Nodelink from ISY or Nodelink when running it in Windows? The restart button on NodeLink admin page only shuts down Nodelink, it doesn't restart it. But how could it - it needs to run the command file to call dotnet first? So what does one need to do? I just tried it again with 0.10.6 for what that's worth.

Link to comment
Share on other sites

How do I restart Nodelink from ISY or Nodelink when running it in Windows? The restart button on NodeLink admin page only shuts down Nodelink, it doesn't restart it. But how could it - it needs to run the command file to call dotnet first? So what does one need to do? I just tried it again with 0.10.6 for what that's worth.

I haven’t run it on Windows in a long time. ... Using it on a RPi.

 

Do you run nodelink from a cmd Window? If so, try closing the window and start it again. Worst case reboot the PC.

 

Io_guy indicated that a bug exists in the restart from web console interface that will be fixed in next release.

Link to comment
Share on other sites

I

12 minutes ago, hart2hart said:

Do you run nodelink from a cmd Window? If so, try closing the window and start it again. Worst case reboot the PC.

 

Yes, I can go in manually and stop/start command window but I'd like the ISY to restart NodeLink when it loses communication with it, like it used to do in 0.9.x. Yes, I can get ISY to reboot the whole computer but it's a bit drastic and it kills other things running, like syslogger, perhaps backups, offsite file copying,  etc. It's a multi purpose home server that's running nodelink.

Is there a way to start a batch file remotely from ISY? Maybe I can start one that waits a few seconds to give time for the "restart Nodelink" command to shut nodelink down, then the batch restarts it?

 

Link to comment
Share on other sites

I
Yes, I can go in manually and stop/start command window but I'd like the ISY to restart NodeLink when it loses communication with it, like it used to do in 0.9.x. Yes, I can get ISY to reboot the whole computer but it's a bit drastic and it kills other things running, like syslogger, perhaps backups, offsite file copying,  etc. It's a multi purpose home server that's running nodelink.
Is there a way to start a batch file remotely from ISY? Maybe I can start one that waits a few seconds to give time for the "restart Nodelink" command to shut nodelink down, then the batch restarts it?
 

What command or are contents of batch file you run to start nodelink on PC? The goal
of what I suggested is just to get nodelink running.
Link to comment
Share on other sites

To start nodelink on windows one needs to run a nodelink.cmd batch file (provided with nodelink), which runs "dotnet NodeLink.dll" in a DOS box. It needs to "start in" Nodelink folder and needs to be run as administrator. These settings are covered by the properties I set for a shortcut/link I created. Now how do I get ISY to run that link, assuming it's all I have to do and it will work? I think I tried to just call it from ISY a while back and it didn't work. There used to be a place where you could define a command that Nodelink could run on the machine but it appears to have been removed in latest version, or I'm just not finding it right now. I suspected at the time that maybe running something as administrator remotely isn't permitted by default, and I'd have to change some settings. Not sure what though.

 

Link to comment
Share on other sites

Just to be clear I'm not having any problems starting it manually using the keyboard in windows. What isn't working is having an ISY program restart it programmatically with no intervention from me. The network resource that used to work in 0.9.x (i.e. sends "RESTART" to Nodelink) returns "Request Failed" message. It also won't restart using the "Restart Nodelink" button on the Nodelink System Config page.

Link to comment
Share on other sites

The first screenshot shows what happens when I manually start it from a command window. This works no problem.

Second screenshot shows the restart button I push from Nodelink page, while the third one shows what happens to windows desktop (command window disappears). So this command does STOP nodelink but it does not restart it. Note that this is not what I need to work. Am just showing it for troubleshooting purposes.

Fourth one shows the network resource that used to work in 0.9.x, with the fifth one showing what happens when I "test" that network resource. Nothing happens to Nodelink in this situation. This is the scenario I'm hoping to get working.

I will mention that I no longer have a Venstar thermostat (I used to) and notice the relay server makes a link to the thermostat (screenshot 6). Does the relay server only work if I have a Venstar stat as a device? I have experienced some problems seeing/opening up the Relay Server page (freezes and needs a restart).

.

nodelinkfromcommandwindow.JPG

nodelinkpage.JPG

nodelinkaftestart.JPG

NetworkResource.JPG

networkresourcecall.JPG

RelayServer.JPG

Link to comment
Share on other sites

If your relay server isn't working it's likely a windows firewall issue.  You can enable debug on the main window and system config page to see what is being received from the ISY.  

Regardless, the restart code is the same (relay or web button).  Not sure why yours just closes.  I tried it on 3 different windows machines and it restarts fine.  

Link to comment
Share on other sites

The windows firewall was already OFF for local network but I went ahead and turned it off for public networks too. It didn't fix the problem.

I turned on debug level for logfile and pushed the Restart Nodelink button. Here's what ended up in the logile:

2020-08-17 19:06:52 - Relay Server Error: Error: OnClientConnection - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
2020-08-17 19:06:52 - DSC Error: Data Arrival - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [dsc1]

Any clues from that?

 

Link to comment
Share on other sites

21 hours ago, io_guy said:

That looks like multiple versions running or an improper shutdown.  

Restart the computer, and then see what the debug log gives you when you send from the ISY.  

I rebooted computer this morning and just got the same behavior and log message when I pushed the "restart nodelink" from web page. 

In case it helps troubleshoot:

Attached are the log entries after restarting Nodelink following the above test to show what a pretty typical day is like as far as log messages.

I'll also mention that yesterday during my testing I did have some problems loading the relay server page. It wouldn't come up even though other pages would. Had to restart nodelink to get it to work properly.

I also had the following happen last night: 

2020-08-17 21:27:04 - DSC Error: Data Arrival Init - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [dsc1]
2020-08-17 21:27:45 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1]
2020-08-17 21:28:15 - DSC Error: Send Data - An existing connection was forcibly closed by the remote host. [dsc1]

 

Followed every 30 seconds by:

2020-08-17 21:28:45 - DSC: Reconnecting To Server [dsc1]
2020-08-17 21:29:15 - DSC: Reconnecting To Server [dsc1]

...

2020-08-18 05:25:04 - DSC: Reconnecting To Server [dsc1]
2020-08-18 05:25:34 - DSC: Reconnecting To Server [dsc1]

until I restarted nodelink this morning.

twice in the stream the following message snuck in

2020-08-18 01:26:19 - DSC Error: Send Data - An existing connection was forcibly closed by the remote host. [dsc1]

2020-08-18 03:02:28 - DSC Error: Send Data - An existing connection was forcibly closed by the remote host. [dsc1]

 

Also the ISY reported Nodelink down around 3:23 AM, even though it was still running. I guess the heartbeat stopped? here's my heartbeat monitoring program:

Check Comms - DSC - [ID 0142][Parent 0016]

If
        '1-MISC (Non Lighting) / Alarm Panel / DSC Alarm' Heartbeat is -1
     Or '1-MISC (Non Lighting) / Alarm Panel / DSC Alarm' Heartbeat is 1
 
Then
        $sZDSC.CommsDown  = 0
        Wait  4 minutes and 4 seconds
        Run Program 'Comms-DSC Down II' (Else Path)
        Wait  1 second
        $sZDSC.CommsDown  = 1
 
Else
   - No Actions - (To add one, press 'Action')
 

 

logfile_2020-08-18-after reboot.txt

Link to comment
Share on other sites

That log file to me looks like sketchy networking.  

Random times throughout the several hours of log you get lost connections and timeouts to each device (DSC, RM and ISY).  

In comparison I can run log for a month and all I see if a few timeouts to Ecobee's unreliable cloud server.  

Link to comment
Share on other sites

On 8/19/2020 at 7:36 AM, io_guy said:

That log file to me looks like sketchy networking.  

Random times throughout the several hours of log you get lost connections and timeouts to each device (DSC, RM and ISY).  

In comparison I can run log for a month and all I see if a few timeouts to Ecobee's unreliable cloud server.  

Ok, I rejigged network connectivity to the machine (yes, it was a higher than normal number of lost connections) and things are better with only 1 or 2 in a day. I will mention that my DSC interface is known to be a little bit flaky. My switch reports RX errs from it even after changing ports and cables with known good ones. There's little I can do except replace the DSC interface, which I don't think is really necessary.

While it certainly was worth improving network connectivity, I don't think it's the reason for nodelink not restarting. Certainly it's still not restarting with a now clean network path.

I tried to completely disable UAC (I had it set to lowest ON setting because any higher did not allow me to run nodelink as admin at all, which is needed) but that didn't help.

Are there security settings other than firewall and UAC that may need to be turned off, or is there a way to make nodelink work without needing to run as administrator?

Link to comment
Share on other sites

I never said restart and network issues were related.  Your log showed a ton of network issues.

Why your restart doesn't work, no idea.  That's why I asked for a console log (watching during restart) because it works fine here in W10.  The log you provided only had network issues.

You can run as non-admin (although I have no idea why you'd want to), just need to open the 8090 port approval, which will pop up in the console window.

Link to comment
Share on other sites

I thought I gave you a console log. I turned nodelink logging to debug and what I gave you was everything that ended up in the log file. If that's not a console log, you'll need to tell me what to do to get one.

 

nodelinklogging.JPG

Link to comment
Share on other sites

  • 3 weeks later...

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...