Re: [users@httpd] Apache rotatelogs performance issues

2018-12-11 Thread Michael Hallager
On 2018-12-12 14:03, Eric Covener wrote: On Tue, Dec 11, 2018 at 6:27 PM Michael Hallager wrote: On 2018-12-12 12:16, Eric Covener wrote: > Rotation is pretty lightweight, just closing and opening a file. Do > you have some reason to suspect rotatelogs is the problem? Terminating the

Re: [users@httpd] Apache rotatelogs performance issues

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 6:27 PM Michael Hallager wrote: > > On 2018-12-12 12:16, Eric Covener wrote: > > > Rotation is pretty lightweight, just closing and opening a file. Do > > you have some reason to suspect rotatelogs is the problem? > > Terminating the rotatelogs processes fixes the

Re: [users@httpd] Apache rotatelogs performance issues

2018-12-11 Thread Michael Hallager
On 2018-12-12 12:16, Eric Covener wrote: Rotation is pretty lightweight, just closing and opening a file. Do you have some reason to suspect rotatelogs is the problem? Terminating the rotatelogs processes fixes the performance issue.

Re: [users@httpd] Apache rotatelogs performance issues

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 6:08 PM Michael Hallager wrote: > > Hi all. > > I am dealing with an Linux + Apache 2.4.x server with a couple of > hundred websites using rotatelogs which intermittently causes a massive > slowdown of the server. > > Setting rotatelogs to slightly different periods so (in

[users@httpd] Apache rotatelogs performance issues

2018-12-11 Thread Michael Hallager
Hi all. I am dealing with an Linux + Apache 2.4.x server with a couple of hundred websites using rotatelogs which intermittently causes a massive slowdown of the server. Setting rotatelogs to slightly different periods so (in theory) it performs this task over an hour and a half for all

RE: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Kathy S Durlacher
Updated as suggested, and getting a different response -- "The requested URL / was not found on this server. IBM_HTTP_Server Server at choiceportal-d Port 8084" Following is the wget response: wget -r http://choiceportal-d:8084 SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc =

Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 2:55 PM Kathy S Durlacher wrote: > > Hi Eric -- first let me thank you for your help - truly appreciated. > Can you please respond placing a space following your https so what you typed > is not converted to https: //urldefense, etc Here's the same reply in a pastebin:

RE: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Kathy S Durlacher
Hi Eric -- first let me thank you for your help - truly appreciated. Can you please respond placing a space following your https so what you typed is not converted to https: //urldefense, etc -Original Message- From: Eric Covener Sent: Tuesday, December 11, 2018 2:38 PM To:

Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 2:28 PM Kathy S Durlacher wrote: > > Wget downloaded and executed, and I'm receiving the following which looks to > point to a possible problem with the recode of the uri to get to test SSL > port 444: > > wget -r http://choiceportal-d:8084 > SYSTEM_WGETRC =

RE: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Kathy S Durlacher
Wget downloaded and executed, and I'm receiving the following which looks to point to a possible problem with the recode of the uri to get to test SSL port 444: wget -r http://choiceportal-d:8084 SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = c:/progra~1/wget/etc/wgetrc --2018-12-11

Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 11:28 AM Kathy S Durlacher wrote: > > Yes, these non-standard ports are defined: > Listen *:8084 > #Listen *:80 > Listen *:444 > #Listen *:443 I'd suggest debugging with a commnand-line client like wget or curl rather than a browser. The former will give you more

[users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Kathy S Durlacher
Yes, these non-standard ports are defined: Listen *:8084 #Listen *:80 Listen *:444 #Listen *:443 -Original Message- From: Eric Covener Sent: Tuesday, December 11, 2018 11:12 AM To: users@httpd.apache.org Subject: [EXTERNAL] Re: [users@httpd] Help

Re: [users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Eric Covener
> How defined in test version 9 using 8084 & SSL 444 > > Did you add `Listen` directives for these non-standard ports? - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail:

[users@httpd] Help Creating Test HTTP Server with SSL

2018-12-11 Thread Kathy S Durlacher
Looking to create a test IBM HTTP Server on z/OS to convert from version 8.5 to version 9. Until the upgrade takes place, I need to keep the current environment active for users, so starting another HTTP server using different ports in place of the port 80 and SSL port 443. Test HTTP server