|Table of Contents|
| The server would not start, what should I do? top|
- Determine whether the server is running already. Stop the running server first.
- If you get complaints when you start the server from command line, fix the complaints.
- Take a look at the server log, which is located at $SERVER_ROOT/logs/error.log or the location you specified.
- Make sure the user who tries to start the web server has write permission to /tmp/lshttpd/, remove the /tmp/lshttpd directory if it exists already.
- Make sure all the files installed still exist. Reinstall server software if needed.
- Post a message on the forum at LiteSpeed Tech web site,
or contact our support department if you are a paid customer.
| The server crashed, what should I do? top|
| Please submit a bug report.
| I forgot my password for the web administration interface, what should I do? top|
| Please run $SERVER_ROOT/admin/misc/admpass.sh to reset the user name and password.
| Using the default installation, I get "Error 503 Service Unavailable" errors when accessing any php page? top|
- If firewall software is running on the server, first check the firewall
settings, local host should be trusted.
For example, Linux firewall IPTables should include a rule like
ALLOW INPUT from LO.
- Rebuild the PHP binary, the pre-built binary may not work in your system.
PHP 4.3.1 is recommended since PHP 4.3.2 is currently buggy using the FastCGI interface.
Use the following commands to rebuild the binary:
./configure --enable-fastcgi --with-config-file-path=../conf
cp -f sapi/cgi/php [lsws_home]/admin/fcgi-bin/admin_php
cp -f sapi/cgi/php [lsws_home]/fcgi-bin/php
- If the problem still persists, enable debug logging and submit a bug report .
Edit config file [lsws_home]/conf/httpd_config.xml, set debugLevel to 10.
Reproduce the error and compress the log file, send the compressed file to firstname.lastname@example.org
| When chroot is enabled, I cannot connect to MySQL, or my CGI scripts do not work anymore, what should I do? top|
| In a chrooted environment, all path settings should be relative to the new root directory
and all necessary dynamic libraries should be available in the chroot file system.|
- PHP usually connects to MySQL via a Unix Domain Socket mounted somewhere
inside the file system. The mount point can be configured in MySQL's configuration file,
usually located at /etc/my.cnf, with configuration entry socket=...
under [mysqld] section.
The configuration for PHP is mysql.default_socket located in php.ini,
default to /tmp/mysql.sock.
When the web server run in a chrooted environment, the PHP engine gets started by web server and
will look for MySQL's socket relative to the new root, but MySQL is not chrooted
and still uses the socket relative to the original root. So, PHP cannot connect to
MySQL any more.
The solution is to change MySQL's configuration to mount the socket relative
to the new chroot.
- In order to run dynamically linked executables in a chrooted environment,
all dynamic libraries must be available in chroot file system. Use the following
command to make sure all required libraries are copied to the /lib directory relative
to the new root,
lsws/admin/misc/chroot.sh [chroot_path] [path_to_executable]
This command should run as the "root" user.
- Some system calls rely on certain system files like /etc/passwd.
If needed, create the required directories and files under the chroot file system.
However, it is not recommended to copy the real files as the idea of chroot is
to protect those files.