Scott - I agree with Eric that setting the hostname and persisting it is
critical for many packages. Varnish is another one that expects to find
a directory called: /var/lib/varnish/<hostname>/
After rebooting the EC2 instance, Varnish fails to start up with this
error message:
$ sudo /etc/init.d/varnish restart
* Stopping HTTP accelerator
...fail!
* Starting HTTP accelerator
...fail!
Error: (-sfile) "/var/lib/varnish/domU-12-31-39-00-20-C2/varnish_storage.bin"
does not exist and could not be created
$ hostname
domU-12-31-39-00-20-C2
$ ls /var/lib/varnish/
domU-12-31-38-04-E1-A2
As you can see the hostname changed after reboot, so Varnish can no
longer find the directory, as it uses "uname -n" to determine what
directory to look in.
from /etc/default/varnish:
INSTANCE=$(uname -n)
DAEMON_OPTS="-a :6081 \
-T localhost:6082 \
-f /etc/varnish/default.vcl \
-s file,/var/lib/varnish/$INSTANCE/varnish_storage.bin,1G"
any chance that you will fix this for Karmic, as you have already done
for Lucid?
--
hostname modifications user are overwritten by ec2init
https://bugs.launchpad.net/bugs/514492
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
