OpenShift maybe likes to sleep far too much... :-(
I sent a test push today morning, but a couple of hours later the pushes were lost because
the server decided to sleep again...
This should be a top priority, because for production such situation shouldn't never
happen.
Miguel
Enviado do meu iPhone
No dia 24/02/2014, às 21:38, Burr Sutter <bsutter(a)redhat.com> escreveu:
OpenShift Online will "sleep" your gears after N hours of
non-use. I am not sure if that is 24 or 48 hours. In theory, as soon as the 2nd hit
comes in (after sleep) it should be back to life - the 1st hit is what causes it to come
back to life but it often errors out.
In any case, I often use the Restart feature that is on the OpenShift console to get
everything back up and running.
> On Feb 24, 2014, at 11:07 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>
>
>
>> On Mon, Feb 24, 2014 at 5:03 PM, Miguel Lemos <miguel21op(a)gmail.com>
wrote:
>> After the reset it's running again. This is indeed a very annoying situation
that should never happen...
>
> Feel free to share your log, we can pass them to the OpenShift guys, to make sure
they are aware of that issue.
>
>>
>>
>>> On Mon, Feb 24, 2014 at 3:59 PM, Farah Juma <fjuma(a)redhat.com> wrote:
>>> Hi Miguel,
>>>
>>> Just to make sure your MySQL cartridge is still up, try running the following
command:
>>>
>>> rhc cartridge status -a <APP_NAME> -c mysql
>>>
>>> Farah
>>>
>>> ----- Original Message -----
>>> > From: "Matthias Wessendorf" <matzew(a)apache.org>
>>> > To: "AeroGear Developer Mailing List"
<aerogear-dev(a)lists.jboss.org>
>>> > Sent: Monday, February 24, 2014 10:52:19 AM
>>> > Subject: Re: [aerogear-dev] Issue
>>> >
>>> > Hey Miguel,
>>> >
>>> >
>>> > did you reboot the instance ?
>>> >
>>> > I just got back a 200 status-code, using your CURL:
>>> >
>>> >
>>> > curl -3 -u "00a21ce3-a7d9-4c8c-b583- 9f0210a634e5:941186b3-ec6a-
>>> > 4f48-b26b-2d061eb23d9b" -v -H "Accept: application/json"
-H "Content-type:
>>> > application/json" -X POST -d '{"message":
{"alert":"This", "aviso":"and
>>> > that", "badge":1}}'
https://aerogear-metalpush.rhcloud.com/rest/sender
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 4:50 PM, Matthias Wessendorf <
matzew(a)apache.org >
>>> > wrote:
>>> >
>>> >
>>> >
>>> > It asks for a password here
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 4:46 PM, Miguel Lemos < miguel21op(a)gmail.com
> wrote:
>>> >
>>> >
>>> >
>>> > I just entered in Openshift with my normal credentials; no problem with
the
>>> > login, but i get a blank screen here when I'm redirected into here:
>>> >
>>> >
https://aerogear-metalpush.rhcloud.com/phpmyadmin/
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 3:42 PM, Matthias Wessendorf <
matzew(a)apache.org >
>>> > wrote:
>>> >
>>> >
>>> >
>>> > I just tested your CURL against my hosted instance - worked fine (sure
I
>>> > changed the credentials)
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 4:36 PM, Miguel Lemos < miguel21op(a)gmail.com
> wrote:
>>> >
>>> >
>>> >
>>> > Something's wrong because I can't even login on the console with
my
>>> > credentials...
>>> > I haven't change anything. i also have my PHP code that was working
and now
>>> > throws the same error...
>>> >
>>> >
https://aerogear-metalpush.rhcloud.com/#/login
>>> >
>>> >
>>> > I bet there is some sort of error on your OpenShift instance - the
cloud
>>> > offerings.
>>> >
>>> > Can you reboot your instance, via the OpenShift console ?
>>> >
>>> > like here - the red icon (->
http://people.apache.org/~matzew/restart_os.png
>>> > )
>>> >
>>> >
>>> >
>>> >
>>> > It sounds like that your account has an issue. I am really sorry for
that
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 3:32 PM, Sebastien Blanc <
scm.blanc(a)gmail.com >
>>> > wrote:
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 4:27 PM, Miguel Lemos < miguel21op(a)gmail.com
> wrote:
>>> >
>>> >
>>> >
>>> > From the console:
>>> >
>>> > curl -3 -u
>>> >
"00a21ce3-a7d9-4c8c-b583-9f0210a634e5:941186b3-ec6a-4f48-b26b-2d061eb23d9b"
>>> > -v -H "Accept: application/json" -H "Content-type:
application/json" -X POST
>>> > -d '{"message": {"alert":"This",
"aviso":"and that", "badge":1}}'
>>> >
https://aerogear-metalpush.rhcloud.com/rest/sender
>>> >
>>> > Well, that looks correct and since you are using your same backend (
>>> >
https://aerogear-metalpush.rhcloud.com/rest/sender ) nothing should
have
>>> > changed ...
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 3:24 PM, Sebastien Blanc <
scm.blanc(a)gmail.com >
>>> > wrote:
>>> >
>>> >
>>> >
>>> > Hi Miguel !
>>> > Can you send us more details, like the request you are sending ?
>>> > Seb
>>> >
>>> >
>>> >
>>> > On Mon, Feb 24, 2014 at 4:19 PM, Miguel Lemos < miguel21op(a)gmail.com
> wrote:
>>> >
>>> >
>>> >
>>> > Have you changed anything in the server API? Using the same code
I've been
>>> > using with success the last days now it returns a " The request
sent by the
>>> > client was syntactically incorrect ()"
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> >
>>> > --
>>> > Matthias Wessendorf
>>> >
>>> > blog:
http://matthiaswessendorf.wordpress.com/
>>> > sessions:
http://www.slideshare.net/mwessendorf
>>> > twitter:
http://twitter.com/mwessendorf
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> >
>>> > --
>>> > Matthias Wessendorf
>>> >
>>> > blog:
http://matthiaswessendorf.wordpress.com/
>>> > sessions:
http://www.slideshare.net/mwessendorf
>>> > twitter:
http://twitter.com/mwessendorf
>>> >
>>> >
>>> >
>>> > --
>>> > Matthias Wessendorf
>>> >
>>> > blog:
http://matthiaswessendorf.wordpress.com/
>>> > sessions:
http://www.slideshare.net/mwessendorf
>>> > twitter:
http://twitter.com/mwessendorf
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev