opscode-analytics-ctl preflight Checklist

Eric Alwais -

If you are about to install Analytics here are a couple of items that you might want to verify before running the opscode-analytics-ctl preflight.  

Items to check on the  Chef Server

1) less /etc/opscode/chef-server.rb

        Look for oc_id['vip'] = 'localhost'

2) Verify in /etc/hosts that 127.0.0.1 has the server name and fqdn

3) Verify in /etc/hosts file of both chef server and analytics that you have FQDN and host name entries. (this may not be needed if DNS entries are already there)

4) Verify both systems are able to ping one another with hostname and IP of the Analytics server as well as the Chef Server. Also telnet over port 443.

5) Verify all services are running.  opscode-analytics-ctl status.  

 It should look similar to this: (the time next to the first PID is the service time up and the time to the second pid is the log time up.  We are only looking for the first one)


run: bookshelf: (pid 683) 72347s; run: log: (pid 666) 72347s
run: nginx: (pid 688) 72347s; run: log: (pid 670) 72347s
run: oc_bifrost: (pid 687) 72347s; run: log: (pid 672) 72347s
run: oc_id: (pid 30769) 2s; run: log: (pid 674) 72347s
run: opscode-erchef: (pid 685) 72347s; run: log: (pid 662) 72347s
run: opscode-expander: (pid 678) 72347s; run: log: (pid 663) 72347s
run: opscode-expander-reindexer: (pid 679) 72347s; run: log: (pid 664) 72347s
run: opscode-solr4: (pid 680) 72347s; run: log: (pid 673) 72347s
run: postgresql: (pid 690) 72347s; run: log: (pid 667) 72347s
run: rabbitmq: (pid 684) 72347s; run: log: (pid 671) 72347s
run: redis_lb: (pid 686) 72347s; run: log: (pid 675) 72347s


Items on the Analytics Server

1) Verify in /etc/hosts that 127.0.0.1 has the server name and fqdn

2) Verify in /etc/hosts file of both chef server and analytics that you have FQDN and host name entries. (this may not be needed if DNS entries are already there)

3) Verify both systems are able to ping one another with the hostname and IP of the Analytics server as well as the Chef Server. Also telnet over port 443.

4) Verify that you can telnet from the Analytics server to the Chef server on port 9090

5) Verify all services are running.  opscode-analytics-ctl status.

     It should look similar to this: (the time next to the first PID is the service time up and the time to the second pid is the log time up.  We are only looking for the first one)


run: actions: (pid 1491) 10s; run: log: (pid 503) 705s 
run: actions_messages: (pid 502) 705s; run: log: (pid 501) 705s 
run: alaska: (pid 1305) 311s; run: log: (pid 520) 704s 
run: memcached: (pid 511) 705s; run: log: (pid 510) 705s 
run: nginx: (pid 513) 705s; run: log: (pid 512) 705s 
run: notifier: (pid 1232) 387s; run: log: (pid 522) 705s 
run: notifier_config: (pid 1192) 395s; run: log: (pid 509) 706s 
run: postgresql: (pid 506) 706s; run: log: (pid 505) 706s 
run: rabbitmq: (pid 1081) 487s; run: log: (pid 507) 706s 
run: zookeeper: (pid 517) 706s; run: log: (pid 516) 706s



6) If you see something like this example where the service is not around the same time frame run the following:

            opscode-analytics-ctl tail actions

7) You may see something similar to this:


2015-09-11_17:14:34.99739 => Booting Puma 
2015-09-11_17:14:34.99815 => Rails 4.1.8 application starting in production on http://0.0.0.0:10011 
2015-09-11_17:14:34.99816 => Run `rails server -h` for more startup options 
2015-09-11_17:14:34.99818 => Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)1-5-0-pushy-1-1-6 
2015-09-11_17:14:34.99819 => Ctrl-C to shutdown server 2015-09-11_17:14:34.99903 A server is already running. Check /opt/opscode-analytics/embedded/service/actions/tmp/pids/server.pid. 
2015-09-11_17:14:35.08441 Exiting


    In this case move the file to the same location but add .old to the file


mv  /opt/opscode-analytics/embedded/service/actions/tmp/pids/server.pid /opt/opscode-analytics/embedded/service/actions/tmp/pids/server.pid.old

    Then restart the services

            opscode-analytics-ctl stop

            opscode-analytics-ctl start

Have more questions? Submit a request

Comments

Powered by Zendesk