Docker image: No Graylog servers available. Cannot log in.

[theduke]

Just tried to use the docker image.

The webserver is reachable, but says No Graylog servers available. Cannot log in.

The log seems fine, and ends wich "Chef client finished, graylog reconfigured"

Full log:

    +# If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5, then 500 threads can block. More than that and an exception will be thrown.
    +# http://api.mongodb.org/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier
    +mongodb_threads_allowed_to_block_multiplier = 5
    +
    +# Drools Rule File (Use to rewrite incoming log messages)
    +# See: http://graylog2.org/resources/documentation/general/rewriting
    +#rules_file = /etc/graylog.drl
    +
    +# Email transport
    +transport_email_enabled = false
    +transport_email_hostname = 
    +transport_email_port = 587
    +transport_email_use_auth = false
    +transport_email_use_tls = true
    +transport_email_use_ssl = true
    +transport_email_auth_username = 
    +transport_email_auth_password = 
    +transport_email_subject_prefix = [graylog]
    +transport_email_from_email = graylog@542d341aac3d
    +
    +# Specify and uncomment this if you want to include links to the stream in your stream alert mails.
    +# This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users.
    +#
    +transport_email_web_interface_url = http://542d341aac3d
    +
    +# HTTP proxy for outgoing HTTP calls
    +#http_proxy_uri =
    +
    +# Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch
    +# on heavily used systems with large indices, but it will decrease search performance. The default is to optimize
    +# cycled indices.
    +#disable_index_optimization = true
    +
    +# Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch
    +# on heavily used systems with large indices, but it will decrease search performance. The default is 1.
    +#index_optimization_max_num_segments = 1
    +
    +# Disable the index range calculation on all open/available indices and only calculate the range for the latest
    +# index. This may speed up index cycling on systems with large indices but it might lead to wrong search results
    +# in regard to the time range of the messages (i. e. messages within a certain range may not be found). The default
    +# is to calculate the time range on all open/available indices.
    +#disable_index_range_calculation = true
    +
    +# The threshold of the garbage collection runs. If GC runs take longer than this threshold, a system notification
    +# will be generated to warn the administrator about possible problems with the system. Default is 1 second.
    +#gc_warning_threshold = 1s
    +
    +# Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds.
    +#ldap_connection_timeout = 2000
    +
    +# https://github.com/bazhenov/groovy-shell-server
    +#groovy_shell_enable = false
    +#groovy_shell_port = 6789
    +
    +# Enable collection of Graylog-related metrics into MongoDB
    +#enable_metrics_collection = false
    +
    +# Disable the use of SIGAR for collecting system stats
    +#disable_sigar = false
    +
    +# TELEMETRY
    +# Enable publishing Telemetry data
    +#telemetry_enabled = false
    +
    +# Base URL of the Telemetry service
    +#telemetry_url = https://telemetry-in.graylog.com/submit/
    +
    +# Authentication token for the Telemetry service
    +#telemetry_token = 
    +
    +# How often the Telemetry data should be reported
    +#telemetry_report_interval = 1m
    +
    +# Number of Telemetry data sets to store locally if the connection to the Telemetry service fails
    +#telemetry_max_queue_size = 10
    +
    +# TTL for Telemetry data in local cache
    +#telemetry_cache_timeout = 1m
    +
    +# Connect timeout for HTTP connections
    +#telemetry_service_connect_timeout =  1s
    +
    +# Write timeout for HTTP connections
    +#telemetry_service_write_timeout = 5s
    +
    +# Read timeout for HTTP connections
    +#telemetry_service_read_timeout = 5s
    - change mode from '' to '0644'
    - change owner from '' to 'graylog'
    - change group from '' to 'graylog'
  * directory[/opt/graylog/sv/graylog-server] action create
    - create new directory /opt/graylog/sv/graylog-server
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * directory[/opt/graylog/sv/graylog-server/log] action create
    - create new directory /opt/graylog/sv/graylog-server/log
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * directory[/opt/graylog/sv/graylog-server/log/main] action create
    - create new directory /opt/graylog/sv/graylog-server/log/main
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/opt/graylog/sv/graylog-server/run] action create
    - create new file /opt/graylog/sv/graylog-server/run
    - update content in file /opt/graylog/sv/graylog-server/run from none to cd9f4a
    --- /opt/graylog/sv/graylog-server/run  2015-03-29 20:55:48.942953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-72blib   2015-03-29 20:55:48.942953000 +0000
    @@ -1 +1,11 @@
    +#!/bin/sh
    +exec 2>&1
    +
    +umask 077
    +export JAVA_HOME=/opt/graylog/embedded/jre
    +export GRAYLOG_SERVER_JAVA_OPTS="-Xms1g -Xmx1g -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow"
    +
    +# check if mongodb is up
    +timeout 600 bash -c "until curl -s http://127.0.0.1:27017; do sleep 1; done"
    +exec chpst -P -U graylog -u graylog /opt/graylog/embedded/bin/authbind $JAVA_HOME/bin/java $GRAYLOG_SERVER_JAVA_OPTS -jar /opt/graylog/server/graylog.jar server -f /opt/graylog/conf/graylog.conf
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/opt/graylog/sv/graylog-server/log/run] action create
    - create new file /opt/graylog/sv/graylog-server/log/run
    - update content in file /opt/graylog/sv/graylog-server/log/run from none to b6ccf1
    --- /opt/graylog/sv/graylog-server/log/run  2015-03-29 20:55:48.954953001 +0000
    +++ /tmp/chef-rendered-template20150329-20-1w2pfnx  2015-03-29 20:55:48.954953001 +0000
    @@ -1 +1,3 @@
    +#!/bin/sh
    +exec svlogd -tt /var/log/graylog/server
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/var/log/graylog/server/config] action create
    - create new file /var/log/graylog/server/config
    - update content in file /var/log/graylog/server/config from none to 623c00
    --- /var/log/graylog/server/config  2015-03-29 20:55:48.966953001 +0000
    +++ /tmp/chef-rendered-template20150329-20-1iowdm6  2015-03-29 20:55:48.966953001 +0000
    @@ -1 +1,7 @@
    +s209715200
    +n30
    +t86400
    +!gzip
    +
    +
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * ruby_block[reload graylog-server svlogd configuration] action nothing (skipped due to action :nothing)
  * file[/opt/graylog/sv/graylog-server/down] action delete (up to date)
  * link[/opt/graylog/init/graylog-server] action create
    - create symlink at /opt/graylog/init/graylog-server to /opt/graylog/embedded/bin/sv
  * link[/opt/graylog/service/graylog-server] action create
    - create symlink at /opt/graylog/service/graylog-server to /opt/graylog/sv/graylog-server
  * ruby_block[supervise_graylog-server_sleep] action run
    - execute the ruby block supervise_graylog-server_sleep
  * service[graylog-server] action nothing (skipped due to action :nothing)
  * execute[/opt/graylog/embedded/bin/graylog-ctl start graylog-server] action run
    - execute /opt/graylog/embedded/bin/graylog-ctl start graylog-server
  * ruby_block[add node to server list] action run
    - execute the ruby block add node to server list
Recipe: graylog::graylog-web
  * directory[/var/log/graylog/web] action create
    - create new directory /var/log/graylog/web
    - change mode from '' to '0700'
    - change owner from '' to 'graylog'
  * template[/opt/graylog/conf/graylog-web-interface.conf] action create
    - create new file /opt/graylog/conf/graylog-web-interface.conf
    - update content in file /opt/graylog/conf/graylog-web-interface.conf from none to 5b47ed
    --- /opt/graylog/conf/graylog-web-interface.conf    2015-03-29 20:55:53.186953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-1nmtp3   2015-03-29 20:55:53.186953000 +0000
    @@ -1 +1,29 @@
    +# graylog-server REST URIs (one or more, comma separated) For example: "http://127.0.0.1:12900/,http://127.0.0.1:12910/"
    +graylog2-server.uris = "http://127.0.0.1:12900/"
    +
    +# Learn how to configure custom logging in the documentation:
    +#    http://support.torch.sh/help/kb/graylog-web-interface/configuring-web-interface-logging
    +
    +# Secret key
    +# ~~~~~
    +# The secret key is used to secure cryptographics functions. Set this to a long and randomly generated string.
    +# If you deploy your application to several instances be sure to use the same key!
    +# Generate for example with: pwgen -s 96
    +application.secret = "9661826b5141161d477b73e44397f2a0b75e700169b30f636e1f863152b73e3276567705e3d5d012e3e9c5a8cd81ea4a75d80b95fafe2691dc5a0bb6a93d4e9e"
    +
    +# Web interface timezone
    +# Graylog stores all timestamps in UTC. To properly display times, set the default timezone of the interface.
    +# If you leave this out, Graylog will pick your system default as the timezone. Usually you will want to configure it explicitly.
    +timezone = Etc/UTC
    +
    +# Message field limit
    +# Your web interface can cause high load in your browser when you have a lot of different message fields. The default
    +# limit of message fields is 100. Set it to 0 if you always want to get all fields. They are for example used in the
    +# search result sidebar or for autocompletion of field names.
    +field_list_limit = 100
    +
    +# Use this to run Graylog with a path prefix
    +
    +# You usually do not want to change this.
    +application.global=lib.Global
    - change mode from '' to '0644'
    - change owner from '' to 'graylog'
    - change group from '' to 'graylog'
  * template[/opt/graylog/conf/web-logger.xml] action create
    - create new file /opt/graylog/conf/web-logger.xml
    - update content in file /opt/graylog/conf/web-logger.xml from none to f80476
    --- /opt/graylog/conf/web-logger.xml    2015-03-29 20:55:53.202953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-6tyc4s   2015-03-29 20:55:53.202953000 +0000
    @@ -1 +1,35 @@
    +<configuration>
    +     <conversionRule conversionWord="coloredLevel" converterClass="play.api.Logger$ColoredLevel" />
    +
    +    <appender name="FILE" class="ch.qos.logback.core.FileAppender">
    +     <file>/var/log/graylog/web/application.log</file>
    +     <encoder>
    +       <pattern>%date - [%level] - from %logger in %thread %n%message%n%xException%n</pattern>
    +     </encoder>
    +   </appender>
    +
    +    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    +        <encoder>
    +           <pattern>%coloredLevel %logger{15} - %message%n%xException{5}</pattern>
    +        </encoder>
    +    </appender>
    +
    +    <root level="ERROR">
    +        <appender-ref ref="STDOUT" />
    +        <appender-ref ref="FILE" />
    +    </root>
    +
    +    <logger name="com.jolbox.bonecp" level="DEBUG">
    +        <appender-ref ref="STDOUT" />
    +    </logger>
    +
    +    <logger name="play" level="INFO">
    +        <appender-ref ref="STDOUT" />
    +    </logger>
    +
    +    <logger name="application" level="INFO">
    +        <appender-ref ref="STDOUT" />
    +    </logger>
    +
    +</configuration>
    - change mode from '' to '0644'
    - change owner from '' to 'graylog'
    - change group from '' to 'graylog'
  * directory[/opt/graylog/sv/graylog-web] action create
    - create new directory /opt/graylog/sv/graylog-web
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * directory[/opt/graylog/sv/graylog-web/log] action create
    - create new directory /opt/graylog/sv/graylog-web/log
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * directory[/opt/graylog/sv/graylog-web/log/main] action create
    - create new directory /opt/graylog/sv/graylog-web/log/main
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/opt/graylog/sv/graylog-web/run] action create
    - create new file /opt/graylog/sv/graylog-web/run
    - update content in file /opt/graylog/sv/graylog-web/run from none to 55cd07
    --- /opt/graylog/sv/graylog-web/run 2015-03-29 20:55:53.218953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-16q8dos  2015-03-29 20:55:53.218953000 +0000
    @@ -1 +1,9 @@
    +#!/bin/sh
    +exec 2>&1
    +
    +umask 077
    +export JAVA_HOME=/opt/graylog/embedded/jre
    +
    +rm -f /var/opt/graylog/web.pid
    +exec chpst -P -U graylog -u graylog /opt/graylog/web/bin/graylog-web-interface -Dconfig.file=/opt/graylog/conf/graylog-web-interface.conf -Dhttp.port=9000 -Dhttp.address=0.0.0.0 -Dpidfile.path=/var/opt/graylog/web.pid -Dlogger.file=/opt/graylog/conf/web-logger.xml
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/opt/graylog/sv/graylog-web/log/run] action create
    - create new file /opt/graylog/sv/graylog-web/log/run
    - update content in file /opt/graylog/sv/graylog-web/log/run from none to 591533
    --- /opt/graylog/sv/graylog-web/log/run 2015-03-29 20:55:53.226953001 +0000
    +++ /tmp/chef-rendered-template20150329-20-i6uqqz   2015-03-29 20:55:53.226953001 +0000
    @@ -1 +1,3 @@
    +#!/bin/sh
    +exec svlogd -tt /var/log/graylog/web
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/var/log/graylog/web/config] action create
    - create new file /var/log/graylog/web/config
    - update content in file /var/log/graylog/web/config from none to 623c00
    --- /var/log/graylog/web/config 2015-03-29 20:55:53.230953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-12aacbk  2015-03-29 20:55:53.230953000 +0000
    @@ -1 +1,7 @@
    +s209715200
    +n30
    +t86400
    +!gzip
    +
    +
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * ruby_block[reload graylog-web svlogd configuration] action nothing (skipped due to action :nothing)
  * file[/opt/graylog/sv/graylog-web/down] action delete (up to date)
  * link[/opt/graylog/init/graylog-web] action create
    - create symlink at /opt/graylog/init/graylog-web to /opt/graylog/embedded/bin/sv
  * link[/opt/graylog/service/graylog-web] action create
    - create symlink at /opt/graylog/service/graylog-web to /opt/graylog/sv/graylog-web
  * ruby_block[supervise_graylog-web_sleep] action run
    - execute the ruby block supervise_graylog-web_sleep
  * service[graylog-web] action nothing (skipped due to action :nothing)
  * execute[/opt/graylog/embedded/bin/graylog-ctl start graylog-web] action run
    - execute /opt/graylog/embedded/bin/graylog-ctl start graylog-web
Recipe: graylog::nginx
  * directory[/opt/graylog/conf/nginx/ca] action create
    - create new directory /opt/graylog/conf/nginx/ca
    - change mode from '' to '0700'
    - change owner from '' to 'root'
  * directory[/var/log/graylog/nginx] action create
    - create new directory /var/log/graylog/nginx
    - change mode from '' to '0700'
    - change owner from '' to 'root'
  * file[/opt/graylog/conf/nginx/ca/graylog.key] action create
    - create new file /opt/graylog/conf/nginx/ca/graylog.key
    - update content in file /opt/graylog/conf/nginx/ca/graylog.key from none to 63fb58
    --- /opt/graylog/conf/nginx/ca/graylog.key  2015-03-29 20:55:55.426953001 +0000
    +++ /opt/graylog/conf/nginx/ca/.graylog.key20150329-20-1gccn9r  2015-03-29 20:55:55.426953001 +0000
    @@ -1 +1,28 @@
    +-----BEGIN RSA PRIVATE KEY-----
    +MIIEogIBAAKCAQEAvRLGvE4gHQ9Xfw999PV6BDQA2K3ppc7VtnyuKRuRdmmNp2XC
    +YSeQmAVSowF4YsQMlN4z2mTRZippfNiH2lVmbRLAc5t+i9bOIvraj0lil+W7UBGO
    +zik8ht+/gvj9hVoVPLrj6Jn6JYs4Fwvz6eQn0ef5GMIexUMQoP5dAnGYsdKhjjBj
    +5S0iDWCDu7/LJoYGRVQElwzGcAig41u3wSU4wPJaJZnvhxvMhNyIRJgZUb+sKh+0
    +GrGKS5t1Sq8NHseR2KI3o9CiVt8QUwz8pT/lwcxJCcqsEn3boIJHqvEP4OiJOavF
    +kZZlwjOfD6JyIYHykEdynuLIe0u/pOfEmowv7wIDAQABAoIBAEVX8ZN2g8ikq85p
    +/CQvM8T+3aCaiCrLpQ38xFNHTR5EsDNI2vWO8TUQHrKyA1kV1hdzN0lN2I7D11R2
    +hbzJvXsbeYHs8YiQC6JAppAOth5Hn19KUTnDXfOJdE+wyipyU3+me5f/gQLsAHJT
    +a+3IQ+J0VaOC7o4ifqLNJ4eR6hKtMBXYyb0iFLy0r9uNNRVV90M2tjRXgy34zAQZ
    +wMm6K2YHbIsNbNqurkLxSHqacVQxge+bCCHAXzkNFG819TcfHQImVj7D2ZQ2mFHQ
    +gPhLb46BmiJzgaiJiCTTk4afInzADkpUEmy2/TeuqyHeOCQxuY+JG9QBKNym66HI
    +nXsQHyECgYEA5XGRGQ/wmHqx+0Ei3kCQ2GBIufVrf0CI6Q6KSvC40y6bhoVG4CrY
    +aMvWzXAcfSLktGO8wF3JC21qzMPl/sCqIze8m6/mz0HGerjwzEH20HSvbHlaiHvv
    +0Z7jyqqb8Jz3A9c8bj799oqrom+eLvRH9zH5MdnoL0jy+SIhxiKMLcUCgYEA0vUI
    +85rJk0G4qqTSLA0Twv3nMR9VHANc2Q1KXWXB2I3rx/gmf54W5vbt1fgcOSVo8LDn
    +iOHBE+CSlhOP4PEMY8BYP7+o+r6yHnr1bvZ5RL1xol5G8OPuGd893Ikv1TkYYo17
    +LTkEy5gHFV8eRXOWHO0KApmkMNfcX1HHESHXFiMCgYAq3MthZjPpGEq1iFaONHua
    +oGoVqz5YuGKbPycgltXARd2yBKXX7Mke0q2fFUmNKv6UoGk7eom7Q8aG2DXYIH/o
    +Mlperz6sCzqb5H6/ebc0/AdleUorYxPLEia1zqdxDLGsmwHkCoqBCyjDIJzpYqMr
    +D7/gyzdv1e3mErVCgWO0jQKBgEbdNy+V3IbR+fWgvlU741qKLiJrMwzg+EyVUVjE
    +ePSE4CJhcpVGBs15P3W0Dc8IiRLpai2qIFDMDJHLanaWoqHTmBF6EYqBipYAmfe3
    +Zg84UDbJ0qzS9EXOnxo5H09SCaX5fto3ICxAGokMVb/gzxlSax1qfSRHLuj6MJPJ
    +uVXfAoGAH8Gw9MCiG8zPqEMOtHhAUiRl37TuOFKlb6xAjW8QSXZUq+tM+OZSA8FK
    +E0QTRg4vNXi3EVzClPdSWZ0S+p+c51dx6z0V3iOLhaJFKBCubV0gT8L2dx24IZBp
    +Ece4Cd5wZnFdIml+jRIhEtcVW0Knv2sYQxg6pzc08AujD6mtYiA=
    +-----END RSA PRIVATE KEY-----
    - change mode from '' to '0644'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * file[/opt/graylog/conf/nginx/ca/graylog-ssl.conf] action create
    - create new file /opt/graylog/conf/nginx/ca/graylog-ssl.conf
    - update content in file /opt/graylog/conf/nginx/ca/graylog-ssl.conf from none to b7a628
    --- /opt/graylog/conf/nginx/ca/graylog-ssl.conf 2015-03-29 20:55:55.446953000 +0000
    +++ /opt/graylog/conf/nginx/ca/.graylog-ssl.conf20150329-20-bclyhz  2015-03-29 20:55:55.446953000 +0000
    @@ -1 +1,13 @@
    +  [ req ]
    +  distinguished_name = req_distinguished_name
    +  prompt = no
    +
    +  [ req_distinguished_name ]
    +  C                      = DE
    +  ST                     = Hamburg
    +  L                      = Hamburg
    +  O                      = Graylog
    +  OU                     = Operations
    +  CN                     = 542d341aac3d
    +  emailAddress           = graylog@542d341aac3d
    - change mode from '' to '0644'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * ruby_block[create crtfile] action run
  Recipe: <Dynamically Defined Resource>
    * file[/opt/graylog/conf/nginx/ca/graylog.crt] action create
      - create new file /opt/graylog/conf/nginx/ca/graylog.crt
      - update content in file /opt/graylog/conf/nginx/ca/graylog.crt from none to 435ba6
      --- /opt/graylog/conf/nginx/ca/graylog.crt    2015-03-29 20:55:55.482953000 +0000
      +++ /opt/graylog/conf/nginx/ca/.graylog.crt20150329-20-1eif1c1    2015-03-29 20:55:55.478953000 +0000
      @@ -1 +1,23 @@
      +-----BEGIN CERTIFICATE-----
      +MIIDpjCCAo4CCQCHBhBY29RHcjANBgkqhkiG9w0BAQUFADCBlDELMAkGA1UEBhMC
      +REUxEDAOBgNVBAgMB0hhbWJ1cmcxEDAOBgNVBAcMB0hhbWJ1cmcxEDAOBgNVBAoM
      +B0dyYXlsb2cxEzARBgNVBAsMCk9wZXJhdGlvbnMxFTATBgNVBAMMDDU0MmQzNDFh
      +YWMzZDEjMCEGCSqGSIb3DQEJARYUZ3JheWxvZ0A1NDJkMzQxYWFjM2QwHhcNMTUw
      +MzI5MjA1NTU1WhcNMjUwMzI2MjA1NTU1WjCBlDELMAkGA1UEBhMCREUxEDAOBgNV
      +BAgMB0hhbWJ1cmcxEDAOBgNVBAcMB0hhbWJ1cmcxEDAOBgNVBAoMB0dyYXlsb2cx
      +EzARBgNVBAsMCk9wZXJhdGlvbnMxFTATBgNVBAMMDDU0MmQzNDFhYWMzZDEjMCEG
      +CSqGSIb3DQEJARYUZ3JheWxvZ0A1NDJkMzQxYWFjM2QwggEiMA0GCSqGSIb3DQEB
      +AQUAA4IBDwAwggEKAoIBAQC9Esa8TiAdD1d/D3309XoENADYremlztW2fK4pG5F2
      +aY2nZcJhJ5CYBVKjAXhixAyU3jPaZNFmKml82IfaVWZtEsBzm36L1s4i+tqPSWKX
      +5btQEY7OKTyG37+C+P2FWhU8uuPomfolizgXC/Pp5CfR5/kYwh7FQxCg/l0CcZix
      +0qGOMGPlLSINYIO7v8smhgZFVASXDMZwCKDjW7fBJTjA8lolme+HG8yE3IhEmBlR
      +v6wqH7QasYpLm3VKrw0ex5HYojej0KJW3xBTDPylP+XBzEkJyqwSfduggkeq8Q/g
      +6Ik5q8WRlmXCM58PonIhgfKQR3Ke4sh7S7+k58SajC/vAgMBAAEwDQYJKoZIhvcN
      +AQEFBQADggEBABgmp1i8YgqrquP7gmJfiQHt/G81nxcIbBTsHoRXFD+wUcE3o/ZZ
      +/U7OBfb+E/Te4lktdiUoCyhvM+RTxmIhIcalr7SzFJ0urQvx3WF20/KHBIHxwH+O
      +4m8ZmsnP7vAZI7MpgGJ9r9CKxzobGqVlwl0tI9I+dDYprOqF+FVOves610Gsdso2
      +r5obxfej3VKw86ONxWvAMPMbU11mBIEywW3fJI2EEI0RHRFYYrz/9UmqgtMyqU2K
      +eaN1Zm7shRlQcpp0g9HQ/AYML0I4eyN25loF5djNxdTA8YGttzvI1DYCPzyuGGhP
      +fEa50X8XsxVEdJf4m2zpmWIKZR3irqRiusY=
      +-----END CERTIFICATE-----
      - change mode from '' to '0644'
      - change owner from '' to 'root'
      - change group from '' to 'root'
    - execute the ruby block create crtfile
