Hi Dan
If you SSH to the box, you can swap the runnix and xrunnix files:
/oldroot/cdrom/runnix
/oldroot/cdrom/runnix.img
/oldroot/cdrom/Xrunnix
/oldroot/cdrom/Xrunnix.img
That should mean that it will reboot without intervention. I’ve had to go
through the same process for live box of ours.
Hope this helps
Tom
From: d...@ryson.org [mailto:d...@ryson.org]
Sent: 16 January 2012 15:21
To: AstLinux Users Mailing List
Cc: AstLinux Users Mailing List (astlinux-users@lists.sourceforge.net)
Subject: Re: [Astlinux-users] AstLinux 1.01 Released
AstLinux Team,
Thank your for your tireless efforts. I know it's often said, but it truly
bears repeating.
I also appreciate the clear, unambiguous upgrade instructions
<http://doc.astlinux.org/userdoc:upgrade-0.7> , which I followed explicitly
when making the effort to upgrade from 0.7.10 to 1.0.1. Everything was going
according to the instructions until I rebooted. My first indication that
things hadn't gone well came from the Web Interface, which revealed a number of
failed registrations. ("Registration Sent" was shown for all providers under
SIP Trunk Registrations.)
Further investigation revealed many pages of Notices, Warnings, and Errors in
the log. There are too many to list here, but I saved the file and would
gladly forward it to one or more developers by private e-mail. Although I was
able to access the machine by SSH and HTTPS, it was apparent that much of the
trouble impacted network functionality. Even a PING to one of our providers
didn't work. No IP address was revealed, suggesting we were having trouble
with DNS resolution. I regret that I wasn't able to do more troubleshooting; I
was anxious to get the unit back in service.
Because the web interface was working, I used it to revert to 0.7.10 and
reboot. However, the hardware didn't successfully boot. A check of the local
monitor suggested (I think) that Runnix 0.4 wasn't compatible with 0.7.10.
After entering "xrunnix" at the local console, everything seems to be working
as it had before - under Runnix 0.3.3 & AstLinux 0.7.10.
My immediate concern is that I'd like to get the hardware to a point where
it'll survive a power failure without trying to boot into the new version of
Runnix or AstLinux. While we don't experience many power failures and the PBX
is on a big, fat UPS, Murphy's Law dictates that any power failure will occur
the next time I'm out-of-town or otherwise unavailable. Until a solution is
found, can you tell me how to temporarily remove the new versions of Runnix and
AstLinux? That would be very helpful.
Of course, it might also be nice to figure out what's causing this trouble -
just in case it impacts other users. Also, while AstLinux 0.7.10 is working
perfectly for my present purposes, I'd prefer to not be stuck-in-time.
By the way, there's a significant likelihood that this problem is a result of
some hardware incompatibility, which I've had before with this machine. It's a
HP DC7300, 1.8 GHz Pentium Dual Core Blade Workstation with 512 MB RAM.
Previously, earlier AstLinux versions wouldn't load from the SATA
Drive-on-module. That was solved quite some time ago and doesn't seem to be
the case now. Also, it appears that both NICs are being detected and drivers
are being loaded.
Thanks in advance for everyone's thoughts and advice.
Dan
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
