As noted in previous articles my laptops Windows 7 Ultimate x64 operating system install became corrupted after I attempted to install the Windows 7 Service Pack 1 update. I believe the issue was related to some sort of software conflict so not necessarily all SP1’s fault though you would think there would be some form of error checking involved in the install. I waited out the upgrade for over 8 hours but in the end it still failed out. Anyhow during the process of reinstalling Windows 7 x64 on my laptop and installing all of the applications that were installed previously I wanted to restore my Trillian chat history for all of the various Trillian Connections. Below I describe what connections were configured and what Trillian Connections chat logs were restored.
git: Error: Some Local Refs Could Not Be Updated; Try Running ‘git remote prune origin’ To Remove Any Old, Conflicting Branches
Lately I have been working on a Ruby project that has a bunch of different branches that various developers are working on. One of the development servers has multiple virtual hosts and at certain points in the code release cycle the various virtual hosts could be completely split from the main branch of Ruby code either because of a bug fix, a specific feature, or any number of other reasons. The other night I needed to bring one of the virtual hosts to a near production release to test some features of a product that uses the web application to record data and when I attempted to “git pull” I received an error which is described in detail below along with what I ended up doing to resolve the problem.
Most of the logging options for LiteSpeed web server are very basic and general however I wanted to detail them to help others make educated decisions when it comes to the logging configuration. There is one option I use outside of the normal log configurations which is configured in a tab other than the log tab under server configuration. Below I will explain all of the configuration options and provide examples of what I recommend for LiteSpeed.
The very first thing I do when configuring a new server is to modify the “Disable Initial Log Rotation” option from “Not Set” to Yes. The purpose of this option is to make the lsws log file directory a bit more manageable. The Disable Initial Log Rotation option will stop the error.log file from being rotated every time the server is restarted. If you are on a development server this might happen numerous times a day thus creating a mess in your log directory. Instead I only rotate the error.log file based on size as described in detail below.
Recently I configured a virtual host in Litespeed outside of the normal Virtual Host Template I use. Typically I use the EasyRailsWithSuEXEC but this time I needed to use the PHP_SuEXEC template. It was easy as most configurations are with the LiteSpeed however when I performed a graceful restart I noticed that the virtual host I had just configured was showing “Restart Required” instead of “Running” as shown in the image below.
Here are the ones I tried. Hope the comments aren’t too confusing
- Simple Rails Log Query Analyzer
ruby bin/query_log_analyzer.rb ../log/production.log
production.log.1 (small log file ~25MB)Just printed the “Totals” heading with no results
production.log (large log file ~400MB)Ran for a long time and nothing happened