Earlier today I was troubleshooting NFS or Network File System issues on a Ubuntu Linux server and ran into some specific errors. Luckily the errors were easily resolved by restarting portmap on the server. Below I show the error output on the server end in more detail, how to resolve the issue, and testing the Network File System mount from OSX.
When attempting to create a new database on a PostgreSQL server running walmgr, which is part of SkyTools by Skype Developers, for real time failover I received an error. Initially I was a bit baffled by the error however I remembered after racking my brain for a little bit that you must stop walmgr’s syncdaemon when adding a new database. Below are more details about the error as well as how to stop walmgr’s syncdaemon and then create the new database.
I had a Redmine ticket I had been working on with our customer support team at work. After working through the initial ticket that was loosely related to a customer initially ended up being a larger issue and I decided to move the ticket to an engineering project as that is where I actively work tickets typically. When I attempted to move the ticket I received an error stating that it had failed to save. Below I describe what the issue ended up being and how I temporarily modified a setting so I could move the ticket.
The below error is another error related to upgrading Redmine. I imagine part of the reason I had a lot of errors is because I hadn’t upgraded this installation of Redmine, which we really just use for development, for a long time. In fact the upgrade took this installation of Redmine from 0.8.3 to Redmine 0.9.3. After I completed all of the steps in the Redmine upgrade I attempted to bring up the Redmine site in my Chrome browser but I received a 500 error from the LiteSpeed web server. The resolution was easy and is displayed below along with more details regarding the error.