nbv4's questions

I want all urls that are http to be redirected to https.

http://example.com/blah/blah

changes to

https://example.com/blah/blah

I have this snippet in my nginx conf that achieves this effect:

upstream examplewsgicluster {
    server unix://tmp/example.sock;
}

server {
    listen         80;
    server_name    beta.example.com www.example.com example.com;
    rewrite        ^ https://example.com$request_uri? permanent;
}

server {
    listen 443;

    location / {
        include uwsgi_params;
        uwsgi_pass examplewsgicluster;
        uwsgi_read_timeout 700;
    }
}

how can I edit this rule so that paths that begin with /admin/ do not get redirected?

so http://example.com/admin/blah/blah does not get redirected.

Google bot is crawling my site right now and it's killing my server. Its only crawiling one or two pages a second, but those pages are really CPU intensive. I have already added those CPU intensive files to the robots.txt file, but googlebot hasn't detected those changes yet. I want to block google bot at the apache.cong level so my site can be back right now. How can I do this? This one apoache instance is hosting a few PHP sites and a django powered site, so I can't use .htaccess files. The server is running Ubuntu 10.04.

this seems really simple, but I can't figure it out. I'm using xname.org since it's free and I own a bunch of domains spread over a few different registrars.

The setup I desire is very simple: one A record that points the bare domain name to my server, plus a wildcard CNAME record pointing all subdomains to the same server.

So if the user goes to domain.com it will point them to 285.24.435.75, if they go to www.domain, blah.domain.com, or any other sub domain, they'll get sent to 285.24.435.75.

All the examples I read on the internet about setting up A records all have the A record set to a subdomain such as www. WWW is deprecated so I want to have noting to do with it. Currently my xname.org zone looks like this:

$TTL 86400 ; Default TTL
domain.com.     IN  SOA ns0.xname.org.  nbvfour.gmail.com. (
            2010052503  ; serial
            10800   ; Refresh period
            3600    ; Retry interval
            604800  ; Expire time
            10800   ; Negative caching TTL
        )

$ORIGIN domain.com.
                    IN      NS      ns2.xname.org.
                    IN      NS      ns0.xname.org.
                    IN      NS      ns1.xname.org.
@                   IN      A       65.49.73.148




*                   IN      CNAME       domain.com

The '@' symbol is something that the godaddy domain interface uses to mean "this root domain', but that may have been specefic to that interface and has no meaning here.

Before I had a 'www' entry in the A rcords and it worked in the sense that I could ping 'www.domain.com' and it returned a response, but pinging the root domain 'domain.com' returned "no host found".

My server does this every few days. What sucks is that it always seems to do this right after I go to bed, so when I wake up, I'm greeted with the fact that my server has been down for the past 6 or 7 hours.

When I first noticed this, I added a cronjob that tries to restart the server every 15 minutes, but I guess that didn't fix it. Once I noticed the server was down, I can this command:

/etc/init.d/apache2 restart
* Restarting web server apache2
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
... waiting ...........................................................apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
httpd (pid 17597) already running

...which is odd, because a restart should restart the server, even if it's already running, correct? I eventually had to "stop" then "start" to get it working again.

I then looked through the logs, and found something very weird. It seems that around the time the server crashed, the logs have entries that are wildly out of order. It looks a little like this:

xx.xxx.xxx.x - - [21/Apr/2010:06:32:05 -0400] "GET / blah"
xx.xxx.xxx.x - - [21/Apr/2010:06:51:25 -0400] "GET / blah"
x.xx.xxx.xxx - - [21/Apr/2010:06:38:23 -0400] "GET / blah"
xxx.xx.xx.xx - - [21/Apr/2010:06:31:56 -0400] "GET / blah"
xxx.xx.xx.xx - - [21/Apr/2010:06:51:49 -0400] "GET / blah"
xx.xx.xxx.xx - - [21/Apr/2010:06:33:20 -0400] "GET / blah"

I don't think the problem is memory, because this:

tells me that right before the crash, memory usage is fine.

I'm running apache with the worker mpm, here are the settings for that:

