Page 1 of 3
Update 4.7a
Posted: Sun Jan 16, 2011 7:58 pm
by admin
Update to Meteohub V4.7a (NSLU2, x86, SheevaPlug) brings some minor bug-fixes:
- switch to non-ssl connection when feeding weather network "meteonews" by a NSLU2 based Meteohub
- fix ssh-tunnel failure when requesting help via "help.cgi"
- fix XML syntax error in meteolog.cgi output
Update Link:
http://www.meteohub.de/files/update-v4.7a.upd
Re: Update 4.7a
Posted: Tue Jan 18, 2011 2:02 pm
by atlantique44
Hello
excuse me for the translation because I am using translation software because I don not write English
When I am connected to the network place window with Meteohub as login and password I Meteohub No more has come to connect for the latest update to 4.7a is as if it was turning loop, I no longer happens access the file.
Thank you for your reply
Re: Update 4.7a
Posted: Tue Jan 18, 2011 7:06 pm
by markhiseman
Boris, I think atlantique44 is reporting the same issue that friese111 and I reported in the NSLU2 forum.
Mark.
Re: Update 4.7a
Posted: Tue Jan 18, 2011 7:22 pm
by EmjayNet
Wish I of read this first!
I updated to 4.7a this morning and also can no longer log-in to meteohub via windows explorer (network share or via SSH)
I also have this in my smb server log:
[2011/01/18 17:16:38, 0] passdb/pdb_smbpasswd.c:build_sam_account(1202)
build_sam_account: smbpasswd database is corrupt! username meteohub with uid 500 is not in unix passwd database!
Re: Update 4.7a
Posted: Tue Jan 18, 2011 8:45 pm
by markhiseman
Yes, I have the same error in smblog.
Mark.
Re: Update 4.7a
Posted: Tue Jan 18, 2011 10:04 pm
by atlantique44
moi also la same Erreur
smb server log:
[2011/01/18 19:45:35, 0] passdb/pdb_smbpasswd.c:build_sam_account(1202)
build_sam_account: smbpasswd database is corrupt! username meteohub with uid 500 is not in unix passwd database!
Re: Update 4.7a
Posted: Tue Jan 18, 2011 10:19 pm
by YJB
Hmmm,
I can't check the share connection, since I'm travelling
What I do see on my
Alix is that meteohub has disappeared from /etc/passwd:
Code: Select all
meteohub:/etc# grep meteohub /etc/passwd
<nothing returned>
The original version does return the meteohub user account:
Code: Select all
meteohub:/etc# grep meteohub /etc/passwd-
meteohub:x:1000:1000:meteohub,,,:/home/meteohub:/bin/bash
I'm not sure if it would make sense to recreate a meteohub account, better wait for Boris to respond, he might have a very good reason for changing things.
WARNING:
If you want to modify /etc/passwd you will need to be careful in doing so. If you don't know
exactly what you are doing you might loose access to your meteohub system. I've seen this happening more than once, so be careful.
Re: Update 4.7a
Posted: Wed Jan 19, 2011 2:02 am
by admin
yes, removing meteohub user from /etc/passwd is the root of the problem.
Will be fixed with next update (coming soon).
Re: Update 4.7a
Posted: Wed Jan 19, 2011 3:50 pm
by Rheintalwetter
Same happened to me, I can't access to pubic directory. So now I can't update my data in WSWIN or is there any workaround to solve this problem with actual firmware in short time? I distribute my data to a lot of other webpages and they have old data now... so please let me know how to solve this problem quickly! Thanks!
Re: Update 4.7a
Posted: Wed Jan 19, 2011 4:04 pm
by Rheintalwetter
I found this entry in the log:
[2011/01/19 14:58:19, 0] passdb/pdb_smbpasswd.c:build_sam_account(1202)
build_sam_account: smbpasswd database is corrupt! username meteohub with uid 500 is not in unix passwd database!
this entry is written several times per second... so ist this a known problem or only my own? thanks for any help!
Re: Update 4.7a
Posted: Wed Jan 19, 2011 4:07 pm
by YJB
Correct, this is a known problem that will be fixed by Boris in the next release, see the posting from Boris in this thread.
Re: Update 4.7a
Posted: Wed Jan 19, 2011 4:18 pm
by EmjayNet
It looks like anyone who updated to 4.7a is in the same boat.
It's a bit of a problem not having shares access, but at least MH is running correctly, so were not losing data.
Just have to wait for Boris to come up with a fix A.S.A.P.
Re: Update 4.7a
Posted: Wed Jan 19, 2011 4:39 pm
by Rheintalwetter
YJB wrote:Correct, this is a known problem that will be fixed by Boris in the next release, see the posting from Boris in this thread.
Yep, it looks like. But because I deliver data to many sites by WSWIN it's a very serious problem for me!! And so I hope for really fast support. At this time I could NOT ACCESS to my weatherbox with user meteohub?!! So I'm asking me how to upgrade or downgrade?! Here I have opened a browser where I still have access to weatherboxx becauase it seems there are working cookies or whatever, but if I try to connect from a different machine I could not connect with meteohub anymore... there is no user meteohub... ??
Re: Update 4.7a
Posted: Wed Jan 19, 2011 4:45 pm
by YJB
As far as I know the access to the gui is not dependent on /etc/passwd so that's the reason you still have access to the web interface. As far as I can see, only share access is impacted (that is what the smb daemon is doing), web interface access, root access and ftp uploads are working as usual.
If you are familiar with *nix systems you can add the meteohub user back to the passwd file, but it's probably safer to wait until Boris has released the fix.
Also, if you feel that you meteohub installation is very important, it's better to wait a couple of days before upgrading. In that way you give others the opportunity to "test" without being impacted yourself. Also, the more experienced users can take the risk being early adopters of a new release, since they might be able to correct things on the fly.
Re: Update 4.7a
Posted: Wed Jan 19, 2011 4:52 pm
by Rheintalwetter
YJB wrote:Also, if you feel that you meteohub installation is very important, it's better to wait a couple of days before upgrading. In that way you give others the opportunity to "test" without being impacted yourself. Also, the more experienced users can take the risk being early adopters of a new release, since they might be able to correct things on the fly.
Last few times I already did it. And right when I do an installation for first time short after it's public, then such a f**** buttshit happens... You could be sure I have learned my lesson now... I NEVER will do an update before I consulted this forum and waited some days... !!
