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.
  • mplmpl
    edited July 31
    Got the same issue today. I think I was uploading new .gcode while printing and the upload just hanged and never finished. Once printer finished printing its UI got stuck on 99.9% (printer runs Repetier firmware so it has custom UI when printing via Repetier server and it still displays this custom UI, even after printing was finished)

    Here is the output from bt command in gdb:
    (gdb) thread apply all bt
    
    Thread 33 (Thread 0xb6a40450 (LWP 738)):
    #0  0xb6eafb30 in __pthread_cond_timedwait (cond=0x3201410, mutex=0x32013f8, abstime=0xb6a3fda8) at pthread_cond_timedwait.c:199
    #1  0x00864ec0 in boost::condition_variable::do_wait_until(boost::unique_lock<boost::mutex>&, timespec const&) [clone .constprop.217] ()
    #2  0x0086544c in boost::this_thread::hiden::sleep_until(timespec const&) ()
    #3  0x002e5d98 in sleep (abs_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:278
    #4  sleep<boost::date_time::subsecond_duration<boost::posix_time::time_duration, 1000ll> > (rel_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:284
    #5  repetier::SleepMS (millis=<optimized out>) at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:920
    #6  0x003449c8 in repetier::ResponseLogger::run () at /home/pi/repetier-server/Repetier-Server/server/RLog.cpp:284
    #7  0x002ed834 in boost::detail::thread_data<void (*)()>::run (this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #8  0x00864b44 in thread_proxy ()
    #9  0xb6eaae90 in start_thread (arg=0xb6a40450) at pthread_create.c:311
    #10 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 32 (Thread 0xb60ff450 (LWP 748)):
    #0  0xb6eafb30 in __pthread_cond_timedwait (cond=0x3230520, mutex=0x3230508, abstime=0xb60fedd0) at pthread_cond_timedwait.c:199
    #1  0x00864ec0 in boost::condition_variable::do_wait_until(boost::unique_lock<boost::mutex>&, timespec const&) [clone .constprop.217] ()
    #2  0x0086544c in boost::this_thread::hiden::sleep_until(timespec const&) ()
    #3  0x002e5d98 in sleep (abs_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:278
    #4  sleep<boost::date_time::subsecond_duration<boost::posix_time::time_duration, 1000ll> > (rel_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:284
    #5  repetier::SleepMS (millis=<optimized out>) at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:920
    #6  0x004357b4 in repetier::Updater::run (this=0x32303c0) at /home/pi/repetier-server/Repetier-Server/server/utils/Updater.cpp:487
    #7  0x00435f44 in operator() (p=<optimized out>, this=<optimized out>) at /usr/include/boost-1_60/boost/bind/mem_fn_template.hpp:49
    #8  operator()<boost::_mfi::mf0<void, repetier::Updater>, boost::_bi::list0> (f=..., this=<optimized out>, a=...) at /usr/include/boost-1_60/boost/bind/bind.hpp:259
    #9  operator() (this=<optimized out>) at /usr/include/boost-1_60/boost/bind/bind.hpp:1222
    #10 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, repetier::Updater>, boost::_bi::list1<boost::_bi::value<repetier::Updater*> > > >::run (
        this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #11 0x00864b44 in thread_proxy ()
    #12 0xb6eaae90 in start_thread (arg=0xb60ff450) at pthread_create.c:311
    #13 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 31 (Thread 0xb56ff450 (LWP 753)):
    #0  0xb6eb2780 in __lll_lock_wait (futex=futex@entry=0x323ca40, private=<optimized out>) at ../ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.c:46
    #1  0xb6ead1a4 in __GI___pthread_mutex_lock (mutex=0x323ca40) at pthread_mutex_lock.c:79
    #2  0x002ffa94 in pthread_mutex_lock (m=<optimized out>) at /usr/include/boost-1_60/boost/thread/pthread/mutex.hpp:62
    #3  lock (this=<optimized out>) at /usr/include/boost-1_60/boost/thread/pthread/mutex.hpp:116
    #4  boost::unique_lock<boost::mutex>::lock (this=0xb56fedb0) at /usr/include/boost-1_60/boost/thread/lock_types.hpp:346
    #5  0x003a3aac in unique_lock (m_=..., this=0xb56feda8) at /usr/include/boost-1_60/boost/thread/lock_types.hpp:124
    #6  repetier::PrintjobManager::manageJobs (this=0x323ca30) at /home/pi/repetier-server/Repetier-Server/server/Printjob.cpp:842
    #7  0x003a6e64 in operator() (p=<optimized out>, this=<optimized out>) at /usr/include/boost-1_60/boost/bind/mem_fn_template.hpp:49
    #8  operator()<boost::_mfi::mf0<void, repetier::PrintjobManager>, boost::_bi::list0> (f=..., this=<optimized out>, a=...) at /usr/include/boost-1_60/boost/bind/bind.hpp:259
    #9  operator() (this=<optimized out>) at /usr/include/boost-1_60/boost/bind/bind.hpp:1222
    #10 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, repetier::PrintjobManager>, boost::_bi::list1<boost::_bi::value<repetier::PrintjobManager*> > > >::---Type <return> to continue, or q <return> to quit---
    run (this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #11 0x00864b44 in thread_proxy ()
    #12 0xb6eaae90 in start_thread (arg=0xb56ff450) at pthread_create.c:311
    #13 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 30 (Thread 0xb4eff450 (LWP 758)):
    #0  0xb6eb2780 in __lll_lock_wait (futex=futex@entry=0x311375c, private=<optimized out>) at ../ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.c:46
    #1  0xb6ead1a4 in __GI___pthread_mutex_lock (mutex=0x311375c) at pthread_mutex_lock.c:79
    #2  0x002f0cf0 in pthread_mutex_lock (m=0x311375c) at /usr/include/boost-1_60/boost/thread/pthread/mutex.hpp:62
    #3  boost::mutex::lock (this=0x311375c) at /usr/include/boost-1_60/boost/thread/pthread/mutex.hpp:116
    
    #4  0x002e33fc in lock_guard (m_=..., this=<synthetic pointer>) at /usr/include/boost-1_60/boost/thread/lock_guard.hpp:38
    #5  repetier::GlobalConfig::getPrinterList (this=0x31136c0) at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:680
    #6  0x003d39d0 in repetier::Printer::fireEvent (this=0x32318e0, eventName="modelGroupListChanged", data=std::map with 0 elements)
        at /home/pi/repetier-server/Repetier-Server/server/printer.cpp:1171
    #7  0x00360884 in repetier::PrinterConfiguration::saveConfiguration (this=0x3006305) at /home/pi/repetier-server/Repetier-Server/server/PrinterConfiguration.cpp:1190
    #8  0x003a38f4 in repetier::PrintjobManager::resetJob (this=0x323ca30) at /home/pi/repetier-server/Repetier-Server/server/Printjob.cpp:917
    #9  0x003d2c9c in repetier::Printer::trySendNextLine (this=0x32318e0) at /home/pi/repetier-server/Repetier-Server/server/printer.cpp:1399
    #10 0x003d89a0 in repetier::Printer::run (this=0x32318e0) at /home/pi/repetier-server/Repetier-Server/server/printer.cpp:676
    #11 0x003d9b0c in operator() (p=<optimized out>, this=<optimized out>) at /usr/include/boost-1_60/boost/bind/mem_fn_template.hpp:49
    #12 operator()<boost::_mfi::mf0<void, repetier::Printer>, boost::_bi::list0> (f=..., this=<optimized out>, a=...) at /usr/include/boost-1_60/boost/bind/bind.hpp:259
    #13 operator() (this=<optimized out>) at /usr/include/boost-1_60/boost/bind/bind.hpp:1222
    #14 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, repetier::Printer>, boost::_bi::list1<boost::_bi::value<repetier::Printer*> > > >::run (
        this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #15 0x00864b44 in thread_proxy ()
    #16 0xb6eaae90 in start_thread (arg=0xb4eff450) at pthread_create.c:311
    #17 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 29 (Thread 0xb46ff450 (LWP 759)):
    #0  0xb6eafb30 in __pthread_cond_timedwait (cond=0x324cad0, mutex=0x324cab8, abstime=0xb46fecb0) at pthread_cond_timedwait.c:199
    #1  0x00864ec0 in boost::condition_variable::do_wait_until(boost::unique_lock<boost::mutex>&, timespec const&) [clone .constprop.217] ()
    #2  0x0086544c in boost::this_thread::hiden::sleep_until(timespec const&) ()
    #3  0x002e5d98 in sleep (abs_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:278
    #4  sleep<boost::date_time::subsecond_duration<boost::posix_time::time_duration, 1000ll> > (rel_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:284
    #5  repetier::SleepMS (millis=<optimized out>) at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:920
    #6  0x002e5e04 in repetier::CronJob::cronThread () at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:199
    #7  0x002ed834 in boost::detail::thread_data<void (*)()>::run (this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #8  0x00864b44 in thread_proxy ()
    #9  0xb6eaae90 in start_thread (arg=0xb46ff450) at pthread_create.c:311
    #10 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 28 (Thread 0xb3eff450 (LWP 764)):
    #0  0xb6eafb30 in __pthread_cond_timedwait (cond=0x32059f0, mutex=0x32059d8, abstime=0xb3efed58) at pthread_cond_timedwait.c:199
    ---Type <return> to continue, or q <return> to quit---
    #1  0x00864ec0 in boost::condition_variable::do_wait_until(boost::unique_lock<boost::mutex>&, timespec const&) [clone .constprop.217] ()
    #2  0x0086544c in boost::this_thread::hiden::sleep_until(timespec const&) ()
    #3  0x002e5d98 in sleep (abs_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:278
    #4  sleep<boost::date_time::subsecond_duration<boost::posix_time::time_duration, 1000ll> > (rel_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:284
    #5  repetier::SleepMS (millis=<optimized out>) at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:920
    #6  0x00429228 in repetier::WifiManager::watch (this=0x1cd7f14 <repetier::wifiManager>) at /home/pi/repetier-server/Repetier-Server/server/utils/FileUtils.cpp:945
    #7  0x0042988c in operator() (p=<optimized out>, this=<optimized out>) at /usr/include/boost-1_60/boost/bind/mem_fn_template.hpp:49
    #8  operator()<boost::_mfi::mf0<void, repetier::WifiManager>, boost::_bi::list0> (f=..., this=<optimized out>, a=...) at /usr/include/boost-1_60/boost/bind/bind.hpp:259
    #9  operator() (this=<optimized out>) at /usr/include/boost-1_60/boost/bind/bind.hpp:1222
    #10 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, repetier::WifiManager>, boost::_bi::list1<boost::_bi::value<repetier::WifiManager*> > > >::run (
        this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #11 0x00864b44 in thread_proxy ()
    #12 0xb6eaae90 in start_thread (arg=0xb3eff450) at pthread_create.c:311
    #13 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 27 (Thread 0xb36ff450 (LWP 771)):
    #0  0xb6eafb30 in __pthread_cond_timedwait (cond=0x3291590, mutex=0x3291578, abstime=0xb36fed60) at pthread_cond_timedwait.c:199
    #1  0x00864ec0 in boost::condition_variable::do_wait_until(boost::unique_lock<boost::mutex>&, timespec const&) [clone .constprop.217] ()
    #2  0x0086544c in boost::this_thread::hiden::sleep_until(timespec const&) ()
    #3  0x002e5d98 in sleep (abs_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:278
    #4  sleep<boost::date_time::subsecond_duration<boost::posix_time::time_duration, 1000ll> > (rel_time=...) at /usr/include/boost-1_60/boost/thread/pthread/thread_data.hpp:284
    #5  repetier::SleepMS (millis=<optimized out>) at /home/pi/repetier-server/Repetier-Server/server/global_config.cpp:920
    #6  0x00380c20 in repetier::WorkDispatcher::run (this=0x380c20 <repetier::WorkDispatcher::run()+948>) at /home/pi/repetier-server/Repetier-Server/server/WorkDispatcher.cpp:493
    #7  0x00380f68 in operator() (p=<optimized out>, this=<optimized out>) at /usr/include/boost-1_60/boost/bind/mem_fn_template.hpp:49
    #8  operator()<boost::_mfi::mf0<void, repetier::WorkDispatcher>, boost::_bi::list0> (f=..., this=<optimized out>, a=...) at /usr/include/boost-1_60/boost/bind/bind.hpp:259
    #9  operator() (this=<optimized out>) at /usr/include/boost-1_60/boost/bind/bind.hpp:1222
    #10 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, repetier::WorkDispatcher>, boost::_bi::list1<boost::_bi::value<repetier::WorkDispatcher*> > > >::run (this=<optimized out>) at /usr/include/boost-1_60/boost/thread/detail/thread.hpp:116
    #11 0x00864b44 in thread_proxy ()
    #12 0xb6eaae90 in start_thread (arg=0xb36ff450) at pthread_create.c:311
    #13 0xb6c9d598 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 26 (Thread 0xb2eff450 (LWP 772)):
    #0  0xb6eb2780 in __lll_lock_wait (futex=futex@entry=0x323ca40, private=<optimized out>) at ../ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.c:46
    #1  0xb6ead1a4 in __GI___pthread_mutex_lock (mutex=0x323ca40) at pthread_mutex_lock.c:79
    #2  0x002f0cf0 in pthread_mutex_lock (m=0x323ca40) at /usr/include/boost-1_60/boost/thread/pthread/mutex.hpp:62
    #3  boost::mutex::lock (this=0x323ca40) at /usr/include/boost-1_60/boost/thread/pthread/mutex.hpp:116
    #4  0x003a10d0 in lock_guard (m_=..., this=<synthetic pointer>) at /usr/include/boost-1_60/boost/thread/lock_guard.hpp:38
    
    
    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?
  • @mpl You are my hero. At first I feared the solution lies in the missing 25 threads but the most critical was included and from there I could in deed find the deadlock.

    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.
  • Cool I was feeling dumb because I couldn't get any output. Sounds like you caught it before the big crash. I thought it was interesting that the only printers that went to the unknown state were the ones running Repetier Firmware.

  • No, error did not depend on firmware. At least directly. Maybe having faster communication with smaller packets made the timing worse in your case, but that is speculation. So for tomorrow my only plan is to fix server issues and make a new release 0.86.0

    I also have added a automatic config backup on every save and automatic restore from backup if original is defect.
  • Sorry for the late Answer,
    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) :D


  • This also happend to one of my printers running a windows 8.1 tablet. Printer also comes up as unknown
  • Any updates on this?  I have been having this problem on my RPi 3 for a few weeks now, and its very frustrating to have to either re-image the Pi or re-add the printer each time.  Now, when I boot to "Unknown" - any network connection causes the server to crash.  Even using the old printer name does not restore my files and history.
  • It's planned to release today. Please visit our homepage in case server does not see this directly. Server might take a week to see the update but running the normal installer on the debian package installs it as well as upgrade.
  • Thanks - trying to install via command line and getting 
    error: Checksum does not match server checksum - aborted
  • Thanks for the hint. Problem is fixed now.
  • I had this happen on a Windows Tablet what is the procedure to recover the lost Printer Profile and GCODE History? I was running 85.2 and I will upgrade to 86.2 once I try to recover this Printer Profile. Everything was fine, I had printed many jobs this week and I decided to give the tablet a reboot and when it came back up the only Printer Profile was listed as "Unknown". 
  • Shutdown server, delete the empty printer config file. Then update to 0.86.2 and add a new printer with same name. It shoudl get same slug name so it reuses all your stored gcode files. These are not damanged, only the config file got truncated to 0 byte making it appear as unknown.
Sign In or Register to comment.