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

Error when submitting to caper server on SGE #17

Closed
asanghi7 opened this issue Jul 11, 2019 · 3 comments
Closed

Error when submitting to caper server on SGE #17

asanghi7 opened this issue Jul 11, 2019 · 3 comments

Comments

@asanghi7
Copy link

When I submit my atac-seq input.json files to the caper server. I get the following error:
HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/workflows/v1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x2b9025e3c7b8>: Failed to establish a new connection: [Errno 111] Connection refused'))...I attached my default.conf file.
default.conf.txt

@leepc12
Copy link
Contributor

leepc12 commented Jul 11, 2019

That HTTP error tells you that Caper server IP address (specified by --ip) is not configured correctly. It's localhost by default. Get a hostname of Caper server and put it into your conf file.

If you qsubed Caper server like echo "caper server" | qsub, then your caper server should be running on a compute node you need to take a hostname of that node.

ip=YOUR_CAPER_SERVER_HOSTNAME

If you ran Caper server on a login node then you don't need to specify --ip.

Also, I don't think your parallel environment is configured correctly. dper730xd-srcf-d16-17 looks like a hostname of Caper server?

sge-pe=dper730xd-srcf-d16-17

@asanghi7
Copy link
Author

Thank you for the response. I understand that I shouldn't be using sge-pe. I will set the ip to the Hostname from my slurm job

@leepc12
Copy link
Contributor

leepc12 commented Jul 12, 2019

Yes sge-pe is for SGE, not for SLURM. We already met in person and fixed this.

@leepc12 leepc12 closed this as completed Jul 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants