What Branko was saying was that there is a bug in the client where it will not register as receiving.
So, occasionally it is possible that 113W and ABS-2 show as receiving from time to time and it’s equally possible that the one receiver on G19 could be any one of Syed’s, Ken’s, or my receivers. Also i believe both Andrean and Branko are on HB13, so there should be two if not more there as well.
But in the server code. The current server code is a duct-tape-wrapped version of the old code. We’re still migrating it to the new server code.
Ah, ok. Got that part mixed up.
im full LH on 2.10000 and 90 kpbs of donwload data
i did not get error 500 on this update, using OTA
i just wait for a status.server update 
outernet@outernet:~$ grep monito /var/log/syslog
Jan 2 20:41:17 outernet user.warn kernel: [ 2.024873@0] ge2d start monitor^M
Jan 2 20:41:17 outernet user.warn kernel: [ 2.027979@1] ge2d workqueue monitor start^M
Jan 2 20:41:43 outernet user.info kernel: [ 43.058614@1] unionfs: new lower inode mtime (bindex=1, name=monitoring)
There’s a good chance the monitoring has to be activated on updated boxes. In future we’ll add a setup step / settings panel which allows you to toggle it.
Activation of monitoring has to be done like so:
sudo touch /mnt/persist/monitoring.yesim sorry , yes i did not run the comand 
sudo touch /mnt/persist/monitoring.yes
Password:
outernet@outernet:~$ grep monitor /var/log/syslog
Dec 17 00:04:49 outernet authpriv.notice sudo: outernet : TTY=pts/0 ; PWD=/home/outernet ; USER=root ; COMMAND=/bin/touch /mnt/persist/monitoring.yes
outernet@outernet:~$
outernet@outernet:~$ grep monito /var/log/syslog
Dec 17 00:04:49 outernet authpriv.notice sudo: outernet : TTY=pts/0 ; PWD=/home/outernet ; USER=root ; COMMAND=/bin/touch /mnt/persist/monitoring.yes
Dec 17 00:05:01 outernet authpriv.notice sudo: outernet : TTY=pts/0 ; PWD=/home/outernet ; USER=root ; COMMAND=/bin/touch /mnt/persist/monitoring.yes
Dec 17 00:05:08 outernet user.info outernet.monitor: Collecting data
Dec 17 00:05:08 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:05:08 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:05:09 outernet user.info outernet.monitor: Finished collecting data in 0.251363992691 seconds
Dec 17 00:05:09 outernet user.info outernet.monitor: Transmitting buffered data
Dec 17 00:05:09 outernet user.info outernet.monitor: Transmission complete, claring local buffer
Dec 17 00:06:09 outernet user.info outernet.monitor: Collecting data
Dec 17 00:06:09 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:06:09 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:06:09 outernet user.info outernet.monitor: Finished collecting data in 0.24271607399 seconds
Except for a miserable typo in the log mesages, it seems to be transmitting. I’ll check the database tomorrow and see if there’s any data from ES113W.
lol, im so drunk , now there is a party at home , all familly , i just showing outernet to the joung hackers…
have fun!
Branko, here’s what I got when I ran the command:
Using username “outernet”.
[email protected]’s password:
outernet@outernet:~$ grep monitor /var/log/syslog
Dec 17 00:43:29 outernet user.info outernet.monitor: Collecting data
Dec 17 00:43:29 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:43:29 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:43:29 outernet user.info outernet.monitor: Finished collecting data in 0.221652030945 seconds
Dec 17 00:44:29 outernet user.info outernet.monitor: Collecting data
Dec 17 00:44:29 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:44:35 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:44:35 outernet user.info outernet.monitor: Finished collecting data in 5.50074195862 seconds
Dec 17 00:45:35 outernet user.info outernet.monitor: Collecting data
Dec 17 00:45:35 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:45:35 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:45:35 outernet user.info outernet.monitor: Finished collecting data in 0.187667131424 seconds
Dec 17 00:46:35 outernet user.info outernet.monitor: Collecting data
Dec 17 00:46:35 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:46:35 outernet user.info outernet.monitor: Connected to socket
Dec 17 00:46:35 outernet user.info outernet.monitor: Finished collecting data in 0.231056928635 seconds
Dec 17 00:46:35 outernet user.info outernet.monitor: Transmitting buffered data
Dec 17 00:46:35 outernet user.info outernet.monitor: Transmission complete, claring local buffer
outernet@outernet:~$
Oh. No 
I took a look at the database, and we have 6 distinct receivers reporting in:
monitoring=# select distinct client_id from stats;
client_id
--------------------------------------
34061a2b-0ffd-4082-995b-***
b0dc9bf7-f92d-4923-a726-***
c3b9a301-abff-435f-88fe-***
d82eeac8-da31-46c6-a41e-***
c117e5a4-ce76-46c8-8278-***
f39156cf-8874-4620-866d-***
(6 rows)
If you want to know if one of those is your device you can take a look at the device ID file:
cat /mnt/persist/monitoring.keyKen’s is the 2nd entry b0dc9bf7-f92d-4923-a726-… reporting on Galaxy 19.
I noticed the status page on 17 Dec 2015 0710 EST (1210 UTC) is not current - - I presume the time posted on the page is in UTC
My LH device id is 4bb3cbce-19fa-47c6-a14f-*** but not listed in the above list. Now it is up and running.
Oh, I see. Yeah, that’s pretty weird.
Is the monitoring running?
I just emailed my LH IP address
Monitoring still not updated on Wiki STATUS. It is still at: 2015-12-16 10:04:54
Ken
We’ll let you know when the new server is deployed.
I checked my Monitoring ID today at 24 Dec 2106 UTC and it is:
Using username “outernet”.
[email protected]’s password:
outernet@outernet:~$ cat /mnt/persist/monitoring.key
6f67d3bf-d837-4fcb-b795-9987bd74d2c6outernet@outernet:~$
outernet@outernet:~$
Am I one of the 2 reporting stations? Ken