:
13-08-2010 15:48
Subject:
Re: [sipx-users] GUI upgrade 4.2 - 4.2.1 fails silently
Sent by:
sipx-users-boun...@list.sipfoundry.org
no argument from me. too much that doesn't see unless it spans a
shell in a browser and logs it for you automatically.
The update from browser might
I have a 4.2 system, installed from ISO (or possibly upgraded from 4.0.4, it
was installed by a predecessor). The GUI tells me I should upgrade to 4.2.1.
When I try and do this, it does it's dependency checking, spends a while
downloading packages, then says it's rebooting. Doesn't seem like
1. Make sure your repo is one of these, meaning delete the one that is there
and put this one in.
http://download.sipfoundry.org
2. DO NOT invoke the upgrade from the GUI, do a yum update from the console.
3. Make sure you do a yum clean all first.
On Fri, Aug 13, 2010 at 9:01 AM, Jesse
Thanks Tony. Frustratingly, I don't have remote shell access so will try this
out when I'm next in the office (or when I otherwise gain remote access).
Cheers
On 13/08/2010, at 10:36 PM, Tony Graziano wrote:
1. Make sure your repo is one of these, meaning delete the one that is there
and
Even though the gui has it, it can be problematic. Do yourself a favor and
do it from an ssh client and log the console output (I always do on a
production system) in the event there are any issues.
The gui doesn't give you the ability to deal with any errors that might come
up in connecting.
On Fri, Aug 13, 2010 at 9:16 AM, Tony Graziano
tgrazi...@myitdepartment.net wrote:
The gui doesn't give you the ability to deal with any errors that might come
up in connecting. It's nice to have, but I NEVER USE IT, as raw messages are
not visible.
+1
I would recommend we remove the update
no argument from me. too much that doesn't see unless it spans a shell in a
browser and logs it for you automatically.
The update from browser might have been better designed to act as a firmware
update. grab the tgz (or whatever the entire package would have been),
downloaded it, expanded it,
That's good to know not to bother with the GUI updater.
I've now got remote shell access, hoorah.
So, currently /etc/yum.repos.d contains many CentOS sections, I assume I leave
all those and just replace the [sipXecs-stable] section at the end of the file
with the following (from