Comments on: Follow-up: Digium AA50 Reboot Issues — A Temporary Work-around http://www.keycruncher.com/blog/2009/11/09/follow-up-digium-aa50-reboot-issues-a-temporary-work-around/ Eclectic Commentary on Technology & Business by Dennis Little Wed, 25 Jan 2012 18:33:15 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Brad http://www.keycruncher.com/blog/2009/11/09/follow-up-digium-aa50-reboot-issues-a-temporary-work-around/comment-page-1/#comment-75695 Brad Tue, 10 Jan 2012 05:54:55 +0000 http://www.keycruncher.com/blog/?p=141#comment-75695 Can you share your trick for using the lan on aa50. Can you share your trick for using the lan on aa50.

]]> By: Dennis Little http://www.keycruncher.com/blog/2009/11/09/follow-up-digium-aa50-reboot-issues-a-temporary-work-around/comment-page-1/#comment-62329 Dennis Little Wed, 28 Sep 2011 13:13:00 +0000 http://www.keycruncher.com/blog/?p=141#comment-62329 Hi Oscar, I wonder if you are using the latest firmware for the AA50, v2.0.0.6? We recently upgraded to this version and the problem seems to be titrated quite a lot. We have not been running this version long enough in the field to tell if the random reboot issue completely went away, but I can tell you that the system is no longer spontaneously rebooting at 1-2 day intervals. Regarding cron on the AA50: I have never been able to get cron on the AA50 to behave properly and I am unsure if this is a AA50 or BusyBox limitation; I am unsure that cron is intended to work on the AA50. Most of the filesystem on the AA50 is volatile, meaning that it is reset to a fixed state upon reboot. To be honest, I have never spent enough time working on the AA50's cron capabilities to know if it stores crontab permanently on the flash or in the volatile RAM. If the case is the latter, your crontab would be erased after the first reboot. In my case, I already had another Linux computer remote to the AA50 and that is where the cron job to reboot the AA50 was running from. I needed some advanced functionality I was not sure BusyBox would support as well, so it made sense for my particular install. I would try out the latest firmware though (2.0.0.6 from Digium) and see if that does not resolve your problem. One point of note: The system I upgraded was no longer under service contract with Digium when the firmware was released. Because I had the problem from the very beginning, Digium agreed to give me the firmware without a support contract, but they could not offer any further support without starting a new contract. I knew what I was doing on the system, so it was a fair compromise for me. If you find you need a hand getting upgraded, please feel free to ping me. -Dennis Hi Oscar,

I wonder if you are using the latest firmware for the AA50, v2.0.0.6?

We recently upgraded to this version and the problem seems to be titrated quite a lot. We have not been running this version long enough in the field to tell if the random reboot issue completely went away, but I can tell you that the system is no longer spontaneously rebooting at 1-2 day intervals.

Regarding cron on the AA50:

I have never been able to get cron on the AA50 to behave properly and I am unsure if this is a AA50 or BusyBox limitation; I am unsure that cron is intended to work on the AA50. Most of the filesystem on the AA50 is volatile, meaning that it is reset to a fixed state upon reboot. To be honest, I have never spent enough time working on the AA50′s cron capabilities to know if it stores crontab permanently on the flash or in the volatile RAM. If the case is the latter, your crontab would be erased after the first reboot.

In my case, I already had another Linux computer remote to the AA50 and that is where the cron job to reboot the AA50 was running from. I needed some advanced functionality I was not sure BusyBox would support as well, so it made sense for my particular install.

I would try out the latest firmware though (2.0.0.6 from Digium) and see if that does not resolve your problem.

One point of note: The system I upgraded was no longer under service contract with Digium when the firmware was released. Because I had the problem from the very beginning, Digium agreed to give me the firmware without a support contract, but they could not offer any further support without starting a new contract. I knew what I was doing on the system, so it was a fair compromise for me.

If you find you need a hand getting upgraded, please feel free to ping me.

-Dennis

]]> By: Oscar D http://www.keycruncher.com/blog/2009/11/09/follow-up-digium-aa50-reboot-issues-a-temporary-work-around/comment-page-1/#comment-62288 Oscar D Wed, 28 Sep 2011 03:39:04 +0000 http://www.keycruncher.com/blog/?p=141#comment-62288 Thanks for sharing this information, we too have been experienced these issues. We would like to implement this procedure, but our AA50 will accept the cron job but it never triggers the script.. By looking into the log (/var/log/messages) file, we see the call to the script but we always get this message "crond couldn't fork(), user root". We added the cron job and created the script with as root , so It shouldn't be a permissions issue. Do you have any idea why our cron job does not execute the script? 20 14 * * * /usr/script.sh nor 20 14 * * * echo "save this" > test.log Thanks in advance. Thanks for sharing this information, we too have been experienced these issues. We would like to implement this procedure, but our AA50 will accept the cron job but it never triggers the script.. By looking into the log (/var/log/messages) file, we see the call to the script but we always get this message “crond couldn’t fork(), user root”. We added the cron job and created the script with as root , so It shouldn’t be a permissions issue. Do you have any idea why our cron job does not execute the script?
20 14 * * * /usr/script.sh
nor
20 14 * * * echo “save this” > test.log
Thanks in advance.

]]> By: Wade Waltman http://www.keycruncher.com/blog/2009/11/09/follow-up-digium-aa50-reboot-issues-a-temporary-work-around/comment-page-1/#comment-12144 Wade Waltman Tue, 09 Mar 2010 12:12:32 +0000 http://www.keycruncher.com/blog/?p=141#comment-12144 Thanks for sharing all this information. I have experienced the same issues as mentioned in your posts. This has allowed me to "band-aid" my AA50 install as well. Also, I wanted to mention that a Digium tech did indicate in an e-mail that the base AA50 system was being upgraded, but isn't expected to be released for months. Hopefully this base upgrade will resolve these particularly major issues. Again; thanks for the invaluable information to keep my AA50 in a closer to production state! Thanks for sharing all this information. I have experienced the same issues as mentioned in your posts. This has allowed me to “band-aid” my AA50 install as well. Also, I wanted to mention that a Digium tech did indicate in an e-mail that the base AA50 system was being upgraded, but isn’t expected to be released for months. Hopefully this base upgrade will resolve these particularly major issues. Again; thanks for the invaluable information to keep my AA50 in a closer to production state!

]]>