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"

Comments

  • edited July 14
    I renamed the syslog to syslog.txt. othervice i cant paste it here
  • Have you already updated to 0.85.2 ?
    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.
  • I have seen this problem a few times on my PI 3, I am not using the repetier image, I installed it on the PI running Raspberian. I have been watching the forum to see if anyone else has had it happen to them. It seems to happen after a print job has completed. I have a prusa I3 running repetier firmware and a mono price mini on the PI, and it loses the one running repetier. Are there any logs that would help trouble shoot this issue?
  • First you should update to 0.85.2 as this fixes a potential source that might already fix it. If it still happens this will greatly help on a po:

    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
    repetie+   972  0.3  1.7 230756 16552 ?        S<sl Jul08  33:17 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon
    pi        1047  0.0  0.1   4276  1808 pts/0    S+   08:04   0:00 grep --color=auto 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.

  • I had the best intentions regarding getting you the dump from my PI 3. It crashed ate one of my licenses and generally made me mad. I am done playing with the PI for a bit. I set the server up on a Linux box and am enjoying the horse power it has. However it too has dropped the same printer, like the PI. What files, or dumps would you like from the Linux box, if you still need them. 

    Thanks for your time
  • Above commands apply to all linux versions where it happens. Important is to do it when crashed and not after restart.

    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.
  • Slowmo said:
    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"
    I have seen this Bug 2 times after i have made a update from Version 0.8 to 0.85.2.
    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

     

  • I also saw it on the Linux install but not as prevalent, I tried to get the debug info as described but the commands didn't work. I didn't take the time to figure out what was wrong, I had a long list of prints to finish.  

    Mint Linux 

    Operating systemDebian Linux 9.0
    Kernel and CPULinux 4.8.0-53-generic on x86_64
  • Yes, whatever the problem is it happens while writing the new config and sets file size to 0 so on next startup it tries to load fails and only keeps default config with printer name "unknown". That much is clear.

    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.

  • I am on a Linux PC now .... I did update the process id and the response was no file or directory found. I apologize for not digging into it I had a lot to do on the printers at the time.

    Mint Linux 

    Operating systemDebian Linux 9.0
    Kernel and CPULinux 4.8.0-53-generic on x86_64



  • You mean " ps aux | grep tier" did not return a file of a running server?

    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.
Sign In or Register to comment.