Web interface stops working


#1

What is the problem?
The web interface only work ~10% of the time, the rest of the time the web interface either isn't found or it only loads partially (404 on either the js files or both the js and css files). Once I'm able to connect and print something, the job persists perfectly fine

What did you already try to solve it?
I have tried restarting both the pi and the service through sudo service octoprint restart but it usually take several restarts for the interface to connect.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)
I'm not sure what version I have since I can't really connect, I installed the latest version of Octoprint about a month ago. Running on a Raspberry A+.

octoprint.log

...
|  hardware:
|    cores: 1
|    freq: 700.0
|    ram: 122912768
|  os:
|    id: linux
|    platform: linux2
|  plugins:
|    octopi_support:
|      model: A+
|      revision: '0012'
|      version: 0.14.0
|  python:
|    pip: 9.0.1
|    version: 2.7.9
|    virtualenv: /home/pi/oprint
2018-04-07 21:30:18,732 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/webassets...
2018-04-07 21:30:18,757 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/.webassets-cache...
2018-04-07 21:30:19,654 - octoprint.server - INFO - Shutting down intermediary server...
2018-04-07 21:30:19,871 - octoprint.server - INFO - Intermediary server shut down
2018-04-07 21:30:19,878 - octoprint.events - INFO - Processing startup event, this is our first event
2018-04-07 21:30:19,883 - octoprint.events - INFO - Adding 1 events to queue that were held back before startup event
2018-04-07 21:30:19,911 - octoprint.filemanager - INFO - Adding backlog items from all storage types to analysis queue...
2018-04-07 21:30:20,006 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2018-04-07 21:30:20,450 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on octopi for _http._tcp
2018-04-07 21:30:20,613 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on octopi for _octoprint._tcp
2018-04-07 21:30:20,651 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on octopi for SSDP
2018-04-07 21:30:20,672 - octoprint.server - INFO - Listening on http://127.0.0.1:5000
2018-04-07 21:30:21,111 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2018-04-07 21:30:21,788 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid
2018-04-07 21:30:22,463 - octoprint.server.preemptive_cache - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://octopi.local/'}
2018-04-07 21:30:23,208 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid
2018-04-07 21:30:33,247 - octoprint.filemanager - INFO - Added 0 items from storage type "local" to analysis queue
2018-04-07 21:31:26,389 - octoprint.server.preemptive_cache - INFO - ... done in 63.96s
2018-04-07 21:31:26,395 - octoprint.server.preemptive_cache - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://192.168.0.32/'}
2018-04-07 21:31:46,963 - octoprint.server.preemptive_cache - INFO - ... done in 20.57s

serial.log

2018-04-03 14:28:10,336 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log

I'm not sure what other info I can provide but I'm happy to try any debugging suggestions.


#2

Hi,

since yesterday I'm experiencing problems like yours, too.

Using Octopi nightly some weeks ago.
Installed all updates available via "apt-get update;apt-get upgrade"
Installed Octoprint 1.3.8 (latest available release)

It worked great some days after update to 1.3.8. But since yesterday I had it twice that after some time of printing the web interface and the webcam interface are not reachable anymore.

sudo service octoprint restart

Which I tried after the print was finished, did not solve the problem.
Additionally I tried to sudo service haproxy stop but this never finished. So I think the haproxy is the problem.

Only solution was a reboot.

In the ~/.octoprint/log/octoprint.log there was nothing about an incoming web request.

telnet octopi 80 got a connect but no more.
The browser only shows a rotating progress symbol.

Is this the same behaviour you have? Did you solve it yet?

I'm using Raspberry Pi 3 B+