search

rdmenezes / measureit

Automatically exported from code.google.com/p/measureit
0 stars 0 forks source link

Readings not uploaded to pvoutput #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Readings from a current cost clamp are received and viewable in the 
measureit database.
2. I've copy & pasted the pvoutput api key & system id into measureit to avoid 
errors.

What is the expected output? What do you see instead?
Measureit appears to be working fine, just nothing is uploaded to pvoutput.

What version of the product are you using? On what operating system?
V116 on Raspberry Pi

Please provide any additional information below.

Original issue reported on code.google.com by kimhea...@gmail.com on 24 May 2014 at 6:54

GoogleCodeExporter commented 9 years ago 
Ok. Lets find out why...

Please start the grabber manually and take a look in the log.

See "Measureit does not upload data to PVOutput" in the faq:
https://code.google.com/p/measureit/wiki/FAQ

Original comment by lalelu...@gmail.com on 24 May 2014 at 9:25

GoogleCodeExporter commented 9 years ago 
I got a permission denied error for the logfile when I tried to run the grabber.
I've attached a photo of the screen as I don't know anything about linux

Original comment by kimhea...@gmail.com on 25 May 2014 at 8:02

Attachments:

GoogleCodeExporter commented 9 years ago 
after login as user pi you had to change to user root with 

sudo bash

To read the log file you can do a

cat /tmp/measureit.log

of if the log is to long and you can not scroll 

cat /tmp/measureit.log | more

this will show the log in parts. If you press space you get the next part

Original comment by lalelu...@gmail.com on 25 May 2014 at 8:07

GoogleCodeExporter commented 9 years ago 
After logging in and running sudo bash,
when starting the grabber manually, I get
Error 11 Resource temporarily unavailable

Original comment by kimhea...@gmail.com on 25 May 2014 at 8:55

GoogleCodeExporter commented 9 years ago 
Sorry, my error.

I had to polish the faq...

You had to shut down the running measureit process first before you can start 
it manually...

svc -d /service/measureit

To start it again after debugging

svc -u /service/measureit

Original comment by lalelu...@gmail.com on 25 May 2014 at 8:58

GoogleCodeExporter commented 9 years ago 
When I run the grabber with the test parameter, data shows on the screen and I 
can open the log file.
When I start it with debug I just get a flashing cursor, if I leave it for a 
while then ctrl+c, the log file is empty.

Original comment by kimhea...@gmail.com on 26 May 2014 at 2:47

GoogleCodeExporter commented 9 years ago 
mhhh

did you start the grabber with svc -u after running it manually? Everytime the 
grabber is startet it will clear the log.

If not. Can you open 2 console windows. One to start the grabber and then the 
2nd to see in real time what happened in the log with

tail -f /tmp/measureit.log

In debug mode the grabber posts nothing on the screen so it is ok that you see 
nothing

Original comment by lalelu...@gmail.com on 27 May 2014 at 6:28

GoogleCodeExporter commented 9 years ago 
Still no luck with the grabber in debug mode even with the 2 console windows.

I've decided to use a spare windows computer rather than persist with the pi so 
I'll close the issue.
Thanks for all your help

Original comment by kimhea...@gmail.com on 1 Jun 2014 at 4:36

GoogleCodeExporter commented 9 years ago

Original comment by lalelu...@gmail.com on 25 Jul 2014 at 7:32