Ticket #2206 (closed Bugs: worksforme)

Opened 5 years ago

Last modified 3 years ago

Error: Did not receive valid response from server

Reported by: razametal Assigned to: gregmac
Priority: minor Milestone: 2.4
Component: Web interface Version: 2.3-branch
Keywords: freepbx error Cc:
Confirmation: Need Feedback SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version:

Description

Option "Continue with reload" that appear after pressing the "Apply Configuration Changes" gives me the following error:

Error: Did not receive valid response from server

The changes are not being updated for this reason. The FreeBPX version used is 2.3.0beta2.

Change History

08/03/07 09:21:23 changed by p_lindheimer

  • confirmation changed from Unreviewed to Need Feedback.

you need to provide what version of framework you are running as well as specific asterisk version (please do a show version or core show version from the CLI and put that in the ticket. And check the FreePBX System Status page for any notifications. This is not necessarily an error, it usually implies inability to access the server.

08/03/07 14:04:46 changed by razametal

sip*CLI> show version Asterisk 1.4.9 built by root @ sip on a i686 running Linux on 2007-08-01 17:01:55 UTC

Core setup 2.3.0beta2.3.2 Feature Code Admin setup 1.0.5.1 FreePBX Framework setup 2.3.0beta2.8 System Dashboard tool 0.2.5.2

System Uptime: 2 days, 9 hours, 45 minutes Asterisk Uptime: 5 hours, 7 minutes Last Reload: 0 minutes

FreePBX Notices

*

Cronmanager encountered 1 Errors Delete this The following commands failed with the listed error /var/lib/asterisk/bin/module_admin listonline (255) Added 1 week, 3 days, 6 hours, 29 minutes ago (cron_manager.EXECFAIL)

*

Could not reload FOP server Could not reload the FOP operator panel server using the bounce_op.sh script. Configuration changes may not be reflected in the panel display. Added 4 days, 3 hours, 46 minutes ago (freepbx.reload_fop)

*

symlink from modules failed

08/04/07 08:38:33 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to worksforme.

update to the latest framework and core, and them make sure that your permissions are such that you are not getting teh symlink from modules failed error (retrieve_conf needs to symlink several files that are included with modules, particularly core).

If you are still having problems, go to /var/lib/asterisk/bin and change to user asterisk and then run ./retrieve_conf and take a look at the output to see what other messages you are getting.

For now closing as worksforme as we have plenty of people running on 1.4 without problems. If you continue to encounter problems, try the IRC and forum first and if approriate after seeking help, reopen the bug but include additional info like the output from retrieve_conf, thanks.

08/04/07 09:47:05 changed by razametal

Hi, thank you for your response.

Plesae check the output of retriveve_conf :

sip:/var/lib/asterisk/bin# su asterisk sip:~/bin$ ./retrieve_conf

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 Added to globals: ASTETCDIR = /etc/asterisk Added to globals: ASTMODDIR = /usr/lib/asterisk/modules Added to globals: ASTVARLIBDIR = /var/lib/asterisk Added to globals: ASTAGIDIR = /var/lib/asterisk/agi-bin Added to globals: ASTSPOOLDIR = /var/spool/asterisk Added to globals: ASTRUNDIR = /var/run/asterisk Added to globals: ASTLOGDIR = /var/log/asterisk Added to globals: CWINUSEBUSY = true Added to globals: AMPMGRUSER = admin Added to globals: AMPMGRPASS = amp111 Please update your modules and reload Asterisk by visiting http://192.168.0.1/admin

Check the following picture of the error:

http://farm2.static.flickr.com/1114/1009840185_32fcac0347_o.png

All the asterisk directory have permission 777 and the owner is asterisk and www-data.

Thank you for the help.

Guillermo.

08/05/07 16:51:46 changed by razametal

Updated to 2.3.0beta2.3.4 and now all works fine.

Thank you very much.

05/13/09 11:14:49 changed by acumensystems

We've found this still exists in the Parking Lot module using Asterisk 1.6 and FreePBX 2.5.1.5. The $parken variable (shown in the first comment) is not initialised leading to the error shown. Disabling parking lot module resolves this problem.