Recipe: graylog::nginx
  * template[/opt/graylog/conf/nginx/nginx.conf] action create
    - update content in file /opt/graylog/conf/nginx/nginx.conf from 95363d to 2b5bc7
    --- /opt/graylog/conf/nginx/nginx.conf  2015-03-13 15:56:15.000000000 +0000
    +++ /tmp/chef-rendered-template20150329-20-1pe8aof  2015-03-29 20:55:55.502953001 +0000
    @@ -1,118 +1,55 @@
    -
    -#user  nobody;
     worker_processes  1;
    +daemon off;

    -#error_log  logs/error.log;
    -#error_log  logs/error.log  notice;
    -#error_log  logs/error.log  info;
    -
    -#pid        logs/nginx.pid;
    -
    -
     events {
         worker_connections  1024;
     }

    -
     http {
    -    include       mime.types;
    +    include       /opt/graylog/conf/nginx/mime.types;
         default_type  application/octet-stream;

    -    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    -    #                  '$status $body_bytes_sent "$http_referer" '
    -    #                  '"$http_user_agent" "$http_x_forwarded_for"';
    -
    -    #access_log  logs/access.log  main;
    -
    -    sendfile        on;
    -    #tcp_nopush     on;
    -
    -    #keepalive_timeout  0;
    -    keepalive_timeout  65;
    -
    -    #gzip  on;
    -
         server {
    -        listen       80;
    -        server_name  localhost;
    -
    -        #charset koi8-r;
    -
    -        #access_log  logs/host.access.log  main;
    -
    -        location / {
    -            root   html;
    -            index  index.html index.htm;
    -        }
    -
    -        #error_page  404              /404.html;
    -
    -        # redirect server error pages to the static page /50x.html
    -        #
    -        error_page   500 502 503 504  /50x.html;
    -        location = /50x.html {
    -            root   html;
    -        }
    -
    -        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
    -        #
    -        #location ~ \.php$ {
    -        #    proxy_pass   http://127.0.0.1;
    -        #}
    -
    -        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    -        #
    -        #location ~ \.php$ {
    -        #    root           html;
    -        #    fastcgi_pass   127.0.0.1:9000;
    -        #    fastcgi_index  index.php;
    -        #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
    -        #    include        fastcgi_params;
    -        #}
    -
    -        # deny access to .htaccess files, if Apache's document root
    -        # concurs with nginx's one
    -        #
    -        #location ~ /\.ht {
    -        #    deny  all;
    -        #}
    +      listen 80;
    +      location / {
    +        proxy_pass http://localhost:9000/;
    +        proxy_set_header Host $host;
    +        proxy_set_header X-Real-IP $remote_addr;
    +        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    +        proxy_pass_request_headers on;
    +        proxy_connect_timeout 150;
    +        proxy_send_timeout 100;
    +        proxy_read_timeout 100;
    +        proxy_buffers 4 32k;
    +        client_max_body_size 8m;
    +        client_body_buffer_size 128k;
    +      }
         }
    +    
    +    server {
    +      listen 443;

    +      ssl on;
    +      ssl_certificate /opt/graylog/conf/nginx/ca/graylog.crt;
    +      ssl_certificate_key /opt/graylog/conf/nginx/ca/graylog.key;
    +      ssl_session_timeout 5m;
    +      ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    +      ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;
    +      ssl_prefer_server_ciphers on;

    -    # another virtual host using mix of IP-, name-, and port-based configuration
    -    #
    -    #server {
    -    #    listen       8000;
    -    #    listen       somename:8080;
    -    #    server_name  somename  alias  another.alias;
    -
    -    #    location / {
    -    #        root   html;
    -    #        index  index.html index.htm;
    -    #    }
    -    #}
    -
    -
    -    # HTTPS server
    -    #
    -    #server {
    -    #    listen       443 ssl;
    -    #    server_name  localhost;
    -
    -    #    ssl_certificate      cert.pem;
    -    #    ssl_certificate_key  cert.key;
    -
    -    #    ssl_session_cache    shared:SSL:1m;
    -    #    ssl_session_timeout  5m;
    -
    -    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    -    #    ssl_prefer_server_ciphers  on;
    -
    -    #    location / {
    -    #        root   html;
    -    #        index  index.html index.htm;
    -    #    }
    -    #}
    -
    +      location / {
    +        proxy_pass http://localhost:9000/;
    +        proxy_set_header Host $host;
    +        proxy_set_header X-Real-IP $remote_addr;
    +        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    +        proxy_pass_request_headers on;
    +        proxy_connect_timeout 150;
    +        proxy_send_timeout 100;
    +        proxy_read_timeout 100;
    +        proxy_buffers 4 32k;
    +        client_max_body_size 8m;
    +        client_body_buffer_size 128k;
    +      }
    +    }
     }
    - change owner from 'root' to 'graylog'
    - change group from 'root' to 'graylog'
  * directory[/opt/graylog/sv/nginx] action create
    - create new directory /opt/graylog/sv/nginx
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * directory[/opt/graylog/sv/nginx/log] action create
    - create new directory /opt/graylog/sv/nginx/log
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * directory[/opt/graylog/sv/nginx/log/main] action create
    - create new directory /opt/graylog/sv/nginx/log/main
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/opt/graylog/sv/nginx/run] action create
    - create new file /opt/graylog/sv/nginx/run
    - update content in file /opt/graylog/sv/nginx/run from none to 4ab11f
    --- /opt/graylog/sv/nginx/run   2015-03-29 20:55:55.558953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-1fkr3a4  2015-03-29 20:55:55.558953000 +0000
    @@ -1 +1,7 @@
    +#!/bin/sh
    +exec 2>&1
    +
    +export LC_ALL=C
    +umask 077
    +exec /opt/graylog/embedded/sbin/nginx -c /opt/graylog/conf/nginx/nginx.conf
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/opt/graylog/sv/nginx/log/run] action create
    - create new file /opt/graylog/sv/nginx/log/run
    - update content in file /opt/graylog/sv/nginx/log/run from none to 43211b
    --- /opt/graylog/sv/nginx/log/run   2015-03-29 20:55:55.566953001 +0000
    +++ /tmp/chef-rendered-template20150329-20-196fk8p  2015-03-29 20:55:55.566953001 +0000
    @@ -1 +1,3 @@
    +#!/bin/sh
    +exec svlogd -tt /var/log/graylog/nginx
    - change mode from '' to '0755'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/var/log/graylog/nginx/config] action create
    - create new file /var/log/graylog/nginx/config
    - update content in file /var/log/graylog/nginx/config from none to 623c00
    --- /var/log/graylog/nginx/config   2015-03-29 20:55:55.574953000 +0000
    +++ /tmp/chef-rendered-template20150329-20-pth6li   2015-03-29 20:55:55.574953000 +0000
    @@ -1 +1,7 @@
    +s209715200
    +n30
    +t86400
    +!gzip
    +
    +
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * ruby_block[reload nginx svlogd configuration] action nothing (skipped due to action :nothing)
  * file[/opt/graylog/sv/nginx/down] action delete (up to date)
  * link[/opt/graylog/init/nginx] action create
    - create symlink at /opt/graylog/init/nginx to /opt/graylog/embedded/bin/sv
  * link[/opt/graylog/service/nginx] action create
    - create symlink at /opt/graylog/service/nginx to /opt/graylog/sv/nginx
  * ruby_block[supervise_nginx_sleep] action run
    - execute the ruby block supervise_nginx_sleep
  * service[nginx] action nothing (skipped due to action :nothing)
  * execute[/opt/graylog/embedded/bin/graylog-ctl start nginx] action run
    - execute /opt/graylog/embedded/bin/graylog-ctl start nginx
Recipe: ntp::default
  * apt_package[ntp] action install (up to date)
  * apt_package[ntpdate] action install (up to date)
  * directory[/var/lib/ntp] action create (up to date)
  * directory[/var/log/ntpstats/] action create (up to date)
  * cookbook_file[/etc/ntp.leapseconds] action create
    - create new file /etc/ntp.leapseconds
    - update content in file /etc/ntp.leapseconds from none to 274665
    --- /etc/ntp.leapseconds    2015-03-29 20:56:02.546953001 +0000
    +++ /etc/.ntp.leapseconds20150329-20-93j4nc 2015-03-29 20:56:02.546953001 +0000
    @@ -1 +1,219 @@
    +#
    +#  In the following text, the symbol '#' introduces
    +#  a comment, which continues from that symbol until 
    +#  the end of the line. A plain comment line has a
    +#  whitespace character following the comment indicator.
    +#  There are also special comment lines defined below. 
    +#  A special comment will always have a non-whitespace 
    +#  character in column 2.
    +#
    +#  A blank line should be ignored.
    +#
    +#  The following table shows the corrections that must
    +#  be applied to compute International Atomic Time (TAI)
    +#  from the Coordinated Universal Time (UTC) values that
    +#  are transmitted by almost all time services.
    +#
    +#  The first column shows an epoch as a number of seconds
    +#  since 1900.0 and the second column shows the number of
    +#  seconds that must be added to UTC to compute TAI for
    +#  any timestamp at or after that epoch. The value on 
    +#  each line is valid from the indicated initial instant
    +#  until the epoch given on the next one or indefinitely 
    +#  into the future if there is no next line.
    +#  (The comment on each line shows the representation of
    +#  the corresponding initial epoch in the usual 
    +#  day-month-year format. The epoch always begins at
    +#  00:00:00 UTC on the indicated day. See Note 5 below.)
    +#  
    +#  Important notes:
    +#
    +#  1. Coordinated Universal Time (UTC) is often referred to
    +#  as Greenwich Mean Time (GMT). The GMT time scale is no
    +#  longer used, and the use of GMT to designate UTC is
    +#  discouraged.
    +#
    +#  2. The UTC time scale is realized by many national 
    +#  laboratories and timing centers. Each laboratory
    +#  identifies its realization with its name: Thus
    +#  UTC(NIST), UTC(USNO), etc. The differences among
    +#  these different realizations are typically on the
    +#  order of a few nanoseconds (i.e., 0.000 000 00x s)
    +#  and can be ignored for many purposes. These differences
    +#  are tabulated in Circular T, which is published monthly
    +#  by the International Bureau of Weights and Measures
    +#  (BIPM). See www.bipm.fr for more information.
    +#
    +#  3. The current defintion of the relationship between UTC 
    +#  and TAI dates from 1 January 1972. A number of different 
    +#  time scales were in use before than epoch, and it can be 
    +#  quite difficult to compute precise timestamps and time 
    +#  intervals in those "prehistoric" days. For more information,
    +#  consult:
    +#
    +#      The Explanatory Supplement to the Astronomical
    +#      Ephemeris.
    +#  or
    +#      Terry Quinn, "The BIPM and the Accurate Measurement
    +#      of Time," Proc. of the IEEE, Vol. 79, pp. 894-905,
    +#      July, 1991.
    +#
    +#  4.  The insertion of leap seconds into UTC is currently the
    +#  responsibility of the International Earth Rotation Service,
    +#  which is located at the Paris Observatory: 
    +#
    +#  Central Bureau of IERS
    +#  61, Avenue de l'Observatoire
    +#  75014 Paris, France.
    +#
    +#  Leap seconds are announced by the IERS in its Bulletin C
    +#
    +#  See hpiers.obspm.fr or www.iers.org for more details.
    +#
    +#  All national laboratories and timing centers use the
    +#  data from the BIPM and the IERS to construct their
    +#  local realizations of UTC.
    +#
    +#  Although the definition also includes the possibility
    +#  of dropping seconds ("negative" leap seconds), this has 
    +#  never been done and is unlikely to be necessary in the 
    +#  foreseeable future.
    +#
    +#  5. If your system keeps time as the number of seconds since
    +#  some epoch (e.g., NTP timestamps), then the algorithm for
    +#  assigning a UTC time stamp to an event that happens during a positive
    +#  leap second is not well defined. The official name of that leap 
    +#  second is 23:59:60, but there is no way of representing that time 
    +#  in these systems. 
    +#  Many systems of this type effectively stop the system clock for 
    +#  one second during the leap second and use a time that is equivalent 
    +#  to 23:59:59 UTC twice. For these systems, the corresponding TAI 
    +#  timestamp would be obtained by advancing to the next entry in the
    +#  following table when the time equivalent to 23:59:59 UTC
    +#  is used for the second time. Thus the leap second which
    +#  occurred on 30 June 1972 at 23:59:59 UTC would have TAI
    +#  timestamps computed as follows:
    +#
    +#  ...
    +#  30 June 1972 23:59:59 (2287785599, first time): TAI= UTC + 10 seconds
    +#  30 June 1972 23:59:60 (2287785599,second time): TAI= UTC + 11 seconds
    +#  1  July 1972 00:00:00 (2287785600)      TAI= UTC + 11 seconds
    +#  ...
    +#
    +#  If your system realizes the leap second by repeating 00:00:00 UTC twice
    +#  (this is possible but not usual), then the advance to the next entry
    +#  in the table must occur the second time that a time equivlent to 
    +#  00:00:00 UTC is used. Thus, using the same example as above:
    +#
    +#  ...
    +#       30 June 1972 23:59:59 (2287785599):        TAI= UTC + 10 seconds
    +#       30 June 1972 23:59:60 (2287785600, first time):    TAI= UTC + 10 seconds
    +#       1  July 1972 00:00:00 (2287785600,second time):    TAI= UTC + 11 seconds
    +#  ...
    +#
    +#  in both cases the use of timestamps based on TAI produces a smooth
    +#  time scale with no discontinuity in the time interval.
    +#
    +#  This complexity would not be needed for negative leap seconds (if they 
    +#  are ever used). The UTC time would skip 23:59:59 and advance from 
    +#  23:59:58 to 00:00:00 in that case.  The TAI offset would decrease by 
    +#  1 second at the same instant.  This is a much easier situation to deal 
    +#  with, since the difficulty of unambiguously representing the epoch 
    +#  during the leap second does not arise.
    +#
    +#  Questions or comments to:
    +#      Jeff Prillaman
    +#      Time Service Department
    +#      US Naval Observatory
    +#      Washington, DC
    +#      jeffrey.prillaman@usno.navy.mil
    +#
    +#  Last Update of leap second values:  11 Feb 2014
    +#
    +#  The following line shows this last update date in NTP timestamp 
    +#  format. This is the date on which the most recent change to
    +#  the leap second data was added to the file. This line can
    +#  be identified by the unique pair of characters in the first two 
    +#  columns as shown below.
    +#
    +#$  3601065600
    +#
    +#  The data in this file will be updated periodically as new leap 
    +#  seconds are announced. In addition to being entered on the line
    +#  above, the update time (in NTP format) will be added to the basic 
    +#  file name leap-seconds to form the name leap-seconds.<NTP TIME>.
    +#  In addition, the generic name leap-seconds.list will always point to 
    +#  the most recent version of the file.
    +#
    +#  This update procedure will be performed only when a new leap second
    +#  is announced. 
    +#
    +#  The following entry specifies the expiration date of the data
    +#  in this file in units of seconds since 1900.0.  This expiration date 
    +#  will be changed at least twice per year whether or not a new leap 
    +#  second is announced. These semi-annual changes will be made no
    +#  later than 1 June and 1 December of each year to indicate what
    +#  action (if any) is to be taken on 30 June and 31 December, 
    +#  respectively. (These are the customary effective dates for new
    +#  leap seconds.) This expiration date will be identified by a
    +#  unique pair of characters in columns 1 and 2 as shown below.
    +#  In the unlikely event that a leap second is announced with an 
    +#  effective date other than 30 June or 31 December, then this
    +#  file will be edited to include that leap second as soon as it is
    +#  announced or at least one month before the effective date
    +#  (whichever is later). 
    +#  If an announcement by the IERS specifies that no leap second is 
    +#  scheduled, then only the expiration date of the file will 
    +#  be advanced to show that the information in the file is still
    +#  current -- the update time stamp, the data and the name of the file 
    +#  will not change.
    +#
    +#  Updated through IERS Bulletin C 47
    +#  File expires on:  1 Dec 2014
    +#
    +#@ 3626380800
    +#
    +2272060800 10  # 1 Jan 1972
    +2287785600 11  # 1 Jul 1972
    +2303683200 12  # 1 Jan 1973
    +2335219200 13  # 1 Jan 1974
    +2366755200 14  # 1 Jan 1975
    +2398291200 15  # 1 Jan 1976
    +2429913600 16  # 1 Jan 1977
    +2461449600 17  # 1 Jan 1978
    +2492985600 18  # 1 Jan 1979
    +2524521600 19  # 1 Jan 1980
    +2571782400 20  # 1 Jul 1981
    +2603318400 21  # 1 Jul 1982
    +2634854400 22  # 1 Jul 1983
    +2698012800 23  # 1 Jul 1985
    +2776982400 24  # 1 Jan 1988
    +2840140800 25  # 1 Jan 1990
    +2871676800 26  # 1 Jan 1991
    +2918937600 27  # 1 Jul 1992
    +2950473600 28  # 1 Jul 1993
    +2982009600 29  # 1 Jul 1994
    +3029443200 30  # 1 Jan 1996
    +3076704000 31  # 1 Jul 1997
    +3124137600 32  # 1 Jan 1999
    +3345062400 33  # 1 Jan 2006
    +3439756800 34  # 1 Jan 2009
    +3550089600 35  # 1 Jul 2012
    +#
    +#  the following special comment contains the
    +#  hash value of the data in this file computed
    +#  use the secure hash algorithm as specified
    +#  by FIPS 180-1. See the files in ~/sha for
    +#  the details of how this hash value is
    +#  computed. Note that the hash computation
    +#  ignores comments and whitespace characters
    +#  in data lines. It includes the NTP values
    +#  of both the last modification time and the 
    +#  expiration time of the file, but not the
    +#  white space on those lines.
    +#  the hash line is also ignored in the
    +#  computation.
    +#
    +#h 6660fba2 47c392c3 fc7bb657 d338b539 ce357d44
    +#
    - change mode from '' to '0644'
    - change owner from '' to 'root'
    - change group from '' to 'root'
  * template[/etc/ntp.conf] action create
    - update content in file /etc/ntp.conf from 4eb9a0 to 49f120
    --- /etc/ntp.conf   2015-02-06 15:24:35.000000000 +0000
    +++ /tmp/chef-rendered-template20150329-20-1uzp1a8  2015-03-29 20:56:02.606953000 +0000
    @@ -1,56 +1,32 @@
    -# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
    -
    +# Generated by Chef for 542d341aac3d
    +# Local modifications will be overwritten.
    +tinker panic 0
    +statsdir /var/log/ntpstats/
    +leapfile /etc/ntp.leapseconds
     driftfile /var/lib/ntp/ntp.drift

    -
    -# Enable this if you want statistics to be logged.
    -#statsdir /var/log/ntpstats/
    -
     statistics loopstats peerstats clockstats
     filegen loopstats file loopstats type day enable
     filegen peerstats file peerstats type day enable
     filegen clockstats file clockstats type day enable

    -# Specify one or more NTP servers.

    -# Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
    -# on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
    -# more information.
    -server 0.ubuntu.pool.ntp.org
    -server 1.ubuntu.pool.ntp.org
    -server 2.ubuntu.pool.ntp.org
    -server 3.ubuntu.pool.ntp.org
    +disable monitor

    -# Use Ubuntu's ntp server as a fallback.
    -server ntp.ubuntu.com

    -# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
    -# details.  The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
    -# might also be helpful.
    -#
    -# Note that "restrict" applies to both servers and clients, so a configuration
    -# that might be intended to block requests from certain clients could also end
    -# up blocking replies from your own upstream servers.
    +server 0.pool.ntp.org iburst
    +restrict 0.pool.ntp.org nomodify notrap noquery
    +server 1.pool.ntp.org iburst
    +restrict 1.pool.ntp.org nomodify notrap noquery
    +server 2.pool.ntp.org iburst
    +restrict 2.pool.ntp.org nomodify notrap noquery
    +server 3.pool.ntp.org iburst
    +restrict 3.pool.ntp.org nomodify notrap noquery

    -# By default, exchange time with everybody, but don't allow configuration.
    -restrict -4 default kod notrap nomodify nopeer noquery
    +restrict default kod notrap nomodify nopeer noquery
    +restrict 127.0.0.1 nomodify
     restrict -6 default kod notrap nomodify nopeer noquery
    +restrict -6 ::1 nomodify

    -# Local users may interrogate the ntp server more closely.
    -restrict 127.0.0.1
    -restrict ::1

    -# Clients from this (example!) subnet have unlimited access, but only if
    -# cryptographically authenticated.
    -#restrict 192.168.123.0 mask 255.255.255.0 notrust
    -
    -
    -# If you want to provide time to your local subnet, change the next line.
    -# (Again, the address is an example only.)
    -#broadcast 192.168.123.255
    -
    -# If you want to listen to time broadcasts on your local subnet, de-comment the
    -# next lines.  Please do this only if you trust everybody on the network!
    -#disable auth
    -#broadcastclient
  * service[ntp] action enable (up to date)
  * service[ntp] action start
    - start service service[ntp]
