Hello,
I got a similar issue and solved it by disabling IPv6 under main host so
lxc containers could communicate through IPv4 and access to external world.
I haven't yet understand the issue but it sounds like if the main host
is IPv6 enabled, then system tries to communicat through IPv6 even
though IPv4 addresses are the only one configured.
If anyone get an idea let me know.
If you think that needs a bug let Jake or me know (at least) as we get
concerned with the issue
Thanks
Thierry
On 03/02/2015 04:03 PM, Dimiter Naydenov wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Jake,
Thanks for the logs! However, I still can't find the reason this
should be happening just from those logs. Can you also send us the
unit logs from wordpress and mysql? A dump of "ifconfig -a" on each of
the machines should also be useful.
Regards,
Dimiter
On 28.02.2015 00:42, Jake Kugel wrote:
Hi Dimiter,
thanks, here are the files:
Jake
[email protected] wrote on 02/27/2015 02:58:01 PM:
From: Dimiter Naydenov <[email protected]> To:
[email protected] Date: 02/27/2015 02:58 PM Subject: Re:
unit-get and ipv6 addresses Sent by:
[email protected]
Hi Jake,
Can you provide some more information: - your environments.yaml
file - machine-0.log, machine-1.log, and machine-2.log from
/var/log/juju/ on each machine Before sending these, please make a
quick check to remove any sensitive info from the files (e.g.
access/secret keys, password, etc.)
You can get the logs by using "juju ssh 0" (or 1 and 2 for the
other machines) to connect, run chown a+r
/var/log/juju/machine*.log, then log back out and use "juju scp
0:/var/log/juju/machine-0.log ~/" (again replace 0 with 1 or 2).
Thanks! Dimiter
On 27.02.2015 22:19, Jake Kugel wrote:
Hi,
I am using juju 1.21.1-trusty-i386 and deploying to a manual
environment, and had a problem deploying wordpress following
the getting started page here [1]. When I tried to view
wordpress with a browser it gave me an "Error establishing a
database connection", and from a little bit of digging found
that wordpress was configured with an ipv6 address for the
mysql host. Switching this manually to the ipv4 address
fixed the problem.
Assuming for a minute that wordpress doesn't support ipv6, is
there a way to avoid having it configured with an ipv6
address? I see that unit-get private-address is returning
the ipv6 address for the mysql host, is that normal behavior?
On the mysql host machine log, I see this:
2015-02-27 14:56:59 INFO juju.worker.machiner machiner.go:94
setting addresses for machine-2 to ["local-machine:127.0.0.1"
"public:9.114.192.29" "local-machine:::1"
"local-cloud:fd55:faaf:e1ab:38d:944a:7931:9b4c:c621"
"local-cloud:fd55:faaf:e1ab:38d:a8c0:f5da:7109:1e67"
"local-cloud:fd55:faaf:e1ab:38d:f816:3eff:fee2:f0fc"]
Thanks in advance for any advice, Jake Kugel
[1] https://jujucharms.com/docs/getting-started
-- Juju mailing list [email protected] Modify settings or
unsubscribe at: https://lists.ubuntu.com/mailman/ listinfo/juju
- --
Dimiter Naydenov <[email protected]>
Juju Core Sapphire team <http://juju.ubuntu.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU9Hu9AAoJENzxV2TbLzHwha4H/0s+UUZr5Z2ov4TcjAIT93cb
I/JqHcpo1ynvOyGCv5/VD801RHnwDi+tWpoKJtUmgQ6PTV8iW78U7C55MgcXsTmz
PKh3Bl5O8IN2oVF3SbVD7jc8P70wtbucIVsml1lsb34TCgJFSA1rJ2R7SrnUMtiE
EXNg455jS84aDiJW+Lw8glXHB1X3f+Kv7jnKN2Bksza+z4T8+hxa7HLc8qCdozD7
MoEVLoJO/75LYVjYCMhqZhkqCUb5T8gvdVcb2zdIOnhk63A+G0FQSPUrvTps3cfv
iCmD1nXUyufFV5FB3ks9nwtlrGjpsAcbJJu0NCwJ9VCOQjxvGXjTYksJNUi8VbU=
=lBiY
-----END PGP SIGNATURE-----
--
Thierry Fauck @ linux.vnet.ibm
--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
