FYI juju deployment used amd64 images; my manual test inadvertently
used the i386 image. I re-confirmed manual apt pkg install with an
amd64 vivid image.
Adding system user `rabbitmq' (UID 111) ...
Adding new user `rabbitmq' (UID 111) with group `rabbitmq' ...
Not creating home directory `/var/lib/rabbitmq'.
* Starting message broker rabbitmq-server
...done.
Processing triggers for libc-bin (2.19-13ubuntu3) ...
Processing triggers for ureadahead (0.100.0-17) ...
ubuntu@vivid181213:~$ apt-cache policy rabbitmq-server
rabbitmq-server:
Installed: 3.4.3-2
Candidate: 3.4.3-2
Version table:
*** 3.4.3-2 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ vivid/main amd64
Packages
100 /var/lib/dpkg/status
ubuntu@vivid181213:~$
** Also affects: rabbitmq-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1417205
Title:
cannot access '/var/lib/rabbitmq': No such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1417205/+subscriptions
--
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
