Sunrise in Rift

I've been playing Rift a lot recently. I like the game. There is a lot to do, tons of options.. it's fun. While playing a new ranger, I happened to get these rather cool shots of the sunrise in Rift. Hope you like them too.

Rift Sunrise

Rift Sunrise

Rift Sunrise

ColdFusion 9 CentOS 6 Connector Issues

Just had an experience installing ColdFusion 9 on to a CentOS 6 system and ran into an issue installing the web connector. I'll step through the process I went through and maybe it will help others installing Adobe ColdFusion on to CentOS 6.

Right after the installation, I got the following error message:

Running apache connector wizard...
=======================================
There was an error while running the connector wizard
Connector installation was not successful
=======================================

This is the output of the cf-connectors.sh script, located here:

/opt/coldfusion9/bin/cf-connectors.sh

You can manually run that script and get the same error message. Looking at the script, I saw I kept a log of it's issues in the following file:

/opt/coldfusion9/ConnectorInstall0.txt
SELinux Penguin Logo

So I naturally checked it out. The first error I got had to do with Apache APXS not being installed. Again, my CentOS 6 install was a "minimal" install, so I was used to installing additional packages to get things to work properly. To address this issue, I just ran the following:

yum -y install httpd-devel

Then ran the cf-connectors.sh file again, and ran into a different issue this time. This one was more peculiar:

Starting httpd: httpd: Syntax error on line 892 of /etc/httpd/conf/httpd.conf: Cannot load /opt/coldfusion9/runtime/lib/wsconfig/1/mod_jrun22.so into server: /opt/coldfusion9/runtime/lib/wsconfig/1/mod_jrun22.so: failed to map segment from shared object: Permission denied

That's odd... I'm running as "root", I shouldn't be getting permission issues. As it turns out, this error is due to SELinux being enabled. However, I an not at liberty to disable SELinux for this particular project, so I had to find a different way. Turns out, the fix just ended up being a simple one-liner to adjust the SELinux config:

chcon --reference=/usr/sbin/httpd /opt/coldfusion9/runtime/lib/wsconfig/1/mod_jrun22.so

After that, Apache started right up and my SELinux rules are still happily in place!

Hope this helps.

Utdream - Neutron

Another attempt by me to make a piece that's a bit more energetic. I was trying for something that would make you tap your foot or nod your head while listening.

 

How To Fix Windows Java Error 1723

Just recently I experienced a problem with both installing or uninstalling Java (the JRE) on a Windows 2003 system. I had to research this quite a bit and there were no clear answers anywhere, so I though I'd post here on how I was able to fix it. In my case, I was using Windows Server 2003 64-bit, but this should apply to other Windows versions as well.

Windows JRE Error 1723The error I was getting was as follows:

"Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor."

This error is caused when you delete the JRE directory without running the uninstallation program. The reason this causes a problem is due to the registry entries that the installer creates when the JRE is installed. There is a DLL that the installer uses to make (and remove during an uninstall) the registry entries. Without this DLL, both the install and the uninstall will fail. This error may also prevent you from installing updated versions of the JRE to your system - which is a security risk.

You can find the path to the DLL that the installer (or uninstaller) is looking for in your Application log. You can get to your Application log (at least on a Windows Server 2003 system) by going to Start - Administrative Tools - Event Viewer, and then selecting Application from the list on the left.

Once you're looking at the Application log, find the error message generated from the "MSI Installer" (It's probably the most recent error there if you just encountered the error.) and bring it up. In the "Description" text area, you should be able to see where the installer or uninstaller was looking for the DLL file it needs. This is important because it will tell you how to fix it.

Finding the DLL

The FIX:

The Fix for this is to give the uninstaller what it wants, and replace the deleted DLL files with ones that can be used by the install/uninstall process to edit the registry, etc. For convenience, I've uploaded a bin zip file that can be used for this purpose.

DOWNLOAD: => bin.zip  (md5: b2594fa66d12a9e8fafb0a1ba3ca555f)

In my case above, you can see where I installed the JRE to the desktop (and then probably deleted it to remove the clutter). Only later, when I tried to install a new version, did it become a problem. So, I downloaded the above zip file, extracted it to my desktop, created a "jdk" directory and moved the "bin" folder inside it, then ran the uninstaller again. I got a few more errors about other files that couldn't be found, but the uninstaller worked and I was able to install an updated version like I wanted to afterwards.

So... the next time you install the JRE or JDK, remember that you can't delete it by hand without problems!

Hope this helps!

-Jordan

mod_cfml graphic

I'm working on the mod_cfml site and while playing with Photoshop and working up graphics for it, I made the following. I really like it! Hope you do too.

mod_cfml logo

impediments