›

After upgrading to 0.86.2 interface is not working.

maverickcciemaverickccie
edited September 2017 in Repetier-Server
I am running on a pi3 with a 7" LCD. I went to upgrade and the automatic upgrade did not work, so I had to do it via the command line. The upgrade work and the UI and webpage came up fine. Then while I working on something else I noticed the the UI had the loast connection to my server message on it and the web interface did the same thing. no the LCD screen is white and has the this site can't be reached 127.0.0.1 refused to connect message. I can still get to the command line via ssh but have no idea what the issue is. Any ides?

Comments

  • maverickcciemaverickccie
    Here is the server.log after the upgrade:
    2017-09-02 15:00:51: Start logging...
    2017-09-02 15:00:51: Imported external command Shutdown Server
    2017-09-02 15:00:51: Imported external command Reboot Server
    2017-09-02 15:00:51: Webdirectory: /usr/local/Repetier-Server/www/
    2017-09-02 15:00:51: Storage directory: /var/lib/Repetier-Server/
    2017-09-02 15:00:51: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2017-09-02 15:00:51: Directory for temporary files: /tmp/
    2017-09-02 15:00:51: Reading firmware data ...
    2017-09-02 15:00:51: Starting Network ...
    2017-09-02 15:00:51: Active features:4095
    2017-09-02 15:00:51: Reading printer configurations ...
    2017-09-02 15:00:51: Reading printer config /var/lib/Repetier-Server/configs/MTPrusaI3Mk21.xml
    2017-09-02 15:00:51: Starting printjob manager thread for MTPrusaI3Mk21
    2017-09-02 15:00:51: Starting printer threads ...
    2017-09-02 15:00:51: Starting printer thread for MTPrusaI3Mk21
    2017-09-02 15:00:51: Starting work dispatcher subsystem ...
    2017-09-02 15:00:51: Starting user database ...
    2017-09-02 15:00:51: Initalizing LUA ...
    2017-09-02 15:00:51: Starting wifi watcher ...
    2017-09-02 15:00:51: Register LUA cloud services
    2017-09-02 15:00:51: add Repetier-Renderer
    2017-09-02 15:00:51: LUA initalization finished.
    2017-09-02 15:00:51: Starting web server ...
    2017-09-02 15:00:51: Work dispatcher thread started.
    2017-09-02 15:00:51: Webserver started.
    2017-09-02 15:00:51: Updating info for /var/lib/Repetier-Server/printer/Robo3d/models/00000047_Links.g printer Robo3d
    2017-09-02 15:00:51: Start logging...
    2017-09-02 15:00:51: Imported external command Shutdown Server
    2017-09-02 15:00:51: Imported external command Reboot Server
    2017-09-02 15:00:51: Webdirectory: /usr/local/Repetier-Server/www/
    2017-09-02 15:00:51: Storage directory: /var/lib/Repetier-Server/
    2017-09-02 15:00:51: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2017-09-02 15:00:51: Directory for temporary files: /tmp/
    2017-09-02 15:00:51: Reading firmware data ...
    2017-09-02 15:00:51: Starting Network ...
    2017-09-02 15:00:51: Active features:4095
    2017-09-02 15:00:51: Reading printer configurations ...
    2017-09-02 15:00:51: Reading printer config /var/lib/Repetier-Server/configs/MTPrusaI3Mk21.xml
    2017-09-02 15:00:51: Starting printjob manager thread for MTPrusaI3Mk21
    2017-09-02 15:00:52: Starting printer threads ...
    2017-09-02 15:00:52: Starting printer thread for MTPrusaI3Mk21
    2017-09-02 15:00:52: Starting work dispatcher subsystem ...
    2017-09-02 15:00:52: Starting user database ...
    2017-09-02 15:00:52: Initalizing LUA ...
    2017-09-02 15:00:52: Starting wifi watcher ...
    2017-09-02 15:00:52: Register LUA cloud services
    2017-09-02 15:00:52: add Repetier-Renderer
    2017-09-02 15:00:52: LUA initalization finished.
    2017-09-02 15:00:52: Starting web server ...
    2017-09-02 15:00:52: Work dispatcher thread started.
    2017-09-02 15:00:52: Updating info for /var/lib/Repetier-Server/printer/Robo3d/models/00000047_Links.g printer Robo3d
  • maverickcciemaverickccie
    edited September 2017
    Just noticed that the last line of the log is looking for a printer I deleted. Looks like its a bug. The server may be stuck in a loop looking for the old printer!
  • RepetierRepetier
    Did you already test rebooting the pi?

    What I also see is that seem to have some reference to a Robo3d printer which is not configured. I guess that is the one you are talking about. You could check if the folder /var/lib/Repetier-Server/printer/Robo3d is still there. If not it is a stored job in workdispatcher that can not be fullfilled any more as the printer is not there any more. In that case shutdown repetier-server and delete 

    /var/lib/Repetier-Server/database/workdispatcher.sql

    and start again. Now it recreates that file but does not try to update that gcode any more.

  • maverickcciemaverickccie
    Repetier said:
    Did you already test rebooting the pi?

    What I also see is that seem to have some reference to a Robo3d printer which is not configured. I guess that is the one you are talking about. You could check if the folder /var/lib/Repetier-Server/printer/Robo3d is still there. If not it is a stored job in workdispatcher that can not be fullfilled any more as the printer is not there any more. In that case shutdown repetier-server and delete 

    /var/lib/Repetier-Server/database/workdispatcher.sql

    and start again. Now it recreates that file but does not try to update that gcode any more.

    I tried rebooting several times, does no good. Hod to just reload from scratch.
Sign In or Register to comment.