AppScale deployment stuck at Starting state

27 views
Skip to first unread message

sh...@cloudypedia.com

unread,
Sep 20, 2018, 12:01:51 PM9/20/18
to AppScale Community
My application runs perfectly in Google App Engine itself but Appscale cannot run it.

----------------------------------------------------------------------------
root@node1234-appscale:~# appscale status
----------------------------------------------------------------------------

AppScale is starting: 1 of 1 nodes are initialized, 1 of 1 nodes are loaded, 1 of 2 services are started

PROJECT ID         SERVICE ID    HTTP/HTTPS    APPSERVERS/PENDING    REQS. ENQUEUED/TOTAL    STATE
appscaledashboard  default       1080/1443     1/0                   0/1194                  Ready
gaeapp                     default       8080/4380     0/1                   0/0                     Starting

As soon as AppScale Dashboard is started you can visit it at http://12.345.6.7:1080/status and see more about your deployment

----------------------------------------------------------------------------

Here's another problem although `appscaledashboard` has started with the Ready state after running `appscale status` after a few minutes it is back in Starting state, is this a bug?
Anyway, my problem is the gaeapp described here is stuck at 'Starting' state what could be wrong with Appscale where it can't run the same app that runs in GAE cloud itself, only modification made was to app.yaml file, inbound_services: - mail_bounce was removed as it is not supported.

Running appscale tail shows the following:
[2018-09-20T15:58:00.475788 #1295]  INFO -- : Reloading nginx service.
W, [2018-09-20T15:58:00.738499 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
I, [2018-09-20T15:58:01.663213 #1295]  INFO -- : Received request to get properties matching login.
I, [2018-09-20T15:58:01.754597 #1295]  INFO -- : Received request to get properties matching login.
W, [2018-09-20T15:58:10.417868 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
W, [2018-09-20T15:58:10.417967 #1295]  WARN -- : Didn't see any request data - not sure whether to scale up or down.
W, [2018-09-20T15:58:10.673805 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
I, [2018-09-20T15:58:10.680797 #1295]  INFO -- : Reloading nginx service.
W, [2018-09-20T15:58:10.988899 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
W, [2018-09-20T15:58:20.641198 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
W, [2018-09-20T15:58:20.641300 #1295]  WARN -- : Didn't see any request data - not sure whether to scale up or down.
W, [2018-09-20T15:58:20.854253 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
I, [2018-09-20T15:58:20.859888 #1295]  INFO -- : Reloading nginx service.
W, [2018-09-20T15:58:21.140838 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
W, [2018-09-20T15:58:30.583200 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
W, [2018-09-20T15:58:30.583301 #1295]  WARN -- : Didn't see any request data - not sure whether to scale up or down.
W, [2018-09-20T15:58:30.788564 #1295]  WARN -- : Couldn't get proxy stats from Hermes: Proxy gae_pythonmysqlapp_default_v1 was not found at 12.345.6.7
I, [2018-09-20T15:58:30.794031 #1295]  INFO -- : Reloading nginx service.




Chris Donati

unread,
Sep 20, 2018, 2:04:58 PM9/20/18
to appscale_...@googlegroups.com
This issue was resolved over IRC. For anyone that's having the same problem on a pre-3.6 deployment, we resolved the issue by downgrading monit with `apt-get install monit=1:5.16-2` and then held the package with `apt-mark hold monit`.

--
You received this message because you are subscribed to the Google Groups "AppScale Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appscale_commun...@googlegroups.com.
To post to this group, send email to appscale_...@googlegroups.com.
Visit this group at https://groups.google.com/group/appscale_community.
For more options, visit https://groups.google.com/d/optout.

linkin xiao

unread,
Sep 26, 2019, 5:54:41 AM9/26/19
to AppScale Community
I meet the same problem, but didn't soloved the problem by holding monit.  Do you solve the problem?
To unsubscribe from this group and stop receiving emails from it, send an email to appscale_community+unsub...@googlegroups.com.

Chris Donati

unread,
Sep 26, 2019, 1:57:12 PM9/26/19
to appscale_...@googlegroups.com
The problem that was originally reported was resolved in the 3.6 release. The latest AppScale release is 3.8, so it is unlikely that monit is the culprit.

Could you provide some more details about the problem you are seeing? What version of AppScale are you using? Did `appscale up` complete successfully? Did `appscale deploy <your-app>` complete successfully?

To unsubscribe from this group and stop receiving emails from it, send an email to appscale_commun...@googlegroups.com.

To post to this group, send email to appscale_...@googlegroups.com.
Visit this group at https://groups.google.com/group/appscale_community.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "AppScale Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appscale_commun...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/appscale_community/30d05ac2-cf72-411a-b7ea-16cb5b644636%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages