Troubleshooting


This chapter contains a large amount of setup, but as this book is about PostNuke and not operating systems or servers, it is important to jump through the material fairly quickly. The following sections discuss some common issues you might come across.

Common Linux Issues

If you are installing MySQL and Apache on an existing Linux workstation and are having problems, you should first remove any existing MySQL or Apache packages on the system. Many Linux installations include both servers in their distribution and perform updates with the Red Hat Package Manager (now simply RPM and used with many distributions). You can get a list of existing installations using these commands:

 # rpm -qa grep | mysql # rpm -qa grep | apache 

This command searches for "mysql" or "apache" in existing package names. For relevant software found, use the following example command to remove it:

 # rpm -e mysql-3.23.58-4 

This helps clean up your system prior to installation. You might also receive warnings about dependent packages. If this is the case, you should remove those packages first.

For best results, the servers should be installed in the following order: MySQL, Apache, PHP. Wait until after installing all servers before customizing any settings.

Common Windows XP Issues

You might find that Apache 2 and PHP 4 do not work automatically after installation on Windows XP. The PHP 4 install does not make all changes to Apache's httpd.conf file, and you have to manually complete the install setup. Open the httpd.conf file and make the following additions in their respective sections:

 ScriptAlias /php/ "c:/php/" AddType application/x-httpd-php .php Action application/x-httpd-php "/php/php.exe" 

This enables PHP through Apache 2 as a Common Gateway Interface (CGI). You can also use a more complicated set of steps to set up PHP as an Apache Module. If you have any problems getting them to work together or want to see the alternatives, go to www.php.net for current documentation.

Those familiar with Windows 2000 Server web services might find it easy to use IIS, but Windows XP Professional has the same single-server limitation found in Windows 2000 Professional. You can use a workaround that allows you to run multiple servers on IIS in Windows XP Professional, but only one server can be running at a given time. From a command prompt, type the following lines:

 cd \Inetpub\AdminScripts adsutil.vbs create_vserv W3SVC/2 adsutil.vbs copy W3SVC/1 W3SVC/2 

This creates a new virtual server and seeds it with the information from the default server. Now reopen your IIS Manager console and you see two "Default Web Site" servers. You can rename the second server and change other settings, such as port, as needed. To start the additional server, simply first stop the one currently running.

Other General Troubleshooting

Remember that PostNuke is written with PHP, and all default directory files are called index.php. Be certain your web server is configured to use index.php as a valid default file when a directory is browsed, and index.php should be listed before other index files. You might also find index.html missing from the list (if you are using IIS, for example).

If you've installed a given server but can't seem to get it to work at all, check to see if it's running. A common mistake is assuming that an installed server is set up to run automatically when the OS starts up. You can check the settings by looking at the Services utility for current status and startup type.



    PostNuke Content Management
    PostNuke Content Management
    ISBN: 0672326868
    EAN: 2147483647
    Year: 2003
    Pages: 207
    Authors: Kevin Hatch

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net