Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: [renamed] Error after updating to Apache 2.0.55  (Read 8157 times)

0 Members and 1 Guest are viewing this topic.

jnendel

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
[renamed] Error after updating to Apache 2.0.55
« on: November 09, 2005, 06:10:02 pm »
I upgraded Apache from the Fedora core 2 binary version of 2.0.49 to version 2.5.0 because of a vulnerability alert.  Since there was no rpm version 2.5.0 I compiled the source with the --enable-so option and added the LoadModule line for the libphp4.so to the httpd.conf file.  My PHP is version 4.3.10.  Now when I go to run Coppermine I get a "template error".  Any idea, because I sure don't?
Thanks. :-\\
« Last Edit: November 09, 2005, 08:25:06 pm by Nibbler »
Logged

Nibbler

  • Guest
Re: Apache Vulnerbility Upgrade
« Reply #1 on: November 09, 2005, 06:16:36 pm »
Probably unrelated, please post the full error message.
Logged

jnendel

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: Apache Vulnerbility Upgrade
« Reply #2 on: November 09, 2005, 06:22:12 pm »
The full error message is:
Failed to find block 'login'(#(<!-- BEGIN login -->)(.*?)(<!-- END login -->)#s) in :
When I revert back to Apache 2.49 the error goes away.
Logged

Nibbler

  • Guest
Re: Apache Vulnerbility Upgrade
« Reply #3 on: November 09, 2005, 06:30:23 pm »
Be accurate with your version numbers please, it is confusing. I have Coppermine running fine on 2.0.54
Logged

jnendel

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: Apache Vulnerbility Upgrade
« Reply #4 on: November 09, 2005, 06:55:50 pm »
I'm trying to run it on Apache 2.0.55.
Logged

Nibbler

  • Guest
Re: Apache Vulnerbility Upgrade
« Reply #5 on: November 09, 2005, 07:34:55 pm »
I just compiled Apache 2.0.55 and am getting template errors also. Looks like a regex problem.
Logged

Nibbler

  • Guest
Re: Apache Vulnerbility Upgrade
« Reply #6 on: November 09, 2005, 08:23:46 pm »
Solved by recompiling PHP with the --with-pcre-regex option enabled. This is not a Coppermine specific error, but this may help others with the same issue.
Logged

jnendel

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: [renamed] Error after updating to Apache 2.0.55
« Reply #7 on: November 09, 2005, 08:33:26 pm »
My PHP already had --with-pcre-regex=/usr - would the /usr be the problem?  Thanks.
Logged

Nibbler

  • Guest
Re: [renamed] Error after updating to Apache 2.0.55
« Reply #8 on: November 09, 2005, 08:38:37 pm »
Yeah, you need to switch to using the bundled pcre instead of specifying an external one.
Logged

jnendel

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: [renamed] Error after updating to Apache 2.0.55
« Reply #9 on: November 09, 2005, 10:18:12 pm »
I followed your instructions and I compiled PHP with the --with-pcre-regex option (I also changed the path of the to apache include to the new Apache 2.0.55 installation).  I still have the production Coppermine running.  If I bring down current apache and start up the 2.0.55 Apache will it automatically find the newly installed PHP or is there somewhere in Coppermine I have to change a setting?  Or do I have to run the Install again.  I'm afraid if I bring it down it might not come back up and I won't know what to do.  Thank you for any help
Logged

Nibbler

  • Guest
Re: [renamed] Error after updating to Apache 2.0.55
« Reply #10 on: November 09, 2005, 10:29:41 pm »
You should be able to switch apaches with no problems, it's all on a different level to anything Coppermine has control over. This really isn't the place for server setup support.
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.03 seconds with 15 queries.