Re: Crashing Apache port

2019-04-02 Thread The Doctor via freebsd-ports
On Tue, Apr 02, 2019 at 05:14:29PM -0700, Jack L. wrote: > Are you using php? Does php -v result in a crash? > Yes I use php and No crash. > On Tue, Apr 2, 2019 at 1:54 PM Jonathan Chen wrote: > > > > On Wed, 3 Apr 2019 at 09:40, The Doctor wrote: > > [...] > > > Just recompiled and still

Re: Crashing Apache port

2019-04-02 Thread Jack L.
Are you using php? Does php -v result in a crash? On Tue, Apr 2, 2019 at 1:54 PM Jonathan Chen wrote: > > On Wed, 3 Apr 2019 at 09:40, The Doctor wrote: > [...] > > Just recompiled and still crashing > > > > [Tue Apr 02 14:38:55.791536 2019] [core:notice] [pid 33235:tid 34380963840] > >

Re: Crashing Apache port

2019-04-02 Thread Jonathan Chen
On Wed, 3 Apr 2019 at 09:40, The Doctor wrote: [...] > Just recompiled and still crashing > > [Tue Apr 02 14:38:55.791536 2019] [core:notice] [pid 33235:tid 34380963840] > AH00052: child pid 33933 exit signal Segmentation fault (11) > [Tue Apr 02 14:38:55.791603 2019] [core:notice] [pid

Re: Crashing Apache port

2019-04-02 Thread The Doctor via freebsd-ports
On Wed, Apr 03, 2019 at 08:48:25AM +1300, Jonathan Chen wrote: > On Wed, 3 Apr 2019 at 07:48, The Doctor via freebsd-ports > wrote: > > > > Got a major concern. > > > > I upgraded to FreeBSD 12.0 over the weekend. > > > > Ports were upgraded correct on the servers. > > > > Made an adjustment for

Re: Crashing Apache port

2019-04-02 Thread Jonathan Chen
On Wed, 3 Apr 2019 at 07:48, The Doctor via freebsd-ports wrote: > > Got a major concern. > > I upgraded to FreeBSD 12.0 over the weekend. > > Ports were upgraded correct on the servers. > > Made an adjustment for apache 2.4 . > > Suddenly one one server httpd is crashing without reason. > > Ran

Crashing Apache port

2019-04-02 Thread The Doctor via freebsd-ports
Got a major concern. I upgraded to FreeBSD 12.0 over the weekend. Ports were upgraded correct on the servers. Made an adjustment for apache 2.4 . Suddenly one one server httpd is crashing without reason. Ran gbd it turns out a module in devel/apr1 might be at issue. Can we get consistency?

Re: "security/py-certbot-apache" port

2018-02-23 Thread Mathieu Arnold
On Fri, Feb 23, 2018 at 12:02:18PM +, Carmel NY wrote: > I just updated my system and installed the "security/py-certbot-apache" port > using "synth". The installation went fine. The problem now is when I attempt > to run "certbot" it fails. The err

"security/py-certbot-apache" port

2018-02-23 Thread Carmel NY
I just updated my system and installed the "security/py-certbot-apache" port using "synth". The installation went fine. The problem now is when I attempt to run "certbot" it fails. The error log is below. I was forced to remove the py-certbot-apache port in order to g

Re: unable to set default apache port

2014-09-19 Thread Mike Clarke
On Tuesday 09 Sep 2014 08:09:10 Vick Khera wrote: Thanks. This seems to be working. Should I file a bug report? It seems to me that the DEFAULT_VERSIONS ought to be sufficient. Things have changed. It looks like it got fixed with version 367897 of Mk/bsd.apache.mk on September 10.

Re: unable to set default apache port

2014-09-09 Thread Vick Khera
On Mon, Sep 8, 2014 at 4:27 PM, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: APACHE_PORT=www/apache22 Thanks. This seems to be working. Should I file a bug report? It seems to me that the DEFAULT_VERSIONS ought to be sufficient. ___

unable to set default apache port

2014-09-08 Thread Vick Khera
My recent run of poudriere to build my package collection rebuilt all my apache dependents against 2.4. I knew this was coming, so had set in my poudriere make.conf the following: DEFAULT_VERSIONS=mysql=5.5 pgsql=9.2 apache=2.2 perl5=5.16 However, that seems to be ignored. The build logs do show

Re: unable to set default apache port

2014-09-08 Thread Mike Clarke
On Monday 08 Sep 2014 15:52:17 Vick Khera wrote: My recent run of poudriere to build my package collection rebuilt all my apache dependents against 2.4. I knew this was coming, so had set in my poudriere make.conf the following: DEFAULT_VERSIONS=mysql=5.5 pgsql=9.2 apache=2.2 perl5=5.16

Re: Apache port

2012-09-09 Thread Jos Chrispijn
Olli Hauer: Hi Jos, it's easy, even quickly overseen DBD != BDB AUTHN_DBD and DBD are SQL modules and this apache options are only valid if APR was build with MYSQL, PGSQL or SQLITE support. In the past we ask the user to specify if APR was build with SQL support, now the port checks the

Re: Apache port

2012-09-09 Thread Jos Chrispijn
Olli, This is my current setup of Apache: === The following configuration options are available for apache22-2.2.22_8: AUTH_BASIC=on: mod_auth_basic AUTH_DIGEST=on: mod_auth_digest AUTHN_ALIAS=on: mod_authn_alias AUTHN_ANON=on: mod_authn_anon AUTHN_DBD=on: mod_authn_dbd

Re: Apache port

2012-09-09 Thread Jos Chrispijn
Sorry, it should work as there is a symbolic link for the one you are searching for... Really don't understand why I still get the port is IGNORED line on portupgrade -a Jos Jos Chrispijn: Olli, This is my current setup of Apache: === The following configuration options are available for

Re: Apache port

2012-09-09 Thread Olli Hauer
On 2012-09-09 12:58, Jos Chrispijn wrote: Sorry, it should work as there is a symbolic link for the one you are searching for... Really don't understand why I still get the port is IGNORED line on portupgrade -a Jos Jos Chrispijn: Olli, This is my current setup of Apache: === The

Apache port

2012-09-08 Thread Jos Chrispijn
Just updating Apache22 (apache-2.2.22_6) and get this error: Port marked as IGNORE: www/apache22: AUTHN_DBD and DBD requires APR-util to have DBD support build in. Please rebuild APR at last with one DBD backend The issue is that I did config APR with DBD support. Currently have

Re: Apache port

2012-09-08 Thread Olli Hauer
On 2012-09-08 16:22, Jos Chrispijn wrote: Just updating Apache22 (apache-2.2.22_6) and get this error: Port marked as IGNORE: www/apache22: AUTHN_DBD and DBD requires APR-util to have DBD support build in. Please rebuild APR at last with one DBD backend The issue is that I did

Re: Apache port

2012-09-08 Thread Warren Block
On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 16:22, Jos Chrispijn wrote: Just updating Apache22 (apache-2.2.22_6) and get this error: Port marked as IGNORE: www/apache22: AUTHN_DBD and DBD requires APR-util to have DBD support build in. Please rebuild APR at last with one DBD

Re: Apache port

2012-09-08 Thread Olli Hauer
On 2012-09-08 17:58, Warren Block wrote: On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 16:22, Jos Chrispijn wrote: Just updating Apache22 (apache-2.2.22_6) and get this error: Port marked as IGNORE: www/apache22: AUTHN_DBD and DBD requires APR-util to have DBD support build in.

Re: Apache port

2012-09-08 Thread Warren Block
On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 17:58, Warren Block wrote: How about adding mention of SQL in the IGNORE message? I will rewrite the message to Please rebuild APR at last with one DBD backend (MYSQL, PGSQL or SQLITE) Hope then is is more clear. That is much better.

Re: Apache port

2012-09-08 Thread Jerry
On Sat, 8 Sep 2012 10:57:35 -0600 (MDT) Warren Block articulated: On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 17:58, Warren Block wrote: How about adding mention of SQL in the IGNORE message? I will rewrite the message to Please rebuild APR at last with one DBD backend

Re: Apache port

2012-09-08 Thread Olli Hauer
On 2012-09-09 00:48, Jerry wrote: On Sat, 8 Sep 2012 10:57:35 -0600 (MDT) Warren Block articulated: On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 17:58, Warren Block wrote: How about adding mention of SQL in the IGNORE message? I will rewrite the message to Please rebuild APR at

Re: change in apache port configuration options

2008-01-29 Thread Vivek Khera
be a good idea to add one. In the past when I've changed variable names in my ports I've added compatibility shims for about 6 months, then warnings for another 6, then dropped support for the old names. It only fails if you use WITH_BDB_VER to set WITH_BERKELEYDB for the apache port like I

Re: change in apache port configuration options

2008-01-28 Thread Clement Laforet
Hi, On Sun, Jan 27, 2008 at 09:36:55PM -0500, Vivek Khera wrote: It seems that the recent changes to the apache20 port Makefile.modules has broken how I've been configuring my systems. In my make.conf file I have globally set the following: WITH_BDB_VER=43 which instructs many ports

Re: change in apache port configuration options

2008-01-28 Thread Doug Barton
Clement Laforet wrote: WITH_BERKELEYDB is now deprecated in favor of WITH_BDB in order to make BDB support consistent with the rest of the ports tree. Is there a warning generated for users that have the old one defined? If not it would be a good idea to add one. In the past when I've

change in apache port configuration options

2008-01-27 Thread Vivek Khera
It seems that the recent changes to the apache20 port Makefile.modules has broken how I've been configuring my systems. In my make.conf file I have globally set the following: WITH_BDB_VER=43 which instructs many ports to use that version of Berkeley DB. Furtnermore, in my apache