I will gladly pay one to help me out here.. We are two developers who cannot deploy
AeroGear to: openshift, aws, or just regular ec2 server.
Please, if anyone have time – contact me.
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm@napp.dk<mailto:mm@napp.dk>
W:
https://napp.dk<https://napp.dk/>
__________________
From: <aerogear-dev-bounces(a)lists.jboss.org> on behalf of "mm(a)napp.dk"
<mm(a)napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
I got more resources connected to my account, but the aerogear server cannot deploy.
This two other apps works just fine:
http://prntscr.com/gqomv3
But unifiedpush-server will not deploy:
http://prntscr.com/gqolyk
I get:
Readiness probe failed: rpc error: code = 13 desc = invalid header field value "oci
runtime error: exec failed: container
\"f15bbd0887b42057604afa2de6a6243b8c3a51b1f97dbb21a809f62a6dc99c54\" does not
exist\n"
Readiness probe failed: sh: cannot set terminal process group (-1): Inappropriate ioctl
for device sh: no job control in this shell --2017-09-28 09:33:01--
http://localhost:8080/ag-push Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting
to localhost (localhost)|::1|:8080... failed: Connection refused. Connecting to localhost
(localhost)|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... Read
error (Connection reset by peer) in headers. Retrying.
Anyone got Unified push server working in Openshift 3?
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm@napp.dk<mailto:mm@napp.dk>
W:
https://napp.dk<https://napp.dk/>
__________________
From: <aerogear-dev-bounces(a)lists.jboss.org> on behalf of "mm(a)napp.dk"
<mm(a)napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
Hi,
I did that and got:
http://prntscr.com/gqnxw9
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm@napp.dk<mailto:mm@napp.dk>
W:
https://napp.dk<https://napp.dk/>
__________________
From: <aerogear-dev-bounces(a)lists.jboss.org> on behalf of Julio Cesar Sanchez
Hernandez <jusanche(a)redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
You can try
https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/opens...
On Thu, Sep 28, 2017 at 10:24 AM, Mads Møller <mm@napp.dk<mailto:mm@napp.dk>>
wrote:
Any guide on how to get it working on openshift 3?
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm@napp.dk<mailto:mm@napp.dk>
W:
https://napp.dk<https://napp.dk/>
__________________
From:
<aerogear-dev-bounces@lists.jboss.org<mailto:aerogear-dev-bounces@lists.jboss.org>>
on behalf of Matthias Wessendorf
<matzew@apache.org<mailto:matzew@apache.org>>
Reply-To: AeroGear Developer Mailing List
<aerogear-dev@lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List
<aerogear-dev@lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
I've no idea, honestly - I've never used AWS
On Thu, Sep 28, 2017 at 10:04 AM, Mads Møller <mm@napp.dk<mailto:mm@napp.dk>>
wrote:
Hi list,
I truly need your help.
We have been trying for days to migrate our Unified Push server from the Openshift 2 that
is sunset at sep 30th.
We have tried to migrate to AWS ECS, but the docker file does not work for us. it's
because of the volumes I think, it wanted some files outside of docker image.
Does anyone know how to get Unified Push og the Keyclock to work with AWS container
service?
If not, then please point me in a direction where I quickly can migrate too.
I would be very grateful if someone can help out.
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm@napp.dk<mailto:mm@napp.dk>
W:
https://napp.dk<https://napp.dk/>
__________________
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev