Archive for August, 2010

Looking for: “java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildListener”

Saturday, August 28th, 2010

When trying to put together a jar file on Ubuntu Lucid with gant, I got this:

java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildListener
        at java.lang.Class.getDeclaredMethods0(Native Method)
        at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
        at java.lang.Class.getMethod0(Class.java:2670)
        at java.lang.Class.getMethod(Class.java:1603)
        at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java                  :99)
        at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:130)
Caused by: java.lang.ClassNotFoundException: org.apache.tools.ant.BuildListener
        at org.codehaus.groovy.tools.RootLoader.findClass(RootLoader.java:156)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at org.codehaus.groovy.tools.RootLoader.loadClass(RootLoader.java:128)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        ... 6 more

After also installing the ant package everything worked fine…

Canon Err 01 – fixed itself

Monday, August 16th, 2010

Last week I went out and took my 550D with me to take some pictures. Unfortunately when I switched it on and tried to taka a pic it gave me this:

Err 01: Communications between camera and lens is faulty. Clean the lens contacts.

Just to be sure I had a look but as clean as it can be – I only have the 15-85 EF-S so I never fiddle with lenses.

A colleague of mine brought his 450D with 50 EF lens to the office. After putting on the 50 mm lens my 550D would still give me the Err 01. So it was clearly an issue with the camera and not the 15-85. After putting the 15-85 back on, everything started worked again like nothing had happened.

This behaviour demonstrates that the Err 01 issue is likely to be caused by some software problem, static electricity or something similar.

The camera had been working fine for a whole month in the US, however this was the first time after I was there that I used it again. I’m guessing the electronics might have had a glitch either on the airport during X-ray scanning, or during transatlantic flight…

Anyway, problem solved (for now) ;-)

Make iscsitarget listen on specific address

Friday, August 13th, 2010

I set up iscsitarget on one of my Ubuntu Lucid boxes and it seemed to work. I let one of my VMware ESX hosts scan it, and it sure enough found my LUN, but via two paths.

Turned out that because the host running iscsitarget has two NICs, the ESX host sees two paths. Not exactly what I wanted, because one NIC sits on the internet, the other on the dedicated iSCSI network.

Unfortunately it is not possible to configure ietd to listen to a specific address by editing any of the configuration files (/etc/default/iscsitarget and /etc/ietd.conf), you have to hack the init script to be able to do this…

Edit /etc/init.d/iscsitarget and go to the function ietd_start(), then change this line:

start-stop-daemon --start --exec $DAEMON --quiet --oknodo

to:

start-stop-daemon --start --exec $DAEMON --quiet --oknodo -- --address 10.10.1.1

(or whatever IP you want to have it listen to).