To enable HTTPS on
influxdb for debian do the following.
Get a certificate. Easy way is to let debian do it for you. The ssl-cert package will generate a self signed cert.
Now pipe the key and pem to somewhere influxdb can get to it.
cat / etc / ssl / private / ssl - cert - snakeoil .key / etc / ssl / certs / ssl - cert - snakeoil .pem > / etc / influxdb / influxdb .pem
Then turn on https in your /etc/influxdb/influxdb.conf and point to your new pem.
vi / etc / influxdb / influxdb .conf
[ admin ] enabled = true bind - address = ":8083" https - enabled = true https - certificate = "/etc/influxdb/influxdb.pem"
[ http ] enabled = true bind - address = ":8086" auth - enabled = true log - enabled = true write - tracing = false pprof - enabled = false https - enabled = true https - certificate = "/etc/influxdb/influxdb.pem"
Start up influxdb and you’re done.
Useful if you want to only output something if a command exists.
if $ ( type YOUR_COMMAND & > / dev / null ) ; then RUN_YOUR_COMMAND ; else echo "" ; fi
For example, I use this on my Proxmox hypervisors with ZFS to get status. Not all my hypervisors have zfs arrays. Makes it easy to blanket ssh to all hypervisors and get zfs status if it exists. For a custom status page I wrote.
if $ ( type zpool & > / dev / null ) ; then zpool list ; else echo "" ; fi
A few quick notes on getting
Proxmox running with Quagga routers so they can serve up OSPF routes. I did this with Proxmox 3.1-3 and Quagga 0.99.22.4-1+wheezy1.
apt-get install quagga
cp /usr/share/doc/quagga/examples/vtysh.conf.sample /etc/quagga/vtysh.conf
cp /usr/share/doc/quagga/examples/ospfd.conf.sample /etc/quagga/ospfd.conf
cp /usr/share/doc/quagga/examples/zebra.conf.sample /etc/quagga/zebra.conf
modify above conf files if you want (can leave default)
turn off annoying splash screens in vtysh
service quagga restart
set the ospf id name. Usually set to this machine’s IP (replace <MACHINE_IP> below)
eg router-id 192.168.1.1
specify networks to route and for what ospf area
network <IP>/<CIDR> area <AREA>
eg. network 192.168.1.0/24 area 1
copy running-config startup-config
now start watching
show ip route for the routes to show up from other ospf routers with an O in the front.
can also look at
show ip ospf neighbor to see your ospf neighbors.
If you’re like me and start forgetting which terminal is which, try changing their background so it’s easier to tell. Most modern terminals can do this out of the box. In putty (and KiTTY) it’s a simple as:
I like to do this on terminals that have critical connections up (like a primary router). So I don’t accidentally type something wrong in there…
If you run into some weird characters while using Fish shell from Putty, try changing Putty’s remote character set to UTF-8:
Right Click Putty -> Change Settings -> Window -> Translation -> Remote Character Set -> UTF-8.
Before and after:
jdrews @ arch ~ > vi / home / jdrews / .config / fish / fish
fish / fish _history â¦ fish / fishd . 00155d03510c jdrews @ arch ~ > vi / home / jdrews / .config / fish / fish
fish / fish _history … fish / fishd . 00155d03510c
And if your Home and End keys don’t work, try putting this into your config.fish file .
jdrews @ arch ~ > cat ~ / .config / fish / config .fish function fish_user_key_bindings bind \ e \ [ 1 ~ beginning - of - line bind \ e \ [ 3 ~ delete - char bind \ e \ [ 4 ~ end - of - line