Apache error for debian 2.6.24

2009-08-25 Thread Michael Kurecka
I'm trying to run Apache on a debian 2.6.24 system but it doesn't seem to be working and I get the following error in the error.log file once a second. (38)Function not implemented: Couldn't create pollset in child; check system or user limits Upon googling I came across various posts that stat

Re: apache error

2009-02-21 Thread Chris Bannister
On Wed, Feb 18, 2009 at 05:20:43PM -0500, Paul Cartwright wrote: > this still doesn't answer my original question of how to actually remove all > the config files for apache, and basically start over. Please read the man page of your preferred package manager. It explains how to remove a package

Re: apache error

2009-02-18 Thread Florian Kulzer
On Wed, Feb 18, 2009 at 17:20:43 -0500, Paul Cartwright wrote: [...] > this still doesn't answer my original question of how to actually remove all > the config files for apache, and basically start over. dpkg -S /etc/apache2 will list all packages that have files in /etc/apache2. Purge all th

Re: apache error-SOLVED

2009-02-18 Thread Paul Cartwright
On Wed February 18 2009, Florian Kulzer wrote: > Try these commands to see which process is bound to port 80: > > lsof -i :80 > netstat -plant | grep ':80 ' I got it. apache2-common was what i had to remove & purge.. apache is working now. I was using nginx as a quick fix, because I couldn't get a

Re: apache error

2009-02-18 Thread Paul Cartwright
On Wed February 18 2009, Florian Kulzer wrote: > > (98)Address already in use: make_sock: could not bind to address [::]:80 > > (98)Address already in use: make_sock: could not bind to address > > 0.0.0.0:80 no listening sockets available, shutting down > > Unable to open logs > >  failed! > > Try

Re: apache error

2009-02-18 Thread Florian Kulzer
On Wed, Feb 18, 2009 at 16:29:14 -0500, Paul Cartwright wrote: > On Wed February 18 2009, ss11223 wrote: > > When I see socket already in use it usually means that apache is > > already running. > > > > check with "ps -A | grep apache" > > > > and then > > > > "killal apache2" and try again [...]

Re: apache error

2009-02-18 Thread Paul Cartwright
On Wed February 18 2009, ss11223 wrote: > When I see socket already in use it usually means that apache is > already running. > > check with "ps -A | grep apache" > > and then > > "killal apache2" and try again # ps -A | grep apache # /etc/init.d/apache2 restart Restarting web server: apache2(98)A

Re: apache error

2009-02-18 Thread ss11223
On Feb 18, 4:10 pm, Paul Cartwright wrote: > # /etc/init.d/apache2 restart > Restarting web server: apache2(98)Address already in use: make_sock: could not > bind to address [::]:80 > (98)Address already in use: make_sock: could not bind to address [::]:80 > (98)Address already in use: make_sock:

apache error

2009-02-18 Thread Paul Cartwright
I was trying to follow the HOW-TO: http://www.howtoforge.com/perfect-server-debian-lenny-ispconfig2 when I got to page 5 and the apache2 setup. I had previously installed apache , and had changed some settings, and apache doesn't work. When i try to remove it, and purge it, it still leaves those

Apache error [emerg] (38) Function not implemented: couldn't create accepte lock

2005-12-19 Thread debian
Hello, I still have problems with apache 2. I installed 2 new identical servers and i have the same error on both when trying to start Apache: [warn] pid file /var/run/apache2.pid overwritten -- Unclean shutdown of previous apache run ? [emerg] (38)Function not implemented: Couldn't create accep

mod_perl for apache (error)

2004-11-08 Thread Umar Draz
hi dear members!    i want comple mod-perl for apache after run make i got this error    /usr/bin/ld: cannot find -lperlcollect2: ld returned 1 exit statusmake[1]: *** [libperl.so] Error 1make[1]: Leaving directory `/home/umar/pkg/mod_perl-1.29/apaci'make: *** [apxs_libperl] Error 2   plz help what

Re: apache error on restart --gaah!

2004-10-20 Thread Matt Price
Matt Price wrote: hey folks, well, after three months I rebooted my computer today -- that was silly! Now apache won't start. I get this error: Starting web server: apachePHP Warning: Unknown(): Unable to load dynamic library '/usr/lib/php4/20020429/curl.so' - /usr/lib/php4/20020429/curl.s

apache error on restart --gaah!

2004-10-20 Thread Matt Price
hey folks, well, after three months I rebooted my computer today -- that was silly! Now apache won't start. I get this error: Starting web server: apachePHP Warning: Unknown(): Unable to load dynamic library '/usr/lib/php4/20020429/curl.so' - /usr/lib/php4/20020429/curl.so: cannot open sha

Re: Apache Error: srm.conf

2000-12-29 Thread Rob VanFleet
On Fri, Dec 29, 2000 at 12:49:50PM -0600, Nathan E Norman wrote: > According to the online Apache documentation [0], the directive > "AddDefaultCharsetName" does not exist. The "AddDefaultCharset" line > appears to do the right thing; I don't kow why that other line got in > there. Comment it out

Re: Apache Error: srm.conf

2000-12-29 Thread Nathan E Norman
On Wed, Dec 27, 2000 at 03:19:13PM -0600, Rob VanFleet wrote: > Invalid command 'AddDefaultCharsetName', perhaps mis-spelled or defined by a > module not included in the server configuration > > I'm somewhat leery of removing the offending line, as it seems to be a > security > fix for cross-site

Re: Apache Error: srm.conf

2000-12-29 Thread Florian Reiser
On Wed, Dec 27, 2000 at 03:19:13PM -0600, Rob VanFleet wrote: > > Apache has been running fine for some time now, and for some reason (I suppose > it was from something being upgraded, but I don't remember seeing anything > apache related) I'm now getting this error whenever attempting to start >

Re: Apache Error: srm.conf

2000-12-28 Thread Wayne Topa
Subject: Apache Error: srm.conf Date: Wed, Dec 27, 2000 at 03:19:13PM -0600 In reply to:Rob VanFleet Quoting Rob VanFleet([EMAIL PROTECTED]): > > Apache has been running fine for some time now, and for some reason (I suppose > it was from something being upgraded, bu

Apache Error: srm.conf

2000-12-27 Thread Rob VanFleet
Apache has been running fine for some time now, and for some reason (I suppose it was from something being upgraded, but I don't remember seeing anything apache related) I'm now getting this error whenever attempting to start apache: Syntax error on line 133 of /etc/apache/srm.conf: Invalid comma