meteohub.de

I have a meteohub Version 2.8f connected via a Vantage Pro 2 (With UV and Solar Radiation Sensor) and a Weather Envoy.

Unfortunately no graphs are generated - see http://static.23.nu/wetter/DE1/
Also the Dashboard and the WD Live Display stays empty.

Upload to weather networks woks - see http://www.wetterarchiv.de/station/3093 ... daten.html

I suspect theMessage "Weather Data Recomputation: waiting" has something to do with the issue - it has been like this for weeks.

Any hints on how to solve that?

--md

Hi,

Have you tried to Reset meteohub? Or Stop it and Turn On again ..

Chill

Yes, I tried

a) rebooting
b) Stopping/Starting the Data Logging Process

didn't help.

easiest would be if you can give me access to ports 22 and 7777.

Anything interesting int "meteohub log" and log files page?

Did this issue ever get fixed as I am now experiencing this. As you recall I had the USB stick problem today and now have it all back up and running....but it is not sending out proper data for WD Live - everything has a 293 in each data field. I suspect that WD Live data is not correct because it has not done a Data recomputation and I have tried starting it etc....but no luck - it just won't do it...

I was able to copy my Weather data from my old USB stick into the new weather folder and my upload to Wunderground is working great and sending the data and it's sending WD Live data - just doesn't make any sense and WD Live errors out.... I suspect all because of of the Recomputation not taking place...

Here are some error logs that I am seeing...


Nov 11 20:24:00 (none) cron.info /USR/SBIN/CRON[3134]: (root) CMD (/bin/pidof wswinimport || /usr/bin/nice /home/meteohub/wswinimport 2>>/data/log/messages)
Nov 11 20:24:00 (none) cron.info /USR/SBIN/CRON[3135]: (root) CMD (/bin/cat /proc/uptime >/home/meteohub/alive)
Nov 11 20:24:01 (none) daemon.info thttpd[1031]: spawned CGI process 3139 for file 'cgi-bin/meteohub.cgi'
Nov 11 20:24:21 (none) daemon.info thttpd[1031]: spawned CGI process 3173 for file 'cgi-bin/meteohub.cgi'
Nov 11 20:24:24 (none) daemon.info thttpd[1031]: spawned CGI process 3195 for file 'cgi-bin/meteohub.cgi'

Also getting this in the meteohub log..

wmr928eval (11.11.2008 20:24:53): illegal data record in line 201732 while reading from file /data/weather/200811/raw: 2081109040204 wind0$268 22 18 0230
wmr928eval (11.11.2008 20:25:35): illegal data record in line 201653 while reading from file /data/weather/200811/raw: 200<1109035706 thb0 214 20 -025 8214 2 10160
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201655 while reading from file /data/weather/200811/raw: 2408110903570> wind0 652 13 13 0041
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201657 while reading from file /data/weather/200811/raw: 20081109035710(wind0 2=2 2: 13,0030
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201659 while reading from file /data/weather/200811/raw: 200:1109035716 ind0 255 22 13 003020081109035718 wind0 257 27 13 0026
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201678 while reading from file /data/weather/200811/raw: 200<110;035<32 wind0 261 22 13 0030
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201723 while reading from file /data/weather/200811/raw: 2008114904<130&winf0 270 1< 18 0035
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201726 while reading from file /data/weather/200811/raw: 2008150906013: wind0 267 22 18 0030
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201729 while reading from file /data/weather/200811/raw: 200:1109040148 wind0 268 18 18 0035
wmr928eval (11.11.2008 20:25:36): illegal data record in line 201732 while reading from file /data/weather/200811/raw: 2081109040204 wind0$268 22 18 0230

You have corrupted entries in your data files.

Two questions:

1. Did you stop all data logging while copying your old data files to the new USB stick, and only resume logging after the copy was completed?

2. Did you wait to copy the data files until after the initial data recomputation was completed?

If you answered No to either of the above questions, that could account for the errors you see. Otherwise, you will need to open the raw data files in a text editor that can handle large files (such as EditPad Lite), find the offending lines as listed in the logs, and either delete or remedy them, then save the raw files and upload them again... then recompute the data again.

Also, the system log you pasted two entries prior to this one is absurdly long and spammy, and it's very difficult to actually locate any error entries within that, so please be more careful in the future about including relevant details while weeding out the regular system information that shows up in everyone's system log.

You've also compromised the security your remote web host because ncftpput calls are included in the system log without obfuscation of the host, username and password, so I strongly recommend you change the remote password (and ideally also change the remote user name if your ISP permits that!)

Thanks Sevenless and my apologies... Most of this is over my head and I've been so frustrated with this platform - hopefully soon I will go to the new platform...

I've deleted entries and changed passwords for security reasons..

As for the files - No and No to your questions - but before I transferred files - I copied the current configuration - so I'm trying to now replace what I did earlier with the original... We'll see where I get with that...

Well deleting and moving original files fixed my WD Live uploads - but it still won't do a data recomputation.....keeps waiting... I've spent way to many hours on this and will probably just start over and erase the stick and give it another try from scratch....still getting tons of messages in the system log too....

Nov 11 23:07:00 (none) cron.info /USR/SBIN/CRON[2558]: (root) CMD (/bin/cat /proc/uptime >/home/meteohub/alive)
Nov 11 23:07:03 (none) daemon.info thttpd[1033]: spawned CGI process 2561 for file 'cgi-bin/meteohub.cgi'

It looks like Metehub ran a data recomputation over night and has caught up with my old data and now working....at least I think so... I'll have to look at my system log this evening to see if anything changed there as I was getting regular reports there...

Is there normal reporting going on in the system log - I don't remember any....? Thanks!

I'll post a new thread if so....

Thanks everyone!

The system log displays all the normal activity that the Meteohub is performing -- every graph creation, every file upload, every recomputation, every cron entry. The uptime/alive function you pasted above is a routine internal check to ensure the system is still running smoothly, and the thttpd cgi process is probably the meteohub webserver (thttpd) responding to your request for a webpage when you actually went to look at the logs!

Unless you see something in the system log that actually says 'error' or 'failed' or similar, don't worry too much about what's in there. It's mainly meant to provide diagnostic output in case something does go wrong, but in and of itself does not indicate a problem. If anything, I'd be worried if the system log wasn't filled with line after line of the above type of output!

Okay - so I got everything working and sometime overnight it pulled my historical data into the mix and uploads it to WD Live and shows my history etc... I figure that took a data Recomputation to get that data..... BUT....

It still says Weather Data Recomputation: WAITING

So something still not right.....even though it all appears to be working..... All of my logs look good except for SMB Log - there are errors that I don't understand...

2008/11/12 02:38:05, 0] smbd/server.c:main(881)
standard input is not a socket, assuming -D option
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0
[2008/11/12 02:38:05, 1] lib/account_pol.c:account_policy_get(329)
account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0

Well I made another USB Stick and rather than copying my settings in - I started from scratch and input everything. That is working and no problems.... Also succesfully add my historical data making sure this time I stopped the data logging and recomputed aggregate data first... I'm also keeping a few backup versions of a USB Stick ready to go.... I still get the SMB errors listed above - so this must be a standard error....

Now it's time to save for a Fit-PC Slim!

You're correct -- those SMB errors pop up occasionally in my log files as well, so they're also likely to be showing up in most people's logs.

SMB (Samba) is the file-sharing protocol used if you transfer files directly between the Meteohub and your local desktop computer (e.g. via rSync, or using shared network drives.) There seem to be a few hiccups here and there with the Meteohub user and security policy settings on the SMB daemon (at least in recent versions). They don't affect the ability of the Meteohub to share folders or use rsync, but it does spam up that log somewhat.