Known Eucalyptus Bugs (1.0)
- Some EC2 command-line utilities will return a 'Read error' to the user, regardless of the actual internal error
- what you should do: try the command again
- There is a condition where eucalyptus instances are started, but the system loses track of their existence.
- what you should do: when users are done using their instances, the admin can forcefully shutdown ALL running instances by running '/opt/eucalyptus-1.0/usr/sbin/euca killall'
- Rarely, an instance will appear to be running even though the actual VM has been terminated
- what you should do: when users are done using their instances, forcefully shutdown all instances and restart eucalyptus on the front-end
- Restarting eucalyptus while instances are running will result in those instances being unknown to the eucalyptus system
- what you should do: when users are done using their instances, forcefully shutdown all instances and restart eucalyptus on the front-end
- Rarely, eucalyptus processes may be left running even after the init script has finished stopping the system (eucalyptus stop).
- what you should do: search for eucalyptus processes and kill them manually (anything process with the string 'euca' contained in the commandline)
- Our log-files can grow rather large (we estimate several hundred megabytes per week).
- what you should do: stop eucalyptus, remove or back up the log files (/opt/eucalyptus-1.0/var/log/eucalyptus/*), and restart eucalyptus
