Repetier Server Pro 0.92.0, Raspberry Pi 4, Random Stop Printing

Lexan

Hello,
I realized it now twice that that my printer freeze during a print.
The last time 2 at the exact same moment.

My Geeetech A30 Stopped completly, the Geeeetech A20M just go veeeeeeeeery veeeeeeeeeeery slow.

On the console of the A30 it just repeat's the last 3 lines over and over again without reaction.
The Temperature stayed stable on both mashines

Any solutions ?

Repetier

To find the reason more information is needed.
Did the printers get disconnected from server and job stop?
What are the lines getting repeated?
Also check with ACK/Commands in log enabled to see all communication.
Any messages in /var/lib/Repetier-Server/logs/server.log or /var/log/syslog
around the time it happened.
One typical reason for problems is undervoltage that caused disconnection of usb ports and hence disconnect printers so server stops printing in that case. So that is first thing to test. Have no experience with pi 4 but pi 0 - pi 3+ had that problem and pi 4 might use even more power. Also same time for all printers points towards that problem if they run on the same pi.

Lexan

no the printer showed still connected.

what i just realized, i also not able to start a new print job without reconnect the printer.

Edit, found this before:

< 23:00:12.011: N608220 G1 X218.207 Y215.904 E3.13490 > 23:00:12.107: ok < 23:00:12.107: N608221 G1 X218.197 Y209.927 E3.29461 > 23:00:12.123: ok < 23:00:12.123: N608222 G1 X218.245 Y209.507 E3.30592 > 23:00:12.139: ok < 23:00:12.139: N608223 G1 X218.294 Y209.341 E3.31053 > 23:00:43.146: Warning: Communication timeout - resetting communication buffer. > 23:00:43.146: Connection status: Buffered:41, Manual Commands: 2, Job Commands: 5000 > 23:00:43.146: Buffer used:41 Enforced free byte:41 lines stored:1 < 23:00:43.146: M117 ETA 23:15:51 day 17 > 23:01:14.149: Warning: Communication timeout - resetting communication buffer. > 23:01:14.149: Connection status: Buffered:25, Manual Commands: 2, Job Commands: 5000 > 23:01:14.150: Buffer used:25 Enforced free byte:18 lines stored:1 < 23:01:14.150: M117 ETE 00:15:34 < 23:01:14.150: N608224 M105 > 23:01:45.158: Warning: Communication timeout - resetting communication buffer. > 23:01:45.158: Connection status: Buffered:34, Manual Commands: 2, Job Commands: 5000 > 23:01:45.158: Buffer used:34 Enforced free byte:21 lines stored:2 > 23:01:45.158: Warning: Too many timeouts without response - disabling timeout message! < 23:01:45.159: M117 Layer 1036/1102 < 23:01:45.159: N608225 M105 < 23:02:16.168: M117 ETA 23:17:21 day 17 < 23:02:47.178: M117 ETE 00:15:34 < 23:02:47.179: N608226 M105

it continues like this for hours

< 1:17:08.497: M117 ETA 01:32:16 day 18
< 1:17:39.506: M117 ETE 00:15:34
< 1:17:39.506: N608400 M105
< 1:18:10.507: M117 Layer 1036/1102
< 1:18:10.507: N608401 M105
< 1:18:41.510: M117 ETA 01:33:46 day 18
< 1:19:12.518: M117 ETE 00:15:34
< 1:19:12.518: N608402 M105
< 1:19:43.527: M117 Layer 1036/1102
< 1:19:43.527: N608403 M105
< 1:20:14.532: M117 ETA 01:35:26 day 18
< 1:20:45.536: M117 ETE 00:15:34
< 1:21:16.543: M117 Layer 1036/1102
< 1:21:47.552: M117 ETA 01:36:56 day 18
< 1:22:18.556: M117 ETE 00:15:34
< 1:22:49.562: M117 Layer 1036/1102
< 1:23:20.566: M117 ETA 01:38:26 day 18
< 1:23:51.569: M117 ETE 00:15:34
< 1:24:22.577: M117 Layer 1036/1102
< 1:24:53.583: M117 ETA 01:40:06 day 18
< 1:25:24.593: M117 ETE 00:15:34
< 1:25:55.601: M117 Layer 1036/1102
< 1:26:26.605: M117 ETA 01:41:36 day 18
< 1:26:57.611: M117 ETE 00:15:34
< 1:27:28.613: M117 Layer 1036/1102
< 1:27:59.615: M117 ETA 01:43:06 day 18
< 1:28:30.616: M117 ETE 00:15:34

i got the original pi psu for the rp4 so i hope thats not the source of trouble.
i can still control other printers or go through the web menu.

can i reach log you wanted via the web interface ?

Lexan

here i tried to reconnect and hoped to continue with the rescue option

9:18:45.301: M117 Layer 1036/1102 < 9:19:16.303: M117 ETA 09:34:23 day 18 < 9:19:38.280: N608404 M112 < 9:19:49.321: N608405 M105 > 9:19:50.314: JumpToApp0 < 9:19:50.325: N608406 M105 > 9:19:50.330: JumpToApp1 > 9:19:50.346: Response while unconnected:MACHINE_TYPE:A30 UUID: FIRMWARE_NAME:V1.xx.59 > 9:19:50.346: Response while unconnected:MACHINE_TYPE:A30 UUID: FIRMWARE_NAME:V1.xx.59 > 9:19:50.346: MACHINE_TYPE:A30 UUID: FIRMWARE_NAME:V1.xx.59 > 9:19:50.442: Response while unconnected:PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1 > 9:19:50.442: Response while unconnected:PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1 > 9:19:50.442: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1 > 9:19:50.554: echo:SD init fail > 9:19:50.570: echo:Unknown command: > 9:19:50.570: Response while unconnected:ok > 9:19:50.573: ok < 9:19:50.573: N1 M110 < 9:19:50.574: N2 M105 < 9:19:50.574: N3 M115 < 9:19:50.574: N4 M220 S100 < 9:19:50.574: N5 M221 S100 < 9:19:50.574: N6 G92 E0 < 9:19:50.574: N7 G90 < 9:19:50.574: N8 M82 > 9:19:50.586: ok > 9:19:50.586: ok < 9:19:50.586: N9 G21 < 9:19:50.587: @getip > 9:19:50.615: ok T:0.0 /0.0 B:0.0 /0.0 T0:0.0 /0.0 T1:0.0 /0.0 T2:0.0 /0.0 F:0 R:0 @:0 B@:0 > 9:19:52.194: Error0: Line Number is not Last Line Number+1, Last Line: 0 > 9:19:52.194: Resend: 1 > 9:19:52.205: ok < 9:19:52.206: Resend: N1 M110 < 9:19:52.206: Resend: N2 M105 < 9:19:52.206: Resend: N3 M115 < 9:19:52.206: Resend: N4 M220 S100 < 9:19:52.206: Resend: N5 M221 S100 < 9:19:52.206: Resend: N6 G92 E0 < 9:19:52.206: Resend: N7 G90 < 9:19:52.206: Resend: N8 M82 > 9:19:52.238: ok > 9:19:52.238: ok T:0.0 /0.0 B:0.0 /0.0 F:0 R:100 @:0 B@:0 > 9:19:52.239: MACHINE_TYPE:A30 UUID: FIRMWARE_NAME:V1.xx.59 < 9:19:52.239: Resend: N9 G21 > 9:19:52.334: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1 > 9:19:52.446: ok > 9:19:52.446: ok > 9:19:52.446: ok > 9:19:52.446: ok > 9:19:52.446: ok > 9:19:52.447: ok < 9:19:52.447: M117 192.168.178.120:3344 < 9:19:52.447: N10 M105 < 9:19:52.447: N11 M105 > 9:19:52.462: ok > 9:19:52.462: ok > 9:19:52.483: ok T:0.0 /0.0 B:0.0 /0.0 F:0 R:100 @:0 B@:0 > 9:19:52.483: ok T:0.0 /0.0 B:0.0 /0.0 F:0 R:100 @:0 B@:0 < 9:19:53.453: N12 M105 > 9:19:53.475: ok T:217.2 /0.0 B:58.0 /0.0 F:0 R:100 @:0 B@:0 < 9:19:54.455: N13 M105

Lexan

checked via putty

/var/lib/Repetier-Server/logs/server.log
Nothink happend at this time

var/log/syslog
just shows some time & date service actions, also only from today no days back

Repetier

server.log rotates on daily basis. Old log is then server.log.0

In the log of the hanging case you see that firmware stopped responding with "ok". Knowing this normally does not happen I think problem was that the driver on one of the sides got a problem not sending the backwards data to server any more. That is a problem that sometimes also happens, also I never had it. But I have seen it happen for others sometimes. That is not the disconnect from undervoltage! That is why server.log showed no reconnect.

I assume reconnect was successful as I see "ok" came back when it was reinitialized.

Lexan

had now 2 sucessfull prints over 5 hours, will keep an eye on it if it happens again

Lexan

it starts again, over and over printers are freezing, getting annoing
here syslog
Read at 14:57

Nov 26 13:45:53 Repetier-Server systemd[1]: Starting Time & Date Service...

Nov 26 13:45:53 Repetier-Server dbus-daemon[328]: [system] Successfully activated service 'org.freedesktop.timedate1'

Nov 26 13:45:53 Repetier-Server systemd[1]: Started Time & Date Service.

Nov 26 13:46:23 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.

Nov 26 13:46:58 Repetier-Server dbus-daemon[328]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.5161' (uid=0 pid=1957 comm="timedatectl ")

Nov 26 13:46:58 Repetier-Server systemd[1]: Starting Time & Date Service...

Nov 26 13:46:58 Repetier-Server dbus-daemon[328]: [system] Successfully activated service 'org.freedesktop.timedate1'

Nov 26 13:46:58 Repetier-Server systemd[1]: Started Time & Date Service.

Nov 26 13:47:28 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.

Nov 26 13:48:04 Repetier-Server dbus-daemon[328]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.5170' (uid=0 pid=2044 comm="timedatectl ")

Nov 26 13:48:04 Repetier-Server systemd[1]: Starting Time & Date Service...

Nov 26 13:48:04 Repetier-Server dbus-daemon[328]: [system] Successfully activated service 'org.freedesktop.timedate1'

Nov 26 13:48:04 Repetier-Server systemd[1]: Started Time & Date Service.

Nov 26 13:48:34 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.

Nov 26 13:49:09 Repetier-Server dbus-daemon[328]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.5176' (uid=0 pid=2120 comm="timedatectl ")

Nov 26 13:49:09 Repetier-Server systemd[1]: Starting Time & Date Service...

Nov 26 13:49:09 Repetier-Server dbus-daemon[328]: [system] Successfully activated service 'org.freedesktop.timedate1'

Nov 26 13:49:09 Repetier-Server systemd[1]: Started Time & Date Service.

Nov 26 13:49:25 Repetier-Server systemd[1]: Created slice User Slice of UID 1000.

Nov 26 13:49:25 Repetier-Server systemd[1]: Starting User Runtime Directory /run/user/1000...

Nov 26 13:49:25 Repetier-Server systemd[1]: Started User Runtime Directory /run/user/1000.

Nov 26 13:49:25 Repetier-Server systemd[1]: Starting User Manager for UID 1000...

Nov 26 13:49:26 Repetier-Server systemd[2170]: Reached target Timers.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).

Nov 26 13:49:26 Repetier-Server systemd[2170]: Listening on GnuPG network certificate management daemon.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Reached target Paths.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Listening on GnuPG cryptographic agent (ssh-agent emulation).

Nov 26 13:49:26 Repetier-Server systemd[2170]: Listening on GnuPG cryptographic agent and passphrase cache.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Starting D-Bus User Message Bus Socket.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).

Nov 26 13:49:26 Repetier-Server systemd[2170]: Listening on D-Bus User Message Bus Socket.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Reached target Sockets.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Reached target Basic System.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Reached target Default.

Nov 26 13:49:26 Repetier-Server systemd[2170]: Startup finished in 183ms.

Nov 26 13:49:26 Repetier-Server systemd[1]: Started User Manager for UID 1000.

Nov 26 13:49:26 Repetier-Server systemd[1]: Started Session c1 of user pi.

Nov 26 13:49:39 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.

Nov 26 13:50:14 Repetier-Server dbus-daemon[328]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.5187' (uid=0 pid=2238 comm="timedatectl ")

Nov 26 13:50:14 Repetier-Server systemd[1]: Starting Time & Date Service...

Nov 26 13:50:14 Repetier-Server dbus-daemon[328]: [system] Successfully activated service 'org.freedesktop.timedate1'

Nov 26 13:50:14 Repetier-Server systemd[1]: Started Time & Date Service.

Nov 26 13:50:45 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.

Nov 26 13:51:20 Repetier-Server dbus-daemon[328]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.5193' (uid=0 pid=2312 comm="timedatectl ")

Nov 26 13:51:20 Repetier-Server systemd[1]: Starting Time & Date Service...

Nov 26 13:51:20 Repetier-Server dbus-daemon[328]: [system] Successfully activated service 'org.freedesktop.timedate1'

Nov 26 13:51:20 Repetier-Server systemd[1]: Started Time & Date Service.

Nov 26 13:51:50 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.

Lexan

der server log scheint nicht zu existieren
Die Drucker lassen sich per Display Steuern.
Allerdings ist die Termperatur Messung vom Server komplett eingefroren.

tgreif

ich hatte ei ahnliches problem .
mein drucker hatte immer gut gearbeitet aber dann nach einiger zeit, manchmal nach stunden manchmal nach minuten , fing er an zu stottern und spaeter blib er stehen.
es lag am netzteil. irgendwann fing es an die serielle ubertragung zu stoeren .
seitdem ich mein cinanetzteil mit einem neuem ersaetzt habe , geht es wie vorher .

Lexan

hab extra n marken netzteil mit dem pi4 gekauft, werde mal schauen was das osziloskop sagt

Repetier

> Read at 14:57

That part of the log is missing.

It is important to use no usb charger as they correct changes too slow sometimes.

Make sure you are on 0.93.0 which has some locks fixed we found.
Is the server still accessible and working apart form not communicating with printer?

Lexan

that were the last lines in the log.
you cant control in this status the printers, also cant acess the complete webinterface, only parts.
yes im running already on 0.93.0

Repetier

If some parts in web interface block so nothing works it could be a dead lock. If you follow
https://www.repetier-server.com/knowledgebase/debugging-crashes-hangs-on-linux/
and send me the full backlog I can analyse if that is the case and fix the lock so it does not happen again.
Unfortunately these locks are hard to detect and do not happen on all systems equally. They just depend on too many things even printer firmware processor and sd card model can influence it.

Lexan

i will do so after the next crash :D

Lexan

i have some trouble to finish the step to get the PID of the serve.
I now made a clean install with the last image, but i want anyway start the documentation.
so before there was no way to find the number, or at least i didnt found the right command to get this number shown.
i always got the feedback that the file is not exsisting.

Repetier

What did you enter to get pid?
ps aux | grep tier
is what I normally send. Do not copy the command prompt left from command.

Lexan

ah there you go, maybe you can mark this command as a command.
For newbies in linux like me there is no way to see in that article that you entered this command to get the PID feedback

Repetier

Have removed the prompt like with the other commands.

Lexan

the correction now is much clearer thank you.
so i understand it right that i will need always a putty open that rund the gdb untill the system crash ?