Following up to the article written yesterday you will likely have also received this error if you also received the error regarding the apt-mirror.lock file when attempting to mirror a repository on Ubuntu Linux using apt-mirror. The current error relates to the fact that a skel directory does not exist in the root directory of the repo you are attempting to create. Below the error is described in more detail as well as instructions for fixing it by creating the skel directory.
When setting up your own repository on Ubuntu Linux using apt-mirror you may run into an error letting you know that the apt-mirror.lock file could not be created. This is likely because a var directory does not already exist in the root of the repository you are creating. Use the information below to create the var directory and resolve the apt-mirror.lock problem.
After upgrading the Fast Secure Contact Form plugin for WordPress you should definitely test to make sure things are working properly because you likely will receive an error when submitting the contact form if you are using the built in captcha. The error which is explained in more detail complains of not being able to read a token file. Below we describe how to quickly resolve the Fast Secure Contact Form captcha error.
Recently received a 1U IPSU NetGate ALIX Single to perform some testing with pfSense on this type of platform. I was looking for a way to track the device and hoping to use DMI information so needed to first install dmidecode. Anyhow ran into a couple issues which are noted below along with resolutions for those issues.
Having trouble logging into an AWS instance using an SSH key? I was too and when I finally figured out what the issue was I was kicking myself. Recently I was called to assist figuring out information about a clients AWS deployment for a project where the original developers were no longer available or answering questions. Most of the instances that I initially worked on had no issues once I was able to obtain the correct SSH key pem file from Amazon. When the project was closing down I was asked to assist backing things up and it appeared the SSH key was failing for two of the instances which also happened to be the oldest two instances (2 years old). Below I describe the error I was seeing via SSH as well as the easy resolution to the problem.