I tried to shutdown FreeSWITCH a few days ago and afterwards I then noted that swap increased drastically on 1st page and there was a large amount of FreeSWITCH related stuff in system log. I didn't take more detailed notice of the contents. I then noted, earlier today, that I now have almost all tabs in FreeSWITCH GUI yielding 404:s.
I then removed FreeSWITCH from package manager.
rebooted
Checked imspector status: RED
Can't start it, again.
reboot again
still cant start imspector
So, imspector won't start due to libiconv.so.3 missing and pkg_info | grep libiconv yields response: "libiconv-1.11_1".
Your symptoms of loosing files could be explained by failing data storage (Hard Drive, or Compact Flash.)
========
Adding:
And trying: "pkg_add -r libiconv" yields error about URLs being incorrect for both http and ftp for the FreeBSD 7.0 version.. files not available it says.
========
If you are using 1.2.1, 1.2.2 they are FreeBSD 7.0. I suggest that you use pfSense 1.2.3 RC1 because it is running FreeBSD 7.1 and has security patches as well as additional fixes that you will benefit from.
. Why is packages obviously ripping shared files or configs pointers being used by others? This is not the first time I've seen this.
The package does add files to /usr/local/lib but does not remove them on when the package is removed because I don't know if some other package is dependent on them.
Is FreeSWITCH to blame here somehow?
I don't think so.
Am I sitting with a mix of older version configs of FreeSWITCH causing this?
I mix of older configs being stored in the pfsense config can make it harder to get working.
The configs that could cause problems is the pages that use textareas.
How do I make sure absolutely everything related to FreeSWITH is removed from the system? One would think it should be possible to remove enough so that a perfectly clean re-install of this (or any other package) is possible?
The correct process to upgrade is:
1. Backup the package from the status page
2. Remove the package. The settings for packages persist in the config.xml.
3. Then install the package again.
When the package is removed it does the following.
exec("killall -9 freeswitch");
unlink_if_exists("/usr/local/pkg/freeswitch.xml");
unlink_if_exists("/usr/local/pkg/freeswitch.inc");
unlink_if_exists("/usr/local/pkg/freeswitch_dialplan.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_extensions.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_external.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_internal.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_modules.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_public.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_vars.xml");
exec("rm -R /usr/local/freeswitch/");
exec("rm -R /usr/local/www/freeswitch/");
exec("rm -R /usr/local/www/packages/freeswitch/");
unlink_if_exists("/usr/local/etc/rc.d/freeswitch.sh");
unlink_if_exists("/tmp/freeswitch.tar.gz");
unlink_if_exists("/tmp/pkg_mgr_FreeSWITCH.log");
Also I think I may have misunderstood some of the config, and turning to guides online can be a bit confusing since they often tend to target installations without any GUI components, only directly editing config files. Are such guides relevant 100% to pfSense version of FreeSWITCH?
This documentation is related to the pfSense FreeSWITCH package interface.
http://doc.pfsense.org/index.php/FreeSWITCH#IP_address_or_DomainStandard FreeSWITCH documentation that is related to the config.
http://wiki.freeswitch.org/wiki/Main_PageOne thing to note about the pfSense FreeSWITCH interface is that the names used are the same names in the config. The GUI gives you paths to the config files that are being edited. The goal of this interface is to make it easier to setup FreeSWITCH and at the same time educate the user. Making it possible for the knowledge gained from the config or the interface would be as interchangeable as possible.
When installing FreeSWITCH in pfSense, the config options of editing XML directly and using the nice GUI to manually adding/editing stuff - which is the case on several tabs - is either of them optional or not etc, this is not apparent from GUI and I guess some errors are present in some installations if XML is not edited at all?
You can install the package and not use the GUI if desired. Or you can use the GUI and still modify xml files that the GUI does not use.
I don't get the feeling that it's clear whether or not editing the GUI is just another way of editing the XML or not.
GUI reads the pfSense config for information and then writes certain xml files but does not write every single xml file. It starts with a default configuration and the GUI modifies areas that are noted in the GUI.
pfSense Forum
