Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 09DBD11830 for ; Sat, 7 Jun 2014 13:50:05 +0000 (UTC) Received: (qmail 77045 invoked by uid 500); 7 Jun 2014 13:50:02 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 77001 invoked by uid 500); 7 Jun 2014 13:50:02 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 76991 invoked by uid 99); 7 Jun 2014 13:50:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 13:50:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [195.67.226.208] (HELO smtp-out21.han.skanova.net) (195.67.226.208) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 13:49:57 +0000 Received: from a (81.170.217.78) by smtp-out21.han.skanova.net (8.5.133) (authenticated as u18417052) id 53804BED00585699 for users@httpd.apache.org; Sat, 7 Jun 2014 15:49:35 +0200 Message-ID: <001901cf8257$50f6c930$4ed9aa51@a> From: "georg chambert" To: References: <004201cf81bc$11729370$42bee55a@a> <5392EAC5.2000400@function2form.net> Date: Sat, 7 Jun 2014 15:49:34 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01CF8268.1448AAB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users] Re: getting stuck ------=_NextPart_000_0016_01CF8268.1448AAB0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, ok, will check the logs, however it is doubtful that they will contain any clues of a system that = just stops responding. But there is some sstate (?) or someting in linux I think that can be = used to check system calls (? typically) and if those can be saved over the boot and if there is any way to find = the last entries before the halt and reboot..... And possilby find what activity was initiated, if from Apache, or = general system services that made the hickup. As to backup, yes, there is no very loss-sensitive info on the disk. And = yes, if you imply with "interresting,,," that there could be problems by just moving a disk with configuration between = computers, yes, that is relevant. And yes, the problem might arise from that, however why would it run = such long time before stalling. Well there could be some "safekeeping" activity that is scheduled with long period, that = tries to reach some of the Hw that has become missconfigured from the possible difference/missmatch in = memory/addresses that might come from just plugging=20 a configured system into another Hw. But still I would like to find = cause and find remedy. There is a bit of configuration work done in setting up the server, which would be nice not having to = repeat (lazy ? :) georgp ----- Original Message -----=20 From: Peter K=C3=BChnlein=20 To: users@httpd.apache.org=20 Sent: Saturday, June 07, 2014 12:34 PM Subject: Re: [users] Re: getting stuck Am 06.06.2014 21:18, schrieb georg chambert: Oh one more thing that might be important. The current system is = created by moving the harddrive=20 from one machine to an identical (however with somewhat different = plugged in Hw), as the first machine=20 just went out and wouldnt boot at all. So having access to a second = DellDimension5000 I just switched drive.=20 On the first machine I didnt have really the same frequency of = hickup, there it was much longer periods between downtimes.p=20 Hi George, interesting that the system is running at all... did you make backups = of the files there? You should, and on occasion do a fresh install and = put the data back in place. Meanwhile, you will find the log files at /var/log, using (as root) ls /var/log and see what is there. You should find /var/log/boot.log showing you = the last boot, and you should have /var/log/httpd/ containing some error = logs, e.g., /var/log/httpd/error_log. You can view the logs using less, e.g. less /var/log/httpd/error_log Cheers, Peter --=20 http://function2form.net http://peter-kuehnlein.net "It is unseemingly for a person to become prideful and extravagant when = things are going well." (Hagakure) ------=_NextPart_000_0016_01CF8268.1448AAB0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Hi, ok, will check the = logs,
however it is doubtful that they will = contain any=20 clues of a system that just stops responding.
But there is some sstate (?) or = someting=20 in linux I think that can be used to check system calls (?=20 typically)
and if those can be saved over the boot = and if=20 there is any way to find the last entries before the halt and=20 reboot.....
And possilby find what activity was = initiated, if=20 from Apache, or general system services that made the = hickup.
 
As to backup, yes, there is no very = loss-sensitive=20 info on the disk. And yes, if you imply with "interresting,,," = that
there could be problems by just moving = a disk with=20 configuration between computers, yes, that is relevant.
And yes, the problem might arise from = that, however=20 why would it run such long time before stalling. Well there = could
 be some "safekeeping" activity = that is=20 scheduled with long period, that tries to reach some of the Hw that has=20 become
missconfigured from the=20 possible difference/missmatch in memory/addresses that might come = from just=20 plugging
a configured system into another Hw. = But still I=20 would like to find cause and find remedy. There is a bit of=20 configuration
work done in setting up the = server, which=20 would be nice not having to repeat (lazy ? :)
 
georgp
 
 
----- Original Message -----
From:=20 Peter=20 K=C3=BChnlein
Sent: Saturday, June 07, 2014 = 12:34=20 PM
Subject: Re: [users] Re: = getting=20 stuck

Am 06.06.2014 21:18, schrieb georg=20 chambert:
Oh one=20 more thing that might be important. The current system is created by = moving=20 the harddrive
from one machine to an identical (however with = somewhat=20 different plugged in Hw), as the first machine
just went out and = wouldnt=20 boot at all. So having access to a second DellDimension5000 I just = switched=20 drive.

On the first machine I didnt have really the same = frequency=20 of hickup, there it was much longer periods between downtimes.p=20
Hi George,

interesting that = the system=20 is running at all... did you make backups of the files there? You = should, and=20 on occasion do a fresh install and put the data back in=20 place.

Meanwhile, you will find the log files at /var/log, = using (as=20 root)
ls /var/log
and see what is there. You should find=20 /var/log/boot.log showing you the last boot, and you should have=20 /var/log/httpd/ containing some error logs, e.g.,=20 /var/log/httpd/error_log.
You can view the logs using less, = e.g.
less=20 /var/log/httpd/error_log

Cheers,
Peter
--=20

http://function2form.net
http://peter-kuehnlein.net

"It is unseemingly for a person to become prideful and extravagant when =
things are going well."
(Hagakure)
------=_NextPart_000_0016_01CF8268.1448AAB0--