Apache :: Rotatelogs Crashes When Used As Piped Logging With Httpd
Apr 16, 2015
I've got a problem at a local customer with rotatelogs.exe and the current release of Apache HTTPD 2.4.12.
I've downloaded the 64-bit zip-file (VC11) and installed the VC11 vcredist in both 32- and 64-bit version.
The project is to upgrade apache 2.2 to apache 2.4. I've adjusted the configuration and added rotatelogs for log rotation for error_log and access_log.
The configuration is 100% correct, I can copy the line to cmd.exe and it runs correctly.
Variables are set in global environment, APACHE_HOME is set with "/" instead of "" to get sure rotatelogs.exe is found.
I tried to upgrade from apache 2.0.51 to 2.0.63 but it crashes as soon as new version is started and httpd is reloaded.
here is a part of the log
[Fri Apr 25 10:57:46 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 3642, waiting for debugger Segmentation Fault in 3697, waiting for debugger Segmentation Fault in 3696, waiting for debugger [Fri Apr 25 10:58:11 2008] [notice] caught SIGTERM, shutting down [Fri Apr 25 10:58:22 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Fri Apr 25 10:58:22 2008] [notice] mod_security/1.9.4 configured [Fri Apr 25 10:58:22 2008] [notice] Digest: generating secret for digest authentication ... [Fri Apr 25 10:58:22 2008] [notice] Digest: done [Fri Apr 25 10:58:22 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK [Fri Apr 25 10:58:22 2008] [notice] LDAP: SSL support unavailable [Fri Apr 25 10:58:23 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 5422, waiting for debugger Segmentation Fault in 5421, waiting for debugger Segmentation Fault in 5452, waiting for debugger Segmentation Fault in 5461, waiting for debugger Segmentation Fault in 5451, waiting for debugger Segmentation Fault in 5466, waiting for debugger Segmentation Fault in 5465, waiting for debugger Segmentation Fault in 7363, waiting for debugger Segmentation Fault in 5435, waiting for debugger Segmentation Fault in 5906, waiting for debugger Segmentation Fault in 7251, waiting for debugger Segmentation Fault in 6041, waiting for debugger Segmentation Fault in 7723, waiting for debugger Segmentation Fault in 7986, waiting for debugger Segmentation Fault in 9659, waiting for debugger Segmentation Fault in 9643, waiting for debugger Segmentation Fault in 9361, waiting for debugger Segmentation Fault in 9744, waiting for debugger Segmentation Fault in 9543, waiting for debugger Segmentation Fault in 9879, waiting for debugger Segmentation Fault in 9794, waiting for debugger Segmentation Fault in 9758, waiting for debugger [Fri Apr 25 11:01:10 2008] [notice] caught SIGTERM, shutting down [Fri Apr 25 11:01:12 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Fri Apr 25 11:01:12 2008] [notice] mod_security/1.9.4 configured [Fri Apr 25 11:01:12 2008] [notice] Digest: generating secret for digest authentication ... [Fri Apr 25 11:01:12 2008] [notice] Digest: done [Fri Apr 25 11:01:12 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK [Fri Apr 25 11:01:12 2008] [notice] LDAP: SSL support unavailable [Fri Apr 25 11:01:13 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 11634, waiting for debugger Segmentation Fault in 11635, waiting for debugger Segmentation Fault in 11661, waiting for debugger Segmentation Fault in 11695, waiting for debugger Segmentation Fault in 11760, waiting for debugger Segmentation Fault in 11723, waiting for debugger Segmentation Fault in 11694, waiting for debugger Segmentation Fault in 11837, waiting for debugger Segmentation Fault in 11812, waiting for debugger Segmentation Fault in 12022, waiting for debugger Segmentation Fault in 11848, waiting for debugger Segmentation Fault in 11879, waiting for debugger Segmentation Fault in 13342, waiting for debugger Segmentation Fault in 12062, waiting for debugger Segmentation Fault in 13428, waiting for debugger Segmentation Fault in 13569, waiting for debugger Segmentation Fault in 11849, waiting for debugger Segmentation Fault in 13881, waiting for debugger Segmentation Fault in 13380, waiting for debugger [Fri Apr 25 11:02:27 2008] [notice] caught SIGTERM, shutting down [Fri Apr 25 11:02:29 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Fri Apr 25 11:02:29 2008] [notice] mod_security/1.9.4 configured [Fri Apr 25 11:02:29 2008] [notice] Digest: generating secret for digest authentication ... [Fri Apr 25 11:02:29 2008] [notice] Digest: done [Fri Apr 25 11:02:29 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK [Fri Apr 25 11:02:29 2008] [notice] LDAP: SSL support unavailable [Fri Apr 25 11:02:30 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 14123, waiting for debugger Segmentation Fault in 14154, waiting for debugger Segmentation Fault in 14156, waiting for debugger Segmentation Fault in 14273, waiting for debugger Segmentation Fault in 14114, waiting for debugger Segmentation Fault in 14308, waiting for debugger Segmentation Fault in 14316, waiting for debugger Segmentation Fault in 14274, waiting for debugger Segmentation Fault in 14315, waiting for debugger Segmentation Fault in 15562, waiting for debugger Segmentation Fault in 14113, waiting for debugger Segmentation Fault in 15583, waiting for debugger Segmentation Fault in 15615, waiting for debugger Segmentation Fault in 15616, waiting for debugger Segmentation Fault in 15584, waiting for debugger Segmentation Fault in 15637, waiting for debugger Segmentation Fault in 15631, waiting for debugger Segmentation Fault in 15614, waiting for debugger Segmentation Fault in 16332, waiting for debugger Segmentation Fault in 14262, waiting for debugger Segmentation Fault in 17504, waiting for debugger Segmentation Fault in 15638, waiting for debugger Segmentation Fault in 17515, waiting for debugger Segmentation Fault in 18105, waiting for debugger Segmentation Fault in 17516, waiting for debugger Segmentation Fault in 18163, waiting for debugger Segmentation Fault in 18175, waiting for debugger Segmentation Fault in 18177, waiting for debugger Segmentation Fault in 18178, waiting for debugger Segmentation Fault in 18149, waiting for debugger Segmentation Fault in 19931, waiting for debugger Segmentation Fault in 20098, waiting for debugger Segmentation Fault in 18176, waiting for debugger
I am on VPS and myself am quite a noob in this. Upgrade is performed by the support people.
If you guys can help please explain in lame terms Let me know if you need some specific info about the system.
I was suggested that some modules might not be upgraded yet and they cause the crash, so to fix I should remove modules one by one from httpd config until get to the problematic one.
I am running CPanel and WHM, and every morning, I need to restart apache manually in order to work. Then it works for the whole day. It crashes I guess, but I don't know why. What logs do I need to check?
I've been trying to see whats going on with this server for a few days now but am unable to resolve the issue.
This is a 3 server setup. One is a mail server, another a mysql server and the host server. The apache on the host has plenty of ram (8 gigs) and it is currently under 5 gigs. The site is mainly a social networking site.
Now the apache would crash at times like 1:16, 2:17, 3:16, 4:18; basically in 1 hour intervals. Now it doesn't always crash every hour. Sometimes it might go up to 5 hours and may crash at say 8:50
Well it turns out that the mail server new mass mailing method has some sort of effect on the host server.
This is what happens.
1.) Host has a ton of apache processes up and running (site is fine and dandy).
2.) Mail server is about to launch its barrage email (load about .5)
3.) Then all of the apache processes stopped appearing on my top (nobody is able to browse the site at this point).
4.) after a few minutes the apache processes reappear and the site loads again.
5.) Mail server is now mass mailing and its loads reaches up to 4.
6.) WHM emails me that apache was down and it restarted the service.
Here is the interesting thing about this. First of all I found out that the apache processes were actually not gone. They were somehow suppressed. For example during this freeze moment, if I run a "ps aux" I see that all the apache process are running yet they are not using any cpu or ram (which is why I don't see them on top). Now if I were to do a "service httpd restart" during this moment, it will restart but will still be frozen until its set time.
When the site is accessible again, that is when the mail starts leaving from the mail server.
The owner thinks this is related, and I tend to agree.
The only problem is that I have no clue as to what is going on. Apache does not leave any error logs period. Nothing in messages or in exim logs. For a while I thought it might be lfd killing the apache but I was wrong. Nothing informative on the lfd logs either.
Could it be perhaps a bind issue? Somehow the mail server takes over the host system before its launch?
I'm posting this in the hope that some of the techies here and give me some hints and directions where I can find an answer. Perhaps someone who read this thread has seen this kind of issue before.
I just bought a new dedicated server and have got Lxadmin on it. Now lxadmin , automatically uses a different loggin system than I would want it to use. It creates a seperate log file for each doamin.
They are located in /home/httpd/EXAMPLE.com/stats
EXAMPLE.com-error_log EXAMPLE.com-custom_log
Now the problem is that I have literally hundreds of domains and I want it to instead log at a single place and not at these hundreds of seperate places.
This is the root cause of my problem
# The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file.
I am unable to have any kind of centralised logging command because of the individual entries for each Virtual host.
Even if i can manually remove those entries once, and new domain created by lxadmin will have that same problem. Morevoer, any kind of update of lxadmin which rebuilds the database will also ruin all the hardwork that I put in.
Is there any suggestion / solution to this problem? Have centralised data at one place in a single file?
I'm using mod_perl 2.0.7 on Windows with Apache 2.2.23. I got Apache from Apachelounge, and compiled mod_perl and perl 5.16.2 myself using Visual Studio 2008. I'm using a 32-bit Windows Vista.
Pretty frequently my app (which works just fine on Linux) makes Apache crash. If I perform 500 requests with Apache Bench, I see this:
Benchmarking localhost (be patient) Completed 100 requests Completed 200 requests Completed 300 requests apr_socket_recv: An existing connection was forcibly closed by the remote host. (730054) Total of 338 requests completed
In the apache error log I see apache is restarting, but this results in some HTTP 500 errors that make the apache-bench results fail. When using a web browser, I also get these http 500 errors.
If I run the application using native CGI (i.e. I turn off mod_perl) I do not see crashes but of course it is *very* slow.
How can I find out what makes apache/mod_perl crash?
I asked the same on the modperl mailing lists, there they said I needed the symbol files for apache (*.pdb files). Where are these?
I encountered a strange problem when installing apache 2.2 or 2.4 as a service and set the service to be automaticly started.On restart of windows, apache service crashes with an access violation.
I recently updated to apache 2.2 and when I went to check
/usr/local/apache/conf/httpd.conf
I noticed that a lot of the stuff was missing from what I usually see in apache 1.3 Was a new file created when the update was finish? I used easyapache to make the update.
how should I optimize httpd.conf on my server. Apache was set up by my friend, unfortunately it started to "stuck" lately during peak time. Browser is connecting to a website for a long time before it actually starts to load it.
I can't reach my website, I get a "corrupted content" error message in the browser.Looking into apache (version 2.4.7), I get
Code: ~$ apachectl -S AH00526: Syntax error on line 22 of /etc/apache2/sites-enabled/000-default.conf: SSLCertificateKeyFile: file '/etc/ssl/private/owncloud.key' does not exist or is empty Action '-S' failed.
However, I double checked that the file is in the appropriate location and does contain the key, so maybe apache has no permission. afaik, it doesn't run as root all the time - or only for a short time?
permissions for the key file are as follows:
Code: ~$ sudo ls -l /etc/ssl/private/owncloud.key -rw-r--r-- 1 root ben 1704 Sep 28 04:01 /etc/ssl/private/owncloud.key
, where ben is my normal user.
It was suggested to me on the httpd IRC channel that maybe apparmor was doing something wrong, but I don't know how to investigate that.
I did some googling and searching on Apache lounge forums prior to posting this question, but I didn't find a definite answer to whether is it ok to use Apache Httpd v2.4.X VC10
I keep trying to restart Apache but it wont restart... I run a command line to restart it, but nothing happens. Here is what I have tried:
Quote:
-bash-3.1# chroot /home/fatehost.net/runtime_layeredpanel/ fatehost:/# /etc/ bash: /etc/: is a directory fatehost:/# /etc/init.d bash: /etc/init.d: is a directory fatehost:/# /etc/init.d/httpd-users Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload fatehost:/# /etc/init.d/httpd-users start Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address 205.209.135.132:80 no listening sockets available, shutting down Unable to open logs fatehost:/# /etc/init.d/httpd-users restart Forcing reload of web server: Apache2httpd (pid 5955) already running . fatehost:/# /etc/init.d/httpd-users force-reload Forcing reload of web server: Apache2. fatehost:/# /etc/init.d/httpd force-reload Forcing reload of web server: Apache2. fatehost:/# /etc/init.d/httpd-users restart Forcing reload of web server: Apache2httpd (pid 13475) already running . fatehost:/# fatehost:/# /etc/init.d/httpd-users start Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address 205.209.135.132:80 no listening sockets available, shutting down Unable to open logs fatehost:/# /etc/init.d/httpd-users stop Stopping web server: Apache2. fatehost:/# fatehost:/# /etc/init.d/httpd-users start Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address 205.209.135.132:80 no listening sockets available, shutting down Unable to open logs fatehost:/# fatehost:/# sudo /etc/init.d/httpd-users stop bash: sudo: command not found fatehost:/# su root /etc/init.d/httpd-users restart Forcing reload of web server: Apache2httpd (pid 20391) already running . fatehost:/# /etc/init.d/httpd-users reboot Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload fatehost:/# reboot WARNING: could not determine runlevel - doing soft reboot (it's better to use shutdown instead of reboot from the command line) shutdown: timeout opening/writing control channel /dev/initctl init: timeout opening/writing control channel /dev/initctl fatehost:/# WARNING: could not determine runlevel - doing soft reboot bash: WARNING:: command not found fatehost:/# (it's better to use shutdown instead of reboot from the command line) > shutdown: timeout opening/writing control channel /dev/initctl > init: timeout opening/writing control channel /dev/initctl > fatehost:/# /home/fatehost.net/runtime_layeredpanel bash: /home/fatehost.net/runtime_layeredpanel: No such file or directory fatehost:/#
It's been happening on both my old and new server, was really hoping this would be fixed.
Basically, the httpd/apache service crashes or goes down making domain names and sites unable to load; although cPanel/WHM still accessible. This would go on for about 5 minutes OR until I restart httpd in root.
sites simply do not load or just timeout after a period of time.
This has become extremely annoying for both me and my clients because it makes it seem like we have downtime.
Code: [root@serwer /]# httpd restart /usr/sbin/httpd restart: httpd not running, trying to start /usr/sbin/httpd restart: httpd could not be started
Code: [root@serwer /]# httpd status Looking up localhost Making HTTP connection to localhost Alert!: Unable to connect to remote host. lynx: Can't access startfile [url]
When I deploy my application into tomcat, and bind httpd with AJP, httpd do not response occasionally, it will halt 2-3 minutes. The quickly way is restart httpd
I am having a problem on my VPS. I am running the latest version of Apache on Windows Server 2K3, and after editing httpd.conf to allow virtual hosts (#Include /conf/extra/httpd-vhosts.conf) and trying to restart the service, an error appears saying the operation failed.
I have even tried restarting/starting the service via services.msc
If I am not using the default httpd.conf Apache will not restart at all... it is very strange. I have also tried doing a repair of the installation of Apache.
I am using windows 2008 R2 64 bit O.S, I downloaded httpd-2.4.10-win64-VC11 and tomcat-connectors-1.2.39-windows-x86_64-httpd-2.4.x and I created 3 tomcat workers and then I configured workers.properties and httpd.conf.
After complete setup when i tried using
http://localhost then
I got It works! message (looks everything is fine).
and then I have deployed my sample web application I tried to access the same application then using
http://localhost/SampleCluster
I am getting
503 service not available.
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
New to Apache Web Server. Built the self signed certs, and tried to bring up server after configuring the httpd.conf file.I also included the section of the error log file that is pertinent.httpd.conf removed, use past bin.
I've got a VPS with XenSmart, and I'm running CentOS. Recently, I have been needing to redirect my users to 'www.', since if they don't put the 'www.' in front of the domain the vB forum doesn't run properly. Though, to do this, I edited the .htaccess file and was using the 'mod_rewrite' command, but this requires Apache.
So, on my VPS I've installed Apache, and set LXAdmin to use 'httpd' instead of 'lighttpd', though now my web pages wont show up and all I've got is the default Apache web page:
[url]
How am I able to use Apache (HTTPD) and have it load my current forum? My current forums hosted in:
