Open GoogleCodeExporter opened 8 years ago
GoogleCodeExporter
commented
8 years ago I probably know where is the error, however, not sure.
Could please tell me your "ADDRESS": "app-domain.rhcloud.com"? Just address is
OK.
On the condition of:
1.remote files in path app_id/
2.have username/password
3.remote json:type HTTPSOriginal comment by goknmuse on 26 Dec 2012 at 10:14
GoogleCodeExporter
commented
8 years ago Have created a new app for you.
steps to deploy:
$ rhc app create -a jap123 -t diy-0.1
(config json and copy files to jap123/ with a file manager)
$ cd jap123/
$ git add -A
$ git commit -m "JAP"
[master 70f5074] JAP
8 files changed, 356 insertions(+)
create mode 100644 JAP/JAP_WS_REMOTE.py
create mode 100644 JAP/__init__.py
create mode 100644 JAP_WS_REMOTE.json
create mode 100644 JAP_WS_REMOTE.py
create mode 100644 MAKE.bat
create mode 100644 README.txt
create mode 100644 app.tac
create mode 100644 requirements.txt
$ git push
Address:
http://jap123-westmin.rhcloud.com/
JAP_WS_REMOTE.json:
{
"LOGGER":
{
"LEVEL": 10
},
"REMOTE_PROXY_SERVER":
{
"TYPE": "HTTPS",
"AUTHENTICATION":
[
{
"USERNAME": "jap",
"PASSWORD": "123"
}
]
}
}
Original comment by westmin...@gmail.com on 26 Dec 2012 at 11:18
GoogleCodeExporter
commented
8 years ago [deleted comment]Have destroyed it and recreated,username/password are still the same.
Use this client
http://jap.googlecode.com/files/JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT.zip
still the same debug output,connectionLost.Original comment by westmin...@gmail.com on 26 Dec 2012 at 1:03
GoogleCodeExporter
commented
8 years ago Apparently, Comment 1 and Comment 3 both are related to the remote part.
As I responded to you in such a short replay in the Comment 3, I'm a little
sure where is the error. You are supposed to find what's wrong with the remote
part too.
After deploying JAP_WS_REMOTE_OPENSHIFT successfully, visiting the address (
https://app-domain.rhcloud.com ) with browser, you should see nothing but a
blank page.
Or, attaching your full logs of the deploying process, just like the Comment 2,
however, if you would put the them in a single text file as a attachment, it
should make your comment in a enjoyable format.Original comment by goknmuse on 26 Dec 2012 at 2:11
GoogleCodeExporter
commented
8 years ago [deleted comment]Ok,I was wrong that did not copy '.openshift' dir to the app_id/ path to cover
the default one.
Destroy and recreate it.But,still fail to work.Here is the new connectionlost
debug output:
Original comment by westmin...@gmail.com on 26 Dec 2012 at 3:16
Attachments:
GoogleCodeExporter
commented
8 years ago I just realized that your OS is Linux, how foolish I am. When I saw your logs
after executing "git commit -m 'JAP'", I knew some files was not in the app_id/
. I stupid think that is because you were using the source, rather than the
bundle files.
The truth is your OS is Linux, any files or directories starting with "."(not
including "") will be hidden. You need put directory of .openshift/ (
https://github.com/jvansteirteghem/jap/tree/master/JAP_WS_REMOTE_PYTHON_OPENSHIF
T/.openshift ) under app_id/ too, maybe overwrite any files in the origin one.
I do think you know how to do it, so I omit.
--"After deploying JAP_WS_REMOTE_OPENSHIFT successfully, visiting the address (
https://app-domain.rhcloud.com ) with browser, you should see nothing but a
blank page."
TRUTH, which is kind of the Jeroen Style.
--"Second,I still DO NOT know what's wrong with the remote part,or what's wrong
with my deploying steps."
That's what we are going to find, however, I need you almost meet my requests.Original comment by goknmuse on 26 Dec 2012 at 3:17
GoogleCodeExporter
commented
8 years ago http://jap123-westmin.rhcloud.com/ still this app address? All we want to see
it a blank page, not the "Service Temporarily Unavailable" :S
It is time for bed. Good night.Original comment by goknmuse on 26 Dec 2012 at 3:27
GoogleCodeExporter
commented
8 years ago This time I copy all the files including '.openshift' to app_id/ and deploy it.
still the same address http://jap123-westmin.rhcloud.com/
still the same username/password.
I have no idea why it's 503 error.
Leave it,come again tomorrow.Good night.Original comment by westmin...@gmail.com on 26 Dec 2012 at 3:53
GoogleCodeExporter
commented
8 years ago I have destroyed and recreated apps again and again with different openshift
accounts exactly follow the steps in Comment 2,be sure that all the files in
JAP_WS_REMOTE_PYTHON_OPENSHIFT are copied to the app_id/ dir.
However,visiting the address https://app-domain.rhcloud.com,every time come is
503 Service Temporarily Unavailable error.
Why why why???Original comment by westmin...@gmail.com on 27 Dec 2012 at 9:10
GoogleCodeExporter
commented
8 years ago [deleted comment][deleted comment][deleted comment][deleted comment]Comment 14 & 15 are wrong,so I delete it.Sorry.
I found the difference:
After recreated jap123 app
Copy all files from the clone of your deployment except .git to jap123/
$ git commit -m "JAP"
[master 5b9e575] JAP
11 files changed, 352 insertions(+), 3 deletions(-)
create mode 100755 .openshift/action_hooks/vars
create mode 100755 JAP/JAP_WS_REMOTE.py
create mode 100755 JAP/__init__.py
create mode 100755 JAP_WS_REMOTE.json
create mode 100755 JAP_WS_REMOTE.py
create mode 100755 README.txt
create mode 100755 app.tac
create mode 100755 requirements.txt
$ git push
...
remote: Running .openshift/action_hooks/pre_build
remote: Running .openshift/action_hooks/build
remote: Running .openshift/action_hooks/deploy
Copy all files from zip file to jap123/
$ git commit -m "JAP"
[master aac5e1d] JAP
11 files changed, 352 insertions(+), 3 deletions(-)
mode change 100755 => 100644 .openshift/action_hooks/deploy
mode change 100755 => 100644 .openshift/action_hooks/start
mode change 100755 => 100644 .openshift/action_hooks/stop
create mode 100644 .openshift/action_hooks/vars
create mode 100644 JAP/JAP_WS_REMOTE.py
create mode 100644 JAP/__init__.py
create mode 100644 JAP_WS_REMOTE.json
create mode 100644 JAP_WS_REMOTE.py
create mode 100644 README.txt
create mode 100644 app.tac
create mode 100644 requirements.txt
$ git push
...
(no remote running!)
Original comment by westmin...@gmail.com on 27 Dec 2012 at 3:39
GoogleCodeExporter
commented
8 years ago I think there is something wrong with the file permissions.
100755 vs 100644Original comment by westmin...@gmail.com on 27 Dec 2012 at 3:42
GoogleCodeExporter
commented
8 years ago [deleted comment]I found the problem!!!!!
The script files in .openshift/action_hooks/ downloaded from zip file or cloned
from the author's github repo are no executable!(permission code are 644)
So after committing,the scripts will not be executed!
This problem only dues to Linux system but not Windows.
To fix it,only need to make all the scripts executable.(permission code are 755)Original comment by westmin...@gmail.com on 27 Dec 2012 at 3:52
GoogleCodeExporter
commented
8 years ago Thank you for reporting the problem! :)Original comment by jeroen.v...@gmail.com on 28 Dec 2012 at 9:27
GoogleCodeExporter
commented
8 years ago think@TANK:~/japlocal$ python JAP_WS_LOCAL.py
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3.zip
JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2.zip
Ubuntu 12.10 x64
- installed PYTHON2.7
- installed TWISTED
- installed PYOPENSSL
- installed AUTOBAHN
I had already done #19 http://code.google.com/p/jap/issues/detail?id=10#c19
Still fail to work. Original comment by Luzifer1...@gmail.com on 22 Jan 2013 at 2:14
GoogleCodeExporter
commented
8 years ago [deleted comment]think@TANK:~/japlocal$ python JAP_WS_LOCAL.py
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
Original comment by Luzifer1...@gmail.com on 22 Jan 2013 at 2:30
GoogleCodeExporter
commented
8 years ago Can you attach your JAP_WS_LOCAL.json and JAP_WS_REMOTE.json?Original comment by jeroen.v...@gmail.com on 22 Jan 2013 at 2:53
GoogleCodeExporter
commented
8 years ago GoogleCodeExporter
commented
8 years ago GoogleCodeExporter
commented
8 years ago [deleted comment]Both JAP_WS_LOCAL.json and JAP_WS_REMOTE.json are configured correctly.
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 comment by jeroen.v...@gmail.com on 22 Jan 2013 at 6:34
GoogleCodeExporter
commented
8 years ago Issue 9 has been merged into this issue.Original comment by goknmuse on 23 Jan 2013 at 9:23
GoogleCodeExporter
commented
8 years ago TO Luzifer...
One problem: Visit https://think-tank.rhcloud.com:8443/ with your browser, you
can get this "The certificate is only valid for ex-std-node30.prod.rhcloud.com".
Not "AUTHENTICATION":{"FILE": "ex-std-node74.prod.rhcloud.com"}, or
"AUTHENTICATION":{"FILE": "ex-std-node99.prod.rhcloud.com"}.
Two: it seems rhcloud.com or OpenShift PaaS has been disturbed by GFW.
First reason: https://think-tank.rhcloud.com can not be directly visit without problem always.
Second: "rhc domain" or "rhc app create <AppName> diy-0.1" often get timeout.
Third: "rhc app delete <AppName>" sometimes get timeout too, however, "rhc app delete <AppName> --comfirm" never come cross any problem, which is a newer disturbing way(you can send requests to the server out of GFW, however, hard to get responds because of GFW.) of GFW.
Fourth: I have been using the YiDong ISP for a long time and seldom have problems list first to third. But when I change to use DianXin ISP, it is so often. :(
Three: there are some problems OpenShift itself.Original comment by goknmuse on 23 Jan 2013 at 9:56
GoogleCodeExporter
commented
8 years ago @jeroen
I had reinstalled JAP_WS_REMOTE_PYTHON_OPENSHIFT
the attached file is my log (installation logs and OPENSHIFT logs)
to @goknmuse #30 I had reinstalled, the certificate was changed
我英文不行,@goknmuse，把我附件里的#注释翻译一下给@jeroen
我的/JAPOS/.openshift/action_hooks文件夹里没有vars,即使我执行了“
cp -r ../JAPOS/* .”
所以我手动复制进/think/.openshift/action_hooks了，权限也改成了75
5.如果没有这个vars，git
push后https://think-tank.rhcloud.com不是空白，应该是部署不成功.
Original comment by Luzifer1...@gmail.com on 23 Jan 2013 at 11:19
GoogleCodeExporter
commented
8 years ago GoogleCodeExporter
commented
8 years ago @goknmuse
openshift.redhat.com is not blocked by GFW , China Telecom ISP，Wuhan, 8.8.8.8Original comment by Luzifer1...@gmail.com on 23 Jan 2013 at 11:37
GoogleCodeExporter
commented
8 years ago [deleted comment][deleted comment][deleted comment]GMT+8：19:48
https://think-tank.rhcloud.com:8443/
certificate
ex-std-node68.prod.rhcloud.com
Right? I reupload the attachments
Original comment by Luzifer1...@gmail.com on 23 Jan 2013 at 11:53
Attachments:
GoogleCodeExporter
commented
8 years ago [deleted comment][deleted comment]Are JAP_WS_LOCAL.json and JAP_WS_LOCAL.json still encoding in UTF-8 without BOM
after you changing it?Original comment by goknmuse on 23 Jan 2013 at 12:07
GoogleCodeExporter
commented
8 years ago Sorry, I can not find the problem.
BTW, hence this issue has too many comments, I have removed some not necessary
comments.Original comment by goknmuse on 23 Jan 2013 at 12:14
GoogleCodeExporter
commented
8 years ago Can you zip and attach your think directory?
Can you check the content of the files in /think/.openshift/action_hooks and
/JAPOS/.openshift/action_hooks?
Can you check the permissions of the files in /JAPOS/.openshift/action_hooks?Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 1:14
GoogleCodeExporter
commented
8 years ago @jeroen
/think/.openshift/action_hooks = /JAPOS/.openshift/action_hooks
ls.txtOriginal comment by Luzifer1...@gmail.com on 23 Jan 2013 at 1:55
Attachments:
GoogleCodeExporter
commented
8 years ago As far as I can see everything is OK, but I do not have a LINUX OS to test.
Maybe @westminboy can help?
Also see http://code.google.com/p/jap/issues/detail?id=22Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 2:24
GoogleCodeExporter
commented
8 years ago Python 2.6 as that is the version of python hosted on OpenShift.
Python 2.7 as default python interpreter in my ubuntu 12.10 x64
@jeroen
Will python version difference cause my problems?
Original comment by Luzifer1...@gmail.com on 23 Jan 2013 at 2:27
GoogleCodeExporter
commented
8 years ago No, I have python 2.7 on windows xp and windows 7 and I have no problems with
openshift.Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 2:31
GoogleCodeExporter
commented
8 years ago @jeroen
I catch http://code.google.com/p/jap/issues/detail?id=22
And i have destroyed and recreated apps again.2013-01-23 10:02:29-0500
GMT+8>=23:xx
Address
-- https://think-tank.rhcloud.com:8443/
Certificate
-- ex-std-node19.prod.rhcloud.com
Issues
-- think@TANK:~/japlocal$ python JAP_WS_LOCAL.py
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
Environment
-- Ubuntu 12.10 x64
-- Python 2.7
-- Twisted 12.3.0
-- pyOpenSSL 0.13
-- autobahn 0.5.9
Attachments
-- My logs (installation logs and OPENSHIFT logs)
-- JAP_WS_LOCAL.json
-- JAP_WS_REMOTE.json
Original comment by Luzifer1...@gmail.com on 23 Jan 2013 at 3:29
Attachments:
GoogleCodeExporter
commented
8 years ago
+ Environment
-- zope.interface 4.0.3
Original comment by Luzifer1...@gmail.com on 23 Jan 2013 at 3:45
GoogleCodeExporter
commented
8 years ago I have installed an UBUNTU VM (ubuntu-12.04.1-desktop-i386) and I have
installed JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3 without problems.
See attached screenshots.Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 7:11
Attachments:
GoogleCodeExporter
commented
8 years ago [deleted comment]
Original issue reported on code.google.com by
westmin...@gmail.comon 26 Dec 2012 at 7:58