question about apache 2.2.21

[Massimo]

hi all,

i'd like to upgrade it, but i've heard around that it has some backward compatibility
problems, am i right?

in the past i allways updated apache just overwriting it's exe and modules

i've a lot of websites hosted here and i can't run any risk

any experiences?

thanks
bye

massimo s.

[Zdenek Wagner]

2011/12/26 Massimo <m...@ecomstation.it>:

I always did the following:

1. Unpacked the new version to directories with the different names
(ie directory with exe, directory with modules)

2. Stopped Apache

3. Renamed the directories with the old version so that the directory
name contained the version number

4. Renamed the directories of the new version so that the names were
the same as before stopping the old version

5. Started Apache

6. If anything did not work and I could not find the reason within a
few minutes, I stopped Apache, renamed the directories back and
started the old version.

I kept the old version until I was pretty sure that the new version
works for me.

Hope this helps.

> thanks
> bye
>
> massimo s.
>
> --
> You received this message because you are subscribed to the Google Groups "Apache for OS/2" group.
> To post to this group, send email to apa...@googlegroups.com.
> To unsubscribe from this group, send email to apache2+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/apache2?hl=en.
>

--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz

[Massimo]

yes, of course me too
i stop apache, and i do a copy of the old installation

massimo s.

[Lewis G Rosenthal]

On 12/26/11 12:54 pm, Massimo thus wrote :

I think the main thing we've seen with the builds of Apache after 2.2.17
or so is that basic auth isn't working with passwords generated under
previous builds. I know this has been a major cause of difficulty for
Dave; luckily, I only have a handful using it, and records of their
passwords, so I regenerated the digests. See this thread for more info:

http://groups.google.com/group/apache2/browse_thread/thread/bb298a31605e7240
(Go down to my own post of Sept 20, 2011 at 4:47pm.)

Essentially, this was changed in the 2.2.18 code (see Dave's reference
in that thread, and Steve's comments, at the bottom).

Other than that, 2.2.21 seems stable enough.

Cheers/2

--
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal& Rosenthal, LLC www.2rosenthals.com
Need a managed Wi-Fi hotspot? www.hautspot.com
visit my IT blog www.2rosenthals.net/wordpress
please do not add my address to any non-bcc mass mailings
-------------------------------------------------------------

[Massimo]

Steve says it's an apache/2 problem

has been fixed on v2.2.21?

i've a lot of auth basic pages (i guess more than 1 hundred), for me
it's a real bad problem

any idea if in v2.2.21 backward compatibility has been fixed?

massimo s.

[Lewis G Rosenthal]

On 12/26/11 03:13 pm, Massimo thus wrote :

> Steve says it's an apache/2 problem
>
> has been fixed on v2.2.21?
>
> i've a lot of auth basic pages (i guess more than 1 hundred), for me
> it's a real bad problem
>
> any idea if in v2.2.21 backward compatibility has been fixed?
>

I just tested this on my local machine. I'm sorry to report that
passwords which were working under 2.2.15 still do not work under 2.2.21.

> Il 26/12/2011 20.47, Lewis G Rosenthal ha scritto:
>> On 12/26/11 12:54 pm, Massimo thus wrote :
>>> hi all,
>>>
>>> i'd like to upgrade it, but i've heard around that it has some backward compatibility
>>> problems, am i right?
>>>
>>> in the past i allways updated apache just overwriting it's exe and modules
>>>
>>> i've a lot of websites hosted here and i can't run any risk
>>>
>>> any experiences?
>>>
>> I think the main thing we've seen with the builds of Apache after 2.2.17 or so is that basic
>> auth isn't working with passwords generated under previous builds. I know this has been a major
>> cause of difficulty for Dave; luckily, I only have a handful using it, and records of their
>> passwords, so I regenerated the digests. See this thread for more info:
>>
>> http://groups.google.com/group/apache2/browse_thread/thread/bb298a31605e7240
>> (Go down to my own post of Sept 20, 2011 at 4:47pm.)
>>
>> Essentially, this was changed in the 2.2.18 code (see Dave's reference in that thread, and
>> Steve's comments, at the bottom).
>>
>> Other than that, 2.2.21 seems stable enough.
>>
>> Cheers/2
>>

--

[Massimo]

so i can't upgrade :(

it's a big trouble for me

massimo s.

[Paul Smedley]

I will try look at the http auth problem today or tomorrow.

Sent from my iPhone

[Paul Smedley]

Hi Lewis,

Can anyone give me some pointers on configuring auth_basic here? I've
spent a little bit of time but am getting a crash in libc064.dll after
the page is authenticated.

Not sure if this is a misconfiguration or a problem with apache/2 and
libc064??

Cheers,

Paul

[Lewis G Rosenthal]

Hi, Paul...

On 12/26/11 07:17 pm, Paul Smedley thus wrote :

Sounds like a misconfiguration, as I haven't seen this happen on mine at
all.

Here's what I have:

Password files are located in a directory outside the web space
(/APPS/Apache2/pass).

In httpd-vhosts.conf, I have a given file protected. In this case,
test.php, which is simply phpinfo();. The section in the conf looks like
this:

<Files test.php>
AuthType Basic
AuthName "Info"
AuthUserFile /APPS/Apache2/pass/users.pass
Require user person person1 person2 person3
</Files>

(Where "person," "person1," etc. refers to a username in the pass.)

Access domain/test.php, and you get the familiar browser authentication
box. If auth fails, the box just pops up again. Cancel it, and you get a
white page advising that the page is protected. Successfully
authenticate, and you just get the page.

For modules, I have (besides those loaded elsewhere, e.g., php, etc.):

modules/actions.dll
modules/alias.dll
modules/asis.dll
modules/authn_fi.dll
modules/authz_ho.dll
modules/authz_us.dll
modules/auth_bas.dll
modules/autoinde.dll
modules/cgi.dll
modules/dir.dll
modules/env.dll
modules/headers.dll
modules/include.dll
modules/info.dll
modules/log_conf.dll
modules/logio.dll
modules/mime.dll
modules/negotiat.dll
modules/proxy.dll
modules/proxy_aj.dll
modules/proxy_ba.dll
modules/proxy_co.dll
modules/proxy_ft.dll
modules/proxy_ht.dll
modules/rewrite.dll
modules/setenvif.dll
modules/status.dll
modules/userdir.dll

Not sure what could be breaking your setup. Mine just works (multiple
systems).

HTH

[Paul Smedley]

Hi Lewis,

<snip>

> Not sure what could be breaking your setup. Mine just works (multiple
> systems).

Have you installed libc064 (and the associated forwarder libc063) on any
systems running Apache2?

I get the same error here with your setup using libc064

Cheers,

Paul

[Paul Smedley]

OK scratch that - I was missing authz_user_module it's working now...

[Paul Smedley]

Fixed in the 2011-12-27 release of Apache2 - downloadable from
http://os2ports.smedley.info/index.php?page=apache2

[Ian Manners]

Hi Paul,

>Have you installed libc064 (and the associated forwarder libc063) on any
>systems running Apache2?

I installed libc064 but had to backlevel libc063.dll to the full DLL, not
the forwarder provided as part of libc064 as the forwarder DLL was
causing problems with Rsync on my personal OS/2 box. I havent done
anything to report the error at present as I'm juggling family at
Christmas
time :)

Cheers
Ian Manners
http://www.os2site.com/

[Lewis G Rosenthal]

Hi again...

On 12/26/11 10:40 pm, Paul Smedley thus wrote :

Indeed, yes:

Directory of C:\os2\dll\libc*

10-03-11 6:07 48,142 0 libc06.dll
10-03-11 6:07 48,142 0 libc061.dll
10-03-11 6:07 157,124 0 libc062.dll
10-03-11 6:07 157,124 0 libc063.dll
10-03-11 6:07 1,345,016 0 libc064.dll
8-11-08 11:53 1,353,252 0 libc064x.dll

The above (form mt ThinkPad) is mirrored on the server. I got rid of
extra copies in \ecs\dll a couple of weeks ago, but they didn't seem to
be causing any difficulty. You're sure there's nothing with the page
itself that you're protecting? If you turn disable auth and then access
the page, Apache stays up?

I'm running your Apache 2.2.21 build from...let's
see...httpd-2.2.21-os2-20110921.zip. On my setup, Apache is installed
under J:\APPS\Apache2 (I have no U: on either the server or my local
machine).

[Lewis G Rosenthal]

On 12/26/11 11:07 pm, Paul Smedley thus wrote :

> OK scratch that - I was missing authz_user_module it's working now...
>

LOL... Guess I should have read *all* of your posts before responding in
order. :-)

<snip>

[Lewis G Rosenthal]

:-)

You're the best, Paul.

On 12/26/11 11:21 pm, Paul Smedley thus wrote :

> Fixed in the 2011-12-27 release of Apache2 - downloadable from
> http://os2ports.smedley.info/index.php?page=apache2
>

<snip>

[Dave Saville]

Hi Ian - what sort of problems? I just loaded all the new dlls and rebooted
to test the new Apache build and apache worked but when I came to shut
apache down I got two Pdumps. :-(

--
Kind regards

Dave Saville

[Dave Saville]

On Tue, 27 Dec 2011 14:51:35 +1030 Paul Smedley wrote:
>
>Fixed in the 2011-12-27 release of Apache2 - downloadable from
>http://os2ports.smedley.info/index.php?page=apache2

pid=0x013c ppid=0x0021 tid=0x0001 slot=0x00ab pri=0x0200 mc=0x0001
D:\APPS\APACHE2\BIN\HTTPD.EXE
LIBC064 0:000f0242
cs:eip=005b:1dd30242 ss:esp=afff:0022fc0e ebp=0022fc64
ds=afff es=afff fs=150b gs=0000 efl=00010206
eax=0000afff ebx=0022fc3c ecx=006c8000 edx=0000150b edi=0022fe48
esi=006c6058
Process has been dumped

On shutdown.

[Paul Smedley]

Hi Dave,

I'm seeing those registers from libc064 a lot when processes are killed.

Does this actually affect anything other than polluting the error_log?

[Dave Saville]

Hi Paul

Happy New Year to you. I don't think so I just get a double beep at
shutdown of apache. The second lasting longer and two Pdump files every
time. Nothing else seems affected. But I am not killing - Right hand X or
close from left hand drop down menu.

[Massimo]

killing apache here sometimes produces ring0 traps...

massimo

[Paul Smedley]

Hi Dave,

With the help of Steven Levine, we've been able to determine/confirm
that the SIGSEGV you posted above (in location LIBC064 0:000f0242) is
definitely a libc defect - see http://svn.netlabs.org/libc/ticket/255
for details

Cheers,
Paul

[Paul Smedley]

Libc064.dll has some serious issues - see the ticket I raised a week
or two ago at http://Svn.netlabs.org/libc/timeline

Probably explains the rsync issues too

Sent from my iPhone

[Steven Levine]

In <6748938154695655270@unknownmsgid>, on 01/14/12
at 08:32 PM, Paul Smedley <pa...@smedley.id.au> said:

Hi,

>Libc064.dll has some serious issues - see the ticket I raised a week or
>two ago at http://Svn.netlabs.org/libc/timeline

>Probably explains the rsync issues too

This is true. In addition, even though rpm/yum requires libc064 to
operate, it is linked against libc063, which makes co-existance difficult.

I'm was wondiering if you should release a libc064w built with wlink and
link against this until we get a libc065.

Steven

--
----------------------------------------------------------------------
"Steven Levine" <ste...@earthlink.net> eCS/Warp/DIY etc.
www.scoug.com www.ecomstation.com
----------------------------------------------------------------------

[Paul Smedley]

Hi Steven,

On 15/01/12 05:05, Steven Levine wrote:
> In<6748938154695655270@unknownmsgid>, on 01/14/12
> at 08:32 PM, Paul Smedley<pa...@smedley.id.au> said:
>
> Hi,
>
>> Libc064.dll has some serious issues - see the ticket I raised a week or
>> two ago at http://Svn.netlabs.org/libc/timeline
>
>> Probably explains the rsync issues too
>
> This is true. In addition, even though rpm/yum requires libc064 to
> operate, it is linked against libc063, which makes co-existance difficult.
>
> I'm was wondiering if you should release a libc064w built with wlink and
> link against this until we get a libc065.

Well I have already built a libc064x with wlink and use this for
postgresql as that one _needs_ the fixes in libc064 to be useful.

I also thought of hacking the build system to regenerate a libc064 but
Knut has several comments/warnings about this kind of thing pissing him
off :) (ie releasing an 'official' build that's not by him :P

For Apache2, I may just rebuild against libc063 and recommend people use
the full libc063 rather than the forwarder to libc064.

Cheers,

Paul

[Steven Levine]

In <4F11FF9...@smedley.id.au>, on 01/15/12

at 08:50 AM, Paul Smedley <pa...@smedley.id.au> said:

Hi,

>I also thought of hacking the build system to regenerate a libc064 but

>Knut has several comments/warnings about this kind of thing pissing him
>off :) (ie releasing an 'official' build that's not by him :P

Well, you could ask him if it would be OK.

>For Apache2, I may just rebuild against libc063 and recommend people use
>the full libc063 rather than the forwarder to libc064.

That will not work for folks that have rpm/yum installed. As I mentioned,
these require libc064, but link to libc063. I already ran into this with
an rsync user. The best solution would be for the rpm/yum maintainers to
build against libc064 and do a new release.

[Paul Smedley]

Hi All,

On 15/01/12 10:26, Steven Levine wrote:
> In<4F11FF9...@smedley.id.au>, on 01/15/12
> at 08:50 AM, Paul Smedley<pa...@smedley.id.au> said:
>
> Hi,
>
>> I also thought of hacking the build system to regenerate a libc064 but
>> Knut has several comments/warnings about this kind of thing pissing him
>> off :) (ie releasing an 'official' build that's not by him :P
>
> Well, you could ask him if it would be OK.

Will do when I see him next on IRC.

>> For Apache2, I may just rebuild against libc063 and recommend people use
>> the full libc063 rather than the forwarder to libc064.
>
> That will not work for folks that have rpm/yum installed. As I mentioned,
> these require libc064, but link to libc063. I already ran into this with
> an rsync user. The best solution would be for the rpm/yum maintainers to
> build against libc064 and do a new release.

fwiw I've been able to build a libc064.dll with wlink that can be used
as a dropin replacement for Knut's ilink built version.

If you're seeing the SIGSEGV in libc064.dll at address 0:000f0242 then
it's likely the DLL I built will fix it.

At this point it will be available by request only.

Cheers,

Paul

[Massimo]

i've tried to generate .htpasswd file on my server with apache 2.2.17
and moved to an apache 2.2.21 of a customer

but it doesn't seem to recognize the password

any idea?

massimo s.

[Massimo]

sorry, ignore this post
the problem it's me that i forgot to load the module authz_user_module