meteohub.de

Hi, I've noticed many MH processes have very low nice levels (-5, -15). They seem to bog down the entire platform (I run MH on a Sheeva Plug). Can't they be just set to zero? Is there a start / config file I can edit to change the default nice levels?

Cheers,
Headworx

Yes sure. Is port 22 / SSH enough? I will have to reconfigure the router. I will do this on Saturday, so you are welcome to have a look at it just after Christmas.

Boris, any idea how to proceed with this issue? My stations are not recording any data for several weeks now...

The logs are empty. Only dmesg shows some entries, the rest of the logs are blank.

Dear,

From time to time (2-3 times a month) I keep getting the following error:

error receive data from socket 127.0.0.1:5555: Resource temporarily unavailable
Warning: Data logging has been halted.

After my recent upgrade to 4.8 (Build 789) it happens every second day. I run quite heavily ...

Not sure about the Ebox. I play quite a lot with the SheevaPlug. On the Sheeva you can install MOTION by executing:

apt-get install motion

and then enable lan access by editing the file
/etc/motion/motion.conf
and changing
webcam_localhost off

after this you can access the attached USB camera ...

Yep. This is the case.

On Nov 30 it was 60%.
On Dec 01 it was 18%.
On Dec 02 it was 10%
Today (Dec 3) is 12%

On the other hand my month highs were:
40% in September
50% in October
60% in November

Wonder if the end of month maximu CPU load has to do with the fact I kept on adding sensors and ...

It has dropped now to 10%... So it really looks like it is a monthly cycle...

Cheers,
Headworx

Nope... MH uses it's own clock.

I think the better idea is to set up ntp clock synchronization at the system level...
HTH,
Headworx

Yest they are working very well. The ones I have have broken clocks, that was the reason they were so cheap... I have 12 of them... MH just takes the temperature and humidity, discards the clock... So it is fine for me...

Cheers,
Headworx

0,54 is 54% load...

My graph is defined as a scalar data on a time line, for the last 100 days, with 6 hour buckets. I use data0 sensor for CPU load. Beforehand there is a Weather Station 1 of System Data type defined, that provides the necessary sensors. Pretty standard stuff... I think the graph ...

Yes... the revised LOG_FORMAT... considering what you said, it should be just like:
LOG_FORMAT "T1 %.0C0"
then the output is like:

Found DS2490 device #1 at 001/005
T1 240
T1 240
T1 240


BUT... the "24" part is rounded to zero decimal places (%.0C in the LOG_FORMAT) and then there is an ...

It seems I am close to the solution.

The steps are as follows (I run MH on Sheeva):

1. install digitemp:
# apt-get install digitemp

2. After plugging in the DS9490 USB to 1-wire converter, I can list (walk) the devices:
# digitemp_DS2490 -w

3. If the output is correct (it should identify ...

I have 3 weather stations (1 Davis and 2 RFXComs), 6 sensors each (that totals to 18 real sensors + 6 additional for system data). The performance of the system (web interface, graphs...) is very good, I have just been wondering if it will settle somewhere around 50% or will continue to climb ...

Looking at the 3-month chart, I see b_l seems to be right... the load rises through the month and then falls down when the next month begins.

To graph system data, just add a system data virtual station and start collecting data points. The important ones for me are the system load and storage.

I ...