Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of ian@ianduffy.ie designates
 209.85.216.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A9E488C@FRSPX100.fr01.awl.atosorigin.net>
References: 
 <C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A9E488C@FRSPX100.fr01.awl.atosorigin.net>
Date: Mon, 20 Oct 2014 09:17:25 +0100
Message-ID: 
 <CAEJ3w4UWJfK3a_b=pDwF1FnpLAu_UjXjV9SfkAOzTbL=2b33=Q@mail.gmail.com>
Subject: Re: Cloudstack 4.3.0 UI impossible login problem : browsers hang
From: Ian Duffy <ian@ianduffy.ie>
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3d4024a2d910505d65807

--001a11c3d4024a2d910505d65807
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Jean-Francois,

What browser are you experiencing this issue with?

Can you try using firefox, it is the primary one the UI team use for
testing.

Thanks,
Ian

On 17 October 2014 08:51, Vincent Jean-Fran=C3=A7ois <
Jean-Francois.Vincent@worldline.com> wrote:

>
> Hello,
>
> Configuration : Cloudstack 4.3.0. with two management servers (named 1 an=
d
> 2) behind a LVS with a configured charge of 100/1 for server1/server2
> (direct routing)
>
> Since two days, we have a login problem on server 1. The login pages load
> correctly. But after typing the correct password (local or LDAP one) the
> browser hangs.
> The first occurrence, two days ago. We restart the management server and
> the problem went away. Today, we cannot anymore use the server 1 and we
> have to user the server 2.
> Both servers are to our knowledge identical. And no change neither have
> been done on the infrastructure configuration.
>
> Is anybody here has experienced a such problem or have any clue ?
>
> The server ran for many weeks without any outage like this until now.
>
> apilog.log when we have recurring events :
> 2014-10-17 09:05:44,446 INFO  [a.c.c.a.ApiServer]
> (http-6443-exec-442:ctx-8a23b456)  10.26.238.65 -- GET
> command=3DlistCapabilities&response=3Djson&sessionkey=3Dnull&_=3D14135295=
44423 401
> unable to verify user credentials
> But we have also the same INFO message on the working server.
>
> Catalina.out :
>
> 2014-10-17 09:42:22,888 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-467:ctx-86fe168f) =3D=3D=3DSTART=3D=3D=3D  10.26.238.65 -=
- POST
> 2014-10-17 09:42:22,891 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-467:ctx-86fe168f) Attempting to log in user: jf in domain=
 1
> 2014-10-17 09:42:22,892 DEBUG [c.c.s.a.SHA256SaltedUserAuthenticator]
> (http-6443-exec-467:ctx-86fe168f) Retrieving user: jf
> 2014-10-17 09:42:22,900 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-467:ctx-86fe168f) User: jf in domain 1 has successfully
> logged in
>
> But browser's stucked...
>
>
> Thank you
>
>
> Jean-Francois
>
>
> Ce message et les pi=C3=A8ces jointes sont confidentiels et r=C3=A9serv=
=C3=A9s =C3=A0 l'usage
> exclusif de ses destinataires. Il peut =C3=A9galement =C3=AAtre prot=C3=
=A9g=C3=A9 par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> imm=C3=A9diatement l'exp=C3=A9diteur et de le d=C3=A9truire. L'int=C3=A9g=
rit=C3=A9 du message ne
> pouvant =C3=AAtre assur=C3=A9e sur Internet, la responsabilit=C3=A9 de Wo=
rldline ne pourra
> =C3=AAtre recherch=C3=A9e quant au contenu de ce message. Bien que les me=
illeurs
> efforts soient faits pour maintenir cette transmission exempte de tout
> virus, l'exp=C3=A9diteur ne donne aucune garantie =C3=A0 cet =C3=A9gard e=
t sa
> responsabilit=C3=A9 ne saurait =C3=AAtre recherch=C3=A9e pour tout dommag=
e r=C3=A9sultant d'un
> virus transmis.
>
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this
> e-mail in error, please notify the sender immediately and destroy it. As
> its integrity cannot be secured on the Internet, the Worldline liability
> cannot be triggered for the message content. Although the sender endeavou=
rs
> to maintain a computer virus-free network, the sender does not warrant th=
at
> this transmission is virus-free and will not be liable for any damages
> resulting from any virus transmitted.
>

--001a11c3d4024a2d910505d65807--