More Problems: When I check for software updates under the system menu I receive the following errors on that page:
Error communicating with host Error encountered while checking for updates / updating The package information was last updated Nov 2, 2009 11:35 AM. Could not determine system's version I'm also receiving a ton of error messages in the job status log. Below is an example: File replication: sipxpark-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: orbits.xml 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: sipxpresence-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: sipxivr.properties 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: autoattendants.xml 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: sipxrls-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: resource-lists.xml 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: mediaserver-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: voicemail.xml 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: voicemail-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: status-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: status-plugin.xml 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: callresolver-config 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: sipxpage.properties 11/2/09 11:38 AM 11/2/09 11:38 AM Failed File replication: phonelog-config 11/2/09 11:38 AM 11/2/09 11:39 AM Failed File replication: config-agent.properties 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipxacd-config 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipxbridge.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: freeswitch.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipX_context.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipX_profile.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: xml_rpc.conf.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: modules.conf.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: switch.conf.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: logfile.conf.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: local_stream.conf.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: nattraversalrules.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: alarm-config.xml 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: registrar-config 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipXproxy-config 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipXproxy-config 11/2/09 11:39 AM 11/2/09 11:39 AM Failed File replication: sipXproxy-config 11/2/09 11:39 AM 11/2/09 11:39 AM Failed Josh McDonald | Systems Administrator | Brammo, Inc. Email: [email protected] | www.brammo.com 550 Clover Lane | Ashland, OR 97520 Phone: 541.482.9555 ext. 339 | Mobile: 541.531.0005 | Fax: 541.552.0414 MCSA 2003 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Josh McDonald Sent: Monday, November 02, 2009 12:00 PM To: [email protected] Subject: [sipx-users] Problems after upgrade from 3 to 4.02 I'm encountering several issues after upgrading from 3 to 4.02. All of the services listed under the System > Server tab show as undefined and cannot be restarted or modified in any way. If I attempt to restart the services I receive the following error message: Error performing operations on services from host: sipx.brammo.main Also I'm receiving ruby errors via email. Below is an example: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize': Connection refused - connect(2) (Errno::ECONNREFUSED) from /usr/lib/ruby/1.8/net/http.rb:560:in `open' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/timeout.rb:48:in `timeout' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/lib/ruby/1.8/soap/netHttpClient.rb:115:in `start' from /usr/lib/ruby/1.8/soap/netHttpClient.rb:92:in `post' from /usr/lib/ruby/1.8/soap/streamHandler.rb:170:in `send_post' from /usr/lib/ruby/1.8/soap/streamHandler.rb:109:in `send' from /usr/lib/ruby/1.8/soap/rpc/proxy.rb:170:in `route' from /usr/lib/ruby/1.8/soap/rpc/proxy.rb:141:in `call' from /usr/lib/ruby/1.8/soap/rpc/driver.rb:178:in `call' from /usr/lib/ruby/1.8/soap/rpc/driver.rb:232:in `getCallHistory' from /usr/lib/ruby/gems/1.8/gems/sipXconfig-report-1.0.0/lib/report.rb:34:in `run' from /usr/bin/sipxconfig-report:133 Any Ideas? Josh McDonald | Systems Administrator | Brammo, Inc. Email: [email protected] | www.brammo.com 550 Clover Lane | Ashland, OR 97520 Phone: 541.482.9555 ext. 339 | Mobile: 541.531.0005 | Fax: 541.552.0414 MCSA 2003 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Weigel, Stefan Sent: Monday, November 02, 2009 1:20 AM To: 'dan'; [email protected] Subject: Re: [sipx-users] yum problem Hi Dan, just check your files under /etc/yum.repos.d/. After I had to handle this bug I had to reinstall the the original release* package, which sipxecs-release-4.0.2.rpm was replacing. It overwrites the /etc/issue, /etc/redhat-release so yum functionality wasn't given. On CentOS 5.4 reinstall the centos-release-5-4.el5.centos.1 Best regards Stefan ----------------------------------------------- Stefan Weigel Advanced IT-Professional Tel.: +49 89 2000 48 975 Fax: +49 89 2000 48 566 eMail: [email protected] Allianz Automotive Services GmbH Einsteinring 28 85609 Aschheim Germany http://www.allianz-warranty.com Geschäftsführung: Andreas Rösing, Horst Ziegler Amtsgericht München, HRB 175682 Für Umsatzsteuerzwecke: Ust-ID-Nr.: DE 262 617 720 ----------------------------------------------- -----Ursprüngliche Nachricht----- Von: dan [mailto:[email protected]] Gesendet: Sonntag, 1. November 2009 00:17 An: [email protected] Betreff: [sipx-users] yum problem I just tried to do a yum update and found that I couldn't because it failed to find any repos for 5.2. I remember that there was a lengthy thread about the 4.0.2 upgrade breaking yum, but I didn't know that it had bit me until now. Here's some relevant info about my system (from memory, so might not be entirely correct). - originally installed from the 4.0.0 iso - upgraded periodically using yum update - I don't remember doing anything to customize Centos repos - system was at Centos 5.3 before it broke Now yum is pointing to the Centos 5.2 repos which have been deprecated and no longer exist. Question: Is there a way to repair my system, or will I need to re-install? -- Dan McDaniel [email protected] Key fingerprint = E295 0313 A68F B6D6 FF33 DE51 27F2 9B91 F68A 1241 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