Recipe: graylog::etcd
  * ruby_block[reload etcd svlogd configuration] action create
    - execute the ruby block reload etcd svlogd configuration
Recipe: graylog::elasticsearch
  * service[elasticsearch] action restart
    - restart service service[elasticsearch]
  * ruby_block[reload elasticsearch svlogd configuration] action create
    - execute the ruby block reload elasticsearch svlogd configuration
Recipe: graylog::mongodb
  * ruby_block[reload mongodb svlogd configuration] action create
    - execute the ruby block reload mongodb svlogd configuration
Recipe: graylog::graylog-server
  * service[graylog-server] action restart
    - restart service service[graylog-server]
  * ruby_block[reload graylog-server svlogd configuration] action create
    - execute the ruby block reload graylog-server svlogd configuration
Recipe: graylog::graylog-web
  * service[graylog-web] action restart
    - restart service service[graylog-web]
  * ruby_block[reload graylog-web svlogd configuration] action create
    - execute the ruby block reload graylog-web svlogd configuration
Recipe: graylog::nginx
  * service[nginx] action restart
    - restart service service[nginx]
  * ruby_block[reload nginx svlogd configuration] action create
    - execute the ruby block reload nginx svlogd configuration
Recipe: ntp::default
  * service[ntp] action restart
    - restart service service[ntp]

