I think you need to blank the database. If this is the case, do both an
export and backup.

Never import superamin (my rule), and consider blanking all the user pins
since they will be tied to the wrong domain.

There might be another way, but this works for me. You do have a lot to
recreate though.

I've never seen an easy way to change the domain name. Is there a working
method?
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

----- Original Message -----
From: [email protected]
<[email protected]>
To: sipx-users <[email protected]>
Sent: Thu May 06 17:39:07 2010
Subject: [sipx-users] 8443 won't come up after domain name change

I'm at a loss so thought I would post for some help.

I changed the domain name of a sipx 4.2 server.
I ran sipxecs-setup and did it there as well.
I rebooted the server and used the following commands to check if everything
is running.

[r...@uc ~]# /etc/init.d/sipxecs status
Checking sipxsupervisor:                                   [  OK  ]

[r...@uc ~]# /etc/init.d/sipxecs configtest
Checking bootstrap setup:                                  [  OK  ]
Checking TLS/SSL configuration:                            [  OK  ]
Checking Per-process file descriptor limits:               [  OK  ]
Checking rpm configuration file updates:                   [  OK  ]
Checking SELinux is not enforcing:                         [  OK  ]
Checking Apache configuration:                             [  OK  ]
Checking hostname is fully qualified:                      [  OK  ]
Checking localhost address configured:                     [  OK  ]
Checking localhost name is not shared:                     [  OK  ]
Checking /tmp directory has correct permissions:           [  OK  ]
Checking sipxsupervisor:                                   [  OK  ]

[r...@uc ~]# sipxproc -l
{"FreeSWITCH"=>"Running",
 "sipXmrtg"=>"Running",
 "SipXrest"=>"Running",
 "SipXopenfire"=>"Disabled",
 "sipXrecording"=>"Running",
 "SIPRegistrar"=>"Running",
 "sipXprovision"=>"Running",
 "ParkServer"=>"Running",
 "ConfigAgent"=>"Disabled",
 "CallResolver"=>"ConfigurationTestFailed",
 "ACDServer"=>"Disabled",
 "SIPStatus"=>"Running",
 "ConfigServer"=>"ConfigurationTestFailed",
 "CallResolver-Agent"=>"Disabled",
 "SipXbridge"=>"Failed",
 "sipXivr"=>"Running",
 "PageServer"=>"Running",
 "PresenceServer"=>"Disabled",
 "ResourceListServer"=>"Running",
 "SipXrelay"=>"Running",
 "SIPXProxy"=>"Running",
 "SharedAppearanceAgent"=>"Running"}

I see config Config test failed which is normal since I can't get into the
GUI to change anything. I did however change the named files to reflect the
changes as well.

I then ran  /usr/bin/ssl-cert/gen-ssl-keys.sh to change any ssl certs that
might be on the system. Rebooted, still can't get into the system.

The only thing I can think of that I might have messed up is that I used a
global text finder/replacer to replace the old domain name all the way from
/. Perhaps this is why the GUI is not coming up?

In the logs, I see...

2010-05-06 16:33:10.544360 [ERR] switch_core_sqldb.c:670 SQL ERR [database
disk image is malformed]
2010-05-06 16:33:10.646367 [CRIT] switch_core_sqldb.c:878 SQL thread unable
to commit transaction, records lost!

The web server does appear to be running. What else can I look for in
finding the answer?

Mike



_______________________________________________
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/

Reply via email to