<IfModule mpm_worker_module>
  StartServers            1
  MaxClients            100
  MinSpareThreads         5
  MaxSpareThreads        10
  ThreadsPerChild        10
  MaxRequestsPerChild  3000
</IfModule>

This apache server is running a bunch of stuff, but most of the traffic comes from a django project I'm hosting, that uses mod_wsgi. There also is a simple machines forum that is running off of mod_fcgid. Those setting are below:

<IfModule mod_fcgid.c>
  MaxRequestsPerProcess 500
  MaxProcessCount 3

  AddHandler fcgid-script .php .fcgi
  AddHandler cgi-script .cgi .pl
  FCGIWrapper "/usr/bin/php-cgi" .php 
</IfModule>

Anyone know of anything else I can check? I've just about tweaked every single setting I can think of, yet these freezes still happen.

Edit: I have both a postgres and mysql server running on this machine, but they both work during this freeze, because my backup script ran during that 5 hour time frame, and it worked perfectly fine.

Edit2: I'm running Ubuntu Server 9.10. When the server is down, all requests just never return. The page hangs. No error messages or anything.

I have a mediawiki install that is acting up. Whenever I try to save an article, it goes to a blank screen. All though if I refresh that blank screen, it will go on to work.

I have no idea why it's doing that, but it seems to be that it's a problem with PHP. I guess by default errors don't get logged when using mod_fcgid, because I can't find an error log anywhere. I tried enabling logging in the /etc/php5/cgi/php.ini, but that didn't do anything. How do I achieve php error logging? I'm using ubuntu 9.10.

I'm using munin as a tool for monitoring my servers. On some of the graphs, the units are marked with a 'm'. For instance, my apache accesses graph is labeled 100m, 200m, 300m, along the y-axis. What does the 'm' mean? I understand 'M' (caps) is mega as in megabytes, the 'k' is kilo, the 'G' is giga, but what about 'm'? At first I thought it was million, but there's no way apache is serving 100 million accesses even per decade.

I want to host five websites on one VPS I just bought.

1. a PHP site called domain.com
2. a django site called beta.domain.com
3. phpmyadmin which will be domain.com/phpmyadmin
4. phppgadmin, which will be beta.domain.com/phppgadmin
5. and another django site called domain2.com

All the django sites will be running with mod_wsgi in apache, and all the PHP sites will be running in nginx with fastcgi.

I'm a developer, not a sysadmin, so I'm having a hard time figuring out the best way to do this. The reason I'm running my PHP from nginx is because I don't want to install mod_php, which allows me to use the worker MPM in apache.

Currently I have nginx running off of port 8080, and apache running off of port 80. When I go to domain.com it brings up the django site. When I go to domain.com:8080, it brings up the PHP site.

Like I said before, I'm not a server person so this stuff is making my head spin. Is there any way to access stuff from nginx without specifying the port number in the URL?

Here is my phpmyadmin config file:

server {
    listen   8080;
    server_name  phpmyadmin;

    access_log  /var/log/nginx/phpmyadmin.access.log;
    error_log   /var/log/nginx/phpmyadmin.error_log warn;

    root   /var/www/phpmyadmin;
    index  index.php index.htm;

    location ~ \.php {
            include /etc/nginx/fastcgi_params;
            keepalive_timeout 0;
            fastcgi_param   SCRIPT_FILENAME  $document_root$fastcgi_script_name;
            fastcgi_pass    127.0.0.1:9000;
    }
}

Right now when I go to http://domain.com:8080 it brings up the phpmysdmin site. I want it to only open phpmyadmin if I go to http://domain.com:8080/phpmyadmin. What change do I need to make here?

I have about 4 or 5 apps that I am going to run from nginx, and I'd prefer to keep each one in it's own sites-enabled profile, instead of one big config file that covers them all.

I have a website we'll call it domain.com, that was originally written in PHP. Every single valid URL contains the letters "php" somewhere after the "domain.com/" part.

I recently finished a complete rewrite of the site using Django, currently located at beta.domain.com

What I want to do is move the old PHP site to old.domain.com, and move the new beta site to domain.com. I want to do this without missing a beat. I want all old links to redirect to the new subdomain. This also includes linked images (that end in .php).