Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect couchIP is pulled #4

Open
PerilousApricot opened this issue Jun 13, 2012 · 2 comments
Open

Incorrect couchIP is pulled #4

PerilousApricot opened this issue Jun 13, 2012 · 2 comments
Labels

Comments

@PerilousApricot
Copy link
Member

Using the following in my secrets:

MYSQL_USER=xxx
MYSQL_PASS=xxx
COUCH_USER=xxx
COUCH_PASS=xxx
COUCH_PORT=5984
COUCH_HOST=127.0.0.1
REQMGR_HOSTNAME=127.0.0.1
REQMGR_PORT=8684
WORKLOAD_SUMMARY_HOSTNAME=127.0.0.1
WORKLOAD_SUMMARY_PORT=5984
WORKLOAD_SUMMARY_DBNAME=workload_summary
CS_HOSTNAME=127.0.0.1
CS_PORT=8888
SB_HOSTNAME=127.0.0.1
UFC_CACHEDIR=/home/meloam/wmagent-new/ufc_cache
UFC_PORT=7778
HOST_DN=/DC=org/DC=doegrids/OU=Services/CN=se2.accre.vanderbilt.edu

My couch server binds correctly to 127.0.0.1, but then the wmagent, etc.. configurations point to

config.JobStateMachine.couchurl = 'http://_:_*@se2.accre.vanderbilt.edu:5984'

Which fails :/ are the manage scrupts supposed to use COUCH_HOST for that value?

@PerilousApricot
Copy link
Member Author

Looking through the manage scripts, there's COUCH_HOST, but also a COUCH_HOST_NAME that is set to hostname. If that necessary?

@stuartw
Copy link
Contributor

stuartw commented Jul 25, 2012

yes, one directs couch what hostname to bind to, the other is the hostname other components use to contact couch (the naming is unclear its true).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants