Out of memory crash repetier-server on raspberry pi

fthome

Hello,

Repetier-server 0.90.7 on raspberry pi 3 (Raspian 9)

During a print, repetier-server was killed by the system and restarted with a "Out of memory: Kill process 680 (RepetierServer) score 867 or sacrifice child" log.

Logs :

/var/lib/Repetier-Server/logs/server.log

2018-10-23 18:07:52: start printjob 34505_manche +4 on printer HD

2018-10-23 18:07:53: LUA job rendering.render#{"id":8,"image":"/var/lib/Repetier-Server/printer/HD/jobs/00000008_34505_manche +4_l.png","layer":"/var/lib/Repetier-Server/printer/HD/jobs/00000008_34505_manche +4.layer","list":"jobs","slug":"HD"}

2018-10-23 18:09:15: Reading configuration file ...

Input file: /var/lib/Repetier-Server/printer/HD/jobs/00000008_34505_manche +4.layer

Rendering shadows ...10.6502 seconds.

Rendering gcode ...54.7037 seconds.

Number of end triangles: 275352

Number of normal triangles: 9381918

Rendering background ...

Time for raytracing: 15.0837 seconds.

images stored.

Computation time: 82.6972 seconds

2018-10-24 00:14:25: error:WifiManager::scanMode:System exception

2018-10-24 00:16:51: error:WifiManager::scanMode:System exception

2018-10-24 00:16:54: error:WifiManager::scanNetworks:System exception

2018-10-24 00:17:58: error:WifiManager::scanMode:System exception

2018-10-24 00:17:59: error:WifiManager::scanNetworks:System exception

2018-10-24 00:19:01: error:WifiManager::scanMode:System exception

2018-10-24 00:19:01: error:WifiManager::scanNetworks:System exception

2018-10-24 00:20:03: error:WifiManager::scanMode:System exception

2018-10-24 00:20:04: error:WifiManager::scanNetworks:System exception

2018-10-24 00:21:07: error:WifiManager::scanMode:System exception

2018-10-24 00:21:08: error:WifiManager::scanNetworks:System exception

2018-10-24 00:22:11: error:WifiManager::scanMode:System exception

2018-10-24 00:22:13: error:WifiManager::scanNetworks:System exception

2018-10-24 00:23:18: error:WifiManager::scanMode:System exception

2018-10-24 00:23:22: error:WifiManager::scanNetworks:System exception

2018-10-24 00:24:31: error:WifiManager::scanMode:System exception

2018-10-24 00:24:34: error:WifiManager::scanNetworks:System exception

2018-10-24 00:25:49: error:WifiManager::scanMode:System exception

2018-10-24 00:26:03: error:WifiManager::scanNetworks:System exception

2018-10-24 00:26:28: Start logging...

2018-10-24 00:26:28: Imported external command Shutdown Server

2018-10-24 00:26:28: Imported external command Reboot Server

.....

/var/log/syslog

Oct 24 00:17:16 Repetier-Server CRON[8933]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094270] usbhid-ups invoked oom-killer: gfp_mask=0x14000c0(GFP_KERNEL), nodemask=(null), order=0, oom_score_adj=0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094285] usbhid-ups cpuset=/ mems_allowed=0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094300] CPU: 2 PID: 814 Comm: usbhid-ups Tainted: G C 4.14.77-v7+ #1154

Oct 24 00:26:26 Repetier-Server kernel: [102028.094303] Hardware name: BCM2835

Oct 24 00:26:26 Repetier-Server kernel: [102028.094324] [<8010ff30>] (unwind_backtrace) from [<8010c174>] (show_stack+0x20/0x24)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094334] [<8010c174>] (show_stack) from [<80788e64>] (dump_stack+0xd4/0x118)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094346] [<80788e64>] (dump_stack) from [<802249e0>] (dump_header+0xac/0x208)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094356] [<802249e0>] (dump_header) from [<80223d48>] (oom_kill_process+0x478/0x584)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094364] [<80223d48>] (oom_kill_process) from [<802246a8>] (out_of_memory+0x124/0x334)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094374] [<802246a8>] (out_of_memory) from [<8022a180>] (alloc_pages_nodemask+0x1060/0x11d8)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094383] [<8022a180>] (__alloc_pages_nodemask) from [<8022a318>] (get_free_pages+0x20/0x6c)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094393] [<8022a318>] (__get_free_pages) from [<805c2be0>] (usbdev_ioctl+0xfb0/0x1ac8)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094404] [<805c2be0>] (usbdev_ioctl) from [<8029eab0>] (do_vfs_ioctl+0xac/0x7c4)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094412] [<8029eab0>] (do_vfs_ioctl) from [<8029f20c>] (SyS_ioctl+0x44/0x6c)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094421] [<8029f20c>] (SyS_ioctl) from [<80108000>] (ret_fast_syscall+0x0/0x28)

Oct 24 00:26:26 Repetier-Server kernel: [102028.094424] Mem-Info:

Oct 24 00:26:26 Repetier-Server kernel: [102028.094436] active_anon:107744 inactive_anon:107805 isolated_anon:0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094436] active_file:250 inactive_file:294 isolated_file:0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094436] unevictable:0 dirty:0 writeback:0 unstable:0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094436] slab_reclaimable:1824 slab_unreclaimable:5291

Oct 24 00:26:26 Repetier-Server kernel: [102028.094436] mapped:1421 shmem:2585 pagetables:955 bounce:0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094436] free:5169 free_pcp:2 free_cma:1271

Oct 24 00:26:26 Repetier-Server kernel: [102028.094444] Node 0 active_anon:430976kB inactive_anon:431220kB active_file:1000kB inactive_file:1176kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:5684kB dirty:0kB writeback:0kB shmem:10340kB writeback_tmp:0kB unstable:0kB all_unreclaimable? yes

Oct 24 00:26:26 Repetier-Server kernel: [102028.094456] Normal free:20676kB min:16384kB low:20480kB high:24576kB active_anon:430976kB inactive_anon:431220kB active_file:1040kB inactive_file:1396kB unevictable:0kB writepending:0kB present:970752kB managed:949448kB mlocked:0kB kernel_stack:1208kB pagetables:3820kB bounce:0kB free_pcp:8kB local_pcp:0kB free_cma:5084kB

Oct 24 00:26:26 Repetier-Server kernel: [102028.094458] lowmem_reserve[]: 0 0

Oct 24 00:26:26 Repetier-Server kernel: [102028.094466] Normal: 15004kB (UMEC) 2948kB (UMEC) 10316kB (UMEC) 2632kB (EC) 1264kB (UEC) 8128kB (UEC) 1256kB (U) 0512kB 21024kB (UE) 12048kB (U) 1*4096kB (C) = 21072kB

Oct 24 00:26:26 Repetier-Server kernel: [102028.094513] 3410 total pagecache pages

Oct 24 00:26:26 Repetier-Server kernel: [102028.094517] 234 pages in swap cache

Oct 24 00:26:26 Repetier-Server kernel: [102028.094521] Swap cache stats: add 27158, delete 26924, find 1712/3144

Oct 24 00:26:26 Repetier-Server kernel: [102028.094523] Free swap = 0kB

Oct 24 00:26:26 Repetier-Server kernel: [102028.094525] Total swap = 102396kB

Oct 24 00:26:26 Repetier-Server kernel: [102028.094529] 242688 pages RAM

Oct 24 00:26:26 Repetier-Server kernel: [102028.094531] 0 pages HighMem/MovableOnly

Oct 24 00:26:26 Repetier-Server kernel: [102028.094533] 5326 pages reserved

Oct 24 00:26:26 Repetier-Server kernel: [102028.094536] 2048 pages cma reserved

Oct 24 00:26:26 Repetier-Server kernel: [102028.094539] [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name

Oct 24 00:26:26 Repetier-Server kernel: [102028.094558] [ 90] 0 90 8779 1229 15 0 59 0 systemd-journal

Oct 24 00:26:26 Repetier-Server kernel: [102028.094564] [ 128] 0 128 3703 30 9 0 159 -1000 systemd-udevd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094571] [ 278] 100 278 4320 14 9 0 95 0 systemd-timesyn

Oct 24 00:26:26 Repetier-Server kernel: [102028.094577] [ 322] 0 322 1324 16 7 0 38 0 cron

Oct 24 00:26:26 Repetier-Server kernel: [102028.094583] [ 327] 0 327 13255 0 18 0 349 0 ModemManager

Oct 24 00:26:26 Repetier-Server kernel: [102028.094589] [ 330] 65534 330 1324 4 6 0 56 0 thd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094596] [ 333] 108 333 1634 47 7 0 68 0 avahi-daemon

Oct 24 00:26:26 Repetier-Server kernel: [102028.094601] [ 336] 0 336 5937 19 9 0 144 0 rsyslogd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094608] [ 342] 105 342 1659 80 7 0 74 -900 dbus-daemon

Oct 24 00:26:26 Repetier-Server kernel: [102028.094613] [ 359] 108 359 1601 5 5 0 72 0 avahi-daemon

Oct 24 00:26:26 Repetier-Server kernel: [102028.094620] [ 371] 0 371 25545 232 26 0 284 0 NetworkManager

Oct 24 00:26:26 Repetier-Server kernel: [102028.094625] [ 373] 0 373 1728 20 8 0 70 0 systemd-logind

Oct 24 00:26:26 Repetier-Server kernel: [102028.094631] [ 389] 0 389 9415 1 13 0 153 0 polkitd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094637] [ 429] 0 429 2418 59 8 0 88 0 wpa_supplicant

Oct 24 00:26:26 Repetier-Server kernel: [102028.094642] [ 430] 0 430 1661 2 8 0 179 0 dhclient

Oct 24 00:26:26 Repetier-Server kernel: [102028.094648] [ 448] 0 448 524 0 5 0 34 0 hciattach

Oct 24 00:26:26 Repetier-Server kernel: [102028.094655] [ 453] 0 453 1818 0 8 0 84 0 bluetoothd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094661] [ 613] 0 613 721 12 5 0 73 0 dhcpcd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094666] [ 635] 0 635 1049 0 7 0 35 0 agetty

Oct 24 00:26:26 Repetier-Server kernel: [102028.094673] [ 649] 0 649 2552 0 8 0 138 -1000 sshd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094678] [ 675] 0 675 11763 6 14 0 266 0 nginx

Oct 24 00:26:26 Repetier-Server kernel: [102028.094684] [ 676] 33 676 11797 2 15 0 308 0 nginx

Oct 24 00:26:26 Repetier-Server kernel: [102028.094690] [ 677] 33 677 11797 18 15 0 297 0 nginx

Oct 24 00:26:26 Repetier-Server kernel: [102028.094696] [ 678] 33 678 11797 18 15 0 297 0 nginx

Oct 24 00:26:26 Repetier-Server kernel: [102028.094701] [ 679] 33 679 11797 22 15 0 297 0 nginx

Oct 24 00:26:26 Repetier-Server kernel: [102028.094707] [ 680] 109 680 296805 211632 498 0 16085 0 RepetierServer

Oct 24 00:26:26 Repetier-Server kernel: [102028.094713] [ 681] 0 681 1266 0 6 0 55 0 repetier_ui.sh

Oct 24 00:26:26 Repetier-Server kernel: [102028.094719] [ 682] 0 682 2082 2 9 0 92 0 sudo

Oct 24 00:26:26 Repetier-Server kernel: [102028.094724] [ 686] 0 686 5964 27 12 0 1140 0 python

Oct 24 00:26:26 Repetier-Server kernel: [102028.094730] [ 687] 0 687 6620 51 16 0 296 0 nmbd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094736] [ 713] 0 713 10164 89 24 0 411 0 smbd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094742] [ 714] 0 714 9663 44 22 0 417 0 smbd-notifyd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094748] [ 715] 0 715 9661 43 21 0 417 0 cleanupd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094754] [ 717] 0 717 10166 84 24 0 397 0 lpqd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094760] [ 814] 111 814 668 25 6 0 41 0 usbhid-ups

Oct 24 00:26:26 Repetier-Server kernel: [102028.094766] [ 824] 111 824 1246 17 7 0 58 0 upsd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094772] [ 1402] 65534 1402 2308 22 9 0 71 0 dnsmasq

Oct 24 00:26:26 Repetier-Server kernel: [102028.094778] [28113] 0 28113 3761 69 12 0 175 0 cupsd

