-
Notifications
You must be signed in to change notification settings - Fork 6
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
Failed to open TCP connection - new item create/edit #266
Comments
I can see 2 possible causes at the moment. Could you check you have the right Also the manager should be running in production mode, ie: the environment variable I don't think this is related by you in api's Could you provide the code you have in |
Thanks @paul-mesnilgrente. My manager production.yml looks like:
I start it with I did get some moderate success editing these environment blocks in the manager.yml, I noticed i could create/edit new items when I removed all but the production block, but when the staging block is removed harvest previews fail. Do i need to generate keys staging for the block, even though I am not running the stager? The api's For the manager
This would prevent me from running the staging API stuff in the manager . . .(but I'm not yet sure how to do that anyways, or how critical is is at this time :) Thanks again. |
Ok, you've done all the right steps. I might have found the issue. Can you replace line 35 in # from
params[:environment] ||= 'staging'
# to
params[:environment] ||= ENV['PREVIEW_WORKER_HOST'] And you should have only the production block in the manager's production:
HOST: https://manager.auxiliator-digitalbc.ca
WORKER_HOST: https://worker.auxiliator-digitalbc.ca
PREVIEW_WORKER_HOST: https://worker.auxiliator-digitalbc.ca
WORKER_KEY: 959933ea2ead4b73a6d8415b4ddad7b931324501a379a9197ca8b38b90eb83f2b1d61bcbded14ddc8820d63f49f700fd6d8294f28e99b5bbcd71b960ab8aec29
API_HOST: https://api.auxiliator-digitalbc.ca
MONGO_HOSTS: mongodb+srv://corymbusaux.d0rvn.mongodb.net:27017
HARVESTER_API_KEY: LxPjQyKyBmo-emc7ATBL
OTP_SECRET_KEY: YOUROTPSECRETKEY
MFA_ENABLED: 'false' It it fixes your problem I'll add the fix at the same as #260 |
Thanks again @paul-mesnilgrente I made the above changes and I can create/edit items, but the harvester preview fails (the icons spins without end) and I get the following error in the console:
I tried a few variants of this: with the staging env excluded in
exists at lines 9 , 14 in The only approach I can get to work for create/edit and previews is the one I outlined above with all the env blocks in
in application.rb and keeping Thanks again for all your help with this, |
Ok, the troubles are not on you. I'll try to get a fix prioritized soon. If you want to keep investigating in the mean time, you can try modifying line 148 of !HarvestSchedule.find_from_environment({ parser_id: self.id }, 'production').empty? with the changes I gave you in the last message. |
Thanks @paul-mesnilgrente! Much appreciated :) I'm happy to investigate. Modifying 148 in
coupled with:
and in the
give me a error (and a failed harvest preview) :
Thanks again for all the assistance. |
What's the back-trace of this error? |
Sorry, I gave you the wrong error: it's this one . . .
I tried replacing lines 9 and 14 in but I got the same error and a spinning logo in the preview window |
👍 We have a story in the backlog to fix it. I don't know how much code needs to be changed in the manager. We have a setup working at the moment in our cluster which is used for testing. This setup is only using staging. You could try running the worker/manager/api in staging mode without modifying the manager. I'm not sure if it's worth investigating for you... Sorry for the inconvenience |
No trouble @paul-mesnilgrente I can work around this. Thanks for all your assistance! |
Hi again,
I'm setting up a new production build (DigitalOcean)
manager - v2.12.11
worker - v2.12.16
and I when I create/edit an 'object' (like a new parser, datasource, or contributor) in the manager, I consistently get a "We're sorry, something went wrong page" , but I can trim the url in the browser and go back and see that the item it created/edited does exist, what's more, I can use the item I created/edit. I thought this might be a route error but my manager log tells me there's a connection failure . . .
to what looks like it should be the api at 127.0.0.1:3000 if I were running it in dev. My application.ymls all point to the API domain:
manager /config/application.yml
worker /config/application.yml
api /config/application.yml
and of course my apache vhost has the HAproxy ref:
I can't locate any reference to 127.0.0.1:3000 in the app to see where this would be coming from, and I'm wondering how this info is generated in the hope that I can correct it.
Thanks for any assistance you could render.
The text was updated successfully, but these errors were encountered: