reef-pi :: An opensource reef tank controller based on Raspberry Pi.

[bishoptf]

Playing with the 2.0 temperature controller for past few days. Here is my pico tank;'s temperature chart, where the temperature controller is set at with larger threshold than than the heater. As a result, heater's internal thermostat is switching hetar on/off while the equipment is always on from reef-pi side, temperature controller is acting as failsafe only, in case things go south then will switch off heater and send alert.

The nano tank is setup in opposite way. With heater itself configured at bit higher setting (80) and reef-pi configured at 79.5, with 30 seconds interval. I am playing with 79.4. 79.3 after few hours to see the effect. Notice heater/cooler graph is now showing heater usage (as it is being turned on/off by reef-pi itself)

my realizations was pretty exciting. reef-pi switching on/off heater almost half the time when run at 60s interval. I get much finer control but it comes at a cost of switching heater on/off more frequently.
I am thinking of adding support for hysteresis and setpoints. Though this whole scheme work for heater, its not useful for chillers (and do they come without thermostat ?? ). I wanted to share this, as it will be really interesting to see how these graphs look after i implement hysteresis /setpoint based logic

Well I was looking on my phone at the dashboard and it kind of reset my graphs, I went from information like you to this now:

I have not rebooted since its linux and should not have to be rebooted but not sure what is going on, my memory usage was climbing but thats normal for linux since it will use whats available, I will go check the logs and see if I can see what may have happened.

Looked at the logs the only thing I see is this -
ERROR:Failed to get controller temperature. Error: fork/exec /usr/bin/vcgencmd: cannot allocate memory

Updates looks like I found the issue:

Jan 19 16:37:27 tankpi kernel: INFO: task kworker/0:0:1177 blocked for more than 120 seconds.
Jan 19 16:37:27 tankpi kernel: Not tainted 4.14.79-v7+ #1159
Jan 19 16:37:27 tankpi kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 19 16:37:27 tankpi kernel: kworker/0:0 D 0 1177 2 0x00000000
Jan 19 16:37:27 tankpi kernel: Workqueue: events_freezable mmc_rescan
Jan 19 16:37:27 tankpi kernel: [<8079ef70>] (__schedule) from [<8079f5d8>] (schedule+0x50/0xa8)
Jan 19 16:37:27 tankpi kernel: [<8079f5d8>] (schedule) from [<8061a2d0>] (__mmc_claim_host+0xb8/0x1cc)
Jan 19 16:37:27 tankpi kernel: [<8061a2d0>] (__mmc_claim_host) from [<8061a414>] (mmc_get_card+0x30/0x34)
Jan 19 16:37:27 tankpi kernel: [<8061a414>] (mmc_get_card) from [<80623010>] (mmc_sd_detect+0x20/0x74)
Jan 19 16:37:27 tankpi kernel: [<80623010>] (mmc_sd_detect) from [<8061ccdc>] (mmc_rescan+0x1c8/0x394)
Jan 19 16:37:27 tankpi kernel: [<8061ccdc>] (mmc_rescan) from [<801379b4>] (process_one_work+0x158/0x454)
Jan 19 16:37:27 tankpi kernel: [<801379b4>] (process_one_work) from [<80137d14>] (worker_thread+0x64/0x5b8)
Jan 19 16:37:27 tankpi kernel: [<80137d14>] (worker_thread) from [<8013dd98>] (kthread+0x13c/0x16c)
Jan 19 16:37:27 tankpi kernel: [<8013dd98>] (kthread) from [<801080ac>] (ret_from_fork+0x14/0x28)
Jan 19 16:37:27 tankpi kernel: reef-pi invoked oom-killer: gfp_mask=0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null), order=0, oom_score_adj=0
Jan 19 16:37:27 tankpi kernel: reef-pi cpuset=/ mems_allowed=0
Jan 19 16:37:27 tankpi kernel: CPU: 0 PID: 6629 Comm: reef-pi Not tainted 4.14.79-v7+ #1159
Jan 19 16:37:27 tankpi kernel: Hardware name: BCM2835
Jan 19 16:37:27 tankpi kernel: [<8010ff30>] (unwind_backtrace) from [<8010c174>] (show_stack+0x20/0x24)
Jan 19 16:37:27 tankpi kernel: [<8010c174>] (show_stack) from [<80788fa4>] (dump_stack+0xd4/0x118)
Jan 19 16:37:27 tankpi kernel: [<80788fa4>] (dump_stack) from [<802249ec>] (dump_header+0xac/0x208)
Jan 19 16:37:27 tankpi kernel: [<802249ec>] (dump_header) from [<80223d54>] (oom_kill_process+0x478/0x584)
Jan 19 16:37:27 tankpi kernel: [<80223d54>] (oom_kill_process) from [<802246b4>] (out_of_memory+0x124/0x334)
Jan 19 16:37:27 tankpi kernel: [<802246b4>] (out_of_memory) from [<8022a18c>] (__alloc_pages_nodemask+0x1060/0x11d8)
Jan 19 16:37:27 tankpi kernel: [<8022a18c>] (__alloc_pages_nodemask) from [<80220578>] (filemap_fault+0x558/0x694)
Jan 19 16:37:27 tankpi kernel: [<80220578>] (filemap_fault) from [<8033fef4>] (ext4_filemap_fault+0x38/0x4c)
Jan 19 16:37:27 tankpi kernel: [<8033fef4>] (ext4_filemap_fault) from [<80255fb0>] (__do_fault+0x28/0x78)
Jan 19 16:37:27 tankpi kernel: [<80255fb0>] (__do_fault) from [<80259c18>] (handle_mm_fault+0x4d4/0xc20)
Jan 19 16:37:27 tankpi kernel: [<80259c18>] (handle_mm_fault) from [<807a564c>] (do_page_fault+0x330/0x3a4)
Jan 19 16:37:27 tankpi kernel: [<807a564c>] (do_page_fault) from [<801012a0>] (do_PrefetchAbort+0x44/0xa8)
Jan 19 16:37:27 tankpi kernel: [<801012a0>] (do_PrefetchAbort) from [<807a50e4>] (ret_from_exception+0x0/0x1c)
Jan 19 16:37:27 tankpi kernel: Exception stack(0x850cdfb0 to 0x850cdff8)
Jan 19 16:37:27 tankpi kernel: dfa0: 2a1f3b34 00000007 00000040 00000040
Jan 19 16:37:27 tankpi kernel: dfc0: 00000007 00000036 00000007 2aa4d93c 2a1f3b36 00000009 11665ce0 2aa4d93e
Jan 19 16:37:27 tankpi kernel: dfe0: 00000038 2aa4d9b0 000782c4 0029b684 60000010 ffffffff
Jan 19 16:37:27 tankpi kernel: Mem-Info:
Jan 19 16:37:27 tankpi kernel: active_anon:49467 inactive_anon:49491 isolated_anon:0
active_file:318 inactive_file:303 isolated_file:32
unevictable:0 dirty:0 writeback:15 unstable:0
slab_reclaimable:1473 slab_unreclaimable:2416
mapped:410 shmem:204 pagetables:389 bounce:0
free:4068 free_pcp:163 free_cma:116
Jan 19 16:37:27 tankpi kernel: Node 0 active_anon:197868kB inactive_anon:197964kB active_file:1272kB inactive_file:1212kB unevictable:0kB isolated(anon):0kB isolated(file):128kB mapped:1640kB dirt
Jan 19 16:37:27 tankpi kernel: Normal free:16272kB min:16384kB low:20480kB high:24576kB active_anon:197884kB inactive_anon:197964kB active_file:1088kB inactive_file:1636kB unevictable:0kB writepen
Jan 19 16:37:27 tankpi kernel: lowmem_reserve[]: 0 0
Jan 19 16:37:27 tankpi kernel: Normal: 273*4kB (UMEHC) 253*8kB (UMEHC) 86*16kB (UMEHC) 24*32kB (MEH) 17*64kB (MEH) 8*128kB (UMEH) 7*256kB (UMEH) 2*512kB (U) 0*1024kB 3*2048kB (UME) 0*4096kB = 1633
Jan 19 16:37:27 tankpi kernel: 897 total pagecache pages
Jan 19 16:37:27 tankpi kernel: 6 pages in swap cache
Jan 19 16:37:27 tankpi kernel: Swap cache stats: add 92893, delete 92887, find 36218/71415
Jan 19 16:37:27 tankpi kernel: Free swap = 0kB
Jan 19 16:37:27 tankpi kernel: Total swap = 102396kB
Jan 19 16:37:27 tankpi kernel: 114688 pages RAM
Jan 19 16:37:27 tankpi kernel: 0 pages HighMem/MovableOnly
Jan 19 16:37:27 tankpi kernel: 4103 pages reserved
Jan 19 16:37:27 tankpi kernel: 2048 pages cma reserved
Jan 19 16:37:27 tankpi kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
Jan 19 16:37:27 tankpi kernel: [ 99] 0 99 7195 99 13 0 74 0 systemd-journal
Jan 19 16:37:27 tankpi kernel: [ 124] 0 124 3585 15 7 0 151 -1000 systemd-udevd
Jan 19 16:37:27 tankpi kernel: [ 241] 100 241 4320 15 10 0 96 0 systemd-timesyn
Jan 19 16:37:27 tankpi kernel: [ 280] 0 280 5937 70 10 0 207 0 rsyslogd
Jan 19 16:37:27 tankpi kernel: [ 282] 65534 282 1324 4 7 0 56 0 thd
Jan 19 16:37:27 tankpi kernel: [ 284] 0 284 1324 15 7 0 41 0 cron
Jan 19 16:37:27 tankpi kernel: [ 287] 108 287 1640 56 7 0 69 0 avahi-daemon
Jan 19 16:37:27 tankpi kernel: [ 288] 0 288 1853 20 7 0 84 0 systemd-logind
Jan 19 16:37:27 tankpi kernel: [ 292] 105 292 1623 2 7 0 105 -900 dbus-daemon
Jan 19 16:37:27 tankpi kernel: [ 296] 108 296 1601 0 7 0 77 0 avahi-daemon
Jan 19 16:37:27 tankpi kernel: [ 428] 0 428 2534 32 9 0 107 0 wpa_supplicant
Jan 19 16:37:27 tankpi kernel: [ 460] 0 460 524 0 4 0 34 0 hciattach
Jan 19 16:37:27 tankpi kernel: [ 466] 0 466 1769 0 7 0 76 0 bluetoothd
Jan 19 16:37:27 tankpi kernel: [ 524] 0 524 721 28 7 0 56 0 dhcpcd
Jan 19 16:37:27 tankpi kernel: [ 536] 0 536 1049 0 6 0 35 0 agetty
Jan 19 16:37:27 tankpi kernel: [ 540] 0 540 2553 0 9 0 138 -1000 sshd
Jan 19 16:37:27 tankpi kernel: [ 5969] 0 5969 201711 98153 240 0 18660 0 reef-pi
Jan 19 16:37:27 tankpi kernel: [ 1678] 0 1678 475 38 5 0 0 0 dhcpcd-run-hook
Jan 19 16:37:27 tankpi kernel: [ 1681] 0 1681 475 31 5 0 0 0 resolvconf
Jan 19 16:37:27 tankpi kernel: [ 1682] 0 1682 673 24 5 0 0 0 mkdir
Jan 19 16:37:27 tankpi kernel: Out of memory: Kill process 5969 (reef-pi) score 833 or sacrifice child
Jan 19 16:37:27 tankpi kernel: Killed process 5969 (reef-pi) total-vm:806844kB, anon-rss:392612kB, file-rss:0kB, shmem-rss:0kB
Jan 19 16:37:27 tankpi kernel: oom_reaper: reaped process 5969 (reef-pi), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Jan 19 16:37:27 tankpi reef-pi[5969]: 2019/01/19 16:34:57 temperature sub-system: sensor Temp3-2.5g value: 77.9
Jan 19 16:35:23 tankpi dhcpcd[524]: wlan0: fe80::21f:29ff:fe5a:17aa: router expired
Jan 19 16:35:24 tankpi dhcpcd[524]: wlan0: deleting default route via fe80::21f:29ff:fe5a:17aa
Jan 19 16:37:27 tankpi systemd[1]: reef-pi.service: Main process exited, code=killed, status=9/KILL
Jan 19 16:37:27 tankpi systemd[1]: reef-pi.service: Unit entered failed state.
Jan 19 16:37:27 tankpi systemd[1]: reef-pi.service: Failed with result 'signal'.
Jan 19 16:37:27 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:27 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:27 tankpi dhcpcd[524]: wlan0: adding default route via fe80::21f:29ff:fe5a:17aa
Jan 19 16:37:28 tankpi systemd[1]: Starting Daily apt download activities...
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:31 tankpi systemd[1]: Started Daily apt download activities.
Jan 19 16:37:31 tankpi systemd[1]: apt-daily.timer: Adding 1h 32min 6.685914s random time.
Jan 19 16:37:31 tankpi systemd[1]: apt-daily.timer: Adding 6h 34min 57.228675s random time.
Jan 19 16:37:37 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:37 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:53 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:53 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:04 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:04 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:22 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:22 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:27 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:27 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:34 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:34 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:46 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:46 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:58 tankpi systemd[1]: reef-pi.service: Service hold-off time over, scheduling restart.
Jan 19 16:38:58 tankpi systemd[1]: Stopped raspberry pi based reef tank controller.
Jan 19 16:38:58 tankpi systemd[1]: Started raspberry pi based reef tank controller.
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: macro
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: system
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 27 State: 1
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 22 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 23 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 24 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 25 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 5 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 6 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 12 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 INFO: equipment subsystem: Finished syncing all equipment
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: equipment
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully added cron entry. ID: 1
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully added cron entry. ID: 2
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: timers
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: ato
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 ERROR: temperature subsystem. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 ERROR: temperature subsystem. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 ERROR: temperature subsystem. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:38:59 tankpi reef-pi[2023]: 2019/01/19 16:38:59 ERROR: health checker. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:39:00 tankpi reef-pi[2023]: 2019/01/19 16:39:00 ERROR: stats for id: '1' not found
Jan 19 16:39:00 tankpi reef-pi[2023]: 2019/01/19 16:39:00 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:01 tankpi reef-pi[2023]: 2019/01/19 16:39:01 ERROR: stats for id: '1' not found
Jan 19 16:39:01 tankpi reef-pi[2023]: 2019/01/19 16:39:01 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:03 tankpi reef-pi[2023]: 2019/01/19 16:39:03 ERROR: stats for id: '2' not found
Jan 19 16:39:03 tankpi reef-pi[2023]: 2019/01/19 16:39:03 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:04 tankpi reef-pi[2023]: 2019/01/19 16:39:04 ERROR: stats for id: '2' not found
Jan 19 16:39:04 tankpi reef-pi[2023]: 2019/01/19 16:39:04 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:06 tankpi reef-pi[2023]: 2019/01/19 16:39:06 ERROR: stats for id: '3' not found
Jan 19 16:39:06 tankpi reef-pi[2023]: 2019/01/19 16:39:06 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:07 tankpi reef-pi[2023]: 2019/01/19 16:39:07 ERROR: stats for id: '3' not found
Jan 19 16:39:07 tankpi reef-pi[2023]: 2019/01/19 16:39:07 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:10 tankpi reef-pi[2023]: 2019/01/19 16:39:10 ERROR: stats for id: '1' not found
Jan 19 16:39:10 tankpi reef-pi[2023]: 2019/01/19 16:39:10 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:11 tankpi reef-pi[2023]: 2019/01/19 16:39:11 ERROR: stats for id: '1' not found
Jan 19 16:39:11 tankpi reef-pi[2023]: 2019/01/19 16:39:11 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:13 tankpi reef-pi[2023]: 2019/01/19 16:39:13 ERROR: stats for id: '2' not found
Jan 19 16:39:13 tankpi reef-pi[2023]: 2019/01/19 16:39:13 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:15 tankpi reef-pi[2023]: 2019/01/19 16:39:15 ERROR: stats for id: '2' not found
Jan 19 16:39:15 tankpi reef-pi[2023]: 2019/01/19 16:39:15 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:16 tankpi reef-pi[2023]: 2019/01/19 16:39:16 ERROR: stats for id: '3' not found
Jan 19 16:39:16 tankpi reef-pi[2023]: 2019/01/19 16:39:16 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:17 tankpi reef-pi[2023]: 2019/01/19 16:39:17 ERROR: stats for id: '3' not found
Jan 19 16:39:17 tankpi reef-pi[2023]: 2019/01/19 16:39:17 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:20 tankpi reef-pi[2023]: 2019/01/19 16:39:20 ERROR: stats for id: '1' not found
Jan 19 16:39:20 tankpi reef-pi[2023]: 2019/01/19 16:39:20 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:21 tankpi reef-pi[2023]: 2019/01/19 16:39:21 ERROR: stats for id: '1' not found
Jan 19 16:39:21 tankpi reef-pi[2023]: 2019/01/19 16:39:21 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:23 tankpi reef-pi[2023]: 2019/01/19 16:39:23 ERROR: stats for id: '2' not found
Jan 19 16:39:23 tankpi reef-pi[2023]: 2019/01/19 16:39:23 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:24 tankpi reef-pi[2023]: 2019/01/19 16:39:24 ERROR: stats for id: '2' not found
Jan 19 16:39:24 tankpi reef-pi[2023]: 2019/01/19 16:39:24 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:26 tankpi reef-pi[2023]: 2019/01/19 16:39:26 ERROR: stats for id: '3' not found
Jan 19 16:39:26 tankpi reef-pi[2023]: 2019/01/19 16:39:26 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:27 tankpi reef-pi[2023]: 2019/01/19 16:39:27 ERROR: stats for id: '3' not found
Jan 19 16:39:27 tankpi reef-pi[2023]: 2019/01/19 16:39:27 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:30 tankpi reef-pi[2023]: 2019/01/19 16:39:30 ERROR: stats for id: '1' not found
Jan 19 16:39:30 tankpi reef-pi[2023]: 2019/01/19 16:39:30 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:31 tankpi reef-pi[2023]: 2019/01/19 16:39:31 ERROR: stats for id: '1' not found
Jan 19 16:39:31 tankpi reef-pi[2023]: 2019/01/19 16:39:31 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:33 tankpi reef-pi[2023]: 2019/01/19 16:39:33 ERROR: stats for id: '2' not found
Jan 19 16:39:33 tankpi reef-pi[2023]: 2019/01/19 16:39:33 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:35 tankpi reef-pi[2023]: 2019/01/19 16:39:35 ERROR: stats for id: '2' not found
Jan 19 16:39:35 tankpi reef-pi[2023]: 2019/01/19 16:39:35 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:36 tankpi reef-pi[2023]: 2019/01/19 16:39:36 ERROR: stats for id: '3' not found
Jan 19 16:39:36 tankpi reef-pi[2023]: 2019/01/19 16:39:36 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:37 tankpi reef-pi[2023]: 2019/01/19 16:39:37 ERROR: stats for id: '3' not found
Jan 19 16:39:37 tankpi reef-pi[2023]: 2019/01/19 16:39:37 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:40 tankpi reef-pi[2023]: 2019/01/19 16:39:40 ERROR: stats for id: '1' not found
Jan 19 16:39:40 tankpi reef-pi[2023]: 2019/01/19 16:39:40 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:41 tankpi reef-pi[2023]: 2019/01/19 16:39:41 ERROR: stats for id: '1' not found
Jan 19 16:39:41 tankpi reef-pi[2023]: 2019/01/19 16:39:41 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:44 tankpi reef-pi[2023]: 2019/01/19 16:39:44 ERROR: stats for id: '2' not found
Jan 19 16:39:44 tankpi reef-pi[2023]: 2019/01/19 16:39:44 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:45 tankpi reef-pi[2023]: 2019/01/19 16:39:45 ERROR: stats for id: '2' not found
Jan 19 16:39:45 tankpi reef-pi[2023]: 2019/01/19 16:39:45 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:46 tankpi reef-pi[2023]: 2019/01/19 16:39:46 ERROR: stats for id: '3' not found
Jan 19 16:39:46 tankpi reef-pi[2023]: 2019/01/19 16:39:46 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:47 tankpi reef-pi[2023]: 2019/01/19 16:39:47 ERROR: stats for id: '3' not found
Jan 19 16:39:47 tankpi reef-pi[2023]: 2019/01/19 16:39:47 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:50 tankpi reef-pi[2023]: 2019/01/19 16:39:50 ERROR: stats for id: '1' not found
Jan 19 16:39:50 tankpi reef-pi[2023]: 2019/01/19 16:39:50 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:51 tankpi reef-pi[2023]: 2019/01/19 16:39:51 ERROR: stats for id: '1' not found
Jan 19 16:39:51 tankpi reef-pi[2023]: 2019/01/19 16:39:51 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:53 tankpi reef-pi[2023]: 2019/01/19 16:39:53 ERROR: stats for id: '2' not found
Jan 19 16:39:53 tankpi reef-pi[2023]: 2019/01/19 16:39:53 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:55 tankpi reef-pi[2023]: 2019/01/19 16:39:55 ERROR: stats for id: '2' not found
Jan 19 16:39:55 tankpi reef-pi[2023]: 2019/01/19 16:39:55 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:56 tankpi reef-pi[2023]: 2019/01/19 16:39:56 ERROR: stats for id: '3' not found
Jan 19 16:39:56 tankpi reef-pi[2023]: 2019/01/19 16:39:56 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:58 tankpi reef-pi[2023]: 2019/01/19 16:39:58 ERROR: stats for id: '3' not found
Jan 19 16:39:58 tankpi reef-pi[2023]: 2019/01/19 16:39:58 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:55:57 tankpi reef-pi[2023]: 2019/01/19 16:55:57 ERROR: Failed to reload reef-pi. Output:. Error: signal: terminated
Jan 19 16:55:57 tankpi reef-pi[2023]: 2019/01/19 16:55:57 ERROR: GET /api/admin/reload Failed to reload reef-pi. Output:. Error: signal: terminated
​

