A checklist for those attempting to only get out of bed when it's important and to be able to debug critial and non-critial issues.
Those emphesised should probably get you out of bed when they're too high/low/gone.
This is super opinionated but I welcome feedback. It's biased to retrofitting/cleaning up/brownfield type work because that's what I know best.
| cd /opt/graphite/webapp/graphite | |
| python ./manage.py shell | |
| P | |
| (InteractiveConsole) | |
| >>> from django.contrib.auth.models import User | |
| >>> users = User.objects.all() | |
| >>> users | |
| [<User: graphite>, <User: default>] | |
| >>> users[0].set_password('password-here') | |
| >>> users[0].save() |
| Based on http://www.alphadevx.com/a/455-Installing-Supervisor-and-Superlance-on-CentOS | |
| Vgrnt box used: https://github.com/tommy-muehle/puppet-vagrant-boxes/releases/download/1.0.0/centos-6.6-x86_64.box | |
| sudo yum install python-setuptools | |
| sudo easy_install supervisor | |
| supervisord --version | |
| echo_supervisord_conf | sudo tee /etc/supervisord.conf | |
| sudo mkdir -p /etc/supervisord/conf.d/ | |
| sudo vi /etc/init.d/supervisord |
| for USERNAME in `aws iam list-users | jq -r '.Users[].UserName'` | |
| do | |
| KEYS=$(aws iam list-access-keys --user-name $USERNAME | jq '.AccessKeyMetadata[].AccessKeyId') | |
| echo $USERNAME, $KEYS | |
| done |
| # I always have to look this up. You need PutObjectAcl as well as putting the object itself. | |
| { | |
| "Version": "2012-10-17", | |
| "Statement": [ | |
| { | |
| "Sid": "Stmt1458821885000", | |
| "Effect": "Allow", |
| # adapted from https://tech.fawk.eu/111/ | |
| echo "show stat" | nc -U /var/lib/haproxy/stats |
| redis-cli lrange 2013_10_26 0 2000 | xargs redis-cli sadd s2013_10_26 |
| grep -n "Connection refused" error.log-20130806 | awk '{print $2}' > errortimes.log | |
| sort errortimes.log | uniq -c |
| // Don't forget this line or signal handling won't work: | |
| declare(ticks = 1); | |
| // This global flag is used to trigger a configuration file reload. | |
| $load_config = true; | |
| // The SIGHUP handler doesn't do any actual work; it just sets the flag. | |
| function handle_hup($signal) { | |
| global $load_config; | |
| $load_config = true; |
| The scripts you pass through as a compiled user-script are split up and expanded into /var/lib/cloud/instance/scripts so you can go and run them again and debug |