ooyala / barkeep

The friendly code review system.
getbarkeep.org
1.42k stars 145 forks source link

installation of barkeep always failed #465

Closed irenejia closed 11 years ago

irenejia commented 11 years ago

I'm interested with barkeep and tried to install it on Ubuntu 12.04 64bit, but always failed. Please correct me if I made any mistakes in the following:

  1. the one-script installation means to install barkeep on the ubuntu server, right? no need to install anything on user client. I suppose all connection to barkeep server is through http web page.
  2. the running of the script failed, so I had to install components step-by-step according to install-barkeep.sh, when I finally installed everything, I was always mentioned that my gmail account failed to be authorized, though I confirmed that the user name and password were correct.
  3. then I resorted to install vagrant, but the problem was that hostname barkeep-vagrant could not be recognized. I don't understand, should the name be created by user? how did it recognize it? through ip match?
  4. when I decided to delete local barkeep folder and went over the installation again from the very beginning, I could see barkeep was running, but I could not connect to 8040 port, what's wrong with it?

Please comment something when I was in such a crazy dilemma. Thank you very much!

dmac commented 11 years ago
  1. Correct.
  2. As noted at the top of the file, the install-barkeep.sh script was initially written for Ubuntu 10.04, so it may not work out of the box with other versions of Ubuntu. Installing step-by-step according to that script is the best course of action, and it sounds like you got pretty close, and all that was left was debugging your Gmail authentication.
  3. We don't recommend installing on vagrant for your production barkeep. In the example you were looking at, barkeep_vagrant is just a hostname that could be anything, and in that example would be specified in your .ssh/config.
  4. Did you install barkeep on a server, or locally on your computer? Could you connect locally? Remotely?
irenejia commented 11 years ago

again, I got barkeep complain that "Sorry, we could not authenticate you with this identifier." where to trace the authenticate problem? my login url is in the following: http://kdis-git-server:8040/signin/complete?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.response_nonce=2013-09-12T02%3A29%3A21Zc_ZGUC33IsaiBg&openid.return_to=http%3A%2F%2Fkdis-git-server%3A8040%2Fsignin%2Fcomplete&openid.assoc_handle=1.AMlYA9UalcIK6us1z1YIDBrX67qGVDB__aGn_6Sf9514I-FzDUdvWD25y8Z_vg&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode%2Cext1.type.ext0%2Cext1.value.ext0&openid.sig=Qmz2jw3Eet0ZW7QJzwg2BLa0Y50%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkktH8SvWaT4ZUoMZnPaWeHZhcORzZMnzw&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkktH8SvWaT4ZUoMZnPaWeHZhcORzZMnzw&openid.ns.ext1=http%3A%2F%2Fopenid.net%2Fsrv%2Fax%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.ext0=http%3A%2F%2Faxschema.org%2Fcontact%2Femail&openid.ext1.value.ext0=barkeep.carestream%40gmail.com

irenejia commented 11 years ago

I've compared the login url with the openID requested parameters shown on http://openid-provider.appspot.com/barkeep.carestream, and found that the format is incompatible. At least at two points: openid.claimed_id and openid.identity are required to be "http://specs.openid.net/auth/2.0/identifier_select", but in my instance, both items were "https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkktH8SvWaT4ZUoMZnPaWeHZhcORzZMnzw". Is there possibly a problem with version conflict of openid lib or anything related?

dmac commented 11 years ago

Ok, let's separate these problems out.

  1. Unable to install on Ubuntu 12.04 with the install_barkeep.sh script. I just tested this and was able to install barkeep on a fresh image from AWS with no problems. It would be helpful if you could describe in what way your installation was failing and include any error messages, but it sounds like you made it past this by manually installing everything.
  2. Unable to authenticate with Google OpenID. I am able to sign in to a clean install of barkeep using both an @gmail.com email and a Google Apps email. What happens if you sign in to your Google account before you try to sign in to Barkeep? What type of server are you installing Barkeep on?

Do note that the GMAIL_ADDRESS and GMAIL_PASSWORD parameters are used for emails from Barkeep, not for OpenID sign in, so they should be unrelated to your problem.

irenejia commented 11 years ago

Daniel,Thank you very much for your response!

For problem 1, yes, I finally did it manually. It was not installed on a fresh image, but on a git server: gitolite+git on Ubuntu 12.04 LTS 64bit. A big problem is that it can not access git://github.com/...., but rather https://github.com/... instead. When I was installing, I skipped the git part, but all other things in the script had been followed.

For problem 2, weird. I could log in gmail with my own account successfully. I once even tried to keep the login status first and then explore to barkeep server port 8040, but, again, I was refused.

When I first completed the installation, the barkeep was in running status, but the web page could not access. From log files in /var/log/barkeep, I found that the application failed to find ruby, the log complained that "/usr/bin/ruby bad interpreter". It seemed that the ruby version installed from rbenv could not be recognized, so I created a symbolic link of /usr/bin/ruby to direct to $HOME/.rbenv/shims/ruby. Later on, I was rejected on web page.

Is there any other log files to monitor the web page response or trace the application problem?

dmac commented 11 years ago

Not knowing the environment in which you're running barkeep, there's not much more we can do. I would strongly suggest installing barkeep in an environment that is known to work: using the install script on a clean Ubuntu 12.04 image from AWS. The further you move from that, the less help we're able to provide.

Best of luck!