Getting Subsonic working behind Nginx

The subsonic Web UI uses frames as if you just proxy subsonic with SSL/TLS termination like you would with any other website you will find the pages does not load. You need to add a directive to your configuration:

add_header X-Frame-Options SAMEORIGIN;

This should also work with madsonic.

Advertisements

Installing LetsEncrypt certbot from GitHub

Sometimes there the delay between a new certbot release from LetsEncrypt and the time it hits the Ubuntu LaunchPad PPA.  However there is not much involved in setting up Ubuntu to use certbot directly from the GitHub source.  I tested the following out on Ubuntu 14.04 LTS and 16.04 LTS and it worked without a hitch:

sudo apt-get remove certbot
sudo add-apt-repository --remove ppa:certbot/certbot
cd /opt
sudo git clone https://github.com/certbot/certbot.git
cd certbot
sudo git checkout v0.21.1
sudo ln -s /opt/certbot/certbot-auto /usr/bin/certbot
certbot renew
sudo apt-get autoremove

To update simply go to the repo and `git checkout` the latest version.

Re-enabling a failed RAID Array HP410

Sometimes a disk will drop out a RAID array, especially if you have drives that don’t support a low latency error recovery such as the Seagate Barracuda SFF drives.  You should notice an alarm in ESX or your operating system that says the Logical Drive has failed.  Associated with this will be a physical drive failure too.

To recovery from the problem you will need to remove the affected drive for 10 seconds and then re-insert the drive into the slot it came from.  You can do all of this while the system is booted into the array management software.

Once you have the physical drive recognised as operational again then you can make steps to recover the logical drive.  In my case I am using ESX but any other operating system that can use the hpssacli utility should be the same.

First show the status of the logical drive:

./hpssacli ctrl slot=0 ld 1 show status

logicaldrive 1 (14.6 TB, 0): Failed

Now re-enable the logical drive:

./hpssacli ctrl slot=0 ld 1 modify reenable forced

Now check the logical drive again:

./hpssacli ctrl slot=0 ld 1 show status

logicaldrive 1 (14.6 TB, 0): OK

For most people the solution to this ongoing problem would be to use drives that support a lower recovery latency such as WD Reds but until they do them in large capacities I will be sticking with my 4TB Barracudas.

Advertisements