Hi Eiji, > 192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET > /client/api?command=listCapabilities&response=json&sessionkey=null&_= > 1561961364158 HTTP/1.1" 401 101
This happens before login and is ok. I see that too when I open the login page without an active session. > ==> /var/log/cloudstack/management/access_log.2019-07-01.txt <== > 192.168.122.1 - - [01/Jul/2019:06:13:10 +0900] "POST /client/api > HTTP/1.1" 200 321 This is the actual login call, and returns status 200 (success). > 192.168.122.1 - - [01/Jul/2019:06:13:10 +0900] "GET > /client/api?command=listCapabilities&response=json&sessionkey=h1Lwsk9 > dqVwZxGAwk0owzFDtmi4%3D&_=1561961591972 HTTP/1.1" 432 151 This happens just after login and indicates something is wrong. It might not help much, but can you post the JSON body of the response? > 2019-07-01 06:13:10,963 DEBUG [cloud.api.ApiServlet] (catalina- > exec-22:null) ===START=== 192.168.122.1 -- > GET command=listCapabilities&response=json&sessionkey=h1Lwsk9dqVwZxG > Awk0owzFDtmi4%3D&_=1561961591972 > 2019-07-01 06:13:10,976 DEBUG [cloud.api.ApiServer] (catalina- > exec-22:null) The given command:listCapabilities does not exist or it > is not available for user with id:2 > > ==> /var/log/cloudstack/management/apilog.log <== > 2019-07-01 06:13:10,979 INFO [cloud.api.ApiServer] (catalina- > exec-22:null) 192.168.122.1 -- GET > command=listCapabilities&response=json&sessionkey=h1Lwsk9dqVwZxGAwk0o > wzFDtmi4%3D&_=1561961591972 432 The given command does not exist or > it is not available for user These log messages relate to the failing listCapabilities call after login. I think you should focus on these. Regards, Gregor
