Storage Gateway Crashing with SIGILL on KVM

Question

I'm running a storage gateway as a KVM VM. Recently I noticed the console log stating that a filesystem was full. I booted the VM from a live CD image to investigate and I found that there were thousands of core files from the ganesha.nfsd process.

I loaded a few of the core files into GDB and they all were reporting that the process was killed by a SIGILL in sha256.c (Obviously I don't have sources, so I wasn't able to map the exact source)

The system log has several of these messages
```
traps: ganesha.nfsd[36846] trap invalid opcode ip: 7f14099ebe74 sp:7ffd9f728c00 error:0 in libk5crypto.so.3.1
```

It appears that something in a recent update has created binaries that my particular CPU doesn't support. I couldn't find any CPU requirements documented anywhere, so I can't determine if my somewhat ancient Opteron that this runs on should be expected to work or not.

Answer

This is a very unusual condition for a Storage Gateway. Please open a customer support ticket with the above information so that AWS can further diagnose the problem directly with this gateway.

Storage Gateway Crashing with SIGILL on KVM

Relevant content