Cant dial out - database problem

rob69

Joined
Sep 19, 2010
Messages
3
Likes
0
Points
0
#1
I have a hosted server with elastix on it, i upgraded A2billing and had issues but finally got it working i fear though that i may have dropped the database for elastix and not just A2billing as i can no longer call out and calls dont register in the CDR but i can get incoming calls and they register and i can dial internally but just not externally here is a copy of the log:

[Sep 19 16:04:54] VERBOSE[19627] logger.c: -- Reloading module 'res_config_pgsql.so' (PostgreSQL RealTime Configuration Driver)
[Sep 19 16:04:54] VERBOSE[19627] logger.c: == Parsing '/etc/asterisk/res_pgsql.conf': [Sep 19 16:04:54] VERBOSE[19627] logger.c: Found
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime Host: 127.0.0.1
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime Port: 5432
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime User: asterisk
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime Password: password
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime DBName: asterisk
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: 133 connInfo=host=127.0.0.1 port=5432 dbname=asterisk user=asterisk password=password
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: 133 connInfo=host=127.0.0.1 port=5432 dbname=asterisk user=asterisk password=password
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: pgsqlConn=0x933cb58
[Sep 19 16:04:54] ERROR[19627] res_config_pgsql.c: Postgresql RealTime: Failed to connect database server asterisk on 127.0.0.1. Check debug for more info.
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime: Cannot Connect:
[Sep 19 16:04:54] WARNING[19627] res_config_pgsql.c: Postgresql RealTime: Couldn't establish connection. Check debug.
[Sep 19 16:04:54] DEBUG[19627] res_config_pgsql.c: Postgresql RealTime: Cannot Connect: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?

[Sep 19 16:04:54] VERBOSE[19627] logger.c: == Postgresql RealTime reloaded.
[Sep 19 16:04:54] VERBOSE[19627] logger.c: -- Reloading module 'cdr_csv.so' (Comma Separated Values CDR Backend)
[Sep 19 16:04:54] VERBOSE[19627] logger.c: == Parsing '/etc/asterisk/cdr.conf': [Sep 19 16:04:54] VERBOSE[19627] logger.c: Found
[Sep 19 16:04:54] DEBUG[19627] cdr_csv.c: logging time in GMT
[Sep 19 16:04:54] DEBUG[19627] cdr_csv.c: logging CDR field UNIQUEID
[Sep 19 16:04:54] DEBUG[19627] cdr_csv.c: logging CDR user-defined field

Any help would be appreciated

Robert
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#2
I have no idea how you did it but FreePBX/Elastix uses mysql and nor postgres as a database backend, you will have to undo whatever you did, if you know what you did, or probably restore from your latest "known good" backup.

sorry.
 

rob69

Joined
Sep 19, 2010
Messages
3
Likes
0
Points
0
#3
Unfortunately i don't have a backup :(
I will need to contact the host and see if they can reload just that slice as i have a server that is virtualized and split and that is one instance only, i did so much so i doubt i could back out either just thought that there may have been an easy fix that i missed!

Robert
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#4
:) the easy fix would have been to revert to your backup, I guess you learned something today. I'm sure you won't do that a again though. You might want to explore your /etc/amportal.conf file though for your AMPDBENGINE, it should be.

AMPDBENGINE=mysql

and your

a2billing.conf

for ill-advised configuration
 

rob69

Joined
Sep 19, 2010
Messages
3
Likes
0
Points
0
#5
Both are set to mySQL do i dont understand where the postgres is coming from :-(
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,915
Messages
130,920
Members
17,595
Latest member
feparra121
Top