I'd like to make sure I can detail how it should work compared to the way I've always done this. Normally I run setup after all updates, it "should" eliminate steps to stop services, update, start or reboot and streamline in place upgrades,etc.
I'll send the logs in the morning. I am going to build both 32 and 64 bit systems because I think there is still a homer issue with the 32 bit version. ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! On Aug 15, 2012 9:11 PM, "Douglas Hubler" <[email protected]> wrote: > > > On Wed, Aug 15, 2012 at 3:29 PM, Tony Graziano < > [email protected]> wrote: > >> OK. So I installed the ISO, but escaped the setup script and did a yum >> update, then reboot. Ran the setup script the first time. >> >> Upon login I saw this: >> >> Configuration generation 8/15/12 3:16 PM 8/15/12 3:16 PM FailedInternal >> Error Could not get JDBC Connection; nested exception is >> java.sql.SQLException: Connections could not be acquired from the >> underlying database! >> >> >> >> If I resend profile to the server, it comes up again. So I thought it >> might be a simple socket binding issue and shut down services and rebooted >> since the configuration had been made. Even though I had run the setup, the >> script came back up again on reboot. This is by design, and what I am >> trying to do is lay the groundwork for "how" one should: >> >> 1. Install and update from ISO. >> 2. Restore a working configuration from a 4.4 system. >> >> I want to create a wiki page accordingly, but I keep running into the >> above error. Any issues with "how" I got to "here? Also, after I enable >> services I get : >> >> Configuration generation 8/15/12 3:27 PM 8/15/12 3:27 PM FailedInternal >> Error null >> >> I also still get sipxhomer dead but pid file exists (still) on a fresh >> install. >> > > > This is embarrassing that you're having so much trouble. > > Normally you do not have to about out of setup script and update first, > but i don't think that is your problem. sipxconfig.log will tell us more > on these errors, can you send it? > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
