[asterisk-bugs] [AsteriskNOW and Packages 0017442]: After the AsteriskNOW 1.7.0 yum update chan_sip and pbx_config could not initialize
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jun 2 15:29:26 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17442
======================================================================
Reported By: vmikhelson
Assigned To: qwell
======================================================================
Project: AsteriskNOW and Packages
Issue ID: 17442
Category: Installer Issues
Reproducibility: have not tried
Severity: major
Priority: normal
Status: assigned
JIRA:
======================================================================
Date Submitted: 2010-06-02 03:46 CDT
Last Modified: 2010-06-02 15:29 CDT
======================================================================
Summary: After the AsteriskNOW 1.7.0 yum update chan_sip and
pbx_config could not initialize
Description:
Applied AsteriskNow 1.7.0 via yum update. Updated modules in FreePBX as
instructed.
Asterisk is not functional as the dialplan and the SIP configuration fail
to load.
======================================================================
----------------------------------------------------------------------
(0122844) vmikhelson (reporter) - 2010-06-02 15:29
https://issues.asterisk.org/view.php?id=17442#c122844
----------------------------------------------------------------------
Ran yum update. Received a bunch of errors and warnings.
Qwell, is there anything I have to do at this point?
The screen log is below:
Resolving Dependencies
--> Running transaction check
---> Package freepbx.i386 0:2.7.0-3_centos5 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository
Size
================================================================================
Updating:
freepbx i386 2.7.0-3_centos5 asterisk-current
6.1 M
Transaction Summary
================================================================================
Install 0 Package(s)
Upgrade 1 Package(s)
Total download size: 6.1 M
Is this ok [y/N]: y
Downloading Packages:
freepbx-2.7.0-3_centos5.i386.rpm | 6.1 MB
00:38
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : freepbx
1/2
Starting httpd:
Starting MySQL: [ OK ]
STARTING ASTERISK
Asterisk Started
Checking for PEAR DB..OK
Checking for PEAR Console::Getopt..OK
Checking user..OK
Checking if Asterisk is running..running with PID: 5074..OK
Checking for /etc/amportal.conf..OK
Reading /etc/amportal.conf..OK
Checking for /etc/asterisk/asterisk.conf..OK
Reading /etc/asterisk/asterisk.conf..OK
Using asterisk as PBX Engine
Checking for Asterisk version..1.6.2.7
Connecting to database..OK
Checking current version of AMP..2.7.0
Installing new FreePBX files..OK (663 files copied, 0 skipped)
Configuring install for your
environment..amportal..fpbx..freepbx_engine..done
apply username/password changes to conf files..sed: can't read
/etc/asterisk/cdr _odbc.conf: No
such file or directory
sed: can't read /etc/asterisk/cdr_odbc.conf: No such file or directory
done
creating missing #include files..OK
No such module 'manager'
No such command 'reload manager' (type 'core show help reload' for other
possibl e commands)
OK
Setting permissions on files..OK
Checking for upgrades..No upgrades found
Generating AMP configs..
Generating Configurations.conf, (if Asterisk is not running, you will get
an err or
In case of error, start Asterisk and hit the red bar in the GUI to
generate the Configurations.conf
files
This account is currently not available.
Generating AMP configs..OK
Restarting Flash Operator Panel..OK
Checking recordings..
Wed, 02 Jun 2010 15:25:35 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:35 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
checking for fcode field..already exists
checking for fcode_pass field..already exists
Module recordings successfully installed
Wed, 02 Jun 2010 15:25:44 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:44 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
The following error(s) occured:
- Module recordings is already enabled
installed
Checking infoservices..
Wed, 02 Jun 2010 15:25:45 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:45 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Module infoservices successfully installed
Wed, 02 Jun 2010 15:25:48 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:48 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
The following error(s) occured:
- Module infoservices is already enabled
installed
Checking featurecodeadmin..
Wed, 02 Jun 2010 15:25:50 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:50 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Module featurecodeadmin successfully installed
Wed, 02 Jun 2010 15:25:53 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:53 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
The following error(s) occured:
- Module featurecodeadmin is already enabled
installed
Checking voicemail..
Wed, 02 Jun 2010 15:25:54 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Wed, 02 Jun 2010 15:25:54 -0500 - Unable to connect to manager
127.0.0.1:5038 (1 11): Connection
refused
Module voicemail successfully installed
Wed, 02 Jun 2010 15:25:57 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Wed, 02 Jun 2010 15:25:57 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
The following error(s) occured:
- Module voicemail is already enabled
installed
Checking framework..
Wed, 02 Jun 2010 15:25:59 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Wed, 02 Jun 2010 15:25:59 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
The following error(s) occured:
- Module framework cannot be enabled
enabled
Checking music..
Wed, 02 Jun 2010 15:26:00 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Wed, 02 Jun 2010 15:26:00 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Module music successfully installed
Wed, 02 Jun 2010 15:26:03 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Wed, 02 Jun 2010 15:26:03 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
The following error(s) occured:
- Module music is already enabled
installed
Checking dashboard..
Wed, 02 Jun 2010 15:26:04 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Wed, 02 Jun 2010 15:26:04 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Module dashboard successfully installed
Wed, 02 Jun 2010 15:26:06 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
Wed, 02 Jun 2010 15:26:06 -0500 - Unable to connect to manager
127.0.0.1:5038 (111): Connection refused
The following error(s) occured:
- Module dashboard is already enabled
installed
Checking customappsreg..
Module customappsreg successfully installed
The following error(s) occured:
- Module customappsreg is already enabled
installed
Checking core..
Checking if directdids need migrating..already done
updating zap callgroup, pickupgroup..not needed
checking for delay_answer field ..already exists
checking for pricid field ..already exists
Checking for Global var RECORDING_STATE..Already exists!
Checking if trunk table migration required..not needed
Checking if trunks_dialpatterns table exists..already exists
Checking if privacy manager options exists..already exists
Module core successfully installed
The following error(s) occured:
- Module core is already enabled
installed
Please update your modules and reload Asterisk by visiting
http://172.17.137.11/admin
*************************************************************************
* Note: It's possible that if you click the red 'Update Now' bar BEFORE *
* updating your modules, your machine will start dropping calls. Ensure *
* that all modules are up to date BEFORE YOU CLICK THE RED BAR. As long *
* as this is observed, your machine will be fully functional whilst the *
* upgrade is in progress. *
*************************************************************************
SETTING FILE PERMISSIONS
Permissions OK
STARTING ASTERISK
Asterisk is already running
STARTING FOP SERVER
FOP server is already running
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. extensionstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event
'extensionstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. extensionstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event
'extensionstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. extensionstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event
'extensionstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. extensionstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event
'extensionstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:19 -0500 - Got event.. extensionstatus
Wed, 02 Jun 2010 15:26:19 -0500 - No event handler for event
'extensionstatus'
Error(s) have occured, the following is the retrieve_conf output:
exit: 1
Checking for PEAR DB..OK
Checking for PEAR Console::Getopt..OK
Checking for /etc/amportal.conf ..OK
Bootstrapping /etc/amportal.conf ..OK
Parsing /etc/amportal.conf ..OK
Parsing /etc/asterisk/asterisk.conf ..OK
Connecting to database..OK
Connecting to Asterisk manager interface..OK
Wed, 02 Jun 2010 15:26:28 -0500 - Got event.. peerstatus
Wed, 02 Jun 2010 15:26:28 -0500 - No event handler for event 'peerstatus'
Wed, 02 Jun 2010 15:26:28 -0500 - Got event.. registry
Wed, 02 Jun 2010 15:26:28 -0500 - No event handler for event 'registry'
[FATAL] Failed to get engine_info retreive_conf failed to get engine
information and cannot configure u p a softwitch with out
it. Error: ERROR-UNABLE-TO-PARSE
odbcinst: Driver installed. Usage count increased to 2.
Target directory is /etc
Cleanup : freepbx
2/2
MySQL usage count has been reduced to 1
odbcinst: DSN removed (if it existed at all). ODBC_BOTH_DSN was used as
the search path.
The FreePBX uninstallation procedure is non-existent. You will need to
manually remove left-over files .
Updated:
freepbx.i386 0:2.7.0-3_centos5
Complete!
[root at pbx sbin]#
Issue History
Date Modified Username Field Change
======================================================================
2010-06-02 15:29 vmikhelson Note Added: 0122844
======================================================================
More information about the asterisk-bugs
mailing list