Hi Pete,
We've seen these processes from time to time (both on the SE and
pool nodes). Stopping them manually and restarting httpd usually sorts
things out. I don't think a new kernel should of itself cause any
problems, but rebooting the SE after 9 months uptime is always
potentially risky (for example: are there any manual changes which won't
be picked up at boot time?).
Cheers,
John
On 07/08/2017 10:12, Peter Gronbech wrote:
> Hi All,
>
> Oxford is failing the http://wlcg-sam-atlas.cern.ch/templates/ember/#/plot?group=ATLAS_Cloud_UK&profile=ATLAS_HTTP
> The (DPM) se head node has not run out of space and the load is not high.
> As I'm pretty rusty I'm inclined to just give it a reboot as it's been up 283 days.
>
> This may bring it up with a new Kernel and could cause new problems of course, any suggestions?
>
> I can see 4 of the following processes
> /usr/sbin/httpd.event -k graceful
>
> Which look like it's failing to restart httpd, (There is a cron job that looks like it restarts it every 6 hours)
>
> Thanks Pete
>
|