John S's questions

I've recently moved my clients from one chef server to another, and now none of my nodes are checking in properly. I can manually run 'chef-client' successfully, and I do have the chef-client::default cookbook defined, yet they will not "check in".

These are Ubuntu 14.04 nodes connecting to a Chef 12 server on Ubuntu 14.04. The only difference between this server and the old one was that I've also moved to using named environments with specific cookbook versions for our own cookbooks. I haven't explicitly provided entries for the chef-client cookbook or any others since I'm fine with running the latest versions.

I can manually run chef-client without error, but I do not see any logs under /var/log/chef so I'm not sure where else to look. I even went so far as to set the chef_client::interval attribute on the environment to 1800, but still no luck. Any help would be greatly appreciated.

I'm using a logstash plug-in for a Java app using logback to forward logs on to my logstash server. I've setup a filter definition as follows:

input {
  tcp {
    port => 2856
    codec => json_lines
  }
}

filter {
  mutate {
    convert => {
      "tenantId" => "integer"
      "userId" => "integer"
    }
  }
}

Logs are being forwarded on to Elasticsearch using the following config:

output {
  elasticsearch {
    hosts => ["127.0.0.1:9200"]
    user => "user"
    password => "secure"
  }
}

The index is just going to logstash-, and when I inspect the mappings in Elasticsearch, I see the following:

  "logstash-2016.04.25" : {
      "mappings" : {
         "logs" : {
            "_all" : {
               "omit_norms" : true,
               "enabled" : true
            },
            "properties" : {
               ...
               "userId" : {
                  "type" : "long"
               },
               "tenantId" : {
                  "type" : "long"
               },
               ...
            }
         }
      }
   }

So I can see that the fields are being set with an appropriate type, but they are neither analyzed nor defined as long values when I check Kibana. What am I missing?

I'm trying to use mod_rewrite to redirect users to the HTTPS equivalent URL unless the URL is for my Jenkins CI server. Here is the rule I have in my default site config (my Jenkins and other sites have their own respective VirtualHost entries:

<VirtualHost _default_:80>
    ServerAdmin [email protected]
    RewriteEngine on
    ReWriteCond %{SERVER_PORT} !^443$
    ReWriteCond %{REQUEST_URI} !^.+/jenkins/(.*)$
    RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R,L]
</VirtualHost>

Any help would be greatly appreciated.

Edit: As requested, here is the output from apache2ctl -S:

VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:443                  is a NameVirtualHost
         default server ip-10-72-226-167.ec2.internal (/etc/apache2/sites-enabled/default-ssl:2)
         port 443 namevhost ip-10-72-226-167.ec2.internal (/etc/apache2/sites-enabled/default-ssl:2)
         port 443 namevhost qa.example.com (/etc/apache2/sites-enabled/example-ssl:2)
*:80                   is a NameVirtualHost
         default server ip-10-72-226-167.ec2.internal (/etc/apache2/sites-enabled/000-default:1)
         port 80 namevhost ip-10-72-226-167.ec2.internal (/etc/apache2/sites-enabled/000-default:1)
         port 80 namevhost qa.example.com (/etc/apache2/sites-enabled/jenkins:1)
Syntax OK

What I am expecting is that when I browse to http://qa.example.com that I get re-directed to https://qa.example.com/, but if I browse to http://qa.example.com/jenkins/ then my Jenkins config kicks in. The latter works, but the former does not, i.e. browsing to http://qa.example.com/ does not re-direct me to https://qa.example.com/.