
Appendices 167
7. Reconfigure authentication as desired.
Web manager stops responding
If the Web Manager stops responding you can perform the following procedure to restart the
Apache web server.
To restart the Web Manager:
1. Enter the
http -k start command as shown in the following screen example.
2. Enter the
ps command with the -ef option and look for a line with apache, as shown in the
following screen example.
If a line like the bottom line in the previous screen example appears, the web application
successfully restarted.
Firmware image is corrupted
Information in Boot file location on page 200 gives an administrator who knows the root password
enough background to be able to boot from an alternate image if the need arises and if the Web
Manager is not available.
Network boots are recommended for troubleshooting only. For example, if you want to test a new
release of the firmware to make sure a problem is fixed, or if the removable Flash memory becomes
corrupted, you could download the firmware to a tftpboot server. After you test the image and
replace the Flash, if needed, you can then save the firmware image to the removable Flash using the
create_cf command.
You can use the create_cf command when troubleshooting problems with the boot image, as
described under To upgrade to a boot image from a network boot: on page 204.
[root@MergePoint5224 root]# /usr/local/apache2/bin/httpd -k start
[root@MergePoint5224 /root]# ps
-fe | grep apache
10131 nobody 3864 S /usr/local/apache2/bin/httpd -k start
Komentarze do niniejszej Instrukcji