Using NFS with Elasticsearch is not recommended. I do understand why this is done in production environments (performance is important). However, I am a home user and my lab uses a different layout. I store all my zones on a

While attempting to install Nuxeo in a zone, I noticed that it spews an error message: Invalid file name for use with -Xloggc: Filename can only contain the characters [A-Z][a-z][0-9]-_.%[p|t] but it has been "/opt/

A great list of self hosted (web) applications is available on GitHub. That will serve as a reference point from now on... Plenty of stuff to try out.

This problem keeps haunting me, and has been since 2012. My NAS (Solaris 11) contains 3 IBM BR10i cards, with a total of 24 drives attached to it in a Supermicro 24 bay case. ZFS is my filesystem of choice.

When a few of my Wordpress installations were hacked, the directories containing the installation got literally infested with thousands of files. Google indexed those files happily. Now everything is clean again, but Google (and other engines, such as Bing and

EDIT: unfortunately SmartOS currently does not support v2 Docker registry images, so the content below will not work anymore. So is it possible to run Docker images on SmartOS? The answer, as it turns out, is yes. Does that get

During my holidays, my webserver was compromised. I noticed because the zone running my site felt laggy. It would take just a tad longer than normal to return a directory listing, for example. After a bit of digging around I

All of a sudden, Uchiwa is reporting connection errors, signaling sensu-server and sensu-api are not running. They indeed are not. Seems I have stumbled on an older issue which should be fixed in Sensu 0.18 - I'm running 0.

Ubuntu 14.04 (lx-brand 20150601), mounting an NFS share results in: NFS fsinfo failed for server xx: error 7 (RPC: Authentication error) mount.nfs: Resource temporarily unavailable The solution is to use sec=sys in the mount options, like so:

Yesterday, I upgraded the SmartOS headnode to a more recent version (20150625) than the 2014 version I was running. Brand LX support is now a lot more stable, which means I can start phasing out KVM hosts. The first image

My SmartOS headnode runs a release from 20141212. I've been looking to update it for some time, but was put off by some misconfiguration I have made with the Sensu clients on SmartOS. I need to start those manually after

Writing this down pretty much to remind me how I fixed this should it occur again... My NAS runs Solaris. Every now and then - for some reason, primarily in summer when temperatures in the garage are a bit higher