search

tel8618217223380 / jap

Automatically exported from code.google.com/p/jap
0 stars 0 forks source link

openshift seems not work #21

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Can you reinstall JAP_WS_REMOTE_PYTHON_OPENSHIFT and attach your installation 
logs?
Can you also attach your OPENSHIFT logs (rhc tail <application-id>)?

Original issue reported on code.google.com by morrla...@gmail.com on 22 Jan 2013 at 3:20

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
My jap on openshift is also not working now (it worked well at the beginning).

Original comment by ksdaf...@gmail.com on 23 Jan 2013 at 9:54

GoogleCodeExporter commented 8 years ago 
http://code.google.com/p/jap/issues/detail?id=10#c30
Skip the "One problem", read it after "Two"

Original comment by goknmuse on 23 Jan 2013 at 10:03

GoogleCodeExporter commented 8 years ago 
I reinstall OPENSHIFT-2.0.0-SNAPSHOT-3 and it works well now;

Besides, it seems
DOTCLOUD-2.0.0-SNAPSHOT-2 works well now;
but
OPENSHIFT-2.0.0-SNAPSHOT-2 does not.

Original comment by ksdaf...@gmail.com on 23 Jan 2013 at 10:19

GoogleCodeExporter commented 8 years ago 
Some files in OPENSHIFT-2.0.0-SNAPSHOT-2 are Windows format EOL "CRLF", which 
causes some errors on the OpenShift Unix server. That's why we update it. :P

Original comment by goknmuse on 23 Jan 2013 at 11:11

GoogleCodeExporter commented 8 years ago 
follow the README.txt steps completely with this revision

@jeroen
diff README.txt
- - open CONSOLE
+ - open CONSOLE and cd to the father dir of 
JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X  ## for cp cmd below
- cp -r ../JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X/* .  ## will not copy hidden 
dir ".openshift"
+ cp -r ../JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X/. .  ## use "." not "*"
- - chmod -R +x ./.openshift/action_hooks
+ - chmod -R +x ./.openshift/action_hooks ./JAP  ## be sure remote scripts can 
be run

Original comment by westmin...@gmail.com on 23 Jan 2013 at 1:39

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
TO goknmuse

The following is my installation log(which is made on Win8 Pro x64).

It contains some sorts of 
"warning: LF will be replaced by CRLF in .openshift/action_hooks/XXXXX"
but I guess it does not matter.

Original comment by ksdaf...@gmail.com on 23 Jan 2013 at 4:13

Attachments:

GoogleCodeExporter commented 8 years ago 
By the way, does openshift use AmazonEC2?

C:\>ping ex-std-node74.prod.rhcloud.com

Pinging ec2-184-72-166-18.compute-1.amazonaws.com [184.72.166.18] with 32 bytes
of data:
Reply from 184.72.166.18: bytes=32 time=544ms TTL=34
Reply from 184.72.166.18: bytes=32 time=559ms TTL=34
Reply from 184.72.166.18: bytes=32 time=531ms TTL=34

Original comment by ksdaf...@gmail.com on 23 Jan 2013 at 4:23

GoogleCodeExporter commented 8 years ago 
REMARK: for now OPENSHIFT websocket protocol support is experimental (and also 
unstable).

See https://openshift.redhat.com/community/blogs/paas-websockets

Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 7:27

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
TO luxry...
REMOTE part is fine. LOCAL part does not meet the PRE-INSTALLATION
1. http://code.google.com/p/jap/wiki/JAP_WS_LOCAL#JAP_WS_LOCAL_PYTHON

2. Or you can try 
http://jap.googlecode.com/files/JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2.zip

Original comment by goknmuse on 27 Jan 2013 at 12:27

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
TO lux...
I have tested your JAP app, and everything is fine.
Try to download the file "ex-std-node94.prod.rhcloud.com", and put it in 
directory of JAP_WS_LOCAL_PYTHON_*.

Original comment by goknmuse on 27 Jan 2013 at 2:38

Attachments:

GoogleCodeExporter commented 8 years ago 
It seems Openshift is not stable:
1. If I use Bitvise SSH Client to connect openshift, the server will disconnect 
about every 25 minutes. It seems like some sort of reboot.
2. If I create a diy-0.1 app and push jap onto the server and use JAP app to 
connect, it will work well at the begining but crack down after a few days (not 
sure the reason). Besides, during the period it works well, "connectionLost" 
appears several minutes later (less than 40 mins) after connection, which means 
I cannot apply this proxy for continuous connection.

Original comment by ksdaf...@gmail.com on 27 Jan 2013 at 5:56