I was going through and cleaning up some plugin settings recently on a WordPress site and received an error when attempting to access Feed Comments Number admin settings page. The error states that you do not have sufficient permissions to access the page though that was not the case because I was logged in as an administrator. Luckily I had run into this exact error awhile back and knew exactly where the problem was. Below I describe the error in more detail and provide resolution to the issue.
Recently I was looking to obtain a couple specific DNS record ID’s for domains with DNS hosted in the RackSpace Cloud so I could use the information to interact with RackSpace Instances through RightScale. Various RightScale ServerTemplates such as the MySQL Cluster ServerTemplates require you to enter the exact DNS record ID as RightScale Inputs for the ServerTemplate. I am not sure why the record ID’s are not listed in a column in the RackSpace Cloud DNS management interface but regardless the below method of querying the RackSpace API make it fairly easy to obtain them regardless.
The default logins are noted in the pfSense documentation as well as numerous locations on the pfSense website however I am noting here for our own benefit. We try to remember so many default logins that we sometimes forget the easiest ones including the fact that pfSense uses a different username as default for SSH and for the pfSense admin GUI. So to make it easiest to find I have noted them below.
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.