I can create a snapshot using ElasticFox (Elasticfox does not show any errors and the snapshot shows up) though in the Cloud-debug.log file it shows what looks like errors.

My main problem is when I do an ec2.creatsnapshot using the right_aws library, I get:
[This wiki has such crappy support for entering code and html info such as this long url, you;ll have to hover over it to see it]

EBS snapshot operation failed: 500: Internal Server Error (http://arryn.runa.com:8773/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOW...)

I can successfully do other operations like create a volume using the right_aws gem. But the create snapshot is failing.
So I'm pretty sure that my right_aws ec2= Ec2.new is correct as the other calls are using the same Ec2.new initialization as shown here.

The call that is failing is effectively:

ec2 = RightAws::Ec2.new(aws_access_key, aws_secret_access_key, { :endpoint_url => 'http://arryn.runa.com:8773/services/Eucalyptus/' })
ec2.create_snapshot('vol-5F25064B')


The only error I see when I run the right_aws script is:

06:20:35 INFO [ServiceSinkHandler:ReplyQueue.8] :1279434035366:eucalyptus:uid:admin:c3265ac7-a5de-47e3-9d85-0737139c91ff:MSG_SERVIC\
ED:DescribeVolumesResponseType:23:
06:20:35 INFO [ServiceSinkHandler:ReplyQueue.8] :1279434035404:eucalyptus:uid:admin:13a2f111-5089-4329-a62e-0be3157f6daf:MSG_SERVIC\
ED:DescribeSnapshotsResponseType:14:
06:20:35 INFO [ServiceSinkHandler:ReplyQueue.8] :1279434035451:eucalyptus:uid:admin:850f2540-c2a5-4704-946d-fff86ed74b01:MSG_SERVIC\
ED:DescribeVolumesResponseType:26:
06:20:35 DEBUG [NioServerHandler:New I/O server worker #1-28] Internal Error.
java.lang.NullPointerException
at com.eucalyptus.ws.util.HmacUtils.makeV2SubjectString(HmacUtils.java:159)
at com.eucalyptus.ws.handlers.HmacV2Handler.incomingMessage(HmacV2Handler.java:153)
at com.eucalyptus.ws.handlers.MessageStackHandler.handleUpstream(MessageStackHandler.java:126)
at com.eucalyptus.ws.server.NioServerHandler.messageReceived(NioServerHandler.java:119)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:114)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:385)
at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:459)
at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:443)
at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:381)
at org.jboss.netty.handler.timeout.ReadTimeoutHandler.messageReceived(ReadTimeoutHandler.java:146)
at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:214)
at com.eucalyptus.ws.handlers.ChannelStateMonitor.messageReceived(ChannelStateMonitor.java:62)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:342)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:329)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:330)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:203)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:53)
at org.jboss.netty.handler.execution.MemoryAwareThreadPoolExecutor$MemoryAwareRunnable.run(MemoryAwareThreadPoolExecutor.jav\
a:502)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

(It repeats this several times which I presume is from the right_aws library doing retries)

Anyone have any idea? Is this a misconfiguration of my SC/CLC/CC? Or a misconfiguration of my right_aws initialization? Or something else?

Eucalyptus version: 1.6.2
Installed from UEC Lucid 10.04 CD
amd64
KVM
1 host doing CC, CLC, SC 4 hosts doing NC
Managed_no_vlan