You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2017-08-01 22:02:00 ERROR | failed to parse XML document /var/lib/eucalyptus/instances/work/AIDAANVOU6GS6SFPFKX5Z/i-8334c266/instance.xml
and in the httpd-node_error_log:
/var/lib/eucalyptus/instances/work/AIDAANVOU6GS6SFPFKX5Z/i-8334c266/instance.xml:120: parser error : Extra content at the end of the document
i-ef93031f</id>
^
These example errors are not from the same occurrence of the the issue as the example instance.xml files.
To reproduce the issue you can churn 8 instances on a node controller and capture all instance.xml files using (for example):
# mkdir -p /tmp/instancexmls; inotifywait -m -r -e close_write /var/lib/eucalyptus/instances/work/ | while read path action file; do if [ "$file" == "instance.xml" ]; then MD5SUM=$(md5sum $path$file | awk '{print $1}'); INSTANCE=$(echo $path | awk -F/ '{print $(NF-1)}'); if [ ! -f "/tmp/instancexmls/$INSTANCE-$MD5SUM-instance.xml" ]; then cp -v $path$file /tmp/instancexmls/$INSTANCE-$MD5SUM-instance.xml; fi; fi; done
which will create a copy for each unique instance xml that is output. Valid instance xml files are typically 6xxx bytes, invalid files 9xxx bytes.
The invalid instance xml file in a churn test occur on launch or termination of an instance when the file can be updated by separate threads concurrently.
This issue does not always cause errors, the invalid files may be overwritten before they are read.
The text was updated successfully, but these errors were encountered:
Issue copied from JIRA https://eucalyptus.atlassian.net/browse/EUCA-13444
The node controller can output invalid instance.xml files when separate threads attempt concurrent updates.
An example is this sequence of writes to an instance.xml file when an instance is launched:
Pending/0.0.0.0:
Pending/10.111.30.100:
Extant/Booting (invalid):
Extant/Running:
The invalid file contains:
which can lead to errors in the nc.log such as:
and in the httpd-node_error_log:
These example errors are not from the same occurrence of the the issue as the example instance.xml files.
To reproduce the issue you can churn 8 instances on a node controller and capture all instance.xml files using (for example):
which will create a copy for each unique instance xml that is output. Valid instance xml files are typically 6xxx bytes, invalid files 9xxx bytes.
The invalid instance xml file in a churn test occur on launch or termination of an instance when the file can be updated by separate threads concurrently.
This issue does not always cause errors, the invalid files may be overwritten before they are read.
The text was updated successfully, but these errors were encountered: