Hi James,
As you had noted, it sounds like there may be connectivity and/or
congestion issues between your Scalr servers and Scalr managed instances
that needs to be checked and mitigated. For your first issue I am glad to
hear you have a workaround, but this should not be necessary. A copy
Anyone? Guidance on increasing the time between msgSender retries, or
increasing the number of retries?
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Quite correct, Marc. I found a correlation between very high network
congestion internally and both the stuck pending and stuck initializing.
For the stuck pending systems, if I ssh into the system and manually
upgrade the agent then restart, it proceeds to the next step. This is an
Hello Slopshid,
In case you did not have the link, our Agent change log is available here
. We have not had similar reports of high-occurrence
intermittent "Pending" or "Initializing" state issues as you have
described. A fully copy of your agent logs from one of these instances
using the
I've been having issues with the scalarizr agent pretty much since I
started using Scalr, and it seems to have gotten worse with each new agent
version.
The environment:
Scalr 5.11.22 Community Edition
Scalarizr stable 4.6.6 through 4.10.0
-or-
Scalarizr latest 4.9.3 through 4.11.10
CentOS 7.2
