Repetier Server Pro 0.92.0, Raspberry Pi 4, Random Stop Printing
in Bug Reports
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 ?
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 ?
Comments
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.
what i just realized, i also not able to start a new print job without reconnect the printer.
Edit, found this before:
it continues like this for hours
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 ?
/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
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.
here syslog
Read at 14:57
Die Drucker lassen sich per Display Steuern.
Allerdings ist die Termperatur Messung vom Server komplett eingefroren.
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 .
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?
you cant control in this status the printers, also cant acess the complete webinterface, only parts.
yes im running already on 0.93.0
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.
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.
ps aux | grep tier
is what I normally send. Do not copy the command prompt left from 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
so i understand it right that i will need always a putty open that rund the gdb untill the system crash ?