Hi All,
Thank you Rick and William for helping me out.
As suggested I had use the apxs to build a module.
Steps as follows:
1> I have commented my module and try to start the apache and it started.
2> I took the default example file that comes with
httpd-2.4.34(httpd-2.4.34/modules/examples/mo
Do you use a "similar" compiler for httpd and the module?
On Wed, Nov 14, 2018 at 1:56 PM wrote:
>
> Hi All,
>
> Thank you Rick and William for helping me out.
>
> As suggested I had use the apxs to build a module.
> Steps as follows:
>
> 1> I have commented my module and try to start the apache a
Did you use the apxs binary compiled with 2.4.34, or could you have executed an
older copy, creating a module for an earlier HTTP product?
Rick Houser
Web Engineer
From: singhal.an...@tcs.com
Sent: Wednesday, November 14, 2018 13:56
To: users@httpd.apache.org
Subject: RE: [users@httpd] URGENT:
I have used the same apxs binary that is available in the installed path
of apache 2.4
/usr/local/apache2.4.34/bin/apxs
My main concern is "expected signature 41503234 but saw "
What could be the reason of signature ?
Thanks & Regards
Ankit Singhal
Tata Consultancy Services
Mail
It's been years since I wrote any modules, so I won't be able to assist
further. Consider repeating the module load test on a "clean" host (Linux Live
DVD or such?) that never had anything BUT Apache 2.4 on it. Good luck!
Rick Houser
Web Engineer
From: singhal.an...@tcs.com
Sent: Wednesday,
We have used the same compiler for both.
My main concern is "expected signature 41503234 but saw "
What could be the reason of signature ?
This implies that no signature is generated in my case
Thanks & Regards
Ankit Singhal
Tata Consultancy Services
Mailto: singhal.an...@tcs.co
Hi,
I have a stock httpd server on a CentOS 7 machine. I have added a file to the
conf.d directory with the following contents :
BalancerMember http://django1 ping=5 disablereuse=on retry=5 ttl=120
BalancerMember http://django2 ping=5 disablereuse=on retry=5 ttl=120
BalancerMember http://d
You are absolutely right, there is a NULL quadword at the expected position
of the module signature. How this happened is the question.
Could it be possible that you are still compiling against httpd 1.3 include
files? The ordering of the module structure has changed. If the -I include
paths are c
