›

Random reboots after updating to 1.4.3

FabrizioFabrizio
in Repetier-Server
I currently have 3 instances of RS running
2 on RPI3b+ and one on a laptop, a couple of days ago I updated all to 1.4.3 and since then, one of the instances running on RPi is having random reboots, the other raspberry and the notebook work without problems with 1.4 .3, but this RPI does not....
I don't know how to diagnose the problem, much less how to solve it.
Thinking that it could be a faulty power supply, I changed the power supply (now it has a 5V 4A one) but last night it restarted again
I copy the log from the last jobs that I sent and after the restart, where it only shows that it was started again but it does not show any error, at least I cannot find it
I was thinking of making a backup and taking out the microSD, formatting it and reinstalling everything again, since something strange happens with this instance, because I have an identical RPi running with 4 identical printers and it has no problems

2022-11-12 04:57:09: Job created: /var/lib/Repetier-Server/printer/MagnaSE1/jobs/00000001_Deadpool Base y Piernas v2.u
2022-11-12 04:57:09: finish job creation /var/lib/Repetier-Server/printer/MagnaSE1/jobs/00000001_Deadpool Base y Piernas v2.u
2022-11-12 04:57:09: start printjob Deadpool Base y Piernas v2 on printer MagnaSE3
2022-11-12 04:57:09: Updating info for /var/lib/Repetier-Server/printer/MagnaSE1/jobs/00000001_Deadpool Base y Piernas v2.g printer MagnaSE1
2022-11-12 04:57:14: Time analysing /var/lib/Repetier-Server/printer/MagnaSE1/jobs/00000001_Deadpool Base y Piernas v2.g:4442470 us
2022-11-12 04:57:14: LUA job rendering.render#{"id":1,"image":"/var/lib/Repetier-Server/printer/MagnaSE1/jobs/00000001_Deadpool Base y Piernas v2_l.png","layer":"/var/lib/Repetier-Server/printer/MagnaSE1/jobs/00000001_Deadpool Base y Piernas v2.layer","list":"jobs","slug":"MagnaSE1"}
2022-11-12 04:57:14: cloudinitalize: application/json
2022-11-12 04:57:23: get 00000001_Deadpool Base y Piernas v2_l.png status 200
2022-11-12 04:57:23: contenttype:application/octet-stream
2022-11-12 04:57:23: get 00000001_Deadpool Base y Piernas v2_m.png status 200
2022-11-12 04:57:23: contenttype:application/octet-stream
2022-11-12 04:57:23: get 00000001_Deadpool Base y Piernas v2_s.png status 200
2022-11-12 04:57:23: contenttype:application/octet-stream
2022-11-12 04:57:23: Images rendered over cloud for 1
2022-11-12 04:59:19: Updating info for /var/lib/Repetier-Server/printer/MagnaSE3/jobs/00000007_Calavera Soporte de Arbol.g printer MagnaSE3
2022-11-12 04:59:20: start printjob Calavera Soporte de Arbol on printer MagnaDual
2022-11-12 04:59:31: Time analysing /var/lib/Repetier-Server/printer/MagnaSE3/jobs/00000007_Calavera Soporte de Arbol.g:12563590 us
2022-11-12 05:09:13: Job created: /var/lib/Repetier-Server/printer/MagnaDual7/jobs/00000014_batman vs joker.u
2022-11-12 05:09:20: finish job creation /var/lib/Repetier-Server/printer/MagnaDual7/jobs/00000014_batman vs joker.u
2022-11-12 05:09:21: Updating info for /var/lib/Repetier-Server/printer/MagnaDual7/jobs/00000014_batman vs joker.g printer MagnaDual7
2022-11-12 05:09:22: start printjob batman vs joker on printer MagnaSE1
2022-11-12 05:09:37: Time analysing /var/lib/Repetier-Server/printer/MagnaDual7/jobs/00000014_batman vs joker.g:15990211 us
2022-11-12 06:00:27: Closing websocket for missing ping
2022-11-12 06:00:41: Websocket opened
2022-11-12 06:04:39: Closing websocket for missing ping
2022-11-12 09:26:36: Start logging...
2022-11-12 09:26:36: Repetier-Server 1.4.3
2022-11-12 09:26:36: Imported external command Shutdown Server
2022-11-12 09:26:36: Imported external command Reboot Server
2022-11-12 09:26:36: Imported allowed execute command shutdown
2022-11-12 09:26:36: Imported allowed execute command reboot
2022-11-12 09:26:36: Webdirectory: /usr/local/Repetier-Server/www/
2022-11-12 09:26:36: Storage directory: /var/lib/Repetier-Server/
2022-11-12 09:26:36: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
2022-11-12 09:26:36: Directory for temporary files: /tmp/
2022-11-12 09:26:36: Reading firmware data ...
2022-11-12 09:26:36: Starting Network ...
2022-11-12 09:26:36: Active features:4095
2022-11-12 09:26:36: Reading printer configurations ...
2022-11-12 09:26:36: Reading printer config /var/lib/Repetier-Server/configs/MagnaSE3.xml
2022-11-12 09:26:36: Reloading Timelapse Entries...
2022-11-12 09:26:36: Starting printjob manager thread for MagnaSE3
2022-11-12 09:26:37: Reading printer config /var/lib/Repetier-Server/configs/MagnaDual8.xml
2022-11-12 09:26:37: Reloading Timelapse Entries...
2022-11-12 09:26:37: Starting printjob manager thread for MagnaDual8
2022-11-12 09:26:37: Reading printer config /var/lib/Repetier-Server/configs/MagnaSE1.xml
2022-11-12 09:26:37: Reloading Timelapse Entries...
2022-11-12 09:26:37: Starting printjob manager thread for MagnaSE1
2022-11-12 09:26:37: Recover file and job found
2022-11-12 09:26:38: Reading printer config /var/lib/Repetier-Server/configs/MagnaDual7.xml
2022-11-12 09:26:38: Reloading Timelapse Entries...
2022-11-12 09:26:38: Starting printjob manager thread for MagnaDual7
2022-11-12 09:26:38: Starting printer threads ...
2022-11-12 09:26:38: Starting printer thread for MagnaDual
2022-11-12 09:26:38: Starting printer thread for MagnaSE3
2022-11-12 09:26:38: Starting printer thread for MagnaSE2
2022-11-12 09:26:38: Starting printer thread for MagnaSE1
2022-11-12 09:26:38: Starting work dispatcher subsystem ...
2022-11-12 09:26:38: Starting user database ...
2022-11-12 09:26:38: Importing projects ...
2022-11-12 09:26:38: Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network.xml
2022-11-12 09:26:38: Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network-stored.xml
2022-11-12 09:26:38: Initializing LUA ...
2022-11-12 09:26:38: Starting wifi watcher ...
2022-11-12 09:26:38: Register LUA cloud services
2022-11-12 09:26:38: add G-Code-Renderer
2022-11-12 09:26:39: LUA initalization finished.
2022-11-12 09:26:39: Setting up MQTT Client ... 
2022-11-12 09:26:39: Work dispatcher thread started.
2022-11-12 09:26:39: Starting web server ... 
2022-11-12 09:26:39: Internal work dispatcher thread started.
2022-11-12 09:26:39: Webserver started.
2022-11-12 09:26:39: Websocket opened
2022-11-12 09:26:40: Connection started: MagnaSE1
2022-11-12 09:26:40: Internal reset printer MagnaSE1
2022-11-12 09:26:40: Reset printer MagnaSE1
2022-11-12 09:26:40: Connection started: MagnaSE3
2022-11-12 09:26:40: Internal reset printer MagnaSE3
2022-11-12 09:26:40: Reset printer MagnaSE3
2022-11-12 09:26:40: Connection started: MagnaDual
2022-11-12 09:26:40: Internal reset printer MagnaDual
2022-11-12 09:26:40: Reset printer MagnaDual
2022-11-12 09:26:43: New SSID Not Connected
2022-11-12 09:26:51: Websocket opened
2022-11-12 09:41:28: Closing websocket for missing ping
2022-11-12 09:41:28: Closing websocket for missing ping
2022-11-12 09:41:30: Websocket opened
2022-11-12 09:41:31: Websocket opened
2022-11-12 13:30:39: Websocket opened
2022-11-12 13:32:16: MainRequestHandler::handleRequest:Assertion violation: !_pStream in file "/builds/repetier/repetier-server/Repetier-Server/Poco/Net/src/HTTPServerResponseImpl.cpp", line 69

