I hadn’t noticed but my log directory was slowly growing. This is running on a digitalocean droplet.

Taken from: https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs

Deleting Old Logs

If you use the –vacuum-size option, you can shrink your journal by indicating a size. This will remove old entries until the total journal space taken up on disk is at the requested size:

sudo journalctl --vacuum-size=1G

Back to a healthier size.

I was recently setting up a test ESXi host with some spare hardware and ran in to an issue with ESXi 5.5.0 whereby I had 3.97G ram available (due to the video card using some RAM) and this was lower than the 4G requirement of ESXi.

I followed the guide at: http://community.spiceworks.com/topic/411970-installing-esxi-5-5-with-4gb-ram-memory_size-error to override this.

1. Boot from VMware ESXi 5.5;

2. wait for the “Welcome to theVMware ESXi 5.5.0 Installation” screen:

Image: //static.spiceworks.com/shared/post/0004/3520/index.jpg

3. Press Alt+F1 for enter console and login as ‘root’ (no password needed);

4. go to:

cd /usr/lib/vmware/weasel/util/

delete file:

rm upgrade_precheck.pyc;

5. remove readonly flags;

mv upgrade_precheck.py upgrade_precheck.py.def

cp upgrade_precheck.py.def upgrade_precheck.py

6. set permissions:

chmod 755 upgrade_precheck.py

7. open script in ‘vi’:

vi upgrade_precheck.py

8. type “/MEM_MIN_SIZE” to find the string “MEM_MIN_SIZE”, press “a” to enter edit mode. “(4 * 1024 – 32)” change to “(2 * 1024 – 32)”, press ‘ESC’ and then type “:wq” (save & exit);

9. look for the installer PID:

ps -c | grep weasel

10. kill the installer (PID = process number):

kill PID

The process installer process will run automatically (with modified config script).

Continue from “Welcome to theVMware ESXi 5.5.0 Installation” as usual.

To resize a disk I had to use Carbon Copy Cloner, cloning the existing disk to another drive, then booting up in to it.

1. VMWare Edit Settings on VM you want to change
2. Add 2nd hard drive with new primary partition size you want
3. Restart the VM to pick up the new drive
4. Open Disk Utility select new hard drive and partition as GUID
5. Run CCC and copy old hard drive to new one. You will be prompted and asked if you would like to create a recovery drive. Select YES if you want to use this feature.
6. Run Systems Preferences and change startup disk to new one and restart VM (confirm that it works)
7. Un-mount old hard drive
8. WMWare Edit Settings remove the old hard drive.
9. Power cycle the VM. And then finally delete the old drive from disk.

This did the trick for me.

I need to connect to a VNC server but do not have a firewall rule to allow that traffic by default.

I do however have an OpenSSH server running which I can connect to through the firewall. To achieve this I issue the following command on my local mac osx in a terminal window

ssh -L 5900:[internal server IP]:5900 username@my-remote-server-ipaddress

After it prompts for a password I then issue the following in Finder -> Go

vnc://127.0.0.1:5900

Connecting to my self on port 5900 forwards to the remote server, and then on to the internal IP. I can then login to the VNC Server as usual.

For a short time I’m having to use a Technicolor TF582n FTTC router whilst I rule out a hardware issue affecting my fibre connection.

THe DNS servers picked up by default don’t tend to be that great, so I prefer to use Google DNS servers. Here’s how I changed the addresses quickly via a telnet session.

Taken from:
http://www.petecooper.org/tutorials/changing-dns-servers-on-a-technicolor-tg582n-fttc

dns server route list
dns server route flush
dns server route add dns=8.8.8.8 metric=10 intf=Internet
dns server route add dns=8.8.8.8 metric=10 intf=Internet
dns server route list

if happy

saveall

No need to reboot the router.

I wanted to check that suPHP was working correctly and executing scripts under a specific user id.

This little PHP script did the trick.

php echo ‘whoim = ‘.exec(‘/usr/bin/whoami’);

That echo’d (outputted) the result of running a file /user/bin/whoami