Lonnie,
I'll "upgrade" Runnix, double check the ver and Xver files, in hopes of getting
back in sync.
Thanks for the reminder about the different repos. We were upgrading from
0.7.10/Asterisk 1.8 so used the http://mirror.astlinux.org/ast18-firmware-1.x
repo.
Really, I wasn't trying to tempt fate!
Dan
-----Original Message-----
From: "Lonnie Abelbeck" <li...@lonnie.abelbeck.com>
Sent: Monday, January 16, 2012 2:12pm
To: "AstLinux Users Mailing List" <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] AstLinux 1.01 Released
Dan,
Yes, there are also /oldroot/cdrom/ver and /oldroot/cdrom/Xver files that need
swapped if you went under the hood and swapped the runnix files.
Probably the safest is to do now is a Runnix "upgrade" via the System tab to
get the latest RUNNIX for that 0.7.10 AstLinux version, and then ignore what
the "previous" RUNNIX is displayed until you do a "upgrade-RUNNIX-image upgrade
http://mirror.astlinux.org/runnix4"; when you want to give 1.0.1 a try again.
Both AstLinux 0.7.x and 1.0.x can use either Asterisk 1.4 or Asterisk 1.8, that
is your choice, but are different images, different repos.
If your 0.7.10 is Asterisk 1.4, you should upgrade to AstLinux 1.0.1 using the
"http://mirror.astlinux.org/firmware-1.x"; to use Asterisk 1.4.
If at a later date you want to upgrade to Asterisk 1.8, you can do that within
the 1.0.x series. One step at a time, please. :-)
Lonnie
On Jan 16, 2012, at 12:48 PM, d...@ryson.org wrote:
> Lonnie,
>
> Thanks for coming to my rescue (yet again).
>
> I wonder if by not using the proper method to revert to runnix-0.4, I've
> managed to get the Web Interface out of sync. When I ask it to Show
> Installed, I get this reply:
>
> Current version is: runnix-0.4-5339, Previous saved version is: runnix-0.3.3
>
> However, I suspect I'm running the older runnix, since the first thing logged
> was use of Busybox v1.12.4.
>
> At this point, shall I use the System tab to "Revert to Previous" to get back
> in sync? At this point, I'm not sure which version "Previous" is referring
> to. I'd like to revert to runnix-0.3.3 but that's what I'm running.
>
> Thanks for agreeing to take a look at the log. I'll send it to you shortly.
>
> Sorry, I'm not sure what you meant by this question, "Is is possible you
> upgraded to a different version of Asterisk than you had previously?" But
> perhaps this will answer it:
>
> • I had been running 0.7.10.
> • I changed the Repository URL in the Web interface to this:
> • http://mirror.astlinux.org/ast18-firmware-1.x
> • When I clicked "Check for New" firmware, I was advised that I was
> running 0.7.10 and new version 1.0.1 was available.
> • After reverting to previous and checking "Show Installed", I now get
> this:
> • Current version is: astlinux-0.7.10, Previous saved version is:
> astlinux-1.0.1
> • However, from the CLI, I verified that Asterisk 1.8.7.1 is operating.
> Isn't that what is supposed to be in 1.0.0? Specifically, core show version
> reveals this:
> • Asterisk 1.8.7.1 built by dhartman @ centos32 on a i686 running Linux
> on 2011-10-18 03:34:39 UTC
>
> Dan
>
>
> -----Original Message-----
> From: "Lonnie Abelbeck" <li...@lonnie.abelbeck.com>
> Sent: Monday, January 16, 2012 12:28pm
> To: "AstLinux Users Mailing List" <astlinux-users@lists.sourceforge.net>
> Subject: Re: [Astlinux-users] AstLinux 1.01 Released
>
> Hi Dan,
>
> The proper method to revert to runnix-0.3 from runnix-0.4 after you upgraded
> was to simply use the System tab ->
>
> RUNNIX Bootloader Upgrade:
>
> [ Revert to Previous ] - Runnix - _x_ Confirm
>
> If you did the above at the same time you reverted from AstLinux 1.0.1 to
> AstLinux 0.7.10 in the System tab all would have been good.
>
> In your case, when you reverted to AstLinux 0.7.10 and were able to boot via
> "xrunnix" you could have also used the same System tab method to make it
> stick.
>
> Tom's suggestion should only be used as a last resort, ie, when AstLinux
> can't be booted because of a RUNNIX / AstLinux mismatch.
>
> Back to your original issue...
>
> It seems to me your hardware is being recognized properly by AstLinux 1.0.1,
> since you booted and SSH and HTTPS worked.
>
> Feel free to privately email your logs to me, that would help.
>
> Is is possible you upgraded to a different version of Asterisk than you had
> previously?
>
> Lonnie
>
>
>
> On Jan 16, 2012, at 9:20 AM, d...@ryson.org wrote:
>
> > 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, 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.
> ------------------------------------------------------------------------------
> 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.
------------------------------------------------------------------------------
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.------------------------------------------------------------------------------
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.
