Hi,
we are operating a Loggernet with some 40-50 weather stations. Installed version is 4.4.02
For a few days now, the Loggernet freezes after some time. The "Status Monitor" displays "Connecting to Localhost" in blue in the lower right corner of the screen, all the Network is collapsed and the "Status Monitor" only displays "Entire Network" in the top left, otherwise the screen is white.
In the Windows Task Manager, "LoggerNetService.exe" is running.
When closing down Loggernet, the usual "closing down" window is appearing and after some time disappearing, but the process would not disappear from the Task Manager. Killing it via the task manager or command line does not work either. Only a reset of the computer helps, then Loggernet will work for a while (couple of hours) and show the same behaviour again.
Any idea what is wrong?
Best regards and thanks in advance!
It sounds like this worked in the past without a problem. Has there been a recent computer update or change with the network?
Is this on windows or Linux? Is the LoggerNet server running as a service?
If this has happened recently there may still be logs available that show the problem.
- Open LogTool, Select File, and Zip All Log Files.
- Also go to Setup Screen, Select Backup, Manual Backup, and save the network for me to take a look at. You do not need to turn on "include cache table files in the backup". That will make the backup larger and I probably won't need them.
The two files are probably too large to send via email, so if you could post them to the cloud to something like Dropbox, OneDrive, etc, then email me a link where I can download them from. (I will send you an email with my email address.)
Go ahead and get these files before you do an update if you want to update to the most recent version of LoggerNet 4.5.
We're also having the exact same issues with our clients Loggernet server. Issues started yesterday after doing a windows updates. We've attempted to roll back the updates but we're still having issues. I'm not sure if the windows updates were just a coincidence but we've also got another LoggerNet server which hasn't had the updates installed and it has had no issues.
We're running the latest version of LoggerNet 4.5 as a service on Windows 7. The server will work initially for a few tens of minutes, then like above we're unable to connect to the server (through Loggernet Admin on another computer) and all collections stop. A reboot is required as we can't restart LoggerNet or kill the task. Until these last few days the server has been solid. We've been running version 4.5 for months.
Terri we could send you a copy of our logs as well? Just send us your email address.
Any help in resolving this would be greatly appreciated as we can't afford any downtime for our clients.
Hi Jonny, I sent an email to you as well so you will have the address where you can send links to logs. Again, it will likely be best to store the files to a drive in the cloud where I can download them from. Attached files may not make it through email systems.
Are you guys Scheduling collections to a Dropbox folder? I had some rather quirky "lock up" behavior recenlty saving to Dropbox.
No we're not scheduling collections to Dropbox. We think at this stage our issues could be related to a windows update in particular KB4338818. There's quite a few ongoing issues with the latest round of windows updates affecting TCP. Microsoft have issued some known issues and update patches but we're still testing rolling back updates to resolve the problem.
The problems also occured first after a windows update. The particular update Jonny is mentioning (KB4338818) was also among the updates installed just before the Loggernet server crashed first.
Until now, we tried three different things:
- update to Loggernet 4.5
- disable the windows firewall
- deleted old modems on COM ports that belonged to USB or serial connections and are not further in use
Without success.
Just to be sure. Are both of you running LoggerNet server as a service on the machines that have the problem?
Jonny, in email you mentioned that one computer has the Windows 7 update KB4338818 with another LoggerNet server but you do not see the problem on that second machine. Are both machines running the server as a service, or only the one that gives you trouble?
If either of you aren't sure what I'm talking about, Go to Windows Start, in the all programs list look for Campbell Scientific. Expand it and select LoggerNet Service Manager. When you open that, you will see a message with the status. If it is not running as a service you will see in red:
Service is not installed.
Service is not running.
My research and personal experience with my own LoggerNet server indicates that the July Windows update appears to have caused numerous issues with server services (Web, FTP, SQL, etc.), particularly regarding opening listening ports. LoggerNet is also a server and opens various listening ports. The following article has links to updated/fixed Microsoft KBs. You may or may not want to give one a try. The one you need depends on which Windows OS you have. The one I downloaded and applied for Windows Server 2012 R2 did fix the listening port issue I ran into on my LoggerNet after the July Windows update.
I believe Microsoft recently added the fix updates to their Windows Update service so you may no longer need to manually get them from the Microsoft Update Catalog website.
We're only running the Loggernet Database as a service actually, we're running LoggerNet server on all machines. Interestingly we have three Loggernet servers with the updates installed but only one has shown the issues so far. The one that's having issues perhaps has the most sites but there's not much between them.
We're just testing after removing the July updates, at this stage we'd just rather wait a little bit before installing the new patches and see how people go.
I uninstalled KB4338818 earlier today. Since then, the server is running, more than 4 hours now where before it was maximum 30 minutes. We'll also look into these patches ChipsNSalsa has hinted at. Will keep you posted on the outcome.
Regardless of whether LoggerNet is installed as a service or not, it does have a communications server at its core, and that communications server is providing communications services, which includes opening listening ports.
If or when you do a Windows Update again, I think you'll find that the original problem KB will be reinstalled, but the fix KB will be shown as an option when you return to Windows Update once the problem KB is installed.