Re: URGENT: Apache HTTP Migration from 1.3 to 2.0 UNIX Solaris

[singhal.ankit@xxxxxxx]

We have used the same compiler for both.

My main concern is "expected signature
41503234 but saw 00000000"

What could be the reason of signature
00000000?

This implies that no signature is generated
in my case

Thanks & Regards
Ankit Singhal
Tata Consultancy Services
Mailto: singhal.ankit@xxxxxxx
Website: http://www.tcs.com
____________________________________________
Experience certainty.        IT Services
                
       Business Solutions
                
       Consulting
____________________________________________




From:      
 Eric Covener <covener@xxxxxxxxx>
To:      
 users@xxxxxxxxxxxxxxxx
Date:      
 14-11-2018 15:58
Subject:    
   Re:
URGENT: Apache HTTP Migration from 1.3 to 2.0 UNIX Solaris

---

"External email. Open with Caution"

Do you use a "similar" compiler for httpd and the module?
On Wed, Nov 14, 2018 at 1:56 PM <singhal.ankit@xxxxxxx> 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 and it
started.
>
> 2> I took the default example file that comes with httpd-2.4.34(httpd-2.4.34/modules/examples/mod_example_hooks.c)
and compile it with apxs by following command:
> apxs -c mod_example_hooks.c
>
> 3> Above command automatically created a folder .libs and in this
there is .so created(.libs/mod_example_hooks.so)
>
> 4> When I loaded the created module and try to start the apache
then also it is giving the same error.
>
> quartz: /usr/local/apache2.4.34/conf/extra > apache2.4 start
> httpd: Syntax error on line 490 of /usr/local/apache2.4.34/conf/httpd.conf:
Syntax error on line 6 of /usr/local/apache2.4.34/conf/extra/httpd-quartz.conf:
API module structure 'example_hooks_module' in file /app/quartz/COMS/EAI_324/ph/http/src/.libs/mod_example_hooks.so
is garbled - expected signature 41503234 but saw 00000000 - perhaps this
is not an Apache module DSO, or was compiled for a different Apache version?
>
>
>
> Thanks & Regards
> Ankit Singhal
> Tata Consultancy Services
> Mailto: singhal.ankit@xxxxxxx
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty.        IT Services
>                    
   Business Solutions
>                    
   Consulting
> ____________________________________________
>
>
>
>
> From:        "Houser, Rick" <rick.houser@xxxxxxxxxxx>
> To:        "users@xxxxxxxxxxxxxxxx"
<users@xxxxxxxxxxxxxxxx>
> Date:        13-11-2018 14:40
> Subject:        RE:  URGENT: Apache
HTTP Migration from 1.3 to 2.0 UNIX Solaris
> ________________________________
>
>
>
> "External email. Open with Caution"
>
> While that is one approach, I'm afraid it won't speed up your exercise;
it is most
> direct to get 2.4 going.
>
>
> Something that will likely speed your transition is to split your
task into as small of portions as possible, and tackle those one at a time
from a higher level perspective.  For example, if a module is doing
some custom authentication, look at what’s available in 2.4 already and
see if something now stock can do the job, or at least get you 90% of the
way there and serve as an updated template for your code.  For example,
there are already modules for authentication providers like ldap, content
caching, database access, etc.
>
> The time savings on the simplified troubleshooting steps are likely
to be far from insignificant, and you would have the benefit of a more
standardized/modern codebase.  For example, get the server up and
running with static content, then compile one module with apxs, get it
to load, then work on the related config.  Work through any issues
you find with this, then move on to the next.  This may be a good
time to split one large config file up in many smaller ones with includes,
etc.  Trying to migrate an existing non-trivial site in one step is
likely to be overwhelming for most, especially for a novice.
>
>
> Rick Houser
> Web Engineer
>
> From: William A Rowe Jr <wrowe@xxxxxxxxxxxxx>
> Sent: Tuesday, November 13, 2018 12:18
> To: users@xxxxxxxxxxxxxxxx
> Subject: Re:  URGENT: Apache HTTP Migration from 1.3
to 2.0 UNIX Solaris
>
> EXTERNAL EMAIL
>
> On Tue, Nov 13, 2018 at 11:04 AM <singhal.ankit@xxxxxxx> wrote:
>
> Our main objective is to migrate to 2.4. Since I faced an issue while
doing so, I thought it would be better to first migrate to 2.0 then to
2.2 and finally to 2.4.
>
> While that is one approach, I'm afraid it won't speed up your exercise;
it is most
> direct to get 2.4 going.
>
> In 2.4 itself the error is same.
>
> The signature created turns out to be 00000000. I could not understand
this part. I have gone through the internet and there are always some definite
signature is available but in my case it turned out to be 0.
>
> It is not a loadable library object.  Rather than fighting with
cc's flags, review
> the helper utility;
>
>   https://httpd.apache.org/docs/2.4/programs/apxs.html
>
> This will make your life much simpler for compiling and linking loadable
modules. It retains the flags initially used for compiling httpd and modules,
so that the results are consistent.
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



-- 
Eric Covener
covener@xxxxxxxxx

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx