I have a web site that has some content protected via apache basic authentication.
Is there a way for me to tell (from the access logs perhaps?) how many users are actually using the login?
Intranet traffic is excluded from having to log in, so I can't just look at how many people are accessing those pages.
Thanks.
Is it still true that you shouldn't use htaccess files if you can use httpd.conf?
The Apache site says "In general, you should never use .htaccess files unless you don't have access to the main server configuration file." But I don't know how old that advice is, or if it's still relevent.
I'm working on a large site that only uses the httpd.conf file. But it's getting very long and of course requires a reboot any time a change gets made. And with the number of departmental sites running under the main site (and all using the httpd.conf file), it's a disincentive to ever make changes.
Now we are running wordpress 3 (in a multisite configuration) as well. I want to test some changes to the config rules, but the only way I can currently do that is to keep restarting apache, which I'd rather not do on the live site. (in particular the rewrite rules seem to be misbehaving where some blog posts are getting prepended with "www.", while others aren't)
I was considering enabling .htaccess just on the wordpress folder, but is it wise?
Our server is busy (about 60k page views a day, according to google), but isn't being taxed too hard.
What is the current best practice? Are servers now sufficiently grunty that a possible slight performace hit is negligable compared to the ease of managment of the .htaccess files?
We are running JRun 4 and have lots of crashes. I am trying to understand where the problems are coming from and have modified the jrun.xml file to enable metrics logging.
This is what I'm seeing...
01/06 15:07:27 metrics Web threads (busy/total/delayed): 2/100/0 Sessions: 0 Total Memory=70720 Free=7464
01/06 15:08:27 metrics Web threads (busy/total/delayed): 1/100/0 Sessions: 0 Total Memory=66944 Free=9199
01/06 15:09:27 metrics Web threads (busy/total/delayed): 3/100/0 Sessions: 0 Total Memory=67456 Free=9644
01/06 15:10:27 metrics Web threads (busy/total/delayed): 3/100/0 Sessions: 0 Total Memory=63360 Free=8368
The book I've been reading (Adobe Coldfusion Anthology, Apress) suggests the "busy" number is the free memory in MB. The Adobe documentation says it's "Threads currently running". Which is correct?
Also, what does all this mean?
If I'm reading it correctly, I have 100 total threads, and 3 busy ones. So what are the other 97 threads doing if they are neither busy nor delayed?
I've been doing web development for some time, but server admin has never been part of my job. I'm finding that more and more I need to learn about what is going on under the hood. Looking at server logs and stuff, I'm seeing some interesting things and learning a lot, but I just don't know what a "normal" server looks like, so it's hard for me to judge how our machine is doing by comparison.
We are running Apache (2.0.54) on Red Hat with JRun (4.0). Most of our content is ColdFusion, with a little PHP thrown in. Google analytics says we have about 1,500,000 page views a month and Apache typically reports 5-7 requests per second.
If I do top on the server it says it's been running for over 700 days. But our Apache instance crashes regularly. Uptime of 3 days would be a long time for our server. I'd say 48 hours would be normal before Apache needs to be rebooted.
I'm keen to hear others say from their experience if that is good or bad. I suspect bad, but I don't have anything to compare it to.
And if this is bad, can anyone point me in the direction of some online resources where I can start learning how to fix this?
I've just started seeing this appearing in our server logs...
/P/2112/FBA73F59E6F7E78CCFF29DD8BDF46ECCAE5B73145E023BFB207C971E835645245C62CA0296DA6CDA4E62613A9C10C0DADBA941D2AD68005E57EFDC84A8ECD0ADC37C0214AD76755E48D6D1BAABF
It goes on and on for a while. In fact that's less than 10% of just one such event and there are many similar events.
I'm suspecting some attempted hack since we have no folder named "/P/" on our server.
Does anyone recognise this?
BTW, the reason I was looking at the logs at that time was that our server had just crashed, and I can't help wondering if it's related.
The server is Apache/2.0.54 (Unix) PHP/4.4.2 mod_ssl/2.0.54 OpenSSL/0.9.7a JRun/4.0
We just had to restart the coldfusion server as it had become unresponsive. Looking at the Apache error log (We have jrun 4 through Apache on a RedHat server), I see the following over and over...
[Tue Jun 02 12:21:45 2009] [info] server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers), spawning 8 children, there are 2 idle, and 59 total children [Tue Jun 02 12:21:45 2009] [notice] jrApache[11773: 62983] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:45 2009] [notice] jrApache[11780: 47108] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:47 2009] [notice] jrApache[11784: 37263] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:47 2009] [notice] jrApache[11786: 774] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:47 2009] [notice] jrApache[11787: 63825] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:47 2009] [notice] jrApache[11788: 45712] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:47 2009] [notice] jrApache[11789: 1286] initialized proxy for 127.0.0.1:51010 [Tue Jun 02 12:21:53 2009] [notice] jrApache[11815: 8710] initialized proxy for 127.0.0.1:51010
This happens again and again, so I assume whatever is causing it is spawing these extra children until the server runs out of memory and stops responding.
What I can't work out is why this is happening. Is anyone familiar with jrun and might know what's going on?
I'm a newbie to server admin, but I'm trying to get my head around our Apache server. I got a shock when I tried to tail the Apache error logs. Even after greping the logs so I was only seeing actual errors, I was getting about 1 error per second. The Apache Server Status page says the server is handling ~6.3 requests per second.
This seems like an insanely high rate of errors to me, but I'm unfamiliar with how most servers in the wild perform.
Am I looking at a server in desperate need of help (as I suspect)?
Or is this normal?