Oct 24 00:26:26 Repetier-Server kernel: [102028.094784] [28114] 0 28114 8824 0 16 0 242 0 cups-browsed

Oct 24 00:26:26 Repetier-Server kernel: [102028.094790] Out of memory: Kill process 680 (RepetierServer) score 867 or sacrifice child

Oct 24 00:26:26 Repetier-Server kernel: [102028.094868] Killed process 680 (RepetierServer) total-vm:1187220kB, anon-rss:846528kB, file-rss:0kB, shmem-rss:0kB

Oct 24 00:26:26 Repetier-Server kernel: [102028.333858] oom_reaper: reaped process 680 (RepetierServer), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

Oct 24 00:26:26 Repetier-Server systemd[1]: RepetierServer.service: Main process exited, code=killed, status=9/KILL

Oct 24 00:26:26 Repetier-Server systemd[1]: RepetierServer.service: Unit entered failed state.

Oct 24 00:26:26 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.

Oct 24 00:26:26 Repetier-Server systemd[1]: RepetierServer.service: Service has no hold-off time, scheduling restart.

Oct 24 00:26:26 Repetier-Server systemd[1]: Stopped Repetier-Server 3D Printer Server.

Oct 24 00:26:26 Repetier-Server systemd[1]: Starting Repetier-Server 3D Printer Server...

Oct 24 00:26:28 Repetier-Server systemd[1]: Started Repetier-Server 3D Printer Server.
...

Repetier

Anything special you did? Do you have a webcam or often wifi disconnects?
Normally the server is using maybe 20MB so either one action causes a memory leak under some conditions or you did something using much memory, also normally big tasks are done outside.

Was the server running for a long time already?

I ask just to find a hint when the problem exactly occurs so I get a chance to find it.

fthome

The webcam was disconnected.
The server was running for 2 or 3 days max.
The raspberry is connected to the lan by ethernet. The wifi (hotspot done by repetier) only manages two connected sockets.

top -H :

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

32014 pi 20 0 390936 98500 58552 S 5,6 10,4 0:15.72 chromium-browse

32531 pi 20 0 8384 3316 2696 R 2,6 0,3 0:00.31 top

9004 repetie+ 0 -20 329812 56200 15844 S 1,6 5,9 17:52.48 RepetierServer

9017 repetie+ 0 -20 329812 56200 15844 S 1,0 5,9 0:33.21 RepetierServer

29455 repetie+ 0 -20 329812 56200 15844 S 1,0 5,9 0:27.09 RepetierServer

28308 repetie+ 0 -20 329812 56200 15844 S 0,7 5,9 6:01.91 RepetierServer

28309 repetie+ 0 -20 329812 56200 15844 S 0,7 5,9 6:28.15 RepetierServer

30820 repetie+ 0 -20 329812 56200 15844 R 0,7 5,9 6:00.44 RepetierServer

24300 repetie+ 0 -20 329812 56200 15844 S 0,7 5,9 0:07.68 RepetierServer

32448 repetie+ 0 -20 329812 56200 15844 S 0,7 5,9 0:00.58 RepetierServer

68 root 20 0 0 0 0 S 0,3 0,0 0:33.28 mmcqd/0

226 root 20 0 0 0 0 S 0,3 0,0 0:17.59 brcmf_wdog/mmc1

371 root 20 0 102180 5556 4420 S 0,3 0,6 0:15.76 NetworkManager

415 root 20 0 102180 5556 4420 S 0,3 0,6 0:08.09 gdbus

814 nut 20 0 2672 100 0 S 0,3 0,0 11:37.72 usbhid-ups

9003 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 1:17.08 RepetierServer

9006 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 0:26.61 RepetierServer

28307 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 6:11.90 RepetierServer

28310 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 2:12.27 RepetierServer

28311 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 6:35.14 RepetierServer

24302 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 0:15.00 RepetierServer

29503 repetie+ 0 -20 329812 56200 15844 S 0,3 5,9 0:07.14 RepetierServer

31829 pi 20 0 591976 123036 103352 S 0,3 13,0 0:01.09 Chrome_IOThread

I see a process "chromium-browser" is-it normal? Why a local browser ?

Repetier

The chromium browser is used for the touchscreen on your pi. If you have none, you should disable it. If you use latest image see here:
https://www.repetier-server.com/knowledgebase/prepare-for-prusa-mk3-on-raspberry-pi-zerow-rambo-einsy-board/<br/>on how to disable it. Otherwise edit /home/pi/.bashrc at end you see

if ! pgrep "xinit" > /dev/null then sudo chmod 660 /dev/tty* xinit -- -nocursor 2> /dev/null > /dev/null & fi
The xinit line is starting xserver with chromium. Put a # in front to comment it and reboot.

Memory usage seems to differ a lot.
13 days up, some prints on a pi zero (512MB):

630 repetie+ 0 -20 193304 27444 16068 S 0.3 6.2 39:51.20 RepetierServer 4 days up multiple printers Pi3, 1GB:

1108 repetie+ 0 -20 280192 21120 13512 S 0.3 2.2 4:43.45 RepetierServer
For clearance - virtual memory is not what is used. RES or MEM% is what the software actively is using. VIRST includes shared memory and shared libraries. Also all threads use the same memory so it is not 15 * RES in your case.Speaking of threads I see 15. My pi zero no external connections has 9. Each connection adds one thread and each printer 2 more threads. Do you have several printers connected? Would at least explain you are using 56MB RAM.One thing I can think of is that one communication thread does not close when connection is closed (e.g. browser closed, pc shut down). If it still stores missing data to send it would at some point use the memory. But all connections have a timeout so that is not happening as fas as I can see.Will keep an eye on this.

fthome

Ok, I disable xserver

I have only 1 printer + 1 web connection + websockets to send gcode when I push physical buttons on the rapsberry (for extracting/pushing filament or pause/cancel print job).
I will check if websocket connection are closed. But when the server crash, no buttons was pushed.

Thanks a lot.

Repetier

So you have a program watching pi pins and sending commands. Can you post it so I can see if that can cause a problem. Just for sending a command on button push a websocket is a bit overkill. Here a simple api call would be more then enough.

fthome

https://github.com/fthome/repetier_ui<br/><br/><blockquote class="Quote">

Repetier said:

fthome

This night, I did a test :
after a new boot, a send a print and every hour I send a "free -m" to a file.
21:00 : 60MB used
22:00 : 66MB used
23:00 : 71MB used
00:00 : 150 MB used
01:00 : 250 MB used
02:00 : 338 MB used
03:00 : 353 MB used
04:00 : 354 MB used
05:00 : 354 MB used
06:00 : 354 MB used
07:00 : 355 MB used
08:00 : 361 MB used

It is the processus Repetier-Server who use the memory

During this period I've just print a job :

/var/lib/Repetier-Server/logs/server.log

2018-10-25 20:11:06: Starting web server ...

2018-10-25 20:11:06: Webserver started.

2018-10-25 20:11:07: Connection started: HD

2018-10-25 20:11:07: Reset printer HD

2018-10-25 20:11:08: New SSID Not Connected

2018-10-25 20:13:48: Activating access point

2018-10-25 20:15:28: Job created: /var/lib/Repetier-Server/printer/HD/jobs/00000001_couvercle +3.u

2018-10-25 20:15:28: finish job /var/lib/Repetier-Server/printer/HD/jobs/00000001_couvercle +3.u

2018-10-25 20:15:29: Updating info for /var/lib/Repetier-Server/printer/HD/jobs/00000001_couvercle +3.g printer HD

2018-10-25 20:15:34: Starting external command /usr/bin/python with 2 parameters.

2018-10-25 20:15:34: start printjob couvercle +3 on printer HD

2018-10-25 20:15:35: LUA job rendering.render#{"id":1,"image":"/var/lib/Repetier-Server/printer/HD/jobs/00000001_couvercle +3_l.png","layer":"/var/lib/Repetier-Server/printer/HD/jobs/00000001_couvercle +3.layer","list":"jobs","slug":"HD"}

2018-10-25 20:17:16: Reading configuration file ...

Input file: /var/lib/Repetier-Server/printer/HD/jobs/00000001_couvercle +3.layer

Rendering shadows ...7.49591 seconds.

Rendering gcode ...76.8074 seconds.

Number of end triangles: 174888

