After adding more instrumentation, including Apache2 processes, Apache2 CPU and a questionable MySQL CPU graph, the first spike of the last half day occurred and there is correlation between the load spikes and sudden increase in Apache2 processes:
But is is not clear what the cause is since there is no strong correlation to users, guests or bot activity. But there is some potential correlation to bot activity:
Which brings me back, full circle, suspecting rogue bot activity, again.... let's see what happens during the next spike.
we have an unix system which has
load average normally about 20.
but while i am running a particular unix batch which performs heavy
operations on filesystem and database average load
reduces to 15.
how can we explain this situation?
while running that batch idle cpu time is about %60-65... (0 Replies)
Hello all, I have a question about load averages.
I've read the man pages for the uptime and w command for two or three different flavors of Unix (Red Hat, Tru64, Solaris). All of them agree that in the output of the 2 aforementioned commands, you are given the load average for the box, but... (3 Replies)
Hello, Here is the output of top command. My understanding here is,
the load average 0.03 in last 1 min, 0.02 is in last 5 min, 0.00 is in last 15 min.
By seeing this load average, When can we say that, the system load averge is too high?
When can we say that, load average is medium/low??... (8 Replies)
Hi,
i have installed solaris 10 on t-5120 sparc enterprise.
I am little surprised to see load average of 2 or around on this OS.
when checked with ps command following process is using highest CPU. looks like it is running for long time and does not want to stop, but I do not know... (5 Replies)
Hello AlL,..
I want from experts to help me as my load average is increased and i dont know where is the problem !!
this is my top result :
root@a4s # top
top - 11:30:38 up 40 min, 1 user, load average: 3.06, 2.49, 4.66
Mem: 8168788k total, 2889596k used, 5279192k free, 47792k... (3 Replies)
Hi ,
I am using 48 CPU sunOS server at my work.
The application has facility to check the current load average before starting a new process to control the load.
Right now it is configured as 48. So it does mean that each CPU can take maximum one proces and no processe is waiting.
... (2 Replies)
Hi,
I am getting a high load average, around 7, once an hour. It last for about 4 minutes and makes things fairly unusable for this time.
How do I find out what is using this. Looking at top the only thing running at the time is md5sum.
I have looked at the crontab and there is nothing... (10 Replies)
Here we go....
Preface:
..... so in a galaxy far, far, far away from commercial, data sharing corporations.....
For this project, I used the ESP-WROOM-32 as an MQTT (publish / subscribe) client which receives Linux server "load averages" as messages published as MQTT pub/sub messages.... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT DEBIAN
apache2::porting
libapache2-mod-perl2-2.0.7::docs::api::Apache2::porting(User Contributed Perl Documentlibapache2-mod-perl2-2.0.7::docs::api::Apache2::porting(3pm)NAME
Apache2::porting -- a helper module for mod_perl 1.0 to mod_perl 2.0 porting
Synopsis
# either add at the very beginning of startup.pl
use Apache2::porting;
# or httpd.conf
PerlModule Apache2::porting
# now issue requests and look at the error_log file for hints
Description
"Apache2::porting" helps to port mod_perl 1.0 code to run under mod_perl 2.0. It doesn't provide any back-compatibility functionality,
however it knows to trap methods calls that are no longer in the mod_perl 2.0 API and tell what should be used instead if at all. If you
attempts to use mod_perl 2.0 methods without first loading the modules that contain them, it will tell you which modules you need to load.
Finally if your code tries to load modules that no longer exist in mod_perl 2.0 it'll also tell you what are the modules that should be
used instead.
"Apache2::porting" communicates with users via the error_log file. Everytime it traps a problem, it logs the solution (if it finds one) to
the error log file. If you use this module coupled with "Apache2::Reload" you will be able to port your applications quickly without
needing to restart the server on every modification.
It starts to work only when child process start and doesn't work for the code that gets loaded at the server startup. This limitation is
explained in the Culprits section.
It relies heavily on "ModPerl::MethodLookup". which can also be used manually to lookup things.
Culprits
"Apache2::porting" uses the "UNIVERSAL::AUTOLOAD" function to provide its functionality. However it seems to be impossible to create
"UNIVERSAL::AUTOLOAD" at the server startup, Apache segfaults on restart. Therefore it performs the setting of "UNIVERSAL::AUTOLOAD" only
during the child_init phase, when child processes start. As a result it can't help you with things that get preloaded at the server
startup.
If you know how to resolve this problem, please let us know. To reproduce the problem try to use an earlier phase, e.g.
"PerlPostConfigHandler":
Apache2::ServerUtil->server->push_handlers(PerlPostConfigHandler => &porting_autoload);
META: Though there is a better solution at work, which assigns AUTOLOAD for each class separately, instead of using UNIVERSAL. See the
discussion on the dev list (hint: search the archive for EazyLife)
See Also
mod_perl 2.0 documentation.
Copyright
mod_perl 2.0 and its core modules are copyrighted under The Apache Software License, Version 2.0.
Authors
The mod_perl development team and numerous contributors.
perl v5.14.2 2011-02-08 libapache2-mod-perl2-2.0.7::docs::api::Apache2::porting(3pm)