Apache error-In-line case

Apache Error -in-line caseTime: 2010-10-25 16:29 Source: Unknown Author: Night Click: 217 times Below is a netizen about Apache wrong row, to everyone very useful oh, 51 open source specially posted to everyone. I share these 2 TS cases in order to allow students to work in the TS, not blindly, there are steps to do, and at one end of time to master their own TS technology. TS is not like other technical work, the key is the methodology, so the first to collect problems

Here is a netizen about Apache row wrong pass, to everybody very useful oh, 51 open source specially posted to everybody. I share these 2 TS cases in order to allow students to work in the TS, not blindly, there are steps to do, and at one end of time to master their own TS technology. TS Unlike other technical work, the key is the methodology, so the first time to collect symptoms and before the adjustment of the data, and then the problem in mind to have a set of processing steps, of course, it is best to write down, you specify the processing method is your usual work accumulated experience to tell you, you are not born, So each time you make a successful TS you will step forward. First, server Apache service up after a few minutes will automatically shut down Symptoms: 1, run/ETC/INIT.D/HTTPD status View Apache status show no process, but PID file exists 2, run/ETC/INIT.D/HTTPD start, not successful 3, run/etc/init.d/httpd Restart, start successfully, but the service will be down in a few minutes 4, the Apache Access log shows 505 errors Check the wrong steps: 1, check the/var/log/messages, did not find the Apache service down information 2. View the partition that holds Apache log is not full 3, view the Apache log files in the Jserv.log reached 2G Explain: 1, log partition full cause Apache log cannot write, so service can get up, but will be down in a few 2, the Apache log for some reason can not write, also can cause the service to rise, but in a moment will be down Reason: The/var/log/httpd/jserv.log reaches 2G and cannot continue to expand. Workaround: echo 0 >/var/log/httpd/jserv.log /ETC/INIT.D/HTTPD restart Second, the server network data transmission speed can reach only 200k (originally can reach 1M) Symptoms: 1, copy data to the same network segment server, data transmission only 200k Check the wrong steps: 1, run ifconfig view collisions parameters 2, view/var/log/messages, found that the network card has been forced into Half-duplex mode 3. Use Mii-tool to view network card information error 4. Using Mii-tool to force the NIC to be full duplex mode error 5, modify the modules.conf parameters, forcing the network card for Full-duplex mode, not effective 6, look at the driver version of the network card, and other running normal server network card driver version 7, replace the switch port Explain: 1, the Ifconfig collisions parameter if has been increasing, explained the network card conflict unceasingly to increase 2, the correct mode of operation of the network card should be full duplex mode 3, the low version of the network card is also caused by the cause of abnormal work 4, causing network card conflicts, network adapters are forced to half-duplex most of the reason is driven and hardware caused by the current driver and other normal operation of the server, as well as the possible switch port is not good or calbe problem Reason: The switch port is broken. Workaround: Replace switch port