Number of normal triangles: 4682176

Rendering background ...

Time for raytracing: 14.5921 seconds.

images stored.

Computation time: 101.199 seconds

2018-10-26 02:14:44: Starting external command /usr/bin/python with 2 parameters.

2018-10-26 02:21:51: Starting external command /usr/bin/python with 2 parameters.

2018-10-26 02:21:55: Starting external command /usr/bin/python with 2 parameters.

2018-10-26 02:21:55: Print of couvercle +3 on printer HD finished. Send 301236 lines. Printing time: 6:06:20

2018-10-26 02:21:55: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2018-10-26 02:22:02: error: Reading serial conection failed: End of file. Closing connection.

2018-10-26 02:22:02: Port closed for HD

2018-10-26 02:22:02: Connection closed: HD

2018-10-26 08:05:02: Starting external command /usr/bin/python with 2 parameters.

2018-10-26 08:06:33: Connection started: HD

2018-10-26 08:06:33: Reset printer HD

2018-10-26 08:20:55: Job created: /var/lib/Repetier-Server/printer/HD/jobs/00000002_support_aiguille.u

2018-10-26 08:20:55: finish job /var/lib/Repetier-Server/printer/HD/jobs/00000002_support_aiguille.u

2018-10-26 08:20:55: Updating info for /var/lib/Repetier-Server/printer/HD/jobs/00000002_support_aiguille.g printer HD

2018-10-26 08:20:56: Starting external command /usr/bin/python with 2 parameters.

2018-10-26 08:20:56: start printjob support_aiguille on printer HD

2018-10-26 08:20:56: LUA job rendering.render#{"id":2,"image":"/var/lib/Repetier-Server/printer/HD/jobs/00000002_support_aiguille_l.png","layer":"/var/lib/Repetier-Server/printer/HD/jobs/00000002_support_aiguille.layer","list":"jobs","slug":"HD"}

2018-10-26 08:22:08: Reading configuration file ...

Input file: /var/lib/Repetier-Server/printer/HD/jobs/00000002_support_aiguille.layer

Rendering shadows ...3.50161 seconds.

Rendering gcode ...51.6429 seconds.

Number of end triangles: 36672

Number of normal triangles: 905560

Rendering background ...

Time for raytracing: 14.0504 seconds.

images stored.

Computation time: 71.3678 seconds

the external command is "python set_ifttt.py CMD" (https://github.com/fthome/repetier_ui)

For the moment my solution is rebooting the raspberry pi every day.

Repetier

Ok, will try the same tomorrow. I would prefer more logging

ps aux | grep tierfree is over all programs.

Can you also try in parallel if this happens if your command is not running. Just to exclude that this is causing the problem. After all I know users running prints much longer without memory issues. So first step should be to find what is triggering the error.

fthome

I monitor the memory usage with ps aux | grep epetier and note the memory usage of Repetier-server

pi@Repetier-Server:~ $ ps aux | grep tier

avahi 317 0.0 0.2 6536 2820 ? Ss 13:48 0:00 avahi-daemon: running [Repetier-Server.local]

repetie+ 674 3.0 2.7 189844 25776 ? S<sl 13:48 5:29 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

root 675 0.0 0.2 5064 2828 ? Ss 13:48 0:00 /bin/bash /home/pi/repetier_ui/repetier_ui.sh

pi 9438 0.0 0.0 4372 560 pts/0 S+ 16:49 0:00 grep --color=auto tier

repetier_ui is my script.
abstract :
from websocket import create_connection
datas = {'action': 'send', 'data': {'cmd': gcode},'printer':printer}

try:

ws = create_connection(self.url, header=self.header)

ws.send(json.dumps(datas))

except Exception as e:

logging.error("WebsocketError: %s"%(err.message))

finally:

ws.close

if repetier_ui is disable, the memory usage is stable
if repetier_ui is enable, the memory usage increase 4 hours after I use my code

If websocket is the problem, can you tell me how to use the api to send gcode to the printer.

the mesures :

Mémoire repetier server 29/10/2018 18:00 73160 repetier_ui inactif 29/10/2018 19:00 73204 29/10/2018 20:00 73204 29/10/2018 21:00 73204 29/10/2018 22:00 73204 29/10/2018 23:00 73204 30/10/2018 00:00 73204 30/10/2018 01:00 73204 30/10/2018 02:00 73204 30/10/2018 03:00 73204 30/10/2018 04:00 73204 30/10/2018 05:00 73204 30/10/2018 06:00 73204 30/10/2018 07:00 73224 30/10/2018 08:00 73224 Mise en route repetier_ui et utilisation 1 fois : 2018-10-30 08:00:38,538 - INFO - GPIO10 FALLING => GCODE : goto_z_max.gcode send to HD.
2018-10-30 08:00:47,181 - INFO - GPIO10 FALLING => GCODE : goto_z_max.gcode send to HD. 30/10/2018 09:00 73252 30/10/2018 10:00 73252 30/10/2018 11:00 73252 30/10/2018 12:00 151584 30/10/2018 13:00 246436 30/10/2018 14:00 18092 reboot serveur 30/10/2018 15:00 22400 30/10/2018 16:00 24268

Repetier

Ok here my test results in parallel:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND

Start

repetie+ 589 4.7 6.1 193304 27444 ? S<sl Oct11 1157:29 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

1h Print

repetie+ 589 4.7 6.3 219256 28256 ? S<sl Oct11 1171:48 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

1h Print

repetie+ 589 4.8 6.8 270456 30444 ? S<sl Oct11 1184:00 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

5h Print

repetie+ 589 5.0 8.6 278092 38604 ? S<sl Oct11 1297:45 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

total used free shared buff/cache available

Mem: 433 100 30 22 302 260

Swap: 99 2 97

8h print

after 1h

repetie+ 589 5.0 7.6 223820 33744 ? S<sl Oct11 1321:47 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

pi@Prusa:~ $ free -m

total used free shared buff/cache available

Mem: 433 102 34 22 296 257

Swap: 99 2 97

repetie+ 589 5.1 8.3 259820 37256 ? S<sl Oct11 1339:21 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

repetie+ 589 5.1 9.5 225004 42576 ? S<sl Oct11 1362:09 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

repetie+ 589 5.2 10.2 228076 45628 ? S<sl Oct11 1376:59 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

repetie+ 589 5.2 10.2 228076 45628 ? S<sl Oct11 1380:57 /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon

So after 15 hours it increased to 45MB memory usage.
I could debug my memory increase and it is a result of the lua interpreter having not run garbage collector. Not sure when it would decide to run, so for next release I have now forced a garbage collection after every call. That may take in total more time but each collection is tiny and still quick I guess. Need to do some more tests.

Communication over websockets might also cause lua calls as that is how normal users could extend the server side to add new functions. But only if the command is not known by the c++ part, so normally not the problem.

I will try to make a websocket tester that runs many websocket reconnects. Maybe there is a memory issue as well. If I have understoo dthe cod ecorrectly you establish for each test a websocket so a problem there could easily increase faster the memory usage.

Using it as simple api call would be better here, see
https://www.repetier-server.com/manuals/programming/API/index.html<br/><br/><h3>User websocket commands directly</h3>In the websocket chapter you will see all the small commands you normally use while you are displaying server status. Soem of them might also be useful for simple apps just wanting to show some informations. For these we offer a access over the REST api. The only thing that does not work are events as they are reported to open sockets only.

http://localhost:3344/printer/api/&lt;slug&gt;?a=&lt;websocket command&gt;&amp;data=&lt;json object properly url-escaped&gt;&amp;apikey=&lt;API key&gt;&gt;

The above schema can be used to send any websocket command as REST call. Use GET or POST just as you like. For bigger data POSt should be preferred. You can replace apikey with sess, but you would normally do this only if you have no session open, so apikey is the normal way to use it.

So essentially you the query you send as url encoded data in data and you get the same json response.

fthome

Ok, I will forget websocket.

But i do not establish a lot of websocket connections : this morning, I just make two short connections.

Thanks a lot

Repetier

Can you test with htop - there you see how much threads the server has. It should stay constant if connection is closed.
Yesterday I trie dusing a browser and reloaded it 50 times without noticeable memory increase. I know it closes connection and leakage tool did not find memory leakage, so in general websockets should not be a problem. But if they keep open it might be a different think.