> Part 2: how do I work out what that failure was (and fix it)? > Looking in the backend log is a good place to start. Where that is will depend on your distribution.