Scenario 2: Troubleshoot a Configuration Problem

Estimated Time: 10 minutes

Background: The San Francisco Web site (http://hostname:8011) is not displaying correctly when you try to access it, and you suspect a configuration error. Use Moonlight to investigate the configuration error. Once you have determined the cause of the problem, use Moonlight to fix it.

If you are not logged in to Moon Portal, do so now. See Starting Moonlight.

To investigate and repair the configuration error

1. Click the Alerts tab to return to the Alerts page.



2. There is one alert remaining on the SanFrancisco server.




Moonlight has detected differences in content and file properties, and some extra files when it was auditing the SanFrancisco server using the Apache Model.

3. Click the Details link for the Apache Model alert.








4. The Status Details report appears.
   
   
   



1. The report shows that someone has made changes to the Apache configuration file, httpd.conf. Moonlight diffs the content of the file, so you can see exactly what changes were made. In this case, someone has changed the HTTP port and the location of the document root.



2. Also, it looks like the Web site content has been tampered with (in the /html directory). Someone has changed the mode (file permissions) on an image file, causing the home page to display without the image.



3. Someone also has created a new directory (/new_site) in the Web server's document root, and added a new home page (index.html). This is an extra file that does not belong here.



5. Click the Report link at the top of the page to see a different view of this information.
   
   
   



1. This report shows the list of files and directories that have been altered on the target.



2. For each file or directory that has a problem, Moonlight shows the file properties that it detected as being different from the model (or master copy).



3. Use the column headings to sort the report by a particular file property.



6. Click Go next to the Fix Target option in the drop-down menu.



7. On the Fix Target page, select the Delete extra files on target check-box, and click Distribute.



8. Moonlight fixes the changed files on the target, removes the extra files, restarts the Apache server, and returns you to the Alerts page.



9. The alert on the SanFrancisco server is now cleared. If you still see the alert, the operation is still in progress. Refresh the page (CTRL + R).




Note: If the alert has not cleared, you may have forgotten to delete the extra files when you fixed the target. Repeat steps 6-9.

10. Now, access the San Francisco Web server to make sure it was fixed and restarted properly.




Solaris Users: The Moonlight evaluation version of Apache uses RedHat rather than Solaris binaries, so you cannot start the Apache server on Solaris. To verify the distribution, open the San Francisco index.html file on disk to verify that it is correct, where <MOON_HOME> is the location where the Moonlight evaluation is installed:

<MOON_HOME>/4.0.0-EVAL/eval/SanFrancisco/html/index.html 

 

Linux Users: Type the following URL in your browser, where hostname is the machine where the Moonlight evaluation is installed:


http://hostname:8011 

11. The San Francisco home page displays.



12. Click the back button on your browser to return to Moon Portal.

Highlights

Move on to Scenario 3: Deploy to a new Location.