wintersolutions's questions

I'd like to run MongoDB on my development machine whenever the Port 27017 requested but not before that. I already got parts of the file /usr/lib/systemd/system/mongodb.socket but now I'm stuck what else goes in there and I don't know if this is the right directory.

[Unit]
Description=High-performance, schema-free document-oriented database Socket

[Socket]
ListenStream=27017

[Install]
WantedBy=sockets.target

My question is basically: What else do I need to write in the file, where do I place this file and do I have to do more than run systemctl enable mongodb.socket after that?

Until a few days ago I was hosting a single domain on my Server. Now I've added a second domain via apache virtual hosts. Both domains are name based and hosted from the same IP.

Now my logs show me that some relative paths are called on the new domains application that obviously belong to the old domain. It seems that all these calls come from searchengine bots and I can still access the two pages without a problem. So there is no real damage done for endusers.

But I'd like to diagnose the problem. I'm a fairly good programmer but I don't know much about administrative tasks. Because of that I'd like to know which steps you would recommend to diagnose the problem and narrow it down?

System:

• Apache 2
• Ubuntu 10.4 64 Bit
• PushionPassenger w. 2 Rails Apps
• DNS are hoster based

I'd like to give the domain names, but I'm not sure if this is ok with SO.

UPDATE with more specific information:

The two domains are: wintersolutions.de ("old") and pollator.com ("new"). According to my log files the google-bot is hitting 500s on the pollator-application when accessing for example /de/knowhow which is a valid relative URL for the wintersolutions.de domain. Another strange phenomena I just discovered is, that if I access the wintersolutions domain via googles cache I get another domainname fitzzle.com which is another domain of mine. This domains DNS also points to my server but there is no application behind it yet.

The only observation I can make until now is, that google seems to favor domains that are in front in the alphabet.

Both vhost-files look the same, except the domainname:

<VirtualHost *:80>
    ServerName wintersolutions.de
    ServerAlias www.wintersolutions.de
    DocumentRoot "/var/www/sites/wintersolutions.de/current/public"
    ErrorLog "/var/log/apache2/wintersolutions.de-error_log"
    CustomLog "/var/log/apache2/wintersolutions.de-access_log" common
    <Directory "/var/www/sites/wintersolutions.de/current/public">
        Options All
        AllowOverride All
        Order allow,deny
        Allow from all
    </Directory>
    <Directory "/var/www/sites/wintersolutions.de/current/public/assets">
    AllowOverride All
    </Directory>
    <LocationMatch "^/assets/.*$">
        Header unset Last-Modified
    Header unset ETag
    FileETag none
    ExpiresActive On
    ExpiresDefault "access plus 1 year"
    </LocationMatch>
    RewriteEngine On
    # Remove the www
    RewriteCond %{HTTP_HOST} ^www.wintersolutions.de$ [NC]
    RewriteRule ^/(.*)$ http://wintersolutions.de/$1 [R=301,L]
</VirtualHost>

I followed the steps described in the blogpost The Asset Pipeline, from development to production and tweaked them to my environment. The two important files are:

/etc/apache/site-available/example.com

<VirtualHost *:80>
    ServerName example.com
    ServerAlias www.example.com
    DocumentRoot "/var/www/sites/example.com/current/public"
    ErrorLog "/var/log/apache2/example.com-error_log"
    CustomLog "/var/log/apache2/example.com-access_log" common
    <Directory "/var/www/sites/example.com/current/public">
        Options All
        AllowOverride All
        Order allow,deny
        Allow from all
    </Directory>
    <Directory "/var/www/sites/example.com/current/public/assets">
        AllowOverride All
    </Directory>
    <LocationMatch "^/assets/.*$">
        Header unset Last-Modified
        Header unset ETag
        FileETag none
        ExpiresActive On
        ExpiresDefault "access plus 1 year"
    </LocationMatch>
    RewriteEngine On
    # Remove the www
    RewriteCond %{HTTP_HOST} ^www.example.com$ [NC]
    RewriteRule ^(.*)$ http://example.com/$1 [R=301,L]
</VirtualHost>

/var/www/sites/example.com/shared/assets/.htaccess

RewriteEngine on
RewriteCond %{HTTP:Accept-Encoding} \b(x-)?gzip\b
RewriteCond %{REQUEST_FILENAME}.gz -s
RewriteRule ^(.+) $1.gz [L]

<FilesMatch \.css\.gz$>
  ForceType text/css
  Header set Content-Encoding gzip
</FilesMatch>

<FilesMatch \.js\.gz$>
  ForceType text/javascript
  Header set Content-Encoding gzip
</FilesMatch>

But apache seems to send empty gzip files because the testsite looses all styles and firebug doesnt find any content for the css files. Altough if I call the assets-path directly I get some gibberish that looks like binary data. If I move the htaccess-file everything is back to normal. How could I find out where/what went wrong or do you have any suggestions what error I made?

> apache2 -v
System: Server version: Apache/2.2.14 (Ubuntu)
Server built:   Mar  5 2012 16:42:17
> uname -a
Linux node0 2.6.18-028stab094.3 #1 SMP Thu Sep 22 12:47:37 MSD 2011 x86_64 GNU/Linux

I've got a postfix & dovecot setup running on my Ubuntu 10.4 server. This works good but the configuration/management seems a bit overblown for my use case. Now I need to reinstall this Server and I'm looking for a solution that is easier to maintain.

Can you suggest a setup with the following features:

• Can recieve/send mail for multiple domains + subdomains
• Recieves mail for all valid email-addresses (catch-all) into one mail account
• Accepts all valid mail-addresses as sender
• IMAP would be a plus but isn't required

Basically I just want scripts to send E-Mail from the server with abritary senders and recieve E-Mail for all possible addresses/domains and then fetch them into my gmail-account.

I do tests atm with Chef and I have a virtual machine which I'm cloning to generate new nodes. I do bootstrap with the knife command and the -N Parameter to give each host a nodename. The Problem is tough, that the hostname on the VM doesn't change and if I'm trying to bootstrap another client it fails because Chef has this node already signed up. I did now try to set the hostname in my base Role with the hostname cookbok but when I run chef-client it gives me a:

---- Begin output of hostname @config[:chef_node_name] ----
STDOUT: 
STDERR: hostname: the specified hostname is invalid
---- End output of hostname @config[:chef_node_name] ----
Ran hostname @config[:chef_node_name] returned 1

The Attributes for the base Role are:

name "base"
description "Base role applied to all nodes"
override_attributes(
  "chef_client" => {
    "init_style" => "upstart",
    "server_url" => "http://chef.ws:4000"
    },
  "set_fqdn" => 
        "@config[:chef_node_name]"
)
run_list(
  "recipe[hostname]",
  "recipe[chef-client::delete_validation]",
  "recipe[chef-client::service]"
)

Do I have a syntax error here in the set_fqdn or is the @config variable simply not accessible on the node? Is there a better way to set the hostname to the nodename?