Running handlers:
Running handlers complete
Chef Client finished, 107/120 resources updated in 36.558666794 seconds
graylog Reconfigured!

[theduke]

My bad.

For others who run into issues on a Debian 7 (Wheezy) installation:

Wheezy ships with the Linux Kernel 3.2, but some Docker features require 3.8. Upgrade your kernel (using the wheezy backports apt repository) and reboot. Then it should work just fine.

[sentient]

:) Same issue here. But my linux kernel and docker are fairly recent.

uname -a

Linux linux-mint-17 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$docker version

Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): a8a31ef
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.4.1
Git commit (server): a8a31ef

So what else can I check if it cannot connect?

[ashishWaghmare]

Same is happening to me using latest graylog docker image.

docker version Client: Version: 1.8.3 API version: 1.20 Go version: go1.4.2

uname -a Linux ashishw 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[mariussturm]

@ashishWaghmare could you please provide some more informations like error messages from the Chef output and errors seen in graylog-server/elasticsearch logs?

[sentient]

Actually in my case I got it to work. It appeared it was not working. But the first time startup took some time (and there was not much feedback). So let it run for a bit before trying to connect with the web interface.

[ashishWaghmare]

@mariussturm got it working as adviced by @sentient . It just took longer to boot initially. Works fine for me now.