I waited and waited, wasn't willing to find out the hard way what would happen but luck did it for me.
For some reason, the system locked up, never seen that happen before, and I had to restart sipx services from the CLI. It came right back up without a hitch. No, I didn't think of looking for the fault at the time since all I could think about was how this was going to be a day in hell so was too stressed to think clearly. When it came back up, I was so elated that I didn't think of it then either. My bad for that but cool that it came back up. Haven't rebooted the server yet so maybe there's something else waiting but I kinda doubt it. I'll run an update again soon since I've seen fixed being posted which I assume are still making it to 4.2.1. Mike On Sat, 28 May 2011 21:15:39 -0400, Gerald Drouillard wrote: > On 5/25/2011 11:11 AM, [email protected] wrote: > >> I haven't updated my 4.2.1 in a while so when doing it I get the >> following error. >> Thought I would check with the list before rebooting, just in case. >> Transaction Check Error: >> file /usr/local/freeswitch/bin/fsxs from install of sipx-freeswitch-1.0.5- >> 17188.16739.2.i386 conflicts with file from package sipx-freeswitch-1.0.5- >> 17188.16739.2.x86_64 >> > > Same problem. What worked for me was: > > > - yum update > > - (you will get the above error) > > - cd /var/cache/yum/sipxecs-stable/packages > > - /etc/init.d/sipXecs stop > > > - download the x64 versions of any 386 packages (for me it was > sipx-freeswitch and sipx-freeswitch-spidermonkey) > > > - remove the 386 packages > > > - rpm -Uvh *.rpm > > - you may get an error about sipx-freeswitch already installed. > Remove that rpm and retry the rpm -Uvh *.rpm > > > -- > Regards > -------------------------------------- > Gerald Drouillard > Technology Architect > Drouillard & Associates, Inc. > http://www.Drouillard.biz _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
