Another recipe to do something with aubergine

I dislike aubergine, but HelloFresh insist on me continuing to try it. This recipe was alright, I guess. Maybe I’ll swap out the aubergine for beans of some kind next time though!


Onion, 1 Flat Leaf Parsley, 1/2 bunch*
Garlic Clove, 2 Sun-dried Tomato, 30g
Aubergine, 1 Chilli Flakes, a pinch*
Wholewheat Tagliatelle, 180g Chopped tomatoes, 1 tin*
Hard Italian Cheese, as much as you like

* Sorry these amounts are so unhelpful.

This is a pretty healthy meal, filling 4 of your 5 a day! (Which I’m sure the NHS told me was supposed to be 11 a day, at some point. You cannot win.)

FYI, so you only have to wash up some things: you’re gonna need one large pan for boiling the tagliatelle, a large frying pan which is big enough to hold all your tomatoes, onion and a baking tray. Also, a couple plates, knifes and forks. You can stop washing up now – just leave those cups for later?

  1. Fill the pan with water, and start it off boiling. Once it’s boiling, throw in the tagliatelle. Cook until it’s sort-of-soft-but-still-firm-kinda. Then take it off the heat.
  2. Cut up the aubergine. Get rid of the middle spongy bit – we won’t be using it.
  3. Throw this onto the baking tray with some oil, and put it in the grill. Cook until it’s a little crispy on the outsides.
  4. Meanwhile, chop the onion, garlic and sun-dried tomatoes. It’s okay to get these all mixed up if you run out of room. They’ll be fried together.
    Here, I’ve not chopped the tomato nearly enough. Keep chopping, otherwise you’ll get surprising chewy bits in your food.
  5. Chop the parsley too, but keep that separate.
  6. Throw the onion, garlic, sun-dried tomatoes, and chili flakes into the frying pan, with a little oil. Mix these up good and proper. I did not mix well enough, and the chili flakes got all clumped in together.
  7. After a few minutes of these cooking, throw in the tinned tomatoes and some black pepper. Let this steam off for a few minutes, til it’s a little thicker.
  8. Throw in the aubergine, if it’s cooked.
  9. Throw in the pasta!
  10. Mix it all up.
  11. Serve with cheese and parsley on top.

Accessing your MySQL server: “Network is unreachable”

This has been a very sysadmin-y week for me, and I’ve mixed feelings about that. For now though, I’d like to tell the story of how I debugged why I couldn’t access my MySQL server.

My standard MO would be to have MySQL and the app running on the same machine. This time though, since I’ve built my app using Docker (which I’m deploying with Docker Cloud) I can’t have the MySQL server on the same box.

I do have a box already with MySQL running, however that box is smartly locked down with all sorts of iptables voodoo. Very few things are allowed to talk out from the server, and even fewer are allowed to talk to the server. Here are the steps I took while learning how to open that box up.

First, on the MySQL box figure out what port it’s running on. The default is 3306, but you can confirm that like so:

sudo netstat --tcp --listening --program --numeric-ports | grep 'mysql'

The number in the forth column, which looks a bunch like an IP address with a port, is the port you’re looking for.

Now we know that, we can check if our app server has access to the database server.

telnet 3306

Hopefully, you won’t get anything back but a quick message about it “Trying” to connect, and eventually “Network is unreachable”. If this command does actually connect you to your MySQL server then you should focus on locking that down as soon as you can.

Assuming that you’ve already got your server locked down via iptables though, you’ll want to open it up so that you app server (and only your app server’s IP) can get access to this port. I don’t know enough about system administration to get dirty with real iptables conf files though, so I much prefer to install webmin which will give you a lovely interface for it.

You want to be setting up rules which look like this:

  • Source address: [Your app’s IP address]
  • Source port: 3306

And then the defaults are largely good enough. Let me know in the comments if there are even more things that I could lock down – I think have the IP address locked to one I’m expecting should be safe enough though.

Once you’ve saved and applied those new rules, you may be able to telnet to your MySQL server now. You’ll see what definitely looks like a MySQL prompt.

If not, there’s another debug tool you can use: tshark. I’ve found this to be super helpful when trying to track down malicious looking traffic I had one time on a server of mine. In this case though, you can run it on your MySQL server and see if the server is even spotting the telnet request.

tshark -ta -n port 3306

This’ll show you data being sent to that port. Try and telnet again, you should see some traffic. If not, your iptables rules are wrong, or you’re mistaken about your IP address.

If all is going well though, you should see the traffic from your telnet request.

This is where I got stuck for a little while, but eventually found that MySQL doesn’t listen to the wider network – only internal network comms. You can fix this in your my.cnf file (likely /etc/mysql/my.cnf):

bind-address            =

Restart MySQL, and you should be able to access it all you need.