No such file or directory (2) in recov_svr_attr, Unable to read server database

The cause of this is failure to run the torque.setup file durring installation

cd /tmp/torque

./torque.setup <someuser>

This is located under section 1.2 of the torque documentation (as of torque 4.0.2)

http://www.adaptivecomputing.com/resources/docs/torque/4-0-2/help.htm#topics/1-installConfig/initializeConfigOnServer.htm

 

moab: error while loading shared libraries: libtorque.so.2: cannot open shared object file: No such file or directory

The way to fix this issue is as follows:

echo ‘/opt/moab/lib’ > /etc/ld.so.conf.d/moab.conf

echo ‘/usr/local/lib’ > /etc/ld.so.conf.d/torque.conf

Then run the command

ldconfig

The reason why this happens is that either moab or torque cant find the location of the libraries.

configure: error: TORQUE needs lib ssl in order to build

The following error will occur while trying to compile torque if the development library for Openssl is missing.

 

configure: error: TORQUE needs lib ssl in order to build

 

Solution:

 Redhat / Fedora 

yum install openssl-devel

Debian / Ubuntu

apt-get install libssl-dev

visudo: no editor found(editor path = /usr/bin)

On a out of the box install of Fedora 16 with KDE, attempting to run visudo results in an error.

visudo: no editor found (editor path = /usr/bin/)


Solution 1: Create symbolic link

ln -s /bin/vi /usr/bin/vi




Solution 2: Create default editor

Change to root user, and manually edit sudoers file
sudo su -

nano /etc/sudoers

insert lines

Defaults env_editor,editor=/usr/bin/vi:/usr/bin/nano:/usr/bin/vim

This will use the system variable $env_editor, if it doesn’t exist it will use vi or nano or vim

Hard Drive Upgrade

My macbook pro came with a tiny 320 gig hard drive. That simply won’t do. Introduce my brand new out of the bag 750 western digital black hard drive. Why western digital black? They are the fastest baddest drives around, that’s why.

I opened the bag and started inspecting it. I noticed something funny on the bottom of the circuit board. Corrosion!

Notice the blue tint.

This had me worried. Arduino recently had a similar quality control problem. I did not want my brand new super fast drive to have issues.

I plugged the 750 into an external enclosure, and tried to copy the data. Thats when the errors really started.

My cd rom drive was removed so I could cram in a solid state drive

I got a strange error that I have never seen before.

I simply formatted the drive, and didn’t worry about it.

I opened my favorite copying software “Carbon Copy Cloner” . Again, I got another error. This isn’t looking good

By this point I was afraid that the drive might have been bad. I gave it a scan with disk warrior. More errors.

Another strange error.

Great! I am defiantly thinking this drive is bad. I really don’t want to have to wait for a replacement.

I heard about a program called Drive Genius. Their software is fantastic. Unfortunately It wasn’t happy either.

Ok time for one last effort. Format it again. What’s this? The drive is now a 2.2 tb drive!!??? Great. I am finally getting past the denial and accepting that this drive could be bad.

Ok time for one last effort before I send the drive back. I borrow my roomate’s agonizingly slow sata to usb adaptor.

SUCCESS!!!!! It worked without a single issue.
The entire drive copied error free.
        I copied some files back and forth, ran a disk integrity check and made sure that it wasn’t a fluke. The USB to Sata adaptor I was using must have had issues. Strange that I could use any other hard drive without incident. Even stranger was that the errors I was getting were at random times throughout the transfer process.

Here is my theory as to why.

The enclosure that I was using was made before the advanced format drives came out. (if you are unfamiliar with Advanced Format, check out this link here). Basically many new drives are using 4000 byte sectors opposed the the traditional 512 byte sectors we have been using since the floppy era.
My old usb to sata drive appeared to work perfectly for a short while before giving random errors.

The apparent corrosion had nothing to do with the errors I was receiving.

Hopefully this helps someone else running into similar problems.

One last step I did was change my icons to a picture of the actual drives.

Update: My drive has been running great for several months now. I would defiantly recommend this drive to a friend as long as they have a high quality sata to usb adaptor to transfer data.

Macbook Pro Left Audio Issue

I got my new unibody macbook pro 15 inch a few weeks ago and it is AWESOME! I was sitting on my couch watching some hulu when I noticed that the sound didn’t seem quite right, It sounded like the audio was coming out of the right speaker louder than the left. I stopped what I was doing and checked the system preferences to see if the balance was off. It was fine, I restarted the computer and tried watching hulu again. The problem was still there. An extensive search on the internet revealed that it is a ‘feature’ not a problem. The reason is that there are 3 speakers in the macbook pro; A Left, Right and “Subwoofer”. Unfortunately the subwoofer had to be placed on the right side by the DVD rom drive for space issues, which results in the right speaker sounding louder than the left.

Photo credit iFixit.com

Left Speaker

Right Speaker and Subwoofer

If you have noticed this issue with the macbook pro’s sound, you are obviously just more observant then the typical mac user. There is nothing wrong with your laptop, continue on as you were.

Windows 7 Install error

If you get an error “Windows is unable to install to the selected location. Error: 0x80300024” while you are installing windows 7, here is why.

1. You are installing to a non NTFS drive. Most likely the drive was formatted as Mac GUID or Linux EFS

Possible Solutions:

1. Disconnect all other drives except the one you want to install to.

1. Format the drive in another windows computer, (for some reason, mac won’t format it correctly, I tried).

1. If you can’t physically remove the drive, do a FIXMBR command from the install cd.

If you are still having problems, chances are that the drive is on the fritz