Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Message in log "ma-start: no restart flag found, not restarting MA"
-
Hi,
I have small problem with mango, from time to time it stops to respond. After correlation of dates in watchlist and ma-script.log, I found that it happens when in ma-script.log occure messages:śro, 8 lut 2017, 03:18:24 CET ma-start: no restart flag found, not restarting MA śro, 8 lut 2017, 03:18:24 CET ma-start: MA doneI don't know why it happens? After that I have to restart mango application. Please help. Best regards.
-
Hi przemom,
The ma-script.log file should only have the output from the Mango/bin scripts in it, which will not tell you why Mango has shut down. For that, you should be looking in your ma.log file. A likely candidate could be that you have the brewersdashboard module installed, which without a license will shut down Mango in 8 hours. An unlicensed NoSQL module will do likewise.
-
Hi,
Mango restarts are due to out of the memory...after restar I noticed in syslog:Normal free:11516kB min:3836kB low:4792kB high:5752kB active_anon:272132kB inactive_anon:334892kB active_file:158044kB inactive_file:109544kB unevictable:2264kB isolated(anon):128kB isolated(file):0kB present:966656kB managed:942128kB mlocked:2264kB dirty:0kB writeback:296kB mapped:42120kB shmem:4856kB slab_reclaimable:16536kB slab_unreclaimable:17068kB kernel_stack:3088kB pagetables:3896kB unstable:0kB bounce:0kB free_pcp:96kB local_pcp:0kB free_cma:28kB writeback_tmp:0kB pages_scanned:708 all_unreclaimable? no [1316838.230279] lowmem_reserve[]: 0 0 [1316838.230300] Normal: 1245*4kB (UME) 828*8kB (UME) 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 11604kB [1316838.230377] 88560 total pagecache pages [1316838.230395] 20168 pages in swap cache [1316838.230407] Swap cache stats: add 12675710, delete 12655542, find 13533006/17454463 [1316838.230418] Free swap = 1621416kB [1316838.230427] Total swap = 2097148kB [1316838.230438] 241664 pages RAM [1316838.230448] 0 pages HighMem/MovableOnly [1316838.230457] 6132 pages reserved [1316838.230467] 2048 pages cma reserved [1316838.230477] [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name [1316838.230539] [ 436] 0 436 1285 599 7 0 37 0 systemd-journal [1316838.230563] [ 466] 0 466 5172 98 6 0 0 0 lvmetad [1316838.230587] [ 505] 0 505 2968 314 8 0 96 -1000 systemd-udevd [1316838.230608] [ 714] 100 714 3064 314 7 0 43 0 systemd-timesyn [1316838.230628] [ 1020] 0 1020 471 19 5 0 0 0 iscsid [1316838.230651] [ 1021] 0 1021 586 531 5 0 0 -17 iscsid [1316838.230673] [ 1027] 104 1027 7794 471 10 0 77 0 rsyslogd [1316838.230696] [ 1030] 107 1030 1303 526 6 0 91 -900 dbus-daemon [1316838.230721] [ 1036] 0 1036 9464 607 12 0 94 0 accounts-daemon [1316838.230742] [ 1041] 0 1041 712 265 6 0 26 0 atd [1316838.230765] [ 1045] 0 1045 1540 314 7 0 31 0 cron [1316838.230785] [ 1051] 0 1051 965 417 6 0 174 0 systemd-logind [1316838.230806] [ 1059] 0 1059 1997 486 8 0 105 -1000 sshd [1316838.230829] [ 1061] 0 1061 9831 243 12 0 21 0 lxcfs [1316838.230848] [ 1070] 0 1070 346 208 4 0 0 0 acpid [1316838.230868] [ 1118] 0 1118 1901 372 9 0 0 0 su [1316838.230888] [ 1119] 0 1119 1901 377 9 0 6 0 su [1316838.230909] [ 1136] 0 1136 8710 458 13 0 60 0 polkitd [1316838.230929] [ 1203] 8 1203 779 323 5 0 7 0 nullmailer-send [1316838.230951] [ 1242] 0 1242 832 300 6 0 17 0 irqbalance [1316838.230971] [ 1246] 1001 1246 1614 389 7 0 430 0 systemd [1316838.230995] [ 1256] 1001 1256 1859 9 7 0 463 0 (sd-pam) [1316838.231015] [ 1277] 0 1277 1272 252 6 0 0 0 agetty [1316838.231035] [ 1278] 0 1278 1012 203 7 0 0 0 agetty [1316838.231055] [ 1286] 0 1286 1509 816 6 0 0 0 systemd [1316838.231084] [ 1289] 0 1289 1859 67 7 0 405 0 (sd-pam) [1316838.231105] [ 1301] 1001 1301 1756 678 7 0 29 0 modbuspoll.sh [1316838.231126] [ 1309] 0 1309 1521 297 7 0 88 0 mysqld_safe [1316838.231147] [ 1312] 1001 1312 341 254 4 0 8 0 autossh [1316838.231167] [ 1346] 0 1346 4481 867 8 0 0 0 rpiShutdown.py [1316838.231190] [ 1630] 0 1630 36544 32367 74 0 1307 0 landscape-clien [1316838.231210] [ 1635] 112 1635 34461 8799 59 0 12656 0 landscape-broke [1316838.231231] [ 1636] 112 1636 27416 19685 55 0 512 0 landscape-monit [1316838.231252] [ 1637] 0 1637 23030 3417 49 0 16374 0 landscape-manag [1316838.231274] [ 1693] 1001 1693 341 253 4 0 8 0 autossh [1316838.231294] [ 1878] 1001 1878 341 257 5 0 5 0 autossh [1316838.231316] [20894] 0 20894 552 265 5 0 16 0 mdadm [1316838.231337] [18724] 114 18724 151608 4448 145 0 41850 0 mysqld [1316838.231359] [18725] 0 18725 1705 99 8 0 45 0 logger [1316838.231381] [17485] 115 17485 1426 280 7 0 93 0 karaf [1316838.231402] [17640] 115 17640 113220 29810 156 0 24123 0 java [1316838.231423] [14474] 1001 14474 1499 741 8 0 88 0 ssh [1316838.231444] [15728] 1001 15728 1468 718 7 0 94 0 ssh [1316838.231464] [15749] 1001 15749 1468 744 8 0 91 0 ssh [1316838.231489] [15943] 0 15943 1490 550 7 0 0 0 ma-start.sh [1316838.231509] [15950] 0 15950 112695 53658 129 0 0 0 java [1316838.231530] [16202] 1001 16202 4647 3288 12 0 0 0 epmmodbuscontro [1316838.231553] [16203] 1001 16203 1159 80 7 0 0 0 sleep [1316838.231574] [16216] 0 16216 2945 1128 9 0 0 0 sshd [1316838.231594] [16219] 0 16219 630 184 5 0 0 0 systemd-cgroups [1316838.231612] Out of memory: Kill process 17640 (java) score 71 or sacrifice child [1316838.247650] Killed process 17640 (java) total-vm:452880kB, anon-rss:114704kB, file-rss:4536kBMy platform: Raspberry Pi 2,
Kernel: Linux rpi2pm 4.4.0-1046-raspi2 #53-Ubuntu SMP Sun Mar 5 13:25:01 UTC 2017 armv7l armv7l armv7l GNU/Linux
Time between restarts is rather random. It can be from a few minutes to sevral hours.
Best regards. -
Hi przemom,
Interesting! Some questions,
- Are you running two instances of Mango? If not, what's the other java process? It looks like it killed PID 17640 but I don't see that as being Mango, since ma-start and 15950 java belong to uid 0.
- Are you using any ext-enabled scripts to set the heap? I think the OS OOM-Killer should only be active if the system as a whole is starved for memory, which means you can probably set the -Xmx (max heap memory) to prevent Java from expanding its heap too large and aggravating the OS. Looks like your RPi has a gig of memory. Depending on what that other Java is doing, I would think you should try a static heap of half the available memory, so move
memory-small.shfrom Mango/bin/ext-available to ext-enabled and set them to-Xmx500m -Xms500mthen restart Mango. With a limited heap, Mango shouldn't use all the systems' memory and thus shouldn't be killed by the OOM-Killer
-
My RPI is a testing machine, so I test mango and openhab. I added memory-small.sh with changes You suggested. Tomorrow I will let You know if it help. Thanks
