New Image for SD has a Bug
After a "long" printjob the server isnt reachable. A new start of the printserver make issues. the printersettings are deletet and a unkown printer is there.
I use a Raspi 3 with a Raspi Touchscreen 7"
After a "long" printjob the server isnt reachable. A new start of the printserver make issues. the printersettings are deletet and a unkown printer is there.
I use a Raspi 3 with a Raspi Touchscreen 7"
Comments
That fixed a possible complication that could lead to this. At least we hope it was the source of the problem. Saw this once on a windows machine but could not reproduce so we only deducted from code analysis.
Go to printer configs, you will probably see yours with size 0 byte. Delete it and add a new printer with same same name after server restart then all files are back, only printer settings must be reconfigured if you haven't stored a backup. If you have upload the configuration instead.
Install gdb
sudo apt-get install gdb
If it happens log in to pi
ps aux | grep pi@Felix:/var/lib/Repetier-Server $ ps aux | grep tier
remember the process id from server here 972 but that is always a different one
The start gdb
attach <pid number>
break
thread apply all bt
c
q
This will output a dump of all threads running with functions. From this I can get a good overview what is going on and who is blocking who.
Thanks for your time
Regarding licenses we can reset them if required from such problems. They are not lost. Just drop us a mail and we reset licenses.
Since the bug just destroys the printerconfig.xml file in configs, it is a good idea to back up a version. If it happens again, do the above sequence to help finding the reason, stop server, replace file, start server. The remaining files still stay intact.
After that i use latest Repetier downloaded at 23.07.
For now the Bug is also present.
I use a Pi3 without any Display.
The Issue i have see after a 1h print. The Repetier Website shows only the Buttons in the right upper corner, No Video, no printer at dashboard. After Reboot the was one unkown printer. (Radds Due @Prgramming Port) see Picture, the Delta_Pi (Mega2560 Ramps)was not conected at this time.
A Friend with PI3 have see this Bug to, after update to 0.85.2
Now i have installed gdb and hope i can give you some debug information next time...
Regards
Sven
Mint Linux
The unclear part is what blocks so that writing the config fails, which is why I need someone with the problem making a backtrace. So far I could not reproduc eit myself so no backtrace.
@Saavik24 where did the sequence fail? I've run them on my pi to make sure it works.
Mint Linux
Ok, that would mean the server crashed so it was not running at all. The starting script normally would restart a new process in that case. But a crash would also explain why it did not finish writing the config file. That is bad as this means to find the error you would need to attach to gdb before it crashes and then see the report. It's unlikely someone else then me runs the server always in debugger. Will see if others can confirm this and this not being a typo.
Here is the output from bt command in gdb:
gdb kind of stuck on the last line. I waited for a few minutes, but it never returned back to gdb console.
UPD: few minutes later and pi just disconnected from the network, as if the whole system crashed. After toggling the power printer is displayed as Unknown. Is there anything that can be done at this point? Or should I just delete/add and try to make it happen again and make another backtrace?
The problem arises at the end of print when an event gets send and a webbrowser requests a special event before writing the config file is finished. Then you get a deadlock and every process requiring that blocked mutex will also block until your pi gets maybe problems from all this stagging up.
Will work on a fixed version as soon as possible.
I also have added a automatic config backup on every save and automatic restore from backup if original is defect.
i update the Server by SSH. Now i have the bug that after printing 99% the Display and the Browser freeze.
ps aux | grep tier
avahi 437 0.0 0.2 3872 2580 ? Ss 18:21 0:00 avahi-daemon: running [RepetierServer.local]
repetie+ 843 2.9 2.8 706696 26788 ? S<sl 18:22 3:21 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon
pi 7129 0.0 0.1 4276 1852 pts/0 S+ 20:17 0:00 grep --color=auto tier
i dont know what to do with the answers above
(my english is bad)