Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loosing config file #471

Closed
mwuerr opened this issue Dec 21, 2021 · 6 comments
Closed

Loosing config file #471

mwuerr opened this issue Dec 21, 2021 · 6 comments

Comments

@mwuerr
Copy link

mwuerr commented Dec 21, 2021

I have now twice lost my config.ini.
I would say that seem to have a 1 out of 10-15 chance when I do a config change in a running system to loose the config.ini.
I have learned now and have downloaded a backup.
The system is still operational after the issue appears. I can use the webserver to upload a new config.ini.

Version: master - v9.2.0 - 2021-12-02

@jomjol
Copy link
Owner

jomjol commented Dec 22, 2021

This is strange. Sometimes my config.ini is not saved, e.g. if the ESP32 is busy with image processing while configuration.
But I never loose the config.ini.'
Is it possible, that your ESP32 or sd card is slightly instable?

There is a request for implementing a full backup through the web interface. I have put this to the request list, but I'm not working on it currently.

@jomjol jomjol closed this as completed Dec 22, 2021
@mwuerr
Copy link
Author

mwuerr commented Dec 22, 2021

Can you give me a hint how I can detect "instability". Is there anything in the logs that I should be looking for, or can you recommend me a stress test program?
I agree to your conclusion that it is most likely a hw related issue; otherwise others should see it also.
Of course I will monitor it; now logging is enabled; If it appears again I will post my findings from the log.

@mwuerr
Copy link
Author

mwuerr commented Dec 22, 2021

Can you confirm that:

  1. xxxx-xx-xxTyy:yy:yy: task_autodoFlow - next round - Round File Server: Option to delete multiple/all files in a directory #4
    should count up to high numbers of round. Basically "Round #" shows how many time an image was processed since the last reboot.
    Correct?
  2. ....= Main Started = ...
    is insterted into the log only after a reboot.

If those are yes's then the following log clearly shows that my device is regularily rebooting. Probably due to power issues.

2021-12-22T12:52:19: task_autodoFlow - round done
2021-12-22T12:52:19: CPU Temperature: 46.7
2021-12-22T12:56:14: task_autodoFlow - next round - Round #4
2021-12-22T12:56:14: FlowControll.doFlow - ClassFlowMakeImage
2021-12-22T12:56:22: FlowControll.doFlow - ClassFlowAlignment
2021-12-22T12:56:34: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T12:56:55: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T12:57:11: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T12:57:11: =============================================================================================
2021-12-22T12:57:11: =================================== Main Started ============================================
2021-12-22T12:57:11: =============================================================================================
2021-12-22T12:57:18: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T12:57:18: task_autodoFlow - next round - Round #1
2021-12-22T12:57:18: FlowControll.doFlow - ClassFlowMakeImage
2021-12-22T12:57:26: FlowControll.doFlow - ClassFlowAlignment
2021-12-22T12:57:37: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T12:57:58: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T12:58:14: FlowControll.doFlow - ClassFlowPostProcessing
2021-12-22T12:58:14: PostProcessing - Raw: 0313.3127 Value: 313.3127 Error: no error

and

2021-12-22T13:41:29: task_autodoFlow - round done
2021-12-22T13:41:29: CPU Temperature: 47.2
2021-12-22T13:45:24: task_autodoFlow - next round - Round #2
2021-12-22T13:45:24: FlowControll.doFlow - ClassFlowMakeImage
2021-12-22T13:45:33: FlowControll.doFlow - ClassFlowAlignment
2021-12-22T13:45:43: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T13:45:57: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T13:45:57: =============================================================================================
2021-12-22T13:45:57: =================================== Main Started ============================================
2021-12-22T13:45:57: =============================================================================================
2021-12-22T13:46:04: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T13:46:04: task_autodoFlow - next round - Round #1
2021-12-22T13:46:04: FlowControll.doFlow - ClassFlowMakeImage
2021-12-22T13:46:12: FlowControll.doFlow - ClassFlowAlignment
2021-12-22T13:46:23: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T13:46:46: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T13:46:46: =============================================================================================
2021-12-22T13:46:46: =================================== Main Started ============================================
2021-12-22T13:46:46: =============================================================================================
2021-12-22T13:46:52: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T13:46:53: task_autodoFlow - next round - Round #1
2021-12-22T13:46:53: FlowControll.doFlow - ClassFlowMakeImage
2021-12-22T13:47:01: FlowControll.doFlow - ClassFlowAlignment
2021-12-22T13:47:11: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T13:47:33: FlowControll.doFlow - ClassFlowCNNGeneral
2021-12-22T13:47:36: download_get_handler
2021-12-22T13:47:49: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
2021-12-22T13:47:49: =============================================================================================
2021-12-22T13:47:49: =================================== Main Started ============================================
2021-12-22T13:47:49: =============================================================================================

I will follow the instructions from:
https://arduino-hannover.de/2018/07/25/die-tuecken-der-esp32-stromversorgung/
and
https://community.hiveeyes.org/t/power-supply-for-the-esp32/1859/4
and throw a few capacitors at the problem.

@friedpa
Copy link

friedpa commented Dec 22, 2021

1 and 2 is correct

@jomjol
Copy link
Owner

jomjol commented Dec 22, 2021

Additionally: capacitor helps and an access to the web server also can trigger a reboot. So a good hint on the overall hardware stability is an undistorted observation of the count e.g. over night. I can reach up to 200 round with a stable system before an unattended reboot.

2021-12-22T01:12:00: CPU Temperature: 41.7
2021-12-22T01:12:00: task_autodoFlow - next round - Round #77
2021-12-22T01:12:00: 	FlowControll.doFlow - ClassFlowMakeImage

@friedpa
Copy link

friedpa commented Dec 22, 2021

I have a lot more rounds :o)
2021-12-22T08:02:24: task_autodoFlow - next round - Round #472
But I have seen over 1000 Rounds so far...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants