[BUG?] Server is offline locally. Fine on LAN. Print sometimes finishes, sometime frozes too

Get Help
1

Extension of what I thought it was issue 2647, I started documenting weird behaviours here:
#2647 (comment)

HOWEVER today, I arrived at the farm and one of the Prusas was reporting SERVER OFFLINE locally, but I was able to access it thru the LAN from another computer. The print was going on.

https://user-images.githubusercontent.com/10992914/153563852-60cb8f6b-4c72-4c0a-b540-8fcd2626ff68.jpg(image larger than 4 MB)

https://user-images.githubusercontent.com/10992914/153563863-b1a153da-e9a7-4a2e-96bc-e6209ce7ba8e.jpg(image larger than 4 MB)

My issue now is that I actually updated buck converters to 5A and this particular printer was NOT complaining of undervoltage, while one of its neighbours is (and completed print fine and still operative so far).

HENCE what I report is that for UNKNOWN reasons, I went from a fully working farm using Octopi 0.16/Python2 to a random hangs Octopi 0.18/Python 3 and Octoprint 1.7.3

I'm really puzzled now as the hardware is essentially the same, SDs were wiped and put a fresh image of Octopi 0.18, basically using any plugins other than stock, TouchUI and Excluderegion and I get this weird behaviour!

I ask for HELP!

Did the issue persist even in safe mode?

I cannot test this issue in safe mode (state why below)

If you could not test in safe mode, please state why

Live farm environment, haven't had the time to test in safe mode.

Version of OctoPrint

1.7.3

Operating system running OctoPrint

OctoPi 0.18

Printer model & used firmware incl. version

Prusa MK3S+

Browser and version of browser, operating system running browser

Chrome 98 on MacOS BigSur. Issues locally with TouchUI though

Checklist of files to include below

  • Systeminfo Bundle (always include!)
  • Contents of the JavaScript browser console (always include in cases of issues with the user interface)
  • Screenshots and/or videos showing the problem (always include in case of issues with the user interface)
  • GCODE file with which to reproduce (always include in case of issues with GCODE analysis or printing behaviour)

Additional information & file uploads

Terminal shows normal printer temp "pings".

SSH to the Pi server is terribly slow.

octoprint-systeminfo-20220211101012.zip

octoprint-logs (1).zip

Top shows this:

top - 10:09:26 up 1 day, 1:08, 1 user, load average: 10.70, 11.01, 9.15
Tasks: 147 total, 1 running, 146 sleeping, 0 stopped, 0 zombie
%Cpu(s): 1.6 us, 5.6 sy, 0.0 ni, 1.4 id, 91.1 wa, 0.0 hi, 0.4 si, 0.0 st
MiB Mem : 871.7 total, 23.8 free, 740.5 used, 107.3 buff/cache
MiB Swap: 100.0 total, 0.0 free, 100.0 used. 19.5 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
65 root 20 0 0 0 0 S 8.7 0.0 11:33.91 kswapd0
434 pi 20 0 307500 54252 3152 D 5.2 6.1 205:57.38 octoprint
11114 root 0 -20 0 0 0 D 3.0 0.0 1:40.75 kworker/0:2H+kblockd
852 pi 20 0 585712 17720 3996 D 1.4 2.0 8:01.07 chromium-browse
1008 pi 20 0 298020 11628 3960 S 1.4 1.3 2:10.47 chromium-browse
1083 pi 20 0 1067480 612304 1932 D 1.1 68.6 1006:06 chromium-browse
22078 pi 20 0 10400 1920 1256 R 1.1 0.2 0:00.14 top
14362 root 20 0 52032 10392 2320 D 0.8 1.2 2:30.47 apt-get
11 root 20 0 0 0 0 S 0.5 0.0 0:30.53 ksoftirqd/0
125 root 20 0 40584 3504 3040 S 0.5 0.4 8:08.49 systemd-journal
382 root 20 0 25512 940 44 S 0.5 0.1 2:28.15 rsyslogd
506 root 20 0 10968 368 128 S 0.5 0.0 1:03.36 wpa_supplicant
21690 root 0 -20 0 0 0 I 0.5 0.0 0:02.15 kworker/0:1H-kblockd
21815 root 20 0 0 0 0 I 0.5 0.0 0:00.40 kworker/0:0-events
22106 root 20 0 3764 1640 1456 D 0.5 0.2 0:00.02 mjpg_streamer
1 root 20 0 33812 1700 584 S 0.3 0.2 10:12.23 systemd
12 root 20 0 0 0 0 I 0.3 0.0 1:15.51 rcu_sched
707 haproxy 20 0 16080 2940 1848 S 0.3 0.3 1:01.20 haproxy
1058 pi 20 0 270980 2748 0 S 0.3 0.3 0:02.04 chromium-browse
22077 root 20 0 7808 1272 1020 D 0.3 0.1 0:00.09 webcamd

So whatever it is, it hogs the server until exthenuation and either kills the serial connection (sometimes!) or ends correctly.

2

Hi

Your swap is at 100% usage and it looks like chromium is eating all your memory.

That's not an OctoPrint bug - the heavy stuff you're running locally (e.g. the browser - which was never recommended anyway) is the issue.

3

OK, WHICH heavy stuff? The only one using chromium is TouchUI and I was already using it on the previous set up. Once again, SAME hardware. Only Pi0.18/Python 3 upgrade.

@BillyBlaze any clues what could be going on here?

4

You updated to a newer OS which means that everything inside that OS has been updated - including the chromium browser.
The chromium browser was always heavy and used a lot of memory compared to other browsers.

It's like updating from Windows 7 to Windows 10. Some things that barely worked before might not work anymore with the new OS version.

I can't tell you what exactly changed - my guess is that the browser has become more complex.

You should check out other projects like OctoDash or OctoScreen.

5

sigh :cry: :sob:

6

Well this is the dawn of a new era... Farewell TouchUI! Good morning OctoDash!

This is from an ongoing print run by OctoPrint+OctoDash:

top - 22:46:32 up 57 min, 2 users, load average: 0.39, 0.38, 0.37
Tasks: 140 total, 1 running, 139 sleeping, 0 stopped, 0 zombie
%Cpu(s): 8.4 us, 3.5 sy, 0.0 ni, 88.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 871.7 total, 149.8 free, 217.9 used, 503.9 buff/cache
MiB Swap: 100.0 total, 100.0 free, 0.0 used. 549.9 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
404 pi 20 0 302472 63512 10644 S 23.0 7.1 15:13.69 octoprint
1089 pi 20 0 322024 104064 75960 S 3.3 11.7 1:00.07 octodash
8092 root 20 0 7808 2796 2544 S 1.6 0.3 0:00.05 webcamd
1 root 20 0 33720 7952 6308 S 1.0 0.9 0:37.07 systemd
117 root 20 0 40592 9300 8380 S 1.0 1.0 0:22.67 systemd-journal
1117 pi 20 0 217008 57808 44468 S 1.0 6.5 0:11.72 octodash
7724 pi 20 0 10396 3176 2576 R 1.0 0.4 0:00.36 top
887 pi 20 0 581716 132884 91960 S 0.7 14.9 0:20.09 octodash
12 root 20 0 0 0 0 I 0.3 0.0 0:02.72 rcu_sched
383 message+ 20 0 6556 3484 3008 S 0.3 0.4 0:13.58 dbus-daemon
390 root 20 0 25512 2852 2464 S 0.3 0.3 0:06.30 rsyslogd
833 root 20 0 193788 39616 28212 S 0.3 4.4 0:01.77 Xorg
1482 root 20 0 0 0 0 I 0.3 0.0 0:00.52 kworker/u8:2-events_unbound
7679 pi 20 0 12204 3476 2684 S 0.3 0.4 0:00.04 sshd

Superb CPU load never seen before with TouchUI around! Whatever has happened with chromium, has sentenced TouchUI to death :frowning:

At least I've recovered control of the farm re: cpu loads. We'll see if problem is gone in a week's time!

Thanks forum!

7

You're welcome :slight_smile:

Btw you should check out htop - it's a lot easier to read than top.

Happy printing :octopus:

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.