Using emonPi/RFM69Pi emonbase ready-to-go SD card image as emonbase (emonhub) only

Submitted by EmilianoM on Tue, 08/09/2015 - 18:50

Hi,

after 1 year and half I tried to upgrade my Raspberry used as emonhub following here:

CURRENT: emonPi and RFM69Pi emonbase ready-to-go SD card image

The system work successfully (after few changes in the configuration).

My simple question is the following: is it possibile to permanently let run only emonhub (without local emoncms e emonLCD) ?

I am using it to collect data from 1 emonTX + 2 emonTH and to send onto emoncms.org.

I wish to minimize resource usage on the Raspberry (especially log writing of emoncms).

Thanks !

Regards,

Emiliano.

Re: Using emonPi/RFM69Pi emonbase ready-to-go SD card image as emonbase (emonhub) only

Submitted by EmilianoM on Tue, 08/09/2015 - 19:04.

Here are some details of growing files (not present before to upgrade):

pi@emonpi /var/log $ ls -al
total 5896
drwxrwxrwt  5 root    root         460 Sep  6 22:37 .
drwxr-xr-x 12 root    root        4096 May  8 16:04 ..
-rw-r-----  1 root    adm       708959 Sep  8 21:01 auth.log
-rw-r-----  1 root    adm         8536 Sep  8 18:41 daemon.log
-rw-r-----  1 root    adm          988 Sep  6 22:18 debug
-rw-r--r--  1 root    adm        12958 Sep  6 22:18 dmesg
-rw-rw-r--  1 root    www-data  314115 Sep  8 21:01 emoncms.log
drwxr-xr-x  2 emonhub root          60 Sep  6 22:18 emonhub
-rw-r--r--  1 pi      pi             0 Sep  6 22:20 emonpiupdate.log
-rw-r--r--  1 root    root         120 Sep  6 22:18 error.log
-rw-r-----  1 root    adm      1130891 Sep  8 21:01 kern.log
-rw-r--r--  1 root    root      292292 Sep  8 20:56 lastlog
-rw-r-----  1 root    adm            0 Sep  6 22:18 lpr.log
-rw-r-----  1 root    adm            0 Sep  6 22:18 mail.err
-rw-r-----  1 root    adm            0 Sep  6 22:18 mail.info
-rw-r-----  1 root    adm            0 Sep  6 22:18 mail.log
-rw-r-----  1 root    adm            0 Sep  6 22:18 mail.warn
-rw-r-----  1 root    adm      1130035 Sep  8 21:01 messages
drwxr-xr-x  2 root    root         100 Sep  6 22:18 news
drwxr-xr-x  3 pi      pi           280 Sep  6 22:38 speedtest-cli
-rw-r-----  1 root    adm      1577208 Sep  8 21:01 syslog
-rw-r-----  1 root    adm      1110982 Sep  8 21:01 ufw.log
-rw-r-----  1 root    adm            0 Sep  6 22:18 user.log

Re: Using emonPi/RFM69Pi emonbase ready-to-go SD card image as emonbase (emonhub) only

Submitted by EmilianoM on Tue, 08/09/2015 - 19:10.

And some examples of what logs are filled with:

pi@emonpi /var/log $ tail -f kern.log
Sep  8 21:05:27 emonpi kernel: [168385.921989] [UFW BLOCK] IN=eth0 OUT= 
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:fc:03:00:00:01:11:1c:0e 
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=64515 PROTO=UDP 
   SPT=59129 DPT=8612 LEN=24
Sep  8 21:05:48 emonpi kernel: [168407.342704] [UFW BLOCK] IN=eth0 OUT= 
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:89:88:00:00:01:11:8e:89 
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=35208 PROTO=UDP 
   SPT=64676 DPT=8612 LEN=24

pi@emonpi /var/log $ tail -f syslog
Sep  8 21:07:01 emonpi /USR/SBIN/CRON[23690]: (pi) 
   CMD (/home/pi/emonpi/update >> /var/log/emonpiupdate.log 2>&1)
Sep  8 21:07:07 emonpi kernel: [168485.891457] [UFW BLOCK] IN=eth0 OUT= 
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:85:74:00:00:01:11:92:9d 
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=34164 PROTO=UDP 
   SPT=49329 DPT=8612 LEN=24

pi@emonpi /var/log $ tail -f messages
Sep  8 21:05:48 emonpi kernel: [168407.342704] [UFW BLOCK] IN=eth0 OUT= 
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:89:88:00:00:01:11:8e:89 
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=35208 PROTO=UDP 
   SPT=64676 DPT=8612 LEN=24
Sep  8 21:06:09 emonpi kernel: [168428.768173] [UFW BLOCK] IN=eth0 OUT= 
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:e1:c6:00:00:01:11:36:4b 
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=57798 PROTO=UDP 
   SPT=51928 DPT=8612 LEN=24

pi@emonpi /var/log $ tail -f ufw.log
Sep  8 21:06:31 emonpi kernel: [168450.193467] [UFW BLOCK] IN=eth0 OUT= 
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:c1:b8:00:00:01:11:56:59    
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=49592 PROTO=UDP 
   SPT=51032 DPT=8612 LEN=24
Sep  8 21:06:45 emonpi kernel: [168464.468550] [UFW BLOCK] IN=eth0 OUT=    
   MAC=01:00:5e:00:00:01:c8:2a:14:1b:3c:fd:08:00:45:00:00:2c:29:09:00:00:01:11:ef:08 
   SRC=192.168.1.6 DST=224.0.0.1 LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=10505 PROTO=UDP 
   SPT=56481 DPT=8612 LEN=24

[Lines wrapped for presentation. Moderator (RW)]

Re: Using emonPi/RFM69Pi emonbase ready-to-go SD card image as emonbase (emonhub) only

Submitted by pb66 on Tue, 08/09/2015 - 22:46.

Hi Emiliano

I would recommend using the previous "pre-emonPi" SDcard image if you just want enonHub especially if you have been using emonHub for sometime and are familiar with it. the 13-03-15 emonSD.img has "original" emonHub, plus the "LAMP" and emoncms is disabled by default.

the "emon-pi variant" is heavily focused on close ties with emoncms and uses MQTT, so even though you just want emonhub there is an apache server, MQTT broker, redis and mySQL servers etc, etc, all unneccesary for a forwarding-only install. Plus as it is focused on a local emoncms, i.e. not remote, there is no in-memory buffering in the "emon-pi variant." Any network issues will result in lost data. IMO, the buffers are essential to a remote install.

emonhub's log files are written to a RAM mounted partition, the partition is limited to 30mb in size and emonhubs logs are limited to a maximum of 2 in rotation, each a max of 5mb, so should not use valuable resourses, or fatigue the SDcard. They are deleted at each reboot,

Paul

Archived Forum