Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 8140 invoked from network); 19 Nov 2009 11:11:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Nov 2009 11:11:57 -0000 Received: (qmail 62722 invoked by uid 500); 19 Nov 2009 11:11:53 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 62693 invoked by uid 500); 19 Nov 2009 11:11:53 -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 62684 invoked by uid 99); 19 Nov 2009 11:11:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2009 11:11:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [195.219.75.113] (HELO smtp1.acotelsa.com) (195.219.75.113) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2009 11:11:41 +0000 Received: from dalopez (195-219-75-1.acotelsa.com [195.219.75.1]) by smtp1.acotelsa.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KTC0099SSEVDN@smtp1.acotelsa.com> for users@httpd.apache.org; Thu, 19 Nov 2009 12:11:19 +0100 (MET) Date: Thu, 19 Nov 2009 12:11:19 +0100 From: =?iso-8859-1?Q?Daniel_L=F3pez_Robles?= To: users@httpd.apache.org Message-id: <010d01ca6909$05577400$88324b0a@acotel.local> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: multipart/alternative; boundary="Boundary_(ID_D2k0igxNPBKrMXQl0RE7OQ)" X-Priority: 3 X-MSMail-priority: Normal References: <011201ca6454$aa3b3d80$88324b0a@acotel.local> <00e001ca66b9$1663c2a0$88324b0a@acotel.local> X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] [SOLVED] Apache 2.2.14 and "Allow service to interact with desktop" --Boundary_(ID_D2k0igxNPBKrMXQl0RE7OQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Hello: We found the problem.=20 We have a lot of virtual hosts, which are launching a lot of = rotatelog.exe processes, which are consuming so much memory that the = desktop heap is getting exhausted. About desktop heap: http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overvie= w.aspx By default, it seems that Windows 2003 Server x64 allows 768 KB for the = desktop heap associated with the non-interactive processes, and 20480 KB = for the desktop heap associated with the interactive processes. This = way, by allowing Apache to interact with the desktop, what we are really = achieving is giving more memory to the rotatelog.exe processes to = consume. Desktop heap is not exhausted and the problems are gone. Of = course, the problem is that this way we see a lot of cmd windows in the = desktop, because now they "are" interactive. The real solution is = changing the following registry value: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session = Manager\SubSystems\Windows The default data for this registry contains: SharedSection=3D1024,20480,768 The second value is for interactive processes, and the third value is = for the non-interactive processes, so we have to increase the third = value. Desktop heap can be monitorized with Microsoft's Desktop Heap Monitor: http://www.microsoft.com/downloads/details.aspx?familyid=3D5CFC9B74-97AA-= 4510-B4B9-B2DC98C8ED8B&displaylang=3Den#RelatedDownloads I hope this will help someone else. Best regards. Daniel ----- Original Message -----=20 From: Daniel L=F3pez Robles=20 To: users@httpd.apache.org=20 Sent: Monday, November 16, 2009 1:34 PM Subject: Re: [users@httpd] Apache 2.2.14 and "Allow service to = interact with desktop" Hello: I tried with the last httpd.exe (2.2.14) and I had the same problem: I = had to check the "Allow service to interact with desktop" checkbox in = the properties of the Apache2.2 service in order to get the Logical disk = manager working. So I change the subject of the mail. Thank you. Daniel ----- Original Message -----=20 From: Daniel L=F3pez Robles=20 To: users@httpd.apache.org=20 Sent: Friday, November 13, 2009 12:30 PM Subject: [users@httpd] Apache 2.2.11 and "Allow service to interact = with desktop" Hello: I have a weird problem with Apache and Windows 2003 Server that I = haven't been able to figure out: HP Proliant DL580 G5 Windows Server 2003 R2 Standard x64 Apache 2.2.11 With that configuration, if I double-click "My PC", "Manage" and I = go to "Disk manage", an error is given: "Unable to connect to logical = disk manager" The weird thing is that if I check the "Allow service to interact = with desktop" checkbox in the properties of the Apache2.2 service, the = problem is solved. =BF? The new problem now is that when connecting to = the machine via Terminal Server with the /console parameter, a lot of = cmd windows appear, due to the rotatelogs.=20 I hope someone could give me some clue about the dependencies = between Apache and Logical disk manager, and/or an alternative to = rotatelog.exe, in order to eliminate those annoying cmd windows. I tried = mod_log_rotate but it didn't work properly with the error log. Thank you very much. Daniel --=20 Mensaje analizado por el sistema de deteccion de virus y antispam de = ACOTEL. El=20 hecho de que dicho mensaje haya sido tratado NO excluye que pueda = contener=20 virus no catalogados a fecha de hoy.=20 ------------------------------------------------------------------=20 Message analyzed by the Antispam-Virus Detection System at ACOTEL. = The fact=20 that this message has passed analysis does not exclude the = posibility of being=20 infected by an undetected virus.=20 --=20 Mensaje analizado por el sistema de deteccion de virus y antispam de = ACOTEL. El=20 hecho de que dicho mensaje haya sido tratado NO excluye que pueda = contener=20 virus no catalogados a fecha de hoy.=20 ------------------------------------------------------------------=20 Message analyzed by the Antispam-Virus Detection System at ACOTEL. The = fact=20 that this message has passed analysis does not exclude the posibility = of being=20 infected by an undetected virus. = --Boundary_(ID_D2k0igxNPBKrMXQl0RE7OQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: quoted-printable
Hello:
 
We found the problem.
 
We have a lot of virtual hosts, which = are launching=20 a lot of rotatelog.exe processes, which are consuming so much memory = that the=20 desktop heap is getting exhausted. About desktop heap:
 
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desk= top-heap-overview.aspx
 
By default, it seems that Windows 2003 = Server x64=20 allows 768 KB for the desktop heap associated with the non-interactive=20 processes, and 20480 KB for the desktop heap associated with the = interactive=20 processes. This way, by allowing Apache to interact with the desktop, = what we=20 are really achieving is giving more memory to the rotatelog.exe = processes to=20 consume. Desktop heap is not exhausted and the problems are gone. Of = course, the=20 problem is that this way we see a lot of cmd windows in the desktop, = because now=20 they "are" interactive. The real solution is changing the following = registry=20 value:
 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session = Manager\SubSystems\Windows
 
The default data for this registry=20 contains:
 
SharedSection=3D1024,20480,768
 
The second value is for interactive = processes, and=20 the third value is for the non-interactive processes, so we have to = increase the=20 third value.
 
Desktop heap can be monitorized with = Microsoft's=20 Desktop Heap Monitor:
 
htt= p://www.microsoft.com/downloads/details.aspx?familyid=3D5CFC9B74-97AA-451= 0-B4B9-B2DC98C8ED8B&displaylang=3Den#RelatedDownloads
 
I hope this will help someone = else.
 
Best regards.
 
Daniel
----- Original Message -----
From:=20 Daniel L=F3pez=20 Robles
Sent: Monday, November 16, 2009 = 1:34=20 PM
Subject: Re: [users@httpd] = Apache 2.2.14=20 and "Allow service to interact with desktop"

Hello:
 
I tried with the last httpd.exe = (2.2.14) and I=20 had the same problem: I had to check the "Allow service to interact = with=20 desktop" checkbox in the properties of the Apache2.2 service in order = to get=20 the Logical disk manager working. So I change the subject of the=20 mail.
 
Thank you.
 
Daniel
----- Original Message -----
From:=20 Daniel=20 L=F3pez Robles
Sent: Friday, November 13, = 2009 12:30=20 PM
Subject: [users@httpd] Apache = 2.2.11=20 and "Allow service to interact with desktop"

Hello:

I have a weird = problem with=20 Apache and Windows 2003 Server that I haven't been able to figure=20 out:

HP Proliant DL580 G5
Windows Server 2003 R2 Standard=20 x64
Apache 2.2.11

With that configuration, if I = double-click "My=20 PC", "Manage" and I go to "Disk manage", an error is given: "Unable = to=20 connect to logical disk manager"

The weird thing is that if I = check=20 the "Allow service to interact with desktop" checkbox in the = properties of=20 the Apache2.2 service, the problem is solved. =BF? The new problem = now is that=20 when connecting to the machine via Terminal Server with the /console = parameter, a lot of cmd windows appear, due to the rotatelogs. =

I=20 hope someone could give me some clue about the dependencies between = Apache=20 and Logical disk manager, and/or an alternative to rotatelog.exe, in = order=20 to eliminate those annoying cmd windows. I tried mod_log_rotate but = it=20 didn't work properly with the error log.

Thank you very=20 much.
 
Daniel

-- =
Mensaje analizado=20 por el sistema de deteccion de virus y antispam de ACOTEL. El =
hecho de=20 que dicho mensaje haya sido tratado NO excluye que pueda contener =
virus=20 no catalogados a fecha de hoy.=20 =
------------------------------------------------------------------=20
Message analyzed by the Antispam-Virus Detection System at = ACOTEL. The=20 fact
that this message has passed analysis does not exclude the=20 posibility of being
infected by an undetected virus. =
--=20
Mensaje analizado por el sistema de deteccion de virus y antispam = de=20 ACOTEL. El
hecho de que dicho mensaje haya sido tratado NO excluye = que=20 pueda contener
virus no catalogados a fecha de hoy.=20
------------------------------------------------------------------ =
Message analyzed by the Antispam-Virus Detection System at ACOTEL. = The=20 fact
that this message has passed analysis does not exclude the = posibility=20 of being
infected by an undetected virus. = --Boundary_(ID_D2k0igxNPBKrMXQl0RE7OQ)--