Comments

  • RepetierRepetier
    If it is really the pi rebooting, the issue is normally not  Repetier-Server.  Apps can not crash linux that easily. In server log I just see

    2022-11-12 06:04:39: Closing websocket for missing ping
    2022-11-12 09:26:36: Start logging...
    2022-11-12 09:26:36: Repetier-Server 1.4.3

    It misses shutdown and has 3 hours between next start. So that is probably when it happened. Since it looks more like linux reboot you should have a look at /var/log/syslog if it contains any info before it crashes. If it is power related you will not see anything, but maybe you see a kernal panic or an issue detected by linux before it stopped.
  • FabrizioFabrizio
    I formatted the SD and reinstalled RS again and I haven't had any server reboots yet, but one of the printers is having random really big pauses, which generates a giant blob

    I look in the "Console" tab and find this message

    Mesg:2:06:44.576: Connection status: Buffered:82, Manual Commands: 0, Job Commands: 5000
    Mesg:2:06:44.576: Buffer used:82 Enforced free byte:41 lines stored:2
    Mesg:2:07:04.577: Warning: Communication timeout - resetting communication buffer.
    Mesg:2:07:04.577: This means that an expected firmware response was not seen within the expected time.
    Mesg:2:07:04.577: The typical reason is a communication error and print should continue after the communication reset.

    I don't understand why it could be happening, could it have something to do with the printer or with the server? I have 3 instances of RS running and in all of them there are machines like this one that are failing, but I did a test print from the SD, without connecting it to the server and I don't have those pauses
    I changed the USB cable and the port to which it is connected and I'm still the same
  • RepetierRepetier
    Timeouts happen when we do not see a "ok" from printer firmware telling us that we can send next line. After timeout seconds we assume it was not returned correctly e.g. only "o" or "k". So first step should be to see if busy is supported. Go to console activate "ack" and send "G4 S10". If you see a few "busy" messages you can safely reduce timeout to 3s so pauses are as short as possible.

    For full analysis you need to activate logging and check the communication around the timeout message to see e.g. a command being send and no "ok" returned or malformed ok. This is priner-usb communication you do not have with sd card print. Works in most cases without issues but sometimes these error happen causing a timeout before it continues.

    Are you already on 1.4.4 - also it only had small fixes. 
Sign In or Register to comment.