Looks memory related as it ran out of memory, do I need to increase swap? Running on a raspberry pi 3 A+, looks very similar to ryan115 issue, I am running the stable image but have not updated to the latest fixes.

Let me know if you need any additional information.​

 

[DirtDiggler2823]

I have seen this on reef builders youtube channel, as macna coverage. I just read through the blog. Its not available yet. Any idea on pricing or api etc?

At least 1k for now

 

[Ranjib]

Well I was looking on my phone at the dashboard and it kind of reset my graphs, I went from information like you to this now:

I have not rebooted since its linux and should not have to be rebooted but not sure what is going on, my memory usage was climbing but thats normal for linux since it will use whats available, I will go check the logs and see if I can see what may have happened.

Looked at the logs the only thing I see is this -
ERROR:Failed to get controller temperature. Error: fork/exec /usr/bin/vcgencmd: cannot allocate memory

Updates looks like I found the issue:

Jan 19 16:37:27 tankpi kernel: INFO: task kworker/0:0:1177 blocked for more than 120 seconds.
Jan 19 16:37:27 tankpi kernel: Not tainted 4.14.79-v7+ #1159
Jan 19 16:37:27 tankpi kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 19 16:37:27 tankpi kernel: kworker/0:0 D 0 1177 2 0x00000000
Jan 19 16:37:27 tankpi kernel: Workqueue: events_freezable mmc_rescan
Jan 19 16:37:27 tankpi kernel: [<8079ef70>] (__schedule) from [<8079f5d8>] (schedule+0x50/0xa8)
Jan 19 16:37:27 tankpi kernel: [<8079f5d8>] (schedule) from [<8061a2d0>] (__mmc_claim_host+0xb8/0x1cc)
Jan 19 16:37:27 tankpi kernel: [<8061a2d0>] (__mmc_claim_host) from [<8061a414>] (mmc_get_card+0x30/0x34)
Jan 19 16:37:27 tankpi kernel: [<8061a414>] (mmc_get_card) from [<80623010>] (mmc_sd_detect+0x20/0x74)
Jan 19 16:37:27 tankpi kernel: [<80623010>] (mmc_sd_detect) from [<8061ccdc>] (mmc_rescan+0x1c8/0x394)
Jan 19 16:37:27 tankpi kernel: [<8061ccdc>] (mmc_rescan) from [<801379b4>] (process_one_work+0x158/0x454)
Jan 19 16:37:27 tankpi kernel: [<801379b4>] (process_one_work) from [<80137d14>] (worker_thread+0x64/0x5b8)
Jan 19 16:37:27 tankpi kernel: [<80137d14>] (worker_thread) from [<8013dd98>] (kthread+0x13c/0x16c)
Jan 19 16:37:27 tankpi kernel: [<8013dd98>] (kthread) from [<801080ac>] (ret_from_fork+0x14/0x28)
Jan 19 16:37:27 tankpi kernel: reef-pi invoked oom-killer: gfp_mask=0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null), order=0, oom_score_adj=0
Jan 19 16:37:27 tankpi kernel: reef-pi cpuset=/ mems_allowed=0
Jan 19 16:37:27 tankpi kernel: CPU: 0 PID: 6629 Comm: reef-pi Not tainted 4.14.79-v7+ #1159
Jan 19 16:37:27 tankpi kernel: Hardware name: BCM2835
Jan 19 16:37:27 tankpi kernel: [<8010ff30>] (unwind_backtrace) from [<8010c174>] (show_stack+0x20/0x24)
Jan 19 16:37:27 tankpi kernel: [<8010c174>] (show_stack) from [<80788fa4>] (dump_stack+0xd4/0x118)
Jan 19 16:37:27 tankpi kernel: [<80788fa4>] (dump_stack) from [<802249ec>] (dump_header+0xac/0x208)
Jan 19 16:37:27 tankpi kernel: [<802249ec>] (dump_header) from [<80223d54>] (oom_kill_process+0x478/0x584)
Jan 19 16:37:27 tankpi kernel: [<80223d54>] (oom_kill_process) from [<802246b4>] (out_of_memory+0x124/0x334)
Jan 19 16:37:27 tankpi kernel: [<802246b4>] (out_of_memory) from [<8022a18c>] (__alloc_pages_nodemask+0x1060/0x11d8)
Jan 19 16:37:27 tankpi kernel: [<8022a18c>] (__alloc_pages_nodemask) from [<80220578>] (filemap_fault+0x558/0x694)
Jan 19 16:37:27 tankpi kernel: [<80220578>] (filemap_fault) from [<8033fef4>] (ext4_filemap_fault+0x38/0x4c)
Jan 19 16:37:27 tankpi kernel: [<8033fef4>] (ext4_filemap_fault) from [<80255fb0>] (__do_fault+0x28/0x78)
Jan 19 16:37:27 tankpi kernel: [<80255fb0>] (__do_fault) from [<80259c18>] (handle_mm_fault+0x4d4/0xc20)
Jan 19 16:37:27 tankpi kernel: [<80259c18>] (handle_mm_fault) from [<807a564c>] (do_page_fault+0x330/0x3a4)
Jan 19 16:37:27 tankpi kernel: [<807a564c>] (do_page_fault) from [<801012a0>] (do_PrefetchAbort+0x44/0xa8)
Jan 19 16:37:27 tankpi kernel: [<801012a0>] (do_PrefetchAbort) from [<807a50e4>] (ret_from_exception+0x0/0x1c)
Jan 19 16:37:27 tankpi kernel: Exception stack(0x850cdfb0 to 0x850cdff8)
Jan 19 16:37:27 tankpi kernel: dfa0: 2a1f3b34 00000007 00000040 00000040
Jan 19 16:37:27 tankpi kernel: dfc0: 00000007 00000036 00000007 2aa4d93c 2a1f3b36 00000009 11665ce0 2aa4d93e
Jan 19 16:37:27 tankpi kernel: dfe0: 00000038 2aa4d9b0 000782c4 0029b684 60000010 ffffffff
Jan 19 16:37:27 tankpi kernel: Mem-Info:
Jan 19 16:37:27 tankpi kernel: active_anon:49467 inactive_anon:49491 isolated_anon:0
active_file:318 inactive_file:303 isolated_file:32
unevictable:0 dirty:0 writeback:15 unstable:0
slab_reclaimable:1473 slab_unreclaimable:2416
mapped:410 shmem:204 pagetables:389 bounce:0
free:4068 free_pcp:163 free_cma:116
Jan 19 16:37:27 tankpi kernel: Node 0 active_anon:197868kB inactive_anon:197964kB active_file:1272kB inactive_file:1212kB unevictable:0kB isolated(anon):0kB isolated(file):128kB mapped:1640kB dirt
Jan 19 16:37:27 tankpi kernel: Normal free:16272kB min:16384kB low:20480kB high:24576kB active_anon:197884kB inactive_anon:197964kB active_file:1088kB inactive_file:1636kB unevictable:0kB writepen
Jan 19 16:37:27 tankpi kernel: lowmem_reserve[]: 0 0
Jan 19 16:37:27 tankpi kernel: Normal: 273*4kB (UMEHC) 253*8kB (UMEHC) 86*16kB (UMEHC) 24*32kB (MEH) 17*64kB (MEH) 8*128kB (UMEH) 7*256kB (UMEH) 2*512kB (U) 0*1024kB 3*2048kB (UME) 0*4096kB = 1633
Jan 19 16:37:27 tankpi kernel: 897 total pagecache pages
Jan 19 16:37:27 tankpi kernel: 6 pages in swap cache
Jan 19 16:37:27 tankpi kernel: Swap cache stats: add 92893, delete 92887, find 36218/71415
Jan 19 16:37:27 tankpi kernel: Free swap = 0kB
Jan 19 16:37:27 tankpi kernel: Total swap = 102396kB
Jan 19 16:37:27 tankpi kernel: 114688 pages RAM
Jan 19 16:37:27 tankpi kernel: 0 pages HighMem/MovableOnly
Jan 19 16:37:27 tankpi kernel: 4103 pages reserved
Jan 19 16:37:27 tankpi kernel: 2048 pages cma reserved
Jan 19 16:37:27 tankpi kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
Jan 19 16:37:27 tankpi kernel: [ 99] 0 99 7195 99 13 0 74 0 systemd-journal
Jan 19 16:37:27 tankpi kernel: [ 124] 0 124 3585 15 7 0 151 -1000 systemd-udevd
Jan 19 16:37:27 tankpi kernel: [ 241] 100 241 4320 15 10 0 96 0 systemd-timesyn
Jan 19 16:37:27 tankpi kernel: [ 280] 0 280 5937 70 10 0 207 0 rsyslogd
Jan 19 16:37:27 tankpi kernel: [ 282] 65534 282 1324 4 7 0 56 0 thd
Jan 19 16:37:27 tankpi kernel: [ 284] 0 284 1324 15 7 0 41 0 cron
Jan 19 16:37:27 tankpi kernel: [ 287] 108 287 1640 56 7 0 69 0 avahi-daemon
Jan 19 16:37:27 tankpi kernel: [ 288] 0 288 1853 20 7 0 84 0 systemd-logind
Jan 19 16:37:27 tankpi kernel: [ 292] 105 292 1623 2 7 0 105 -900 dbus-daemon
Jan 19 16:37:27 tankpi kernel: [ 296] 108 296 1601 0 7 0 77 0 avahi-daemon
Jan 19 16:37:27 tankpi kernel: [ 428] 0 428 2534 32 9 0 107 0 wpa_supplicant
Jan 19 16:37:27 tankpi kernel: [ 460] 0 460 524 0 4 0 34 0 hciattach
Jan 19 16:37:27 tankpi kernel: [ 466] 0 466 1769 0 7 0 76 0 bluetoothd
Jan 19 16:37:27 tankpi kernel: [ 524] 0 524 721 28 7 0 56 0 dhcpcd
Jan 19 16:37:27 tankpi kernel: [ 536] 0 536 1049 0 6 0 35 0 agetty
Jan 19 16:37:27 tankpi kernel: [ 540] 0 540 2553 0 9 0 138 -1000 sshd
Jan 19 16:37:27 tankpi kernel: [ 5969] 0 5969 201711 98153 240 0 18660 0 reef-pi
Jan 19 16:37:27 tankpi kernel: [ 1678] 0 1678 475 38 5 0 0 0 dhcpcd-run-hook
Jan 19 16:37:27 tankpi kernel: [ 1681] 0 1681 475 31 5 0 0 0 resolvconf
Jan 19 16:37:27 tankpi kernel: [ 1682] 0 1682 673 24 5 0 0 0 mkdir
Jan 19 16:37:27 tankpi kernel: Out of memory: Kill process 5969 (reef-pi) score 833 or sacrifice child
Jan 19 16:37:27 tankpi kernel: Killed process 5969 (reef-pi) total-vm:806844kB, anon-rss:392612kB, file-rss:0kB, shmem-rss:0kB
Jan 19 16:37:27 tankpi kernel: oom_reaper: reaped process 5969 (reef-pi), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Jan 19 16:37:27 tankpi reef-pi[5969]: 2019/01/19 16:34:57 temperature sub-system: sensor Temp3-2.5g value: 77.9
Jan 19 16:35:23 tankpi dhcpcd[524]: wlan0: fe80::21f:29ff:fe5a:17aa: router expired
Jan 19 16:35:24 tankpi dhcpcd[524]: wlan0: deleting default route via fe80::21f:29ff:fe5a:17aa
Jan 19 16:37:27 tankpi systemd[1]: reef-pi.service: Main process exited, code=killed, status=9/KILL
Jan 19 16:37:27 tankpi systemd[1]: reef-pi.service: Unit entered failed state.
Jan 19 16:37:27 tankpi systemd[1]: reef-pi.service: Failed with result 'signal'.
Jan 19 16:37:27 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:27 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:27 tankpi dhcpcd[524]: wlan0: adding default route via fe80::21f:29ff:fe5a:17aa
Jan 19 16:37:28 tankpi systemd[1]: Starting Daily apt download activities...
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:28 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:28 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:31 tankpi systemd[1]: Started Daily apt download activities.
Jan 19 16:37:31 tankpi systemd[1]: apt-daily.timer: Adding 1h 32min 6.685914s random time.
Jan 19 16:37:31 tankpi systemd[1]: apt-daily.timer: Adding 6h 34min 57.228675s random time.
Jan 19 16:37:37 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:37 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:37:53 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:37:53 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:04 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:04 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:22 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:22 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:27 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:27 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:34 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:34 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:46 tankpi dhcpcd[524]: wlan0: adding address 2001:470:7c:4ef:3f5f:fb0d:5a08:4bc7/66
Jan 19 16:38:46 tankpi dhcpcd[524]: if_addaddress6: Invalid argument
Jan 19 16:38:58 tankpi systemd[1]: reef-pi.service: Service hold-off time over, scheduling restart.
Jan 19 16:38:58 tankpi systemd[1]: Stopped raspberry pi based reef tank controller.
Jan 19 16:38:58 tankpi systemd[1]: Started raspberry pi based reef tank controller.
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: macro
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: system
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 27 State: 1
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 22 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 23 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 24 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 25 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 5 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 6 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Setting GPIO Pin: 12 State: 0
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 INFO: equipment subsystem: Finished syncing all equipment
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: equipment
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully added cron entry. ID: 1
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully added cron entry. ID: 2
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: timers
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 Successfully started subsystem: ato
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 ERROR: temperature subsystem. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 ERROR: temperature subsystem. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:38:58 tankpi reef-pi[2023]: 2019/01/19 16:38:58 ERROR: temperature subsystem. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:38:59 tankpi reef-pi[2023]: 2019/01/19 16:38:59 ERROR: health checker. Failed to load usage. Error: json: cannot unmarshal object into Go struct field StatsOnDisk.current of type []json.RawMessage
Jan 19 16:39:00 tankpi reef-pi[2023]: 2019/01/19 16:39:00 ERROR: stats for id: '1' not found
Jan 19 16:39:00 tankpi reef-pi[2023]: 2019/01/19 16:39:00 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:01 tankpi reef-pi[2023]: 2019/01/19 16:39:01 ERROR: stats for id: '1' not found
Jan 19 16:39:01 tankpi reef-pi[2023]: 2019/01/19 16:39:01 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:03 tankpi reef-pi[2023]: 2019/01/19 16:39:03 ERROR: stats for id: '2' not found
Jan 19 16:39:03 tankpi reef-pi[2023]: 2019/01/19 16:39:03 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:04 tankpi reef-pi[2023]: 2019/01/19 16:39:04 ERROR: stats for id: '2' not found
Jan 19 16:39:04 tankpi reef-pi[2023]: 2019/01/19 16:39:04 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:06 tankpi reef-pi[2023]: 2019/01/19 16:39:06 ERROR: stats for id: '3' not found
Jan 19 16:39:06 tankpi reef-pi[2023]: 2019/01/19 16:39:06 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:07 tankpi reef-pi[2023]: 2019/01/19 16:39:07 ERROR: stats for id: '3' not found
Jan 19 16:39:07 tankpi reef-pi[2023]: 2019/01/19 16:39:07 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:10 tankpi reef-pi[2023]: 2019/01/19 16:39:10 ERROR: stats for id: '1' not found
Jan 19 16:39:10 tankpi reef-pi[2023]: 2019/01/19 16:39:10 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:11 tankpi reef-pi[2023]: 2019/01/19 16:39:11 ERROR: stats for id: '1' not found
Jan 19 16:39:11 tankpi reef-pi[2023]: 2019/01/19 16:39:11 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:13 tankpi reef-pi[2023]: 2019/01/19 16:39:13 ERROR: stats for id: '2' not found
Jan 19 16:39:13 tankpi reef-pi[2023]: 2019/01/19 16:39:13 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:15 tankpi reef-pi[2023]: 2019/01/19 16:39:15 ERROR: stats for id: '2' not found
Jan 19 16:39:15 tankpi reef-pi[2023]: 2019/01/19 16:39:15 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:16 tankpi reef-pi[2023]: 2019/01/19 16:39:16 ERROR: stats for id: '3' not found
Jan 19 16:39:16 tankpi reef-pi[2023]: 2019/01/19 16:39:16 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:17 tankpi reef-pi[2023]: 2019/01/19 16:39:17 ERROR: stats for id: '3' not found
Jan 19 16:39:17 tankpi reef-pi[2023]: 2019/01/19 16:39:17 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:20 tankpi reef-pi[2023]: 2019/01/19 16:39:20 ERROR: stats for id: '1' not found
Jan 19 16:39:20 tankpi reef-pi[2023]: 2019/01/19 16:39:20 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:21 tankpi reef-pi[2023]: 2019/01/19 16:39:21 ERROR: stats for id: '1' not found
Jan 19 16:39:21 tankpi reef-pi[2023]: 2019/01/19 16:39:21 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:23 tankpi reef-pi[2023]: 2019/01/19 16:39:23 ERROR: stats for id: '2' not found
Jan 19 16:39:23 tankpi reef-pi[2023]: 2019/01/19 16:39:23 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:24 tankpi reef-pi[2023]: 2019/01/19 16:39:24 ERROR: stats for id: '2' not found
Jan 19 16:39:24 tankpi reef-pi[2023]: 2019/01/19 16:39:24 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:26 tankpi reef-pi[2023]: 2019/01/19 16:39:26 ERROR: stats for id: '3' not found
Jan 19 16:39:26 tankpi reef-pi[2023]: 2019/01/19 16:39:26 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:27 tankpi reef-pi[2023]: 2019/01/19 16:39:27 ERROR: stats for id: '3' not found
Jan 19 16:39:27 tankpi reef-pi[2023]: 2019/01/19 16:39:27 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:30 tankpi reef-pi[2023]: 2019/01/19 16:39:30 ERROR: stats for id: '1' not found
Jan 19 16:39:30 tankpi reef-pi[2023]: 2019/01/19 16:39:30 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:31 tankpi reef-pi[2023]: 2019/01/19 16:39:31 ERROR: stats for id: '1' not found
Jan 19 16:39:31 tankpi reef-pi[2023]: 2019/01/19 16:39:31 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:33 tankpi reef-pi[2023]: 2019/01/19 16:39:33 ERROR: stats for id: '2' not found
Jan 19 16:39:33 tankpi reef-pi[2023]: 2019/01/19 16:39:33 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:35 tankpi reef-pi[2023]: 2019/01/19 16:39:35 ERROR: stats for id: '2' not found
Jan 19 16:39:35 tankpi reef-pi[2023]: 2019/01/19 16:39:35 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:36 tankpi reef-pi[2023]: 2019/01/19 16:39:36 ERROR: stats for id: '3' not found
Jan 19 16:39:36 tankpi reef-pi[2023]: 2019/01/19 16:39:36 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:37 tankpi reef-pi[2023]: 2019/01/19 16:39:37 ERROR: stats for id: '3' not found
Jan 19 16:39:37 tankpi reef-pi[2023]: 2019/01/19 16:39:37 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:40 tankpi reef-pi[2023]: 2019/01/19 16:39:40 ERROR: stats for id: '1' not found
Jan 19 16:39:40 tankpi reef-pi[2023]: 2019/01/19 16:39:40 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:41 tankpi reef-pi[2023]: 2019/01/19 16:39:41 ERROR: stats for id: '1' not found
Jan 19 16:39:41 tankpi reef-pi[2023]: 2019/01/19 16:39:41 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:44 tankpi reef-pi[2023]: 2019/01/19 16:39:44 ERROR: stats for id: '2' not found
Jan 19 16:39:44 tankpi reef-pi[2023]: 2019/01/19 16:39:44 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:45 tankpi reef-pi[2023]: 2019/01/19 16:39:45 ERROR: stats for id: '2' not found
Jan 19 16:39:45 tankpi reef-pi[2023]: 2019/01/19 16:39:45 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:46 tankpi reef-pi[2023]: 2019/01/19 16:39:46 ERROR: stats for id: '3' not found
Jan 19 16:39:46 tankpi reef-pi[2023]: 2019/01/19 16:39:46 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:47 tankpi reef-pi[2023]: 2019/01/19 16:39:47 ERROR: stats for id: '3' not found
Jan 19 16:39:47 tankpi reef-pi[2023]: 2019/01/19 16:39:47 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:50 tankpi reef-pi[2023]: 2019/01/19 16:39:50 ERROR: stats for id: '1' not found
Jan 19 16:39:50 tankpi reef-pi[2023]: 2019/01/19 16:39:50 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:51 tankpi reef-pi[2023]: 2019/01/19 16:39:51 ERROR: stats for id: '1' not found
Jan 19 16:39:51 tankpi reef-pi[2023]: 2019/01/19 16:39:51 ERROR: GET /api/tcs/1/usage stats for id: '1' not found
Jan 19 16:39:53 tankpi reef-pi[2023]: 2019/01/19 16:39:53 ERROR: stats for id: '2' not found
Jan 19 16:39:53 tankpi reef-pi[2023]: 2019/01/19 16:39:53 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:55 tankpi reef-pi[2023]: 2019/01/19 16:39:55 ERROR: stats for id: '2' not found
Jan 19 16:39:55 tankpi reef-pi[2023]: 2019/01/19 16:39:55 ERROR: GET /api/tcs/2/usage stats for id: '2' not found
Jan 19 16:39:56 tankpi reef-pi[2023]: 2019/01/19 16:39:56 ERROR: stats for id: '3' not found
Jan 19 16:39:56 tankpi reef-pi[2023]: 2019/01/19 16:39:56 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:39:58 tankpi reef-pi[2023]: 2019/01/19 16:39:58 ERROR: stats for id: '3' not found
Jan 19 16:39:58 tankpi reef-pi[2023]: 2019/01/19 16:39:58 ERROR: GET /api/tcs/3/usage stats for id: '3' not found
Jan 19 16:55:57 tankpi reef-pi[2023]: 2019/01/19 16:55:57 ERROR: Failed to reload reef-pi. Output:. Error: signal: terminated
Jan 19 16:55:57 tankpi reef-pi[2023]: 2019/01/19 16:55:57 ERROR: GET /api/admin/reload Failed to reload reef-pi. Output:. Error: signal: terminated
​

Looks memory related as it ran out of memory, do I need to increase swap? Running on a raspberry pi 3 A+, looks very similar to ryan115 issue, I am running the stable image but have not updated to the latest fixes.

Let me know if you need any additional information.​

the error is related to out of memory, but the graph does not really show anything remotely memory constrained. I think this is a specific scenario where reef-pi is doing something that suddenly requires a lot of memory. Did the whole system restarted (uptime)? or just reef-pi was restarted?
Which version of reef-pi you are running? Are you using GUI or touchscreen ? Pi 3 or zero?

 

[bishoptf]

the error is related to out of memory, but the graph does not really show anything remotely memory constrained. I think this is a specific scenario where reef-pi is doing something that suddenly requires a lot of memory. Did the whole system restarted (uptime)? or just reef-pi was restarted?
Which version of reef-pi you are running? Are you using GUI or touchscreen ? Pi 3 or zero?

Looks like it was just the reef-pi service that was affected:
Saturday, 19 January 2019, 7:04:02 pm CST
Linux 4.14.79-v7+ armv7l GNU/Linux

Filesystem Size Used Avail Use% Mounted on
/dev/root 7.3G 1.1G 5.9G 16% /
Uptime.............: 7 days, 02h29m36s
Memory.............: 296704kB (Free) / 442340kB (Total)
Running Processes..: 98
IP Address.........: 10.99.99.9
Temperature........: CPU: 44°C/111°F GPU: 45°C/113°F

Running on a pi3 A+ which only has 512K memory vs the B+ that has 1024, no gui, no touchscreen, just reef-pi. I am running reef-pi-2.0-pi3.deb version. Let me know if you need additional information. It pretty much ran out of memory,

reef-pi invoked oom-killer: gfp_mask=0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null), order=0, oom_score_adj=0
Jan 19 16:37:27 tankpi kernel: reef-pi cpuset=/ mems_allowed=0

Jan 19 16:37:27 tankpi kernel: CPU: 0 PID: 6629 Comm: reef-pi Not tainted 4.14.79-v7+ #1159​

I rebuilt my bench pc last night, re-installing OS and getting things setup, plan is to kick the tires from git-hub and coming up to speed.

 

[b4tn]

Playing with the 2.0 temperature controller for past few days. Here is my pico tank;'s temperature chart, where the temperature controller is set at with larger threshold than than the heater. As a result, heater's internal thermostat is switching hetar on/off while the equipment is always on from reef-pi side, temperature controller is acting as failsafe only, in case things go south then will switch off heater and send alert.

The nano tank is setup in opposite way. With heater itself configured at bit higher setting (80) and reef-pi configured at 79.5, with 30 seconds interval. I am playing with 79.4. 79.3 after few hours to see the effect. Notice heater/cooler graph is now showing heater usage (as it is being turned on/off by reef-pi itself)

my realizations was pretty exciting. reef-pi switching on/off heater almost half the time when run at 60s interval. I get much finer control but it comes at a cost of switching heater on/off more frequently.
I am thinking of adding support for hysteresis and setpoints. Though this whole scheme work for heater, its not useful for chillers (and do they come without thermostat ?? ). I wanted to share this, as it will be really interesting to see how these graphs look after i implement hysteresis /setpoint based logic

@Ranjib its very funny that you bring this up. I was just thinking about doing this today. My heater is switching on and off almost every minute and I was thinking to adjust the heater to control but have reefpi turn it off if it gets too hot or runs out of control.

 

[rushbattle]

At least 1k for now

I was quoted $899 from coralvue. Not sure on the API details yet. I’ll update when I get the info.

 

[Bigtrout]

Playing with the 2.0 temperature controller for past few days. Here is my pico tank;'s temperature chart, where the temperature controller is set at with larger threshold than than the heater. As a result, heater's internal thermostat is switching hetar on/off while the equipment is always on from reef-pi side, temperature controller is acting as failsafe only, in case things go south then will switch off heater and send alert.

The nano tank is setup in opposite way. With heater itself configured at bit higher setting (80) and reef-pi configured at 79.5, with 30 seconds interval. I am playing with 79.4. 79.3 after few hours to see the effect. Notice heater/cooler graph is now showing heater usage (as it is being turned on/off by reef-pi itself)

my realizations was pretty exciting. reef-pi switching on/off heater almost half the time when run at 60s interval. I get much finer control but it comes at a cost of switching heater on/off more frequently.
I am thinking of adding support for hysteresis and setpoints. Though this whole scheme work for heater, its not useful for chillers (and do they come without thermostat ?? ). I wanted to share this, as it will be really interesting to see how these graphs look after i implement hysteresis /setpoint based logic

It think a swing/hysteresis should be a definite feature. Like I posted before the finer the temp control, the more frequently the heater cycles. More frequent cycles are harder on the heater or your relay board/power power controller, whichever is controlling the heater. This is especially important for smaller setups which heat and cool quicker.
Being able to tune this in would be helpful!

 

[Ranjib]

I would like to also know when I should expect these things to fail. Or some way to detect that they are going bad...

 

[bishoptf]

Funny since this weeks BRStv was all about heaters, its a good watch -https://www.bulkreefsupply.com/vide...nk-temperature-the-brs-wwc-system-ep14-brstv/

Pretty much summed up what I thought that no one makes a really good heater, that was one of my goals for reef-pi, to use as a failsafe for my heaters.

Is there anything I can do to help with the memory leak?

 

[Bigtrout]

I would like to also know when I should expect these things to fail. Or some way to detect that they are going bad...

Its a crapshoot, because most heaters have a bimetallic strip in them, and the songle relays in the 8 channel boards and the american dj strip have a rough life of 100,000 operations. That life depends on the current they switch on and off. When they fail the contacts tend to weld closed which is why you see alot of instances of runaway heaters.
So the best thing is to have failsafes in place, which is where reef pi comes in!

Solid state relays are better in this respect because they have no moving parts, but are more expensive and the ones that can handle more than 2 amps are larger physically and may need to be heatsinked.

 

[bishoptf]

Well this is funny, I think you may have a typo in your development instructions, lol, doesn't help that I am really tired and it takes me awhile to see the forrest for the trees.

git clone https://github.com/ranjin/reef-pi.git $GOPATH/src/github.com/ranjib/reef-pi
​

I looked that one up and was scratching my head, thinking I don't think thats Ranjib

 

[bishoptf]

I'm getting down to the make part but getting the following error:

pwd = /home/bishop/gospace/src/github.com/ranjib/reef-pi
make
make go
make[1]: Entering directory '/home/bishop/gospace/src/github.com/ranjib/reef-pi'
go build -o bin/reef-pi -ldflags "-s -w -X main.Version=2.1-20-g7415295" ./commands
commands/daemon.go:11:2: cannot find package "github.com/reef-pi/reef-pi/controller/daemon" in any of:
/usr/lib/go/src/github.com/reef-pi/reef-pi/controller/daemon (from $GOROOT)
/home/bishop/gospace/src/github.com/reef-pi/reef-pi/controller/daemon (from $GOPATH)
commands/reset_password.go:8:2: cannot find package "github.com/reef-pi/reef-pi/controller/storage" in any of:
/usr/lib/go/src/github.com/reef-pi/reef-pi/controller/storage (from $GOROOT)
/home/bishop/gospace/src/github.com/reef-pi/reef-pi/controller/storage (from $GOPATH)
make[1]: *** [Makefile:21: go] Error 1
make[1]: Leaving directory '/home/bishop/gospace/src/github.com/ranjib/reef-pi'
make: *** [Makefile:12: bin] Error 2
​

Like I said its probably something obvious but I'm tired, if you have any ideas on what I am missing let me know, the next part compiling the jsx code worked, just the make part that I am having issues with...

Thanks

 

[Dave B]

I have a thermostat issue that I am attempting to trace down. The thermostat sensor works fine for several hours then I get a cold warning followed by a tstat off line warning. Yesterday I soldered up a new sensor and plug but the same thing happened after several hours last night. I woke up to 100 warning emails. So my next step is to try a different socket and different jump wires. In fact, I may remove the pins on the Pi Hat and solder the wires direct. Any further ideas would be appreciated.

 

[Ryan115]

Its a crapshoot, because most heaters have a bimetallic strip in them, and the songle relays in the 8 channel boards and the american dj strip have a rough life of 100,000 operations. That life depends on the current they switch on and off. When they fail the contacts tend to weld closed which is why you see alot of instances of runaway heaters.
So the best thing is to have failsafes in place, which is where reef pi comes in!

Solid state relays are better in this respect because they have no moving parts, but are more expensive and the ones that can handle more than 2 amps are larger physically and may need to be heatsinked.

With reef-pi controlling the heater, and the heater set higher, the bi-metallic strip in the heater should typically remain closed. That should tremendously extend the life of the heater.
The 8 channel boards are cheap and easy to switch out should a relay fail (or change the relay itself). As far as the ADJ boards, what are they running internally? Would you be able to service them to replace a relay if one failed? If not, that may be a situation of having the heater control itself and have reef-pi running as the secondary control.
Currently I dont think that we would ever know if either the heater or relay failed on, as we do not have any way of sensing whether a device is actually on. @Ranjib is power/voltage/current sensing in the works at all? I know it has been mentioned in the past, but I dont know if it is going anywhere.
How does Apex monitor power?

 

[dmolavi]

How long should 'make ui-dev' take? It's been sitting here for almost 5 minutes....

dari@sheldon:~/gospace/src/github.com/reef-pi/reef-pi$ make ui-dev
npm run ui-dev

> [email protected] ui-dev /home/dari/gospace/src/github.com/reef-pi/reef-pi
> webpack -d --watch

clean-webpack-plugin: /home/dari/gospace/src/github.com/reef-pi/reef-pi/ui has been removed.

Webpack is watching the files…

Hash: 6b2e9022514358ae6c6c
Version: webpack 4.14.0
Time: 13607ms
Built at: 01/20/2019 9:03:12 AM
Asset Size Chunks Chunk Names
assets/css/main.3ace807c456ac8cb6683.css 160 KiB main [emitted] main
assets/js/main.41cd4f81d10cf7efbe79.js 1.43 MiB main [emitted] main
assets/js/vendors~main.867036f7abcecbc2c2b9.js 10.6 MiB vendors~main [emitted] vendors~main
favicon.ico 3.69 KiB [emitted]
home.html 542 bytes [emitted]
[./assets/sass/style.scss] 39 bytes {main} [built]
[./jsx/app.jsx] 3.07 KiB {main} [built]
[./jsx/ato/main.jsx] 3.67 KiB {main} [built]
[./jsx/camera/main.jsx] 4.64 KiB {main} [built]
[./jsx/configuration/main.jsx] 3.91 KiB {main} [built]
[./jsx/dashboard/main.jsx] 8.89 KiB {main} [built]
[./jsx/dlipower/main.jsx] 2.35 KiB {main} [built]
[./jsx/doser/main.jsx] 7.37 KiB {main} [built]
[./jsx/entry.js] 339 bytes {main} [built]
[./jsx/main_panel.jsx] 8.06 KiB {main} [built]
[./jsx/redux/reducer.js] 4.93 KiB {main} [built]
[./jsx/redux/store.js] 851 bytes {main} [built]
[./jsx/sign_in.jsx] 6.35 KiB {main} [built]
[./jsx/timers/main.jsx] 6.58 KiB {main} [built]
[./jsx/ui_components/error_boundary.jsx] 3.1 KiB {main} [built]
+ 944 hidden modules
Child html-webpack-plugin for "home.html":
1 asset
[./node_modules/html-webpack-plugin/lib/loader.js!./assets/home.html] 453 bytes {0} [built]
[./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 489 bytes {0} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/index.js!node_modules/postcss-loader/src/index.js??ref--5-2!node_modules/sass-loader/lib/loader.js!assets/sass/style.scss:
[./node_modules/css-loader/index.js!./node_modules/postcss-loader/src/index.js??ref--5-2!./node_modules/sass-loader/lib/loader.js!./assets/sass/style.scss] ./node_modules/css-loader!./node_modules/postcss-loader/src??ref--5-2!./node_modules/sass-loader/lib/loader.js!./assets/sass/style.scss 166 KiB {mini-css-extract-plugin} [built]
+ 1 hidden module

 

[DirtDiggler2823]

Its a crapshoot, because most heaters have a bimetallic strip in them, and the songle relays in the 8 channel boards and the american dj strip have a rough life of 100,000 operations. That life depends on the current they switch on and off. When they fail the contacts tend to weld closed which is why you see alot of instances of runaway heaters.
So the best thing is to have failsafes in place, which is where reef pi comes in!

Solid state relays are better in this respect because they have no moving parts, but are more expensive and the ones that can handle more than 2 amps are larger physically and may need to be heatsinked.

My heaters are set to just above what the reef pi is. If the relay fails closed then the native control of the heaters would kick in.

 

[Bigtrout]

I have a thermostat issue that I am attempting to trace down. The thermostat sensor works fine for several hours then I get a cold warning followed by a tstat off line warning. Yesterday I soldered up a new sensor and plug but the same thing happened after several hours last night. I woke up to 100 warning emails. So my next step is to try a different socket and different jump wires. In fact, I may remove the pins on the Pi Hat and solder the wires direct. Any further ideas would be appreciated.

How long are your sensor leads? And how many sensors?
Once you have ruled out faulty wiring, how long are your sensor runs? Very long runs or several sensors in the string, may require the pullup resistor to be lower than 4.7K ohms. I wouldn't go too low with it but you can go to 2.2kohms if needed.

 

[Bigtrout]

My heaters are set to just above what the reef pi is. If the relay fails closed then the native control of the heaters would kick in.

I run mine the opposite way because aqueon pros are solid state, not bimetal strips. My heaters control temp, and reef pi is set a degree higher in case the heater control goes haywire. Plus with aqueons being electronic control, switching on and off alot probably isnt good for them

 

[b4tn]

This is probably nothing new lol but last night I was messing with doser calibration. I would get them dialed in only to have it way off in the long run. For instance I set dosers to 90% for 10 seconds for 10ml. Works fine for one dose but after running the doser for 5 seconds 10 times my cylinder had 45ml instead of the expected 50. I got to thinking and looked up what the weight of water is and figured 1 gram per 1 ml. So I dialed the doser in by weight instead. 93% for 10 seconds came to 10 grams. I ran the doser rule at 93% 10 times and was spot on at 50ml. Just a little hack for anyone calibrating the doser.

 

[Bigtrout]

With reef-pi controlling the heater, and the heater set higher, the bi-metallic strip in the heater should typically remain closed. That should tremendously extend the life of the heater.
The 8 channel boards are cheap and easy to switch out should a relay fail (or change the relay itself). As far as the ADJ boards, what are they running internally? Would you be able to service them to replace a relay if one failed? If not, that may be a situation of having the heater control itself and have reef-pi running as the secondary control.
Currently I dont think that we would ever know if either the heater or relay failed on, as we do not have any way of sensing whether a device is actually on. @Ranjib is power/voltage/current sensing in the works at all? I know it has been mentioned in the past, but I dont know if it is going anywhere.
How does Apex monitor power?

The internal relays on the ADJ strip are the same brand and family of relays that are on the 8 channel relay boards. They are Songle branded SRD relays. The 8 channel boards are 5v relays, and the ADJ strip are 12v relays. Both are rated at 10amps at 250V, meaning for longevity running them under 5 amps is wise.

Here is the SRD family datasheet
https://www.google.com/url?sa=t&sou...FjAAegQIAhAB&usg=AOvVaw1jp0lAaqaJ9gb15aqbN-6t