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.

LM reboots
#1
This morning the LM restarted 8 times at a distance of 2/3 minutes from each other. 
I know this because I have inserted a init script that sends an email. 
However, the system only recorded  in the Alert the last "system start" reboot, why didn't it log in all the reboots? 
And what can be the cause of reboots apart from CPU overload?

BR

Peppe
Reply
#2
Anything what happens during first 30 min after reboot will not be saved if reboot happens again. This is how often data is saved on the sd card. Reboot is most likely memory issue.
------------------------------
Ctrl+F5
Reply
#3
(03.06.2025, 17:33)Daniel Wrote: Anything what happens during first 30 min after reboot will not be saved if reboot happens again. This is how often data is saved on the sd card. Reboot is most likely memory issue.

nginx is always on the top of memory usage, maybe because a lot of people are logged at same time.

is it possible to force writing on sd card by a script? I could put it in init script....
Reply
#4
The 30 min rule is for a reason, often saving will shorten lifespan of SD and brake LM. How many users at the same time?
------------------------------
Ctrl+F5
Reply
#5
(04.06.2025, 08:06)Daniel Wrote: The 30 min rule is for a reason, often saving will shorten lifespan of SD and brake LM.  How many users at the same time?

sometimes could be 10 or more users...and I guess they have more than a browser card open at time.

about the 30 min rule, I can understand. But I would run it only in case of reboot.
Reply
#6
Taking away a symptom without addressing the origin / root cause / putting a bandage in place is a bad approach..

You should look into the reasons of the restarts as the controller should run 24/7 without the need of extra savings to SD what certainly leads to a short lifetime span..
Reply
#7
(04.06.2025, 21:03)Erwin van der Zwart Wrote: Taking away a symptom without addressing the origin / root cause / putting a bandage in place is a bad approach..

You should look into the reasons of the restarts as the controller should run 24/7 without the need of extra savings to SD what certainly leads to a short lifetime span..



I agree with you, but that is long time issue without solution:

https://forum.logicmachine.net/showthrea...8#pid37448

I tried everything to understand the reason for these overloads.
 I also trended the cpu and memory load, but it all seems absolutely random.

Attached Files Thumbnail(s)
   
Reply
#8
If this graph is correct then your CPU is very high.
------------------------------
Ctrl+F5
Reply
#9
(09.06.2025, 07:00)Daniel Wrote: If this graph is correct then your CPU is very high.

yes, that is...

Code:
-- Indirizzo oggetto virtuale
local ga = '50/0/4'

-- Legge il primo valore di load average da /proc/loadavg
local loadavg_raw = io.open('/proc/loadavg', 'r'):read('*a')
local load_1min = tonumber(loadavg_raw:match('(%d+%.?%d*)'))

-- Scrive il valore nell'oggetto virtuale, se valido
if load_1min then
  grp.write(ga, load_1min, dt.float16)
end

 the way I get the cpu load
Reply
#10
Reboots lately are more and more frequent, and it is not a temperature problem because the CED is air-conditioned. 

After trying to optimize the execution of the multiple scripts, I just have to think that the number of users who connect at the same time also has an influence. 

Is there no way to limit user access at the same time, or at least to warn you that you are reaching the limit? 

I see from the "system load" that the nginx process is often on top of cpu/memory consumption.

Thanks for you attention


Peppe
Reply
#11
If one LM cannot handle it then the only way is to divide project into two.
------------------------------
Ctrl+F5
Reply
#12
(05.07.2025, 12:01)gdimaria Wrote: Reboots lately are more and more frequent, and it is not a temperature problem because the CED is air-conditioned. 

After trying to optimize the execution of the multiple scripts, I just have to think that the number of users who connect at the same time also has an influence. 

Is there no way to limit user access at the same time, or at least to warn you that you are reaching the limit? 

I see from the "system load" that the nginx process is often on top of cpu/memory consumption.

Thanks for you attention


Peppe
share KNX statistic screen, maybe you have loop between event scripts
maybe system load app could show you the problem
Reply


Forum Jump: