- When troubleshooting the web interface, helpful information is often in your web server's error log.
- Internet Explorer will not work with Freeside's HTML interface.
Netscape,
Lynx, and
Emacs/W3,
among others, should work fine.
- If bin/svc_acct.import fails with an "Out of memory!" error using MySQL, upgrede MySQL and recompile the Perl DBD. There was a memory leak in some older versions of MySQL.
- If you get tons of errors in your web server's error log like this:
Ambiguous use of value => resolved to "value" =>
at /usr/lib/perl5/site_perl/File/CounterFile.pm line 132.
This clutters up your log files but is otherwise harmless. Upgrade to the latest File::CounterFile.
- If you get an Internal Server Error when adding or editing, but find that the update has occured, and you get something like the following in your web server's error log:
access to /your/path/edit/process/some_table.cgi failed for
machine.domain.tld, reason: malformed header from script.
Bad header=HTTP/1.0 302 Moved Temporarily
Then you forgot to apply this patch as mentioned in the New Installation section of the documentation.
- If you get errors like this:
UID.pm: Can't open /var/spool/freeside/conf/secrets: Permission denied
at /your/path/site_perl/FS/UID.pm line 26.
BEGIN failed--compilation aborted at
/your/path/edit/process/part_svc.cgi line 15.
Then the scripts are not running setuid freeside. If you were editing
the files, it is possible you inadvertantly removed the setuid bit.
As mentioned in the New Installation section of the documentation, set ownership and permissions for the web interface. Your system should support secure setuid scripts or Perl's emulation, see perlsec: Security Bugs for information and workarounds.
cd /usr/local/apache/htdocs/freeside
chown -R freeside .
chmod 4755 browse/*.cgi edit/*.cgi edit/process/*.cgi misc/*.cgi misc/process/*.cgi search/*.cgi view/*.cgi
- If you receive `can not connect to server' errors using MySQL on a system that doesn't support native threading, you may need to specify the full hostname in your DBI datasource. See the MySQL documentation, DBI manpage and the DBD::mysql manpage for details.