Hi All,
Today I installed ecs-3.11.5-008715-013249-i386.iso using iso image.
I ran into same issue! However, after the second reboot sipXivr came up.
Following are the events that occurred while installing the build.
1. Installed ecs-3.11.5-008715-013249-i386.iso ( Using ISO not rpm ) and
rebooted the machine. (This is the first reboot as soon as the initial
configuration is done ). This reboot resulted in the FAILURE of
Freeswitch parameter.
2. Then I set the log levels and RESTARTED the machine. The sipXivr
FAILED this time as well. The restart status was shown as;
[EMAIL PROTECTED] etc]# /etc/init.d/sipxpbx restart
Stopping apache:
Stopping sipXpbx:
Stopping: sipxsupervisor
Stopping: freeswitch
Stopping: sipregistrar
Stopping: sipstatus
Stopping: sipxacd
Stopping: sipxbridge
Stopping: sipxcallresolver-agent (Not started)
Stopping: sipxcallresolver
Stopping: sipxconfig-agent
Stopping: sipxconfig
Stopping: sipxivr (Started but not running)
Stopping: sipxpage
Stopping: sipxpark
Stopping: sipxpresence
Stopping: sipXproxy
Stopping: sipxrelay
Stopping: sipxrls
Stopping: sipXvxml
Confirm Stop: sipxsupervisor [ OK ]
Confirm Stop: freeswitch [ OK ]
Confirm Stop: sipregistrar [ OK ]
Confirm Stop: sipstatus [ OK ]
Confirm Stop: sipxacd [ OK ]
Confirm Stop: sipxbridge [ OK ]
Confirm Stop: sipxcallresolver-agent (Not started) [ OK ]
Confirm Stop: sipxcallresolver [ OK ]
Confirm Stop: sipxconfig-agent [ OK ]
Confirm Stop: sipxconfig [ OK ]
Confirm Stop: sipxivr (Not started) [ OK ]
Confirm Stop: sipxpage [ OK ]
Confirm Stop: sipxpark [ OK ]
Confirm Stop: sipxpresence [ OK ]
Confirm Stop: sipXproxy [ OK ]
Confirm Stop: sipxrelay [ OK ]
Confirm Stop: sipxrls [ OK ]
Confirm Stop: sipXvxml [ 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 configuration service hostname and address: [ OK ]
Checking /tmp directory has correct permissions: [ OK ]
Checking sipxsupervisor: [ OK ]
Checking freeswitch: [ OK ]
Checking sipregistrar: [ OK ]
Checking sipstatus: [ OK ]
Checking sipxacd: [ OK ]
Checking sipxbridge: [ OK ]
Checking sipxcallresolver-agent: (Disabled) [ OK ]
Checking sipxcallresolver: [ OK ]
Checking sipxconfig-agent: [ OK ]
Checking sipxconfig: [ OK ]
Checking sipxivr: [FAILED]
Checking sipxpage: [ OK ]
Checking sipxpark: [ OK ]
Checking sipxpresence: [ OK ]
Checking sipXproxy: [ OK ]
Checking sipxrelay: [ OK ]
Checking sipxrls: [ OK ]
Checking sipXvxml: [ OK ]
sipXpbx:
sipXpbx: sipXpbx configuration problems found:
sipXpbx:
sipXpbx: Check sipxivr
sipXpbx: ==== /etc/sipxpbx/autoattendants.xml:
sipXpbx: Not readable.
sipXpbx: ==== /etc/sipxpbx/validusers.xml:
sipXpbx: Not readable.
sipXpbx:
Attempting to start despite configuration problems
Starting sipXpbx:
Starting sipxsupervisor: [ OK ]
Starting httpd: [ OK ]
[EMAIL PROTECTED] etc]#
[EMAIL PROTECTED] etc]# /etc/init.d/sipxpbx status
Checking sipxsupervisor: [ OK ]
Checking freeswitch: [ OK ]
Checking sipregistrar: [ OK ]
Checking sipstatus: [ OK ]
Checking sipxacd: [ OK ]
Checking sipxbridge: [ OK ]
Checking sipxcallresolver-agent: [Disabled]
Checking sipxcallresolver: [ OK ]
Checking sipxconfig-agent: [ OK ]
Checking sipxconfig: [ OK ]
Checking sipxivr: [FAILED]
Checking sipxpage: [ OK ]
Checking sipxpark: [ OK ]
Checking sipxpresence: [ OK ]
Checking sipXproxy: [ OK ]
Checking sipxrelay: [ OK ]
Checking sipxrls: [ OK ]
Checking sipXvxml: [ OK ]
[EMAIL PROTECTED] etc]#
3. Then I logged into the Config UI and set all log levels to DEBUG.
Then I REBOOTED the machine from back end. This time ( i.e. on second
reboot ) the sipXivr parameter came up and the status showed up and running.
4. While the sipXivr FAILED, there ware three core dumps from
Freeswitch. Cores dumps were stopped once the sipXivr came up. I got one
alarm mail for Alarm SPX00006 saying,
Alarm Text: Process sipXivr was found in a non-running state, and failed MAX
restarts. Process cannot be restarted!
Suggested Resolution: If the process is required, check logs for more details.
6. After second reboot the sipXivr was up and running.
Is sipxivr still under development. If not, can we go ahead and have
adhoc features testing with ecs-3.11.5-008715-013249-i386.iso build.
Please suggest.
-Akshata
Andy Spitzer wrote:
Woof!
On Tue, 19 Aug 2008 17:37:45 -0400, Marden P. Marshall <[EMAIL PROTECTED]>
wrote:
On Aug 19, 2008, at 5:00 PM, Scott Lawrence wrote:
This is probably because autoattendants.xml is marked as a %config file
in the rpm - so a new rpm will not overwrite one that has been modified.
So any modified autoattendant won't be updated to match the new
schema.
Actually no, the file is not installed by the RPM.
-Mardy
Whew! For a moment there I thought I screwed that up. autoattendants.xml
is only generated by sipXconfig. There is no "default" version checked in
anywhere. sipXconfig is supposed to generate one, and sipXivr isn't
supposed to start until such time as that file appears.
--Woof!
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
