Hi all,
I seem to have a bit of a problem with my (newish) B2 WiFi - the unit stays on for about 12hrs and then dies. The symptoms are
o cant login with ssh
o no webadmin - occasionally a 500 internal server error, usually browser timeout
o ping works
o I can access internet via B2 WLAN
The unit is two weeks old, I haven't installed anything which should break it (only updates and phpmyadmin from packages)
Any ideas? Should I check the logs for something?
Please note the new address for this forum : forum.excito.org. The old address redirects here but I don't know for how long. Thanks !
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
B2 dies regularly
-
- Posts: 904
- Joined: 09 Oct 2009, 18:49
Re: B2 dies regularly
Definitely have a look through /var/log/syslog and see if there's any messages at around the time it goes down.
Re: B2 dies regularly
you can't login, but you can "access" internet via B2 WAN? So you mean it's still routing but does no longer respond to ssh or httpd? That's quite weird. Unless the problem is in the routing/firewall area that is. Or if the unit is completely overloaded and can't manage to responding to external services.
Re: B2 dies regularly
Yes, the unit routes OK but I cannot access the web admin or connect with ssh. The button on the back doesn't work, I have to unplug the power to reboot it.
syslog didn't show anything but as I just tried to check it once more with ssh i got the following error
malloc: ../../bash/builtins/evalfile.c:160: assertion botched
free: start and end chunk sizes differ
last command: (null)
Aborting...Connection to bubba.local closed.
syslog didn't show anything but as I just tried to check it once more with ssh i got the following error
malloc: ../../bash/builtins/evalfile.c:160: assertion botched
free: start and end chunk sizes differ
last command: (null)
Aborting...Connection to bubba.local closed.
Re: B2 dies regularly
quite an unusual error. Did you alter, add or remove anything on the machine in any way that required SSH access or root privileges?
Re: B2 dies regularly
Yes, I have updated the packages and installed phpmyadmin. (edit: changed the repo as instructed here and apt-get update, apt-get install phpmyadmin)
When I reboot the unit webadmin, ssh etc work just OK until the problems mentioned above arise, usually it has been some 12 hrs but this time ssh died in just 2 hrs.
Could it be that something is eating up all the free memory? Or could it be a hardware defect? All suggestions are welcome.
When I reboot the unit webadmin, ssh etc work just OK until the problems mentioned above arise, usually it has been some 12 hrs but this time ssh died in just 2 hrs.
Could it be that something is eating up all the free memory? Or could it be a hardware defect? All suggestions are welcome.
Re: B2 dies regularly
There is a reason there are assertion checks in the code.
It might very well indicate a hardware problem.
Please email [email protected]
Best regards,
Cheeseboy
It might very well indicate a hardware problem.
Please email [email protected]
Best regards,
Cheeseboy
Re: B2 dies regularly
Hi,
I have already emailed excito last week but haven't had any response yet. It seems to take around three days to get a reply so I am expecting it latest on monday.
If you have any ideas what to try I would be very happy. Is there any good memcheck etc which I could try?
I have already emailed excito last week but haven't had any response yet. It seems to take around three days to get a reply so I am expecting it latest on monday.
If you have any ideas what to try I would be very happy. Is there any good memcheck etc which I could try?
-
- Posts: 904
- Joined: 09 Oct 2009, 18:49
Re: B2 dies regularly
If it's no great effort I would just try a fresh install and keep it clean for a few days to see if this persists. If it doesn't happen from new then try installing phpmyadmin again and see if it's that.
Re: B2 dies regularly
phpmyadmin is just a dir with some php pages and no support code. It's highly unlikely to have caused this issue. But I agree on the suggested route of reinstalling from scratch.