Portal Home > Knowledgebase > Articles Database > problem in apache
problem in apache
| Posted by temoinlove, 03-20-2016, 10:36 AM |
| Hello
I have problem in apache can any one help to know why this error
|
| Posted by temoinlove, 03-20-2016, 10:37 AM |
| Startup Log
Mar 20 15:07:11 server.file4down.om systemd[1]: Starting Apache webserver managed by cPanel EasyApache...
Mar 20 15:07:12 server.file4down.om systemd[1]: Started Apache webserver managed by cPanel EasyApache.
Log Messages
[Sun Mar 20 15:16:22.001947 2016] [core:notice] [pid 7106] AH00094: Command line: '/usr/local/apache/bin/httpd'
[Sun Mar 20 15:16:22.001932 2016] [mpm_prefork:notice] [pid 7106] AH00163: Apache/2.4.18 (Unix) OpenSSL/1.0.1e-fips mod_bwlimited/1.4 configured -- resuming normal operations
[Sun Mar 20 15:13:29.863397 2016] [cgi:error] [pid 8697] [client 115.231.222.14:2813] AH02811: script not found or unable to stat: /usr/local/apache/cgi-bin/common
[Sun Mar 20 15:13:24.001677 2016] [core:notice] [pid 7106] AH00094: Command line: '/usr/local/apache/bin/httpd'
[Sun Mar 20 15:13:24.001650 2016] [mpm_prefork:notice] [pid 7106] AH00163: Apache/2.4.18 (Unix) OpenSSL/1.0.1e-fips mod_bwlimited/1.4 configured -- resuming normal operations
[Sun Mar 20 15:07:13.003153 2016] [core:notice] [pid 7106] AH00094: Command line: '/usr/local/apache/bin/httpd'
[Sun Mar 20 15:07:13.003115 2016] [mpm_prefork:notice] [pid 7106] AH00163: Apache/2.4.18 (Unix) OpenSSL/1.0.1e-fips mod_bwlimited/1.4 configured -- resuming normal operations
[Sun Mar 20 15:07:12.000997 2016] [:notice] [pid 7092] ModSecurity for Apache/2.9.0 (http://www.modsecurity.org/) configured.
[Sun Mar 20 15:07:12.000921 2016] [suexec:notice] [pid 7092] AH01232: suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
|
| Posted by net, 03-20-2016, 10:39 AM |
| Moved > Hosting Security and Technology.
|
| Posted by temoinlove, 03-20-2016, 10:44 AM |
| Thanks Friend
|
| Posted by andrewn, 03-20-2016, 10:57 AM |
| What is the problem here exactly? As I see from the logs Apache restart just fine.
|
| Posted by temoinlove, 03-20-2016, 12:24 PM |
| Web site stop after half houre
Http://Media4up.com
|
| Posted by oldgrunt, 03-20-2016, 01:03 PM |
| The parent nameserver i.gtld-servers.net is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)"
"INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
217.160.82.2
217.160.80.2
217.160.83.2
217.160.81.2
You can fix this for example by adding A records to your nameservers for the zones listed above. "
Could be DNS issue, as it appears that the link is trying to resolve from here.
Fix and give it some time.
Hope this helps.
|
| Posted by temoinlove, 03-20-2016, 02:35 PM |
| every thing work good after restart apache and stop after 10 m
|
| Posted by Bitpalace, 03-20-2016, 03:13 PM |
| Aren't you starting very many instances? Could this become a resource issue for your system?
|
| Posted by temoinlove, 03-20-2016, 03:58 PM |
| I didn't think
Server Load 0.003906 (8 CPUs)
Memory Used 4.56% (1,490,120 of 32,679,364)
|
| Posted by Bitpalace, 03-20-2016, 06:06 PM |
| What is possibly happening is that the instances all sit there waiting on traffic. Then traffic comes in, e.g. a brute-force attack on a Wordpress site, trying wp-login.php over and over again. So all the sudden the load increases. What is the resource situation when the issue appears? Are the Apache instances still in the list? What is their CPU and RAM usage at that time?
|
| Posted by BugBytez, 03-20-2016, 07:37 PM |
| I would agree with @Bitpalace. I would suggest monitoring the server until the issue occurs once more. It could be a script that isn't closing properly and using up your resources. When your website stops, do you have to restart apache each time to bring it back up? If so, it may be related to the resources as suggested.
|
| Posted by DewlanceHosting, 03-21-2016, 01:57 AM |
| First time I see this type of long errors while restarting apache. You are using a any control panel like cPanel?
Maybe debug option is on so its show each logs but you can try to kill all PID, stop apache and restart.
|
| Posted by tech-for-you, 03-21-2016, 05:35 AM |
| Hi,
Do you have the error logs at the time when the apache gets stopped. This will help us to troubleshoot the error. Also just check if there is any cron setup in the server to stop apache (rare possibility).
|
Add to Favourites 
Print this Article
Also Read
