** Description changed:
euca-get-console-output does not provide all of a console's output.
To reproduce this behavior, run an instance that executes user-data as a
script (ie, the uec-images), like this:
- $ cat user-data-loop.sh
+ $ cat user-data-loop.sh
#!/bin/bash
max=5000;
sleep_often=50
sleep=.2
for((i=0;i<${max};i++)); do
- echo "hello, number ${i}"
- [ $((${i}%${sleep_often})) -eq 0 ] && sleep ${sleep}
+ echo "hello, number ${i}"
+ [ $((${i}%${sleep_often})) -eq 0 ] && sleep ${sleep}
done
$ euca-run-instances --user-data-file=user-data-loop.sh --key mykey \
- --instance-type=m1.small emi-abcdefgh
+ --instance-type=m1.small emi-abcdefgh
# wait
$ time euca-get-console-output i-4537075F | tail -n 5
hello, number 2454
hello, number 2455
hello, number 2456
hello, number 2457
hello, number 2458
real 5m9.557s
user 0m0.130s
sys 0m0.050s
If I ssh to the node controller, and look at
/var/lib/eucalyptus/instances/admin/i-4537075F/console.log I see that
the count went all the way to 4999.
Note, I've waited minutes after the VM wrote the data before getting
console output, it doesn't seem like just a (resonable) caching issue.
Also note, that the get-console-output takes an extremely long amount of
time (minutes).
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: eucalyptus-common 1.6.2-0ubuntu30
ProcVersionSignature: Ubuntu 2.6.32-21.31-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-server x86_64
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="cluster1"
Architecture: amd64
Date: Mon Apr 19 11:47:55 2010
ProcEnviron:
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: eucalyptus
+
+ ======
+ IMPACT:
+ * This bug affects mostly people trying to debug a UEC instance which is not
behaving (or starting) properly. If verbose logging is turned on on something
like upstart at init, the 64k limit in eucalyptus' euca-get-console buffer will
easily overflow.
+
+ ADDRESSED:
+ * This bug is addressed by cherry-picking a patch from the upstream stable
release branch.
+
+ REPRODUCE:
+ * To reproduce this issue, turn on verbose upstart logging in an image,
register it, and run it. Then, run euca-get-console against the instance id.
You should on see the first 64K of data.
+
+ REGRESSION POTENTIAL:
+ * The chances for regression are relatively low. Perhaps the console output
not not be correct, or might be less.
+ ======
--
[SRU] euca-get-console-output gives first 64k of output, not most recent
https://bugs.launchpad.net/bugs/566793
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
