This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

No HTTP respond
#21
New findings.

I tried to change the device address in the KNX settings from 15/15/255 to 1/1/30. Did a reboot and when it came up again the http server is not working again. The rest seems to work.

Should I get the new card and flash it with the recovery image? And then run a restore when I get it up and running?

Is there something I can do to stop this from happening in the future. I am thinking of maybe login through ssh or telnet and restart the http server?
Reply
#22
In did it sound strange. If I were you I would replace the card anyway just to make sure that if this happens next time you will be sure that the problem is elsewhere.
------------------------------
Ctrl+F5
Reply
#23
(06.12.2016, 17:33)mlaudren Wrote: Corruption data is very unlikely to happened, the only thing that came to my mind will be data loss if you have trends. I think it's 5min between saves on the memory.

I had a corrupt sd-card after a power off, of the whole building.
card wasn't working anymore, and I had to make a new card and set backup, back to the Wiser (LM).
now it works again.
Reply
#24
I dont have trends so I dont loose anything other then my scripts and objects that I have made myself.

It actually managed to reboot once today and the http server started up again. This was after trying to change the address in knx connections but the change didnt stick. It was still 15.15.255 after reboot. Still the old card though.

I have made the new card with recovery image for my cpu now, and will try this to see what happens.
Reply
#25
Managed to fix it with new card, recovery image and firmware from 20170620. After that a bit of struggling but finally it came up and everything went fine. Upgraded to 20200720 after that.

Hopefully it will be ok from now on.

What I do not have is my scripts and I am reluctant to restore from backup since I am now on newer firmware. I have saved copies from all of my scripts and I will add them manually.

Looks good now and hopefully it will be in the future
Reply
#26
I experience the same thing since some weeks now. I'm literally unable to open web config pages now - server works for just several seconds and then it's dead for several minutes. I thought SD card as well, so I dd-ed the SD card to a new one (high endurance 32GB) - worked for a while but eventually ended with the same result pretty soon after. I have root ssh access and check processes and resources - 2-4% CPU load and 223772K free memory. Any ideas how to debug? Could it be a corrupted SD card after all that I shouldn't dd (low-level byte copy)?
Reply
#27

  1. Which firmware version are you using?
  2. Are you connected directly on the same network or externally (VPN, ZeroTier or port forwarding)?
  3. When the web server is not responding can you still ping LM? Check system uptime in System config > Status > System status. Maybe LM is rebooted when this happens.
  4. Try this script and see if it helps: https://forum.logicmachine.net/showthrea...7#pid23987
  5. Check for any errors in /var/log/nginx/error.log
Reply
#28
(06.04.2024, 10:10)admin Wrote:
  1. Which firmware version are you using?
  2. Are you connected directly on the same network or externally (VPN, ZeroTier or port forwarding)?
  3. When the web server is not responding can you still ping LM? Check system uptime in System config > Status > System status. Maybe LM is rebooted when this happens.
  4. Try this script and see if it helps: https://forum.logicmachine.net/showthrea...7#pid23987
  5. Check for any errors in /var/log/nginx/error.log

Hi,

1. I've recently upgraded to the latest stable release - 2023.06. However I did that in hopes newer version will fix the issue if it's some kind of a known bug. This issue was present before the update and stayed after.
2. I access only via VPN and locally. Issue is with both.
3. Yes, ping works, as well as scripts. I use LM as KNX Ethernet gateway as well, and KNX works. I'm literally unable to access the web UI anymore for more than couple of seconds, so there's no way to reach System config > Status > System status.
4. Unfortunately can't access the web UI and try the script. I'll keep trying and be fast as possible.
5. Not a single error in /var/log/nginx/error.log
Reply
#29
You can try a fresh install on a different card using the recovery firmware: https://kb.logicmachine.net/misc/reflash...ng-player/
The script that increases the web server worker count can be run from ssh, just copy/paste and run everything that is inside os.execute('...') (without single quotes).
Reply
#30
(08.04.2024, 12:15)admin Wrote: You can try a fresh install on a different card using the recovery firmware: https://kb.logicmachine.net/misc/reflash...ng-player/
The script that increases the web server worker count can be run from ssh, just copy/paste and run everything that is inside os.execute('...') (without single quotes).

Increasing the worker count didn't help. I'll try a fresh install tomorrow.

Funny thing is even after nginx reload or reboot the whole device, http is gone, and is back couple of mins after that out of nowhere.

I've also increased the worker_connections from 512 to 1024. But seems it's not nginx the one to blame.
HTTP error is "ERR_CONNECTION_TIMED_OUT"
Reply
#31
So, I haven't tried a fresh install, because it started to work again. Till yesterday. Since yesterday I experience exactly the same issue.

The problem with the fresh install is I'm not able to back up anything because I'm not able to reach the web ui. Apparently I was stupid not to back up during the time I was able to reach it.

1. Any suggestions how to back up from terminal?
2. Any ideas how to debug and get closer to what could be the root of the problem? I have root terminal access.
Reply
#32
Try the recovery method on a different card just to check whether it has the same issue or not.
Reply
#33
(20.04.2024, 06:04)admin Wrote: Try the recovery method on a different card just to check whether it has the same issue or not.

Please keep in mind I've copied (sing dd) to a new card 3 weeks ago. LM is running now on that copy, not on the original card. It shouldn't be hardware. Maybe if it was something corrupted and was copied to the new card? But what could that be that affects it so randomly?
Reply
#34
If something was corrupted on the original card it will stay that way when doing a clone copy. That's why I'm suggesting using recovery. Instead of backup/restore you can simply copy all files from the third partition from the old card to the new.
Reply


Forum Jump: