PDA

View Full Version : Unable to connect to remote asterisk



fsinetworks
10-14-11, 01:54 PM
With two warp pika asterisk i have the same problem. With telnet command asterisk -rvvvvv i have the error message
Unable to connect to remote asterisk ( does /var/run/asterisk/asterisk.ctl exist ?)

But i can connect by http and i use the command cli by freepbx.

Have you a solution ?

Best Regards,
Fabien

fsinetworks
10-15-11, 09:18 AM
Also I click on the button "Show Channels" of the menu "Warp System Administration" in FreePBX, i have the follow message :
WARP Channel Status

Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

Best Regards,
Fabien

mrecoskie
10-17-11, 08:18 AM
Sounds like Asterisk is failing. Can you confirm Asterisk is started successfully?
First I would suggest checking 'dmesg' to see if there are any errors. Also ensure you are starting asterisk/freepbx with the 'amportal start' command.

fsinetworks
10-18-11, 02:20 AM
Hi,

Yes asterisk is running on the two pika warp .
I included the dmesg in a file.

Best Regards,
Fabien

fsinetworks
10-20-11, 11:10 AM
How to resolve these problems, may be to reinstall the system but how, be careful with the problem attended transfer ?

Best Regards,
Fabien

mrecoskie
10-20-11, 11:10 AM
Perhaps the AMI interface is not working? Have you changed anything in manager.conf?
Could you also include '/var/log/messages' from the unit?

fsinetworks
01-04-12, 01:02 PM
my /var/log/messages is

Jan 4 08:15:53 warp syslog.info syslogd exiting
Jan 1 00:01:20 warp user.info kernel: [ 121.588908] kjournald starting. Commit interval 5 seconds
Jan 1 01:01:20 warp user.warn kernel: [ 121.608596] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 1 01:01:20 warp user.info kernel: [ 121.621375] EXT3 FS on mmcblk0p1, internal journal
Jan 1 01:01:20 warp user.info kernel: [ 121.626278] EXT3-fs: recovery complete.
Jan 1 01:01:21 warp user.info kernel: [ 121.873795] EXT3-fs: mounted filesystem with writeback data mode.
Jan 1 01:01:31 warp user.warn kernel: [ 132.038826] pikalcd: lcd_init_module
Jan 4 09:18:22 warp user.warn kernel: [ 137.680279] pikahsp: module license 'PIKA Technologies Inc.' taints kernel.
Jan 4 09:18:22 warp user.warn kernel: [ 137.687343] Disabling lock debugging due to kernel taint
Jan 4 09:18:22 warp user.warn kernel: [ 137.714183] PIKA HSP Starting. HZ=1000.
Jan 4 09:18:22 warp user.info kernel: [ 137.721219] pikacore: registered 253.0
Jan 4 09:18:22 warp user.info kernel: [ 137.783085] taco: FPGA 00F13011
Jan 4 09:18:22 warp user.info kernel: [ 137.786325] Modules A: FXO B: empty
Jan 4 09:18:26 warp user.warn kernel: [ 138.299400] Performing Calibration. Please wait.
Jan 4 09:18:26 warp user.warn kernel: [ 140.864808] Calibration Complete.
Jan 4 09:18:26 warp user.info kernel: [ 141.015972] pikacore: registered 253.1
Jan 4 09:18:26 warp user.info kernel: [ 141.140448] Zapata Telephony Interface Registered on major 196
Jan 4 09:18:26 warp user.info kernel: [ 141.146344] Zaptel Version: 1.4.9.2
Jan 4 09:18:26 warp user.warn kernel: [ 141.149866] Zaptel Echo Canceller: MG2
Jan 4 09:18:26 warp user.warn kernel: [ 141.507874] pkdummy: init() finished
Jan 1 00:01:00 warp user.info kernel: [ 101.162312] kjournald starting. Commit interval 5 seconds
Jan 1 01:01:00 warp user.warn kernel: [ 101.177139] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 1 01:01:00 warp user.info kernel: [ 101.189902] EXT3 FS on mmcblk0p1, internal journal
Jan 1 01:01:00 warp user.info kernel: [ 101.194800] EXT3-fs: recovery complete.
Jan 1 01:01:00 warp user.info kernel: [ 101.201857] EXT3-fs: mounted filesystem with writeback data mode.
Jan 1 01:01:10 warp user.warn kernel: [ 111.602203] pikalcd: lcd_init_module
Jan 4 10:14:07 warp user.warn kernel: [ 117.953307] pikahsp: module license 'PIKA Technologies Inc.' taints kernel.
Jan 4 10:14:07 warp user.warn kernel: [ 117.960372] Disabling lock debugging due to kernel taint
Jan 4 10:14:07 warp user.warn kernel: [ 117.987216] PIKA HSP Starting. HZ=1000.
Jan 4 10:14:07 warp user.info kernel: [ 117.994434] pikacore: registered 253.0
Jan 4 10:14:07 warp user.info kernel: [ 118.056266] taco: FPGA 00F13011
Jan 4 10:14:07 warp user.info kernel: [ 118.059504] Modules A: FXO B: empty
Jan 4 10:14:11 warp user.warn kernel: [ 118.585405] Performing Calibration. Please wait.
Jan 4 10:14:11 warp user.warn kernel: [ 121.150849] Calibration Complete.
Jan 4 10:14:11 warp user.info kernel: [ 121.295273] pikacore: registered 253.1
Jan 4 10:14:11 warp user.info kernel: [ 121.422496] Zapata Telephony Interface Registered on major 196
Jan 4 10:14:11 warp user.info kernel: [ 121.428404] Zaptel Version: 1.4.9.2
Jan 4 10:14:11 warp user.warn kernel: [ 121.431919] Zaptel Echo Canceller: MG2
Jan 4 10:14:11 warp user.warn kernel: [ 121.790051] pkdummy: init() finished

fsinetworks
01-04-12, 01:23 PM
Hi mrecoskie,


The Asterisk server status is error in the FreePBX System Status. I shut down the pika warp without success.
Therefore no alternative to it is no longer reachable by phone.
I think the only solution is to upgrade to the last version with an usb key.
How to make this please with the problem of the attended transfer ?

Best Regards,
Fabien SEUX

PS: The telephony is a tool vital for this customer.

mrecoskie
01-04-12, 03:41 PM
If you are using 2.2.7 have you tried the following package?
ftp://ftp.pikatech.com/outgoing/customercare/xferpatch227.tgz

fsinetworks
01-04-12, 05:35 PM
Hi mrecoskie,

i don't know why that is the version 2.2.7.
Is it possible an automatic upgrade by internet ?
The only upgrade by an usb key it was the time so as to fix the problem with the attended transfer
http://forum.pikatechnologies.com/showthread.php?609-Problem-with-attended-transfer

Best Regards,
Fabien.

fsinetworks
01-05-12, 04:46 AM
Hi mrecoskie,

Today, I upgraded with an usb key with this patch but i have the same problem. I think i have to restore the pika warp, how to make it ?

Best regards,
Fabien

mrecoskie
01-05-12, 09:47 AM
Before reformatting the box and losing your configuration you may want to try the following commands.


amportal stop
pikacf (answering the questions presented)
/persistent/autorun/S65freepbx

fsinetworks
01-05-12, 10:55 AM
Unfortunately, doesn't work i have the following messages error :



STARTING ASTERISK
1024
Unable to open pid file '/var/run/asterisk/asterisk.pid': No space left on device
Unable to bind socket to /var/run/asterisk/asterisk.ctl: No space left on device
Logger Warning: Unable to open log file '/var/log/asterisk/messages': No space left on device
Logger Warning: Unable to open log file '/var/log/asterisk/full': No space left on device
[Jan 5 16:04:20] ERROR[3042]: logger.c:609 init_logger: Unable to create event log: No space left on device
Asterisk ended with exit status 1
Asterisk died with code 1.
cat: can't open '/var/run/asterisk/asterisk.pid': No such file or directory
Automatically restarting Asterisk.
killall: mpg123: no process killed
Unable to open pid file '/var/run/asterisk/asterisk.pid': No space left on device
Unable to bind socket to /var/run/asterisk/asterisk.ctl: No space left on device
Logger Warning: Unable to open log file '/var/log/asterisk/messages': No space left on device
Logger Warning: Unable to open log file '/var/log/asterisk/full': No space left on device
[Jan 5 16:04:21] ERROR[3047]: logger.c:609 init_logger: Unable to create event log: No space left on device
Asterisk ended with exit status 1
Asterisk died with code 1.
cat: can't open '/var/run/asterisk/asterisk.pid': No such file or directory
Automatically restarting Asterisk.
killall: mpg123: no process killed
Unable to open pid file '/var/run/asterisk/asterisk.pid': No space left on device
Unable to bind socket to /var/run/asterisk/asterisk.ctl: No space left on device
Logger Warning: Unable to open log file '/var/log/asterisk/messages': No space left on device
Logger Warning: Unable to open log file '/var/log/asterisk/full': No space left on device
[Jan 5 16:04:24] ERROR[3055]: logger.c:609 init_logger: Unable to create event log: No space left on device
Asterisk ended with exit status 1
Asterisk died with code 1.
cat: can't open '/var/run/asterisk/asterisk.pid': No such file or directory
Automatically restarting Asterisk.

I prefer reformatting the box and losing my configuration but after have a clean box.
How to make this, please ?

Best Regards,
Fabien

fsinetworks
01-08-12, 03:18 PM
Hi mrecoskie,

i reformated my asterisk warp with your file recovery.tgz and upgraded to version 2.2.7 xferpatch

BusyBox v1.10.3 (2011-04-01 13:49:52 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/persistent/root # image_versions
version-u-boot = u-boot-1.3.0-95:1282575924
version-fpga = 3.0.1.1:1271345381
version-kernel = 2.6.31.7-7:1287762492
version-persistent = 2.2.7-3:1287762494
version-persistent1 = 2.2.7-3:1287762494
version-persistent2 = 2.2.7-3:1287762495
version-ramdisk = 2.2.7-3-xferpatch:1301681692
/persistent/root #
/persistent/root #
I will test.

Best Regards,
Fabien