Difference between revisions of "Troubleshooting"
From FusionPBX
| Line 1: | Line 1: | ||
Two main types of error occur with FusionPBX. | Two main types of error occur with FusionPBX. | ||
| + | # Error messages in FusionPBX's GUI | ||
| + | # Call behavior doesn't do what you expect. | ||
| − | + | =Error messages in FusionPBX's GUI= | |
| − | |||
| − | |||
| − | |||
| − | |||
Fatal error: Call to undefined function recording_js() in /var/www/fusionpbx/www/mod/recordings/v_recordings.php on line 40 | Fatal error: Call to undefined function recording_js() in /var/www/fusionpbx/www/mod/recordings/v_recordings.php on line 40 | ||
| − | + | *this may be because mod_spidermonkey is not loaded. See the notes on [[modules]] | |
| − | + | *it also may be because you have upgraded using the upgrade button - note that at the present time the upgrade button is unreliable - it is recommended to upgrade using svn until this is resolved. | |
| − | |||
Errors when you apply settings | Errors when you apply settings | ||
| − | + | *please see [[Apply Settings]] | |
Error number: 111 error description: connection refused no handle | Error number: 111 error description: connection refused no handle | ||
| − | + | *usually this means that freeswitch isn't started. If you are using linux try '''ps -ef |grep freeswitch''' from the command line to see if it is running. | |
| + | |||
| + | =Error messages at the FreeSWITCH command line= | ||
| + | You need to use the FreeSWITCH command line to see the error that is happenning | ||
| − | + | An essential tool for troubleshooting is the FreeSWITCH command line. See [[fs_cli]] for more information. It is probably worth noting that any error displayed at the fs_cli is not technically from FusionPBX, but because FusionPBX works on top of FreeSWITCH, errors seen there may affect functionality. You might want to look in the FreeSWITCH wiki for more information on other errors. | |
| − | An essential tool for troubleshooting is the FreeSWITCH command line. See [[fs_cli]] for more information. It is probably worth noting that any error displayed at the fs_cli is not technically from FusionPBX, but because FusionPBX | ||
Seen in fs_cli (FreeSWITCH command line interface): SQL ERR [attempt to write a readonly database] | Seen in fs_cli (FreeSWITCH command line interface): SQL ERR [attempt to write a readonly database] | ||
| − | + | *This relates to a permission problem on your machine. FreeSWITCH is unable to write to its database files located in freeswitch/db. Correct your permissions and restart freeswitch. | |
Revision as of 21:55, 9 February 2011
Two main types of error occur with FusionPBX.
- Error messages in FusionPBX's GUI
- Call behavior doesn't do what you expect.
Error messages in FusionPBX's GUI
Fatal error: Call to undefined function recording_js() in /var/www/fusionpbx/www/mod/recordings/v_recordings.php on line 40
- this may be because mod_spidermonkey is not loaded. See the notes on modules
- it also may be because you have upgraded using the upgrade button - note that at the present time the upgrade button is unreliable - it is recommended to upgrade using svn until this is resolved.
Errors when you apply settings
- please see Apply Settings
Error number: 111 error description: connection refused no handle
- usually this means that freeswitch isn't started. If you are using linux try ps -ef |grep freeswitch from the command line to see if it is running.
Error messages at the FreeSWITCH command line
You need to use the FreeSWITCH command line to see the error that is happenning
An essential tool for troubleshooting is the FreeSWITCH command line. See fs_cli for more information. It is probably worth noting that any error displayed at the fs_cli is not technically from FusionPBX, but because FusionPBX works on top of FreeSWITCH, errors seen there may affect functionality. You might want to look in the FreeSWITCH wiki for more information on other errors.
Seen in fs_cli (FreeSWITCH command line interface): SQL ERR [attempt to write a readonly database]
- This relates to a permission problem on your machine. FreeSWITCH is unable to write to its database files located in freeswitch/db. Correct your permissions and restart freeswitch.
