Loading ...
Sorry, an error occurred while loading the content.

Re: compile error

Expand Messages
  • J S
    ... smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep Perl_vmess [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
    Message 1 of 30 , May 1, 2003
    View Source
    • 0 Attachment
      >J S wrote:
      >
      >>I need to keep the mod_perl dynamic so that I can upgrade it later if need
      >>be, and also I don't want to have to rebuild Apache as well. I did get the
      >>libperl.so to build today by adding -DUSE_HSREGEX to EXTRA_CFLAGS in the
      >>Makefile. Not sure if that was right but it at least got the compile to
      >>work.
      >
      >Great
      >
      >>The problem now is I can't get apache to start:
      >>
      >>smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
      >>Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
      >>Cannot load /opt/apache_1.3.27/libexec/libperl.so into server: ld.so.1:
      >>/opt/apache_1.3.27/bin/httpd: fatal: relocation error: file
      >>/opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess: referenced
      >>symbol not found
      >
      >[...]
      >
      >>I have a bit more debug for you but I'm not sure how meaningful this is:
      >
      >All, but one bit is missing from the puzzle
      >
      >># ldd ../libexec/libperl.so
      >> libperl.so =>
      >>/opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
      >
      >># nm -r ../libexec/libperl.so
      >
      >>[1356] | 0| 0|FUNC |GLOB |0 |UNDEF
      >>|libperl.so:Perl_vmess
      >
      >What's the output of
      >
      >nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
      >Perl_vmess
      >

      smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
      Perl_vmess
      [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess


      _________________________________________________________________
      Stay in touch with absent friends - get MSN Messenger
      http://www.msn.co.uk/messenger
    • Stas Bekman
      ... are you sure that ../libexec/libperl.so is /opt/apache_1.3.27/libexec/libperl.so? Since you show below that
      Message 2 of 30 , May 1, 2003
      View Source
      • 0 Attachment
        J S wrote:
        >
        >
        >
        >> J S wrote:
        >>
        >>> I need to keep the mod_perl dynamic so that I can upgrade it later if
        >>> need be, and also I don't want to have to rebuild Apache as well. I
        >>> did get the libperl.so to build today by adding -DUSE_HSREGEX to
        >>> EXTRA_CFLAGS in the Makefile. Not sure if that was right but it at
        >>> least got the compile to work.
        >>
        >>
        >> Great
        >>
        >>> The problem now is I can't get apache to start:
        >>>
        >>> smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
        >>> Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
        >>> Cannot load /opt/apache_1.3.27/libexec/libperl.so into server:
        >>> ld.so.1: /opt/apache_1.3.27/bin/httpd: fatal: relocation error: file
        >>> /opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess: referenced
        >>> symbol not found
        >>
        >>
        >> [...]
        >>
        >>> I have a bit more debug for you but I'm not sure how meaningful this is:
        >>
        >>
        >> All, but one bit is missing from the puzzle
        >>
        >>> # ldd ../libexec/libperl.so
        >>> libperl.so =>
        >>> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so

        are you sure that ../libexec/libperl.so is
        /opt/apache_1.3.27/libexec/libperl.so? Since you show below that
        /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so has the symbol
        Perl_vmess defined and it's the one ldd sees in
        /opt/apache_1.3.27/libexec/libperl.so it should work just fine. Usually when
        this problem happens when you get the wrong .so loaded.

        >>> # nm -r ../libexec/libperl.so
        >>
        >>
        >>> [1356] | 0| 0|FUNC |GLOB |0 |UNDEF
        >>> |libperl.so:Perl_vmess
        >>
        >>
        >> What's the output of
        >>
        >> nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
        >> Perl_vmess
        >>
        >
        > smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
        > Perl_vmess
        > [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
        >
        >
        > _________________________________________________________________
        > Stay in touch with absent friends - get MSN Messenger
        > http://www.msn.co.uk/messenger


        --


        __________________________________________________________________
        Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
        http://stason.org/ mod_perl Guide ---> http://perl.apache.org
        mailto:stas@... http://use.perl.org http://apacheweek.com
        http://modperlbook.org http://apache.org http://ticketmaster.com
      • Stas Bekman
        ... Looks absolutely fine to me. The first and the last are the same files. ... I m not familiar with peculiarities of Solaris. Perhaps someone knows can give
        Message 3 of 30 , May 2, 2003
        View Source
        • 0 Attachment
          J S wrote:
          >
          >
          >
          >>>>> The problem now is I can't get apache to start:
          >>>>>
          >>>>> smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
          >>>>> Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
          >>>>> Cannot load /opt/apache_1.3.27/libexec/libperl.so into server:
          >>>>> ld.so.1: /opt/apache_1.3.27/bin/httpd: fatal: relocation error:
          >>>>> file /opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess:
          >>>>> referenced symbol not found
          >>>>
          >>>>
          >>>>
          >>>> [...]
          >>>>
          >>>>> I have a bit more debug for you but I'm not sure how meaningful
          >>>>> this is:
          >>>>
          >>>>
          >>>>
          >>>> All, but one bit is missing from the puzzle
          >>>>
          >>>>> # ldd ../libexec/libperl.so
          >>>>> libperl.so =>
          >>>>> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
          >>>>
          >>
          >> are you sure that ../libexec/libperl.so is
          >> /opt/apache_1.3.27/libexec/libperl.so?
          >
          >
          > Definitely.
          >
          > Since you show below that
          >
          >> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so has the symbol
          >> Perl_vmess defined and it's the one ldd sees in
          >> /opt/apache_1.3.27/libexec/libperl.so it should work just fine.
          >> Usually when this problem happens when you get the wrong .so loaded.
          >
          >
          > These are the only libperl.so files on the box:
          >
          > smpd9$ find / -name libperl.so 2>/dev/null
          > /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
          > /opt/apache_1.3.27/libexec/libperl.so
          > /home/src/perl-5.8.0/libperl.so
          > smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
          > -i vmess
          > [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
          > smpd9$ nm /opt/apache_1.3.27/libexec/libperl.so | grep -i vmess
          > [1645] | 0| 0|FUNC |GLOB |0 |UNDEF |Perl_vmess
          > smpd9$ nm /home/src/perl-5.8.0/libperl.so | grep -i vmess
          > [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess

          Looks absolutely fine to me. The first and the last are the same files.

          >>>>> # nm -r ../libexec/libperl.so
          >>>>
          >>>>
          >>>>
          >>>>> [1356] | 0| 0|FUNC |GLOB |0 |UNDEF
          >>>>> |libperl.so:Perl_vmess
          >>>>
          >>>>
          >>>>
          >>>> What's the output of
          >>>>
          >>>> nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
          >>>> Perl_vmess
          >>>>
          >>>
          >>> smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so |
          >>> grep Perl_vmess
          >>> [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess

          I'm not familiar with peculiarities of Solaris. Perhaps someone knows can give
          us help here. May be ask at some Solaris specific list? Since it seems to be a
          generic linking/loading problem.

          Have you see any problems of a similar kind in the archives?

          __________________________________________________________________
          Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
          http://stason.org/ mod_perl Guide ---> http://perl.apache.org
          mailto:stas@... http://use.perl.org http://apacheweek.com
          http://modperlbook.org http://apache.org http://ticketmaster.com
        • Ed Grimm
          ... Apache is reporting that it s using the one version of libperl.so which does not have the symbol definition, so there s no surprise that it doesn t work.
          Message 4 of 30 , May 4, 2003
          View Source
          • 0 Attachment
            On Sat, 3 May 2003, Stas Bekman wrote:

            > J S wrote:
            >>
            >>>>>> The problem now is I can't get apache to start:
            >>>>>>
            >>>>>> smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
            >>>>>> Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
            >>>>>> Cannot load /opt/apache_1.3.27/libexec/libperl.so into server:
            >>>>>> ld.so.1: /opt/apache_1.3.27/bin/httpd: fatal: relocation error:
            >>>>>> file /opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess:
            >>>>>> referenced symbol not found
            >>>>>
            >>>>> [...]
            >>>>>
            >>>>>> I have a bit more debug for you but I'm not sure how meaningful
            >>>>>> this is:
            >>>>>
            >>>>> All, but one bit is missing from the puzzle
            >>>>>
            >>>>>> # ldd ../libexec/libperl.so
            >>>>>> libperl.so =>
            >>>>>> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
            >>>>>
            >>>
            >>> are you sure that ../libexec/libperl.so is
            >>> /opt/apache_1.3.27/libexec/libperl.so?
            >>
            >>
            >> Definitely.
            >>
            >> Since you show below that
            >>
            >>> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so has the symbol
            >>> Perl_vmess defined and it's the one ldd sees in
            >>> /opt/apache_1.3.27/libexec/libperl.so it should work just fine.
            >>> Usually when this problem happens when you get the wrong .so loaded.
            >>
            >>
            >> These are the only libperl.so files on the box:
            >>
            >> smpd9$ find / -name libperl.so 2>/dev/null
            >> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
            >> /opt/apache_1.3.27/libexec/libperl.so
            >> /home/src/perl-5.8.0/libperl.so
            >> smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
            >> -i vmess
            >> [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
            >> smpd9$ nm /opt/apache_1.3.27/libexec/libperl.so | grep -i vmess
            >> [1645] | 0| 0|FUNC |GLOB |0 |UNDEF |Perl_vmess
            >> smpd9$ nm /home/src/perl-5.8.0/libperl.so | grep -i vmess
            >> [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
            >
            > Looks absolutely fine to me. The first and the last are the same files.
            >
            >>>>>> # nm -r ../libexec/libperl.so
            >>>>>
            >>>>>
            >>>>>
            >>>>>> [1356] | 0| 0|FUNC |GLOB |0 |UNDEF
            >>>>>> |libperl.so:Perl_vmess
            >>>>>
            >>>>>
            >>>>>
            >>>>> What's the output of
            >>>>>
            >>>>> nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
            >>>>> Perl_vmess
            >>>>>
            >>>>
            >>>> smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so |
            >>>> grep Perl_vmess
            >>>> [368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
            >
            > I'm not familiar with peculiarities of Solaris. Perhaps someone knows
            > can give us help here. May be ask at some Solaris specific list? Since
            > it seems to be a generic linking/loading problem.



            Doing a closer read, I'm seeing the issue:

            >>>>>> smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
            >>>>>> Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
            >>>>>> Cannot load /opt/apache_1.3.27/libexec/libperl.so into server:
            >>>>>> ld.so.1: /opt/apache_1.3.27/bin/httpd: fatal: relocation error:
            >>>>>> file /opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess:
            >>>>>> referenced symbol not found

            >> smpd9$ nm /opt/apache_1.3.27/libexec/libperl.so | grep -i vmess
            >> [1645] | 0| 0|FUNC |GLOB |0 |UNDEF |Perl_vmess

            Apache is reporting that it's using the one version of libperl.so which
            does not have the symbol definition, so there's no surprise that it
            doesn't work. Fix that one version of libperl.so

            Now, as far as

            >>>>>> # ldd ../libexec/libperl.so
            >>>>>> libperl.so =>
            >>>>>> /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so

            ldd determines linkage by its current LD_LIBRARY_PATH, as well as other
            factors. Given that apache puts its libexec directory in said
            environment variable, apache is seeing a recursive dependancy, which is
            resolved immediately, because it has, of course, already begun the load
            of that file. To verify, try (assuming a Bourne shell)

            # LD_LIBRARY_PATH=/opt/apache_1.3.27/libexec:$LD_LIBRARY_PATH ldd ../libexec/libperl.so

            The Solaris quirk is that dynamic loaded libraries are almost always
            dynamically located. In fact, I'm not certain it supports compile-time
            locating dynamic libraries.

            Ed
          • Stas Bekman
            ... Confusingly, mp1 is using the same libname as perl. Do you say that this is the cause of the problem? ... So J.S. should start httpd as:
            Message 5 of 30 , May 4, 2003
            View Source
            • 0 Attachment
              Ed Grimm wrote:
              > On Sat, 3 May 2003, Stas Bekman wrote:
              >
              >
              >>J S wrote:
              >>
              >>>>>>>The problem now is I can't get apache to start:
              >>>>>>>
              >>>>>>>smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
              >>>>>>>Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
              >>>>>>>Cannot load /opt/apache_1.3.27/libexec/libperl.so into server:
              >>>>>>>ld.so.1: /opt/apache_1.3.27/bin/httpd: fatal: relocation error:
              >>>>>>>file /opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess:
              >>>>>>>referenced symbol not found
              >>>>>>
              >>>>>>[...]
              >>>>>>
              >>>>>>
              >>>>>>>I have a bit more debug for you but I'm not sure how meaningful
              >>>>>>>this is:
              >>>>>>
              >>>>>>All, but one bit is missing from the puzzle
              >>>>>>
              >>>>>>
              >>>>>>># ldd ../libexec/libperl.so
              >>>>>>> libperl.so =>
              >>>>>>>/opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
              >>>>>>
              >>>>are you sure that ../libexec/libperl.so is
              >>>>/opt/apache_1.3.27/libexec/libperl.so?
              >>>
              >>>
              >>>Definitely.
              >>>
              >>>Since you show below that
              >>>
              >>>
              >>>>/opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so has the symbol
              >>>>Perl_vmess defined and it's the one ldd sees in
              >>>>/opt/apache_1.3.27/libexec/libperl.so it should work just fine.
              >>>>Usually when this problem happens when you get the wrong .so loaded.
              >>>
              >>>
              >>>These are the only libperl.so files on the box:
              >>>
              >>>smpd9$ find / -name libperl.so 2>/dev/null
              >>>/opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
              >>>/opt/apache_1.3.27/libexec/libperl.so
              >>>/home/src/perl-5.8.0/libperl.so
              >>>smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
              >>>-i vmess
              >>>[368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
              >>>smpd9$ nm /opt/apache_1.3.27/libexec/libperl.so | grep -i vmess
              >>>[1645] | 0| 0|FUNC |GLOB |0 |UNDEF |Perl_vmess
              >>>smpd9$ nm /home/src/perl-5.8.0/libperl.so | grep -i vmess
              >>>[368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
              >>
              >>Looks absolutely fine to me. The first and the last are the same files.
              >>
              >>
              >>>>>>># nm -r ../libexec/libperl.so
              >>>>>>
              >>>>>>
              >>>>>>
              >>>>>>>[1356] | 0| 0|FUNC |GLOB |0 |UNDEF
              >>>>>>>|libperl.so:Perl_vmess
              >>>>>>
              >>>>>>
              >>>>>>
              >>>>>>What's the output of
              >>>>>>
              >>>>>>nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so | grep
              >>>>>>Perl_vmess
              >>>>>>
              >>>>>
              >>>>>smpd9$ nm /opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so |
              >>>>>grep Perl_vmess
              >>>>>[368] | 995152| 716|FUNC |GLOB |0 |8 |Perl_vmess
              >>>>
              >>I'm not familiar with peculiarities of Solaris. Perhaps someone knows
              >>can give us help here. May be ask at some Solaris specific list? Since
              >>it seems to be a generic linking/loading problem.
              >
              >
              >
              >
              > Doing a closer read, I'm seeing the issue:
              >
              >
              >>>>>>>smpd9$ /opt/apache_1.3.27/bin/apachectl configtest
              >>>>>>>Syntax error on line 208 of /opt/apache_1.3.27/conf/httpd.conf:
              >>>>>>>Cannot load /opt/apache_1.3.27/libexec/libperl.so into server:
              >>>>>>>ld.so.1: /opt/apache_1.3.27/bin/httpd: fatal: relocation error:
              >>>>>>>file /opt/apache_1.3.27/libexec/libperl.so: symbol Perl_vmess:
              >>>>>>>referenced symbol not found
              >>>>>>
              >
              >>>smpd9$ nm /opt/apache_1.3.27/libexec/libperl.so | grep -i vmess
              >>>[1645] | 0| 0|FUNC |GLOB |0 |UNDEF |Perl_vmess
              >>
              >
              > Apache is reporting that it's using the one version of libperl.so which
              > does not have the symbol definition, so there's no surprise that it
              > doesn't work. Fix that one version of libperl.so

              Confusingly, mp1 is using the same libname as perl. Do you say that this is
              the cause of the problem?

              > Now, as far as
              >
              >
              >>>>>>># ldd ../libexec/libperl.so
              >>>>>>> libperl.so =>
              >>>>>>>/opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/libperl.so
              >>>>>>
              >
              > ldd determines linkage by its current LD_LIBRARY_PATH, as well as other
              > factors. Given that apache puts its libexec directory in said
              > environment variable, apache is seeing a recursive dependancy, which is
              > resolved immediately, because it has, of course, already begun the load
              > of that file. To verify, try (assuming a Bourne shell)
              >
              > # LD_LIBRARY_PATH=/opt/apache_1.3.27/libexec:$LD_LIBRARY_PATH ldd ../libexec/libperl.so
              >
              > The Solaris quirk is that dynamic loaded libraries are almost always
              > dynamically located. In fact, I'm not certain it supports compile-time
              > locating dynamic libraries.

              So J.S. should start httpd as:

              LD_LIBRARY_PATH=/opt/perl-5.8.0/lib/5.8.0/sun4-solaris/CORE/:LD_LIBRARY_PATH \
              httpd

              ?

              Hmm, should renaming /opt/apache_1.3.27/libexec/libperl.so to
              /opt/apache_1.3.27/libexec/libmodperl.so help?

              Of course you need to adjust httpd.conf as well.


              __________________________________________________________________
              Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
              http://stason.org/ mod_perl Guide ---> http://perl.apache.org
              mailto:stas@... http://use.perl.org http://apacheweek.com
              http://modperlbook.org http://apache.org http://ticketmaster.com
            • Angie Ahl
              Hi guys (and gals) I m Complete newbie to Linux/Perl/and Mod_perl (No it s not that bad ;) I have used apache on OSX for a couple of years now and happy in
              Message 6 of 30 , May 5, 2003
              View Source
              • 0 Attachment
                Hi guys (and gals)

                I'm Complete newbie to Linux/Perl/and Mod_perl

                (No it's not that bad ;)

                I have used apache on OSX for a couple of years now and happy in httpd.conf /
                command line

                I'm a long time Lasso user looking for something more OO and tied into apache,
                and it's got to do regex really really well. I think I found the right thing.

                I'm currently terrified of having to recompile Apache and mod_perl as I'm on one
                of these ensim box things. which seems to have a perl for the box and one per
                site. I am the owner of the box, but I want to have as little impact on other
                sites (that don't use mod_perl) as possible.

                Got mod_perl working, but only with apache:registry, apache:DBI would appear to
                not be there for the whole server (not in any of the @inc's that I can find).

                Are there any Ensim users out there who could just point me in the right
                direction, would I be right in saying seeing as Mod_perl is installed and
                working (I checked the environment things are running through mod_perl) that I
                can just add a path to where I want to put my modules to perl's @INC and then
                continue as normal.

                Sorry if I sound like a complete newbie in some respects (mod_perl) I totally
                am.

                But I will persevere and get this working....

                any tips from ensim users most welcome

                PS feel free to say RTFM... if you could suggest which Manual and which page
                that would be even better. I've got about 5 books and the online docs
                permanently open at this time.

                Thanks so much

                Angie
              • Ged Haywood
                Hi there, ... Hi. :) ... Not many of those I m afraid... ... NOt a big OO fan myself, Perl sort of lets you do it, Perl Regex features are second to none of
                Message 7 of 30 , May 5, 2003
                View Source
                • 0 Attachment
                  Hi there,

                  On Mon, 5 May 2003, Angie Ahl wrote:

                  > Hi guys

                  Hi. :)

                  > (and gals)

                  Not many of those I'm afraid...

                  > I'm a long time Lasso user looking for something more OO and tied into apache,
                  > and it's got to do regex really really well. I think I found the right thing.

                  NOt a big OO fan myself, Perl sort of lets you do it, Perl Regex features are
                  second to none of course.

                  > I'm currently terrified of having to recompile Apache and mod_perl as I'm on one
                  > of these ensim box things.

                  You need to get over the terror. All you need is the gnu tools, have you got gcc?

                  > I want to have as little impact on other
                  > sites (that don't use mod_perl) as possible.

                  No problem there, you could just run two Apache servers.

                  > Got mod_perl working, but only with apache:registry, apache:DBI would appear to
                  > not be there for the whole server (not in any of the @inc's that I can find).

                  You need to put something in startup.pl or whatever. Please note that
                  there are *two* colons in Apache::Registry and Apache::DBI. Also the
                  capitalisation is important if you go searching on the Web for example.

                  > Are there any Ensim users out there who could just point me in the right
                  > direction

                  Could you find out a little more about your box and let us know what
                  else you have in there? A quick glance at the Ensim web site wasn't
                  particularly informative. Nor inspiring:

                  "Where other software providers fail, Ensim has the expertise to
                  deliver professional software to professional hosting businesses.
                  With a seasoned executive management team and strong backing from
                  leading members of the investment community, only Ensim has the
                  products, technology, customers, partners and resources to lead and
                  deliver the next generation of professional hosting solutions."

                  Yuk.

                  > would I be right in saying seeing as Mod_perl is installed and
                  > working (I checked the environment things are running through
                  > mod_perl) that I can just add a path to where I want to put my
                  > modules to perl's @INC and then continue as normal.

                  Don't see why not. It's all in the Guide.

                  > PS feel free to say RTFM... if you could suggest which Manual

                  RTFM. Feel free to say which version of mod_perl you have... :)

                  http://perl.apache.org/docs/1.0/guide/index.html

                  for Apache/mod_perl V1.xx, if you have 2.xx/1.99xx or whatever then I
                  guess you'll need to hang around here for a while, the V2 docs aren't
                  in such good shape as 1.x yet.

                  > and which page

                  All of them. Twice at least. (Start with part 1... :)

                  73,
                  Ged.
                • Michael Koob
                  Angie, Here is how I have my mod_perl server working with ENSIM. Maybe this configuration will work for you it seems to be working out alright for me
                  Message 8 of 30 , May 5, 2003
                  View Source
                  • 0 Attachment
                    Angie,

                    Here is how I have my mod_perl server working with ENSIM. Maybe this
                    configuration will work for you it seems to be working out alright for
                    me currently. If you are an ENSIM user on a sub account then ENSIM does
                    only have the single mod_perl/Apache instance running on the box and the
                    server configuration lays out as follows.

                    Httpd.conf -> /etc/httpd/conf/httpd_app.conf (main configuration file
                    which uses the Include directive to pull in the following files)

                    /etc/appliance/apacheconf - Defines the default
                    virtual host (Basically Rewrite rules for ENSIM)
                    /etc/httpd/conf/jserv.conf - Included based on
                    whether mod_jserv.c is linked in
                    /etc/httpd/conf/roaming.conf - Included based on
                    whether mod_roaming.c is linked in
                    /etc/httpd/conf/asp.conf - Requires mod_perl as
                    well as being uncommented by administrator
                    /etc/httpd/conf/virtual - Directory that includes
                    the virtual host configurations for all other domains/ips

                    The last directory is the important one it contains at most 2 files
                    (i.e. siteX/siteX.ssl) which are the virtual host configuration files
                    for a site numbered X under ENSIM. These contain some very basic info
                    like servername, administrator, document root, and some redirect rules,
                    again for ENSIM. The important stuff in here is the User/Group that the
                    virtual host runs as well as the ssl certificate information. These two
                    files both Include another directory.

                    /etc/httpd/conf/site7

                    This is the most important of the configuration directories. If I
                    understand it correctly when you configure a site using ENSIM to use SSI
                    for example a file is dropped into this directory configuring said
                    option (i.e. /etc/httpd/conf/site7/cgi/ssi). The same applies for
                    mod_perl, with the straightforward filename
                    /etc/httpd/conf/site7/cgi/mod_perl which contains the following
                    directives on my machine.

                    <IfModule mod_perl.c>
                    Alias /perl /home/virtual/site7/fst/var/www/perl
                    <Directory /home/virtual/site7/fst/var/www/perl>
                    Allow from All
                    AllowOverride All
                    Order allow,deny
                    Options +ExecCGI
                    </Directory>
                    SetEnv SITE_PERL /home/virtual/site7/fst/var/www/perl
                    </IfModule>

                    What is important to note here is that no handler is defined so this
                    will execute as cgi as there are no mod_perl handlers defined. I am not
                    sure exactly why this is but you must configure some PerlHandler for
                    this directory if you wish to run mod_perl. It would appear as though
                    they are really aiming for the use of Apache::Registry but since my
                    site(s) make copious use of regular handlers I have done the following.

                    In order to impact the other sites and the overall ENSIM configuration
                    minimally I have placed a symbolic link from these original files/names
                    to files in the directory of the user under which the mod_perl site
                    runs. Something like /etc/httpd/conf/site7 ->
                    /home/virtual/site7/fst/etc/httpd/conf/virtual/ssl-site.conf. I have
                    also done the same for the files for SSI, mod_perl, cgi etc. This has
                    the advantage of allowing you to log in as the sites user and make
                    alterations to the configurations as needed. Since all of the users for
                    the virtual hosts in this environment are chroot on login they could not
                    see/access the configuration files themselves without these
                    modifications.

                    I then added some configuration changes to my mod_perl file including a
                    startup.pl file that pre-compiles all of my important Perl modules and
                    specifies the Perl library that I am using (use lib
                    "/home/virtual/site7/fst/var/www/mod_perl";). If you have the mod_perl
                    cookbook or online guide you should be familiar with this file. This
                    configuration has me up and running and has no interaction with the
                    other sites. If I used ENSIM to remove the mod_perl site everything
                    would be clean however I have the following problems with this solution:

                    A.) The user for the mod_perl virtual host cannot reboot the site
                    themselves. This is a problem if you are running standard handlers as
                    opposed to an Apache::Registry solution with Apache::RegistryLoader.
                    This is due to the fact that any updates to code will require a restart
                    to take effect which is a serious issue if the site is undergoing a lot
                    of changes. You must log in as root in order to reboot the site.
                    B.) Apache/mod_perl responds strangely to restarts in this environment.
                    When I restart the server its memory footprint grows drastically on
                    every restart. This is something I have not seen before and I would love
                    to know why it is happening, but I have not had a chance to research it.
                    This dictates full stop/start whenever changes are made to the Perl
                    modules.

                    As for some of your specific questions:

                    1.) Apache::DBI needs to be downloaded and installed. Just install as
                    root it should not impact any other sites. (If you are really concerned
                    about putting it in the main Perl installation then install it to the
                    directory included in the startup.pl file and it should work fine.)
                    2.) Guides recommended: http://perl.apache.org/docs/1.0/guide/index.html
                    (This is the one with the real details), mod_perl Developer's Cookbook
                    by Geoffrey Young (good quick overview, but you will end up looking to
                    the first for specifics), and CPAN documentation/man pages.

                    If I had more time to get my own server set-up I think that the optimal
                    way to not impact the other sites and have your mod_perl Apache server
                    running would be to install another instance of mod_perl in the file
                    system of the site and proxy the requests from the main Apache server to
                    the other instance for mod_perl requests. This would allow complete
                    configuration of the new server with zero impact to the existing server
                    and if you ever remove the site using ENSIM everything will be nice and
                    clean. All that would be necessary is a few mod_proxy directives in the
                    siteX.conf/ssl-siteX.conf files and everything else is easy. This
                    certainly would be the ideal and would give you quite a few other
                    benefits like proxy caching and memory conservation etc. This type of
                    installation is described in detail in the mod_perl guide referred to in
                    the url above.

                    Sorry about being so verbose but explaining this to you helps me
                    understand where I am at if you know what I mean.

                    Regards,


                    Michael Koob
                    MDK & Associates Inc.
                    michael@...


                    -----Original Message-----
                    From: Angie Ahl [mailto:angie@...]
                    Sent: Monday, May 05, 2003 6:50 AM
                    To: modperl@...
                    Subject: Ensim


                    Hi guys (and gals)

                    I'm Complete newbie to Linux/Perl/and Mod_perl

                    (No it's not that bad ;)

                    I have used apache on OSX for a couple of years now and happy in
                    httpd.conf / command line

                    I'm a long time Lasso user looking for something more OO and tied into
                    apache, and it's got to do regex really really well. I think I found the
                    right thing.

                    I'm currently terrified of having to recompile Apache and mod_perl as
                    I'm on one of these ensim box things. which seems to have a perl for the
                    box and one per site. I am the owner of the box, but I want to have as
                    little impact on other sites (that don't use mod_perl) as possible.

                    Got mod_perl working, but only with apache:registry, apache:DBI would
                    appear to not be there for the whole server (not in any of the @inc's
                    that I can find).

                    Are there any Ensim users out there who could just point me in the right
                    direction, would I be right in saying seeing as Mod_perl is installed
                    and working (I checked the environment things are running through
                    mod_perl) that I can just add a path to where I want to put my modules
                    to perl's @INC and then continue as normal.

                    Sorry if I sound like a complete newbie in some respects (mod_perl) I
                    totally am.

                    But I will persevere and get this working....

                    any tips from ensim users most welcome

                    PS feel free to say RTFM... if you could suggest which Manual and which
                    page that would be even better. I've got about 5 books and the online
                    docs permanently open at this time.

                    Thanks so much

                    Angie
                  • Tom Gazzini
                    ... Personally, I ditched ensim on my box and just did a complete rebuild of Apache/1.3.27 with mod_perl/1.27. I abandoned Ensim s directory structure for a
                    Message 9 of 30 , May 5, 2003
                    View Source
                    • 0 Attachment
                      > > Are there any Ensim users out there who could just point me in the
                      > > right direction
                      >
                      > Could you find out a little more about your box and let us
                      > know what else you have in there? A quick glance at the
                      > Ensim web site wasn't particularly informative. Nor inspiring:
                      >
                      > "Where other software providers fail, Ensim has the expertise
                      > to deliver professional software to professional hosting
                      > businesses. With a seasoned executive management team and
                      > strong backing from leading members of the investment
                      > community, only Ensim has the products, technology,
                      > customers, partners and resources to lead and deliver the
                      > next generation of professional hosting solutions."
                      >
                      > Yuk.

                      Personally, I ditched ensim on my box and just did a complete rebuild of
                      Apache/1.3.27 with mod_perl/1.27. I abandoned Ensim's directory
                      structure for a pure and simple one that doesn't depart too much from
                      the default Apache config. This directory structure can grow in
                      complexity according to MY requirements and understanding, and NOT
                      according to some flaky commercial 3rd party software.

                      I can envisage Ensim being useful for a linux box being used for
                      reselling domain space, and by an administrator who has a fear of the
                      command line that cannot be overcome (ie., they need a web interface).
                      However, for any other scenario I cannot understand why you would need
                      to keep Ensim. Sure, some web hosts pre-install it on their linux boxes
                      (like mine did), but if you have full root access (like I do), I see no
                      reason why you should keep ensim around. I don't like dictators... you
                      have nothing to lose but your chains.

                      Of course, if you don't have full root access it's another story.

                      Tom
                    • Michael Koob
                      Have to agree with Tom. If you don t have need to allow large numbers of users control their sites and configs then ditch the ENSIM. If you do then it is a
                      Message 10 of 30 , May 5, 2003
                      View Source
                      • 0 Attachment
                        Have to agree with Tom. If you don't have need to allow large numbers of
                        users control their sites and configs then ditch the ENSIM. If you do
                        then it is a useful tool and can minimize some headaches. However, it
                        certainly takes some getting used to and I would really recommend
                        installing another Apache instance for mod_perl if you decide to keep
                        ENSIM. This allows you to put both pieces of software to their best use
                        without too much interaction between the them.

                        Michael

                        -----Original Message-----
                        From: Tom Gazzini [mailto:tomg@...]
                        Sent: Monday, May 05, 2003 8:36 AM
                        To: modperl@...
                        Subject: RE: Ensim


                        > > Are there any Ensim users out there who could just point me in the
                        > > right direction
                        >
                        > Could you find out a little more about your box and let us
                        > know what else you have in there? A quick glance at the
                        > Ensim web site wasn't particularly informative. Nor inspiring:
                        >
                        > "Where other software providers fail, Ensim has the expertise
                        > to deliver professional software to professional hosting
                        > businesses. With a seasoned executive management team and
                        > strong backing from leading members of the investment
                        > community, only Ensim has the products, technology,
                        > customers, partners and resources to lead and deliver the
                        > next generation of professional hosting solutions."
                        >
                        > Yuk.

                        Personally, I ditched ensim on my box and just did a complete rebuild of
                        Apache/1.3.27 with mod_perl/1.27. I abandoned Ensim's directory
                        structure for a pure and simple one that doesn't depart too much from
                        the default Apache config. This directory structure can grow in
                        complexity according to MY requirements and understanding, and NOT
                        according to some flaky commercial 3rd party software.

                        I can envisage Ensim being useful for a linux box being used for
                        reselling domain space, and by an administrator who has a fear of the
                        command line that cannot be overcome (ie., they need a web interface).
                        However, for any other scenario I cannot understand why you would need
                        to keep Ensim. Sure, some web hosts pre-install it on their linux boxes
                        (like mine did), but if you have full root access (like I do), I see no
                        reason why you should keep ensim around. I don't like dictators... you
                        have nothing to lose but your chains.

                        Of course, if you don't have full root access it's another story.

                        Tom
                      • Angie Ahl
                        ... this looks exactly the same as my server. ... THat s what I ve got, although just hacking away (gently) to get things working I changed mine to:
                        Message 11 of 30 , May 5, 2003
                        View Source
                        • 0 Attachment
                          > Angie,
                          >
                          > Here is how I have my mod_perl server working with ENSIM. Maybe this
                          > configuration will work for you it seems to be working out alright for
                          > me currently. If you are an ENSIM user on a sub account then ENSIM does
                          > only have the single mod_perl/Apache instance running on the box and the
                          > server configuration lays out as follows.
                          >
                          > Httpd.conf -> /etc/httpd/conf/httpd_app.conf (main configuration file
                          > which uses the Include directive to pull in the following files)
                          >
                          > /etc/appliance/apacheconf - Defines the default
                          > virtual host (Basically Rewrite rules for ENSIM)
                          > /etc/httpd/conf/jserv.conf - Included based on
                          > whether mod_jserv.c is linked in
                          > /etc/httpd/conf/roaming.conf - Included based on
                          > whether mod_roaming.c is linked in
                          > /etc/httpd/conf/asp.conf - Requires mod_perl as
                          > well as being uncommented by administrator
                          > /etc/httpd/conf/virtual - Directory that includes
                          > the virtual host configurations for all other domains/ips
                          >

                          this looks exactly the same as my server.

                          <SNIP>

                          > The same applies for
                          > mod_perl, with the straightforward filename
                          > /etc/httpd/conf/site7/cgi/mod_perl which contains the following
                          > directives on my machine.
                          >
                          > <IfModule mod_perl.c>
                          > Alias /perl /home/virtual/site7/fst/var/www/perl
                          > <Directory /home/virtual/site7/fst/var/www/perl>
                          > Allow from All
                          > AllowOverride All
                          > Order allow,deny
                          > Options +ExecCGI
                          > </Directory>
                          > SetEnv SITE_PERL /home/virtual/site7/fst/var/www/perl
                          > </IfModule>
                          >

                          THat's what I've got, although just hacking away (gently) to get things working
                          I changed mine to:

                          file: /etc/httpd/conf/site8/cgi/mod_perl

                          <IfModule mod_perl.c>
                          PerlModule Apache::Registry
                          PerlRequire /home/virtual/site8/fst/var/www/perl/Examples/WebClock.pm
                          Alias /perl /home/virtual/site8/fst/var/www/perl
                          <Directory /home/virtual/site8/fst/var/www/perl>
                          SetHandler perl-script
                          PerlHandler Apache::Registry
                          Options ExecCGI
                          </Directory>
                          <Location /time>
                          SetHandler perl-script
                          PerlHandler Examples::WebClock
                          </Location>
                          SetEnv SITE_PERL /home/virtual/site8/fst/var/www/perl
                          </IfModule>

                          Just to see if I could get a custom module operational. after making
                          webclock.pm executable it worked perfectly.... Yipee

                          > What is important to note here is that no handler is defined so this
                          > will execute as cgi as there are no mod_perl handlers defined. I am not
                          > sure exactly why this is but you must configure some PerlHandler for
                          > this directory if you wish to run mod_perl. It would appear as though
                          > they are really aiming for the use of Apache::Registry but since my
                          > site(s) make copious use of regular handlers I have done the following.
                          >

                          Yep. I took me a few days to realise that it was all set up for people porting
                          cgi's rather than people wanting to use actual modules

                          > In order to impact the other sites and the overall ENSIM configuration
                          > minimally I have placed a symbolic link from these original files/names
                          > to files in the directory of the user under which the mod_perl site
                          > runs. Something like /etc/httpd/conf/site7 ->
                          > /home/virtual/site7/fst/etc/httpd/conf/virtual/ssl-site.conf. I have
                          > also done the same for the files for SSI, mod_perl, cgi etc. This has
                          > the advantage of allowing you to log in as the sites user and make
                          > alterations to the configurations as needed. Since all of the users for
                          > the virtual hosts in this environment are chroot on login they could not
                          > see/access the configuration files themselves without these
                          > modifications.
                          >

                          That's quite a problem if you don't have root access I think (I do fortunately),
                          I just wanted to try and get everything set up right in the first place. but I
                          do need to get on with trying perl as I learn that stuff so this could be a good
                          stop gap. I'm still finding my way around Linux a bit too.

                          > I then added some configuration changes to my mod_perl file including a
                          > startup.pl file that pre-compiles all of my important Perl modules and
                          > specifies the Perl library that I am using (use lib
                          > "/home/virtual/site7/fst/var/www/mod_perl";).

                          could you give me an example of what you mean by precompile... do you mean call
                          them via PerlRequire ro something?

                          I'm going to re read that startup stuff .I missed something while being buried
                          in books I'm sure.


                          > A.) The user for the mod_perl virtual host cannot reboot the site
                          > themselves. This is a problem if you are running standard handlers as
                          > opposed to an Apache::Registry solution with Apache::RegistryLoader.
                          > This is due to the fact that any updates to code will require a restart
                          > to take effect which is a serious issue if the site is undergoing a lot
                          > of changes. You must log in as root in order to reboot the site.
                          > B.) Apache/mod_perl responds strangely to restarts in this environment.
                          > When I restart the server its memory footprint grows drastically on
                          > every restart. This is something I have not seen before and I would love
                          > to know why it is happening, but I have not had a chance to research it.
                          > This dictates full stop/start whenever changes are made to the Perl
                          > modules.

                          We could write a script that does it for them...

                          A proper Stop/Start script.
                          and protect it with the same username/password set up in ensim for them

                          > As for some of your specific questions:
                          >
                          > 1.) Apache::DBI needs to be downloaded and installed. Just install as
                          > root it should not impact any other sites. (If you are really concerned
                          > about putting it in the main Perl installation then install it to the
                          > directory included in the startup.pl file and it should work fine.)

                          I think I'll try the later. It helps with backups etc too.

                          > 2.) Guides recommended: http://perl.apache.org/docs/1.0/guide/index.html
                          > (This is the one with the real details), mod_perl Developer's Cookbook
                          > by Geoffrey Young (good quick overview, but you will end up looking to
                          > the first for specifics), and CPAN documentation/man pages.

                          I'll get that book.

                          I've already got the "Web Development with Apache and Perl" book wich has been
                          quite a help. Also got "Perl Cookbook" and Programming Perl. Didn't realise
                          there was a Mod_perl cookbook

                          >
                          > If I had more time to get my own server set-up I think that the optimal
                          > way to not impact the other sites and have your mod_perl Apache server
                          > running would be to install another instance of mod_perl in the file
                          > system of the site and proxy the requests from the main Apache server to
                          > the other instance for mod_perl requests. This would allow complete
                          > configuration of the new server with zero impact to the existing server
                          > and if you ever remove the site using ENSIM everything will be nice and
                          > clean. All that would be necessary is a few mod_proxy directives in the
                          > siteX.conf/ssl-siteX.conf files and everything else is easy. This
                          > certainly would be the ideal and would give you quite a few other
                          > benefits like proxy caching and memory conservation etc. This type of
                          > installation is described in detail in the mod_perl guide referred to in
                          > the url above.
                          >

                          I'll have agood read on that. Not sure how Ensim will react to a second Apache
                          having the Vhosts for that site but will have a look anyway.

                          > Sorry about being so verbose but explaining this to you helps me
                          > understand where I am at if you know what I mean.
                          >

                          No. Thanks very much for being so verbose. This is the biggest hurdle for me.
                          the language makes a lot of sense and does the structures of calling modules
                          etc. I was going mad trying to get other tools to behave this way... then I
                          realised I had the wrong tool.
                        • Marc Slagle
                          We use Ensim for one of our mod_perl platforms. It was a bit odd to configure at first, but heres what we do: Make sure you have the CPAN module installed and
                          Message 12 of 30 , May 6, 2003
                          View Source
                          • 0 Attachment
                            We use Ensim for one of our mod_perl platforms. It was a bit odd to
                            configure at first, but heres what we do:

                            Make sure you have the CPAN module installed and then install all the
                            modules you'll need (Apache::DBI) etc. You can get at the main apache conf
                            file in /etc/httpd/conf. The bottom of the file contains the includes for
                            the virtual hosts. You can place your own includes for a startup.pl in the
                            file as usual.

                            Each hosts configuration lives in its own sub-directory under
                            /etc/httpd/conf. The have names like "siteXX", where XX would be some
                            number. If you cant figure out which directory is for the site you are
                            configuring, you can have a look under /home/virtual. The actual
                            directories the files live in are there, along with a bunch of links. The
                            links will be the names of your configured sites. You should be able to get
                            the name of your configuration directory via ls -l.

                            Once you know what "siteXX" folders your site lives in, you can go back to
                            /etc/httpd/conf/siteXX. There will be several files in that directory. You
                            can create any filename you want to be included in the <virtualhost> block
                            of httpd.conf. When the server is restarted it'll grab every file in that
                            directory.

                            An example of the default mod_perl file under your site configuration would
                            be:

                            [root@ensim site67]# more mod_perl
                            <IfModule mod_perl.c>
                            Alias /perl /home/virtual/site67/fst/var/www/perl
                            <Directory /home/virtual/site67/fst/var/www/perl>
                            Allow from All
                            AllowOverride All
                            Order allow,deny
                            Options +ExecCGI

                            SetHandler perl-script
                            PerlHandler Apache::Registry
                            PerlSendHeader On

                            </Directory>
                            SetEnv SITE_PERL /home/virtual/site67/fst/var/www/perl
                            </IfModule>

                            One we added to make the site be handled by our module was:

                            <IfModule mod_perl.c>
                            Alias / /home/virtual/site67/fst/var/www/perl/
                            PerlSetVar region cincinnati
                            PerlSetVar tmplpath /home/virtual/site67/fst/var/www
                            <Directory /home/virtual/site67/fst/var/www/perl/>
                            SetHandler perl-script
                            PerlHandler Our::Handler
                            Allow from All
                            AllowOverride All
                            Order allow,deny
                            Options +ExecCGI
                            </Directory>
                            SetEnv SITE_PERL /home/virtual/site67/fst/var/www/perl/
                            </IfModule>

                            Once you do that you're all set. Since there isnt an apachectl program
                            anywhere to be found to check the configuration of your apache config files,
                            you'll need to run /usr/sbin/httpd -t, and then restart apache through the
                            Ensim web console.

                            One note: make backup copies of the files you create under the
                            /etc/httpd/conf/siteXX directory, since Ensim can overwrite those files if
                            you change anything via the web console for that site.

                            Hope that helps get you started.

                            Marc Slagle

                            ----- Original Message -----
                            From: "Angie Ahl" <angie@...>
                            To: <modperl@...>
                            Sent: Monday, May 05, 2003 6:49 AM
                            Subject: Ensim


                            > Hi guys (and gals)
                            >
                            > I'm Complete newbie to Linux/Perl/and Mod_perl
                            >
                            > (No it's not that bad ;)
                            >
                            > I have used apache on OSX for a couple of years now and happy in
                            httpd.conf /
                            > command line
                            >
                            > I'm a long time Lasso user looking for something more OO and tied into
                            apache,
                            > and it's got to do regex really really well. I think I found the right
                            thing.
                            >
                            > I'm currently terrified of having to recompile Apache and mod_perl as I'm
                            on one
                            > of these ensim box things. which seems to have a perl for the box and one
                            per
                            > site. I am the owner of the box, but I want to have as little impact on
                            other
                            > sites (that don't use mod_perl) as possible.
                            >
                            > Got mod_perl working, but only with apache:registry, apache:DBI would
                            appear to
                            > not be there for the whole server (not in any of the @inc's that I can
                            find).
                            >
                            > Are there any Ensim users out there who could just point me in the right
                            > direction, would I be right in saying seeing as Mod_perl is installed and
                            > working (I checked the environment things are running through mod_perl)
                            that I
                            > can just add a path to where I want to put my modules to perl's @INC and
                            then
                            > continue as normal.
                            >
                            > Sorry if I sound like a complete newbie in some respects (mod_perl) I
                            totally
                            > am.
                            >
                            > But I will persevere and get this working....
                            >
                            > any tips from ensim users most welcome
                            >
                            > PS feel free to say RTFM... if you could suggest which Manual and which
                            page
                            > that would be even better. I've got about 5 books and the online docs
                            > permanently open at this time.
                            >
                            > Thanks so much
                            >
                            > Angie
                            >
                          • Michael Koob
                            Has anyone else noticed that in this environment that restarts of Apache cause the memory usage of the process increase on each restart. I have not noticed
                            Message 13 of 30 , May 6, 2003
                            View Source
                            • 0 Attachment
                              Has anyone else noticed that in this environment that restarts of Apache
                              cause the memory usage of the process increase on each restart. I have
                              not noticed this in any other environment and suspect that it may have
                              to due with the ENSIM configuration. I have not dug into the problem to
                              attempt a solution yet but was wondering if anyone else had experienced
                              similar issues when pre-compiling Perl modules through startup.pl. I do
                              have the FreshRestart option turned on, but this configuration has been
                              used many times on a standard Apache configuration with no problems.

                              Any ideas???

                              Thanks in advance.


                              Michael Koob
                              MDK & Associates Inc.
                              michael@...


                              -----Original Message-----
                              From: Marc Slagle [mailto:marc.slagle@...]
                              Sent: Tuesday, May 06, 2003 4:26 PM
                              To: Angie Ahl
                              Cc: modperl@...
                              Subject: Re: Ensim


                              We use Ensim for one of our mod_perl platforms. It was a bit odd to
                              configure at first, but heres what we do:

                              Make sure you have the CPAN module installed and then install all the
                              modules you'll need (Apache::DBI) etc. You can get at the main apache
                              conf file in /etc/httpd/conf. The bottom of the file contains the
                              includes for the virtual hosts. You can place your own includes for a
                              startup.pl in the file as usual.

                              Each hosts configuration lives in its own sub-directory under
                              /etc/httpd/conf. The have names like "siteXX", where XX would be some
                              number. If you cant figure out which directory is for the site you are
                              configuring, you can have a look under /home/virtual. The actual
                              directories the files live in are there, along with a bunch of links.
                              The links will be the names of your configured sites. You should be
                              able to get the name of your configuration directory via ls -l.

                              Once you know what "siteXX" folders your site lives in, you can go back
                              to /etc/httpd/conf/siteXX. There will be several files in that
                              directory. You can create any filename you want to be included in the
                              <virtualhost> block of httpd.conf. When the server is restarted it'll
                              grab every file in that directory.

                              An example of the default mod_perl file under your site configuration
                              would
                              be:

                              [root@ensim site67]# more mod_perl
                              <IfModule mod_perl.c>
                              Alias /perl /home/virtual/site67/fst/var/www/perl
                              <Directory /home/virtual/site67/fst/var/www/perl>
                              Allow from All
                              AllowOverride All
                              Order allow,deny
                              Options +ExecCGI

                              SetHandler perl-script
                              PerlHandler Apache::Registry
                              PerlSendHeader On

                              </Directory>
                              SetEnv SITE_PERL /home/virtual/site67/fst/var/www/perl
                              </IfModule>

                              One we added to make the site be handled by our module was:

                              <IfModule mod_perl.c>
                              Alias / /home/virtual/site67/fst/var/www/perl/
                              PerlSetVar region cincinnati
                              PerlSetVar tmplpath /home/virtual/site67/fst/var/www
                              <Directory /home/virtual/site67/fst/var/www/perl/>
                              SetHandler perl-script
                              PerlHandler Our::Handler
                              Allow from All
                              AllowOverride All
                              Order allow,deny
                              Options +ExecCGI
                              </Directory>
                              SetEnv SITE_PERL /home/virtual/site67/fst/var/www/perl/
                              </IfModule>

                              Once you do that you're all set. Since there isnt an apachectl program
                              anywhere to be found to check the configuration of your apache config
                              files, you'll need to run /usr/sbin/httpd -t, and then restart apache
                              through the Ensim web console.

                              One note: make backup copies of the files you create under the
                              /etc/httpd/conf/siteXX directory, since Ensim can overwrite those files
                              if you change anything via the web console for that site.

                              Hope that helps get you started.

                              Marc Slagle

                              ----- Original Message -----
                              From: "Angie Ahl" <angie@...>
                              To: <modperl@...>
                              Sent: Monday, May 05, 2003 6:49 AM
                              Subject: Ensim


                              > Hi guys (and gals)
                              >
                              > I'm Complete newbie to Linux/Perl/and Mod_perl
                              >
                              > (No it's not that bad ;)
                              >
                              > I have used apache on OSX for a couple of years now and happy in
                              httpd.conf /
                              > command line
                              >
                              > I'm a long time Lasso user looking for something more OO and tied into
                              apache,
                              > and it's got to do regex really really well. I think I found the right
                              thing.
                              >
                              > I'm currently terrified of having to recompile Apache and mod_perl as
                              > I'm
                              on one
                              > of these ensim box things. which seems to have a perl for the box and
                              > one
                              per
                              > site. I am the owner of the box, but I want to have as little impact
                              > on
                              other
                              > sites (that don't use mod_perl) as possible.
                              >
                              > Got mod_perl working, but only with apache:registry, apache:DBI would
                              appear to
                              > not be there for the whole server (not in any of the @inc's that I can
                              find).
                              >
                              > Are there any Ensim users out there who could just point me in the
                              > right direction, would I be right in saying seeing as Mod_perl is
                              > installed and working (I checked the environment things are running
                              > through mod_perl)
                              that I
                              > can just add a path to where I want to put my modules to perl's @INC
                              > and
                              then
                              > continue as normal.
                              >
                              > Sorry if I sound like a complete newbie in some respects (mod_perl) I
                              totally
                              > am.
                              >
                              > But I will persevere and get this working....
                              >
                              > any tips from ensim users most welcome
                              >
                              > PS feel free to say RTFM... if you could suggest which Manual and
                              > which
                              page
                              > that would be even better. I've got about 5 books and the online docs
                              > permanently open at this time.
                              >
                              > Thanks so much
                              >
                              > Angie
                              >
                            • Ged Haywood
                              Hi there, ... I ve seen this and I m sure it s been mentioned before, on this List, outside the Ensim setup. Check the List archives. The last time I saw it
                              Message 14 of 30 , May 6, 2003
                              View Source
                              • 0 Attachment
                                Hi there,

                                On Tue, 6 May 2003, Michael Koob wrote:

                                > Has anyone else noticed that in this environment that restarts of Apache
                                > cause the memory usage of the process increase on each restart. I have
                                > not noticed this in any other environment and suspect that it may have
                                > to due with the ENSIM configuration.

                                I've seen this and I'm sure it's been mentioned before, on this List,
                                outside the Ensim setup. Check the List archives. The last time I
                                saw it mentioned was a couple of years ago I think. It was never a
                                big problem, how big are the increases?

                                73,
                                Ged.
                              • Michael Koob
                                The increase is very consistent on each restart and approximately the same as the size of the Perl modules imported. This makes sense. What I can t understand
                                Message 15 of 30 , May 6, 2003
                                View Source
                                • 0 Attachment
                                  The increase is very consistent on each restart and approximately the
                                  same as the size of the Perl modules imported. This makes sense. What I
                                  can't understand is why I seem to be getting a fresh set of Perl
                                  modules/memory on each restart. I will review the archives though.

                                  Thx

                                  Michael

                                  -----Original Message-----
                                  From: Ged Haywood [mailto:ged@...]
                                  Sent: Tuesday, May 06, 2003 8:10 PM
                                  To: Michael Koob
                                  Cc: mod_perl Mailing List
                                  Subject: RE: Ensim


                                  Hi there,

                                  On Tue, 6 May 2003, Michael Koob wrote:

                                  > Has anyone else noticed that in this environment that restarts of
                                  > Apache cause the memory usage of the process increase on each restart.

                                  > I have not noticed this in any other environment and suspect that it
                                  > may have to due with the ENSIM configuration.

                                  I've seen this and I'm sure it's been mentioned before, on this List,
                                  outside the Ensim setup. Check the List archives. The last time I saw
                                  it mentioned was a couple of years ago I think. It was never a big
                                  problem, how big are the increases?

                                  73,
                                  Ged.
                                • Victor Tsang
                                  We here suffer from the same problem, and have since changed our restart code to do stop and start instead which cure the problem. I have never digged
                                  Message 16 of 30 , May 8, 2003
                                  View Source
                                  • 0 Attachment
                                    We here suffer from the same problem, and have since changed our restart
                                    code to do 'stop' and 'start' instead which cure the problem. I have
                                    never digged deep into this, but one thing we realize is the restart
                                    command doesn't terminate the parent process, it only terminate all
                                    children and request parent to reload.


                                    Tor.

                                    Michael Koob wrote:
                                    >
                                    > The increase is very consistent on each restart and approximately the
                                    > same as the size of the Perl modules imported. This makes sense. What I
                                    > can't understand is why I seem to be getting a fresh set of Perl
                                    > modules/memory on each restart. I will review the archives though.
                                    >
                                    > Thx
                                    >
                                    > Michael
                                    >
                                    > -----Original Message-----
                                    > From: Ged Haywood [mailto:ged@...]
                                    > Sent: Tuesday, May 06, 2003 8:10 PM
                                    > To: Michael Koob
                                    > Cc: mod_perl Mailing List
                                    > Subject: RE: Ensim
                                    >
                                    > Hi there,
                                    >
                                    > On Tue, 6 May 2003, Michael Koob wrote:
                                    >
                                    > > Has anyone else noticed that in this environment that restarts of
                                    > > Apache cause the memory usage of the process increase on each restart.
                                    >
                                    > > I have not noticed this in any other environment and suspect that it
                                    > > may have to due with the ENSIM configuration.
                                    >
                                    > I've seen this and I'm sure it's been mentioned before, on this List,
                                    > outside the Ensim setup. Check the List archives. The last time I saw
                                    > it mentioned was a couple of years ago I think. It was never a big
                                    > problem, how big are the increases?
                                    >
                                    > 73,
                                    > Ged.
                                  • Ged Haywood
                                    Hi there, ... I m sure that s the best way to do it. 73, Ged.
                                    Message 17 of 30 , May 8, 2003
                                    View Source
                                    • 0 Attachment
                                      Hi there,

                                      On Fri, 9 May 2003, Victor Tsang wrote:

                                      > We here suffer from the same problem, and have since changed our restart
                                      > code to do 'stop' and 'start' instead which cure the problem.

                                      I'm sure that's the best way to do it.

                                      73,
                                      Ged.
                                    Your message has been successfully submitted and would be delivered to recipients shortly.