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.

Sign up for GitHub

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

Jump to bottom

knife-ec-backup FAILING with GATEWAY TIMEOUT #81

Open
nathan-lochala opened this issue Aug 2, 2016 · 8 comments
Open

knife-ec-backup FAILING with GATEWAY TIMEOUT #81

nathan-lochala opened this issue Aug 2, 2016 · 8 comments

Comments

@nathan-lochala
Copy link

I get the following error when attempting to backup a single org. I'm running the knife command off the chef server itself. Any help would be appreciated!

...
Created /cookbooks/windows-1.44.1/resources/reboot.rb
Created /cookbooks/windows-1.44.1/resources/path.rb
Created /cookbooks/windows-1.44.1/resources/task.rb
Created /cookbooks/windows-1.44.1/resources/zipfile.rb
ERROR: Gateway Time-out
Response: <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>openresty/1.9.7.2</center>
</body>
</html>
@marcparadise
Copy link
Member

This looks like one of the services isn't up and running, most likely oc_erchef.

What does chef-server-ctl status tell you? And (to save a step) does chef-server-ctl start + retry of ec backup resolve this for you?

@MichaelRolandD
Copy link

I have this same issue, it seems to be after getting through the last of the cookbooks. I have checked that all the chef-server services are running and they seem to be fine. Generally, I have had success with this on some servers and not on others...

chef-server-ctl status
run: bookshelf: (pid 18594) 160377s; run: log: (pid 1343) 179489s
run: nginx: (pid 18669) 160376s; run: log: (pid 1376) 179489s
run: oc_bifrost: (pid 18678) 160376s; run: log: (pid 1346) 179489s
run: oc_id: (pid 18755) 160375s; run: log: (pid 6731) 7323s
run: opscode-erchef: (pid 18762) 160375s; run: log: (pid 1355) 179489s
run: opscode-expander: (pid 18809) 160375s; run: log: (pid 1350) 179489s
run: opscode-reporting: (pid 19014) 160375s; run: log: (pid 1380) 179489s
run: opscode-solr4: (pid 19095) 160374s; run: log: (pid 1340) 179489s
run: postgresql: (pid 19118) 160373s; run: log: (pid 1375) 179489s
run: rabbitmq: (pid 19523) 160367s; run: log: (pid 1344) 179489s
run: redis_lb: (pid 6715) 7325s; run: log: (pid 1364) 179489s

@kishorerc
Copy link

kishorerc commented Jul 29, 2019 •
edited
Loading

We are facing similar issue as per our recent observation using knife ec backup. Is there a fix at all for this, as from long time this issue seems to be open.

INFO: HTTP Request Returned 504 Gateway Time-out: 
ERROR: Gateway Time-out
Response: <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>openresty/1.11.2.1</center>
</body>
</html>

@mithujose
Copy link

mithujose commented Oct 1, 2019 •
edited
Loading

We are seeing this issue randomly on our chef server backups. The backup tar seems to be incomplete because of this.

``INFO: HTTP Request Returned 504 Gateway Time-out:
ERROR: Gateway Time-out

@nicknameyu
Copy link

Get the same problem, same error message. chef-server-ctl status shows everything good. Anyone can follow up this issue?

@karalov
Copy link

karalov commented May 18, 2020

I have the same issue. After running ec backup again and again it worked fine on the third time.

@amcappelli
Copy link

amcappelli commented Jul 19, 2020 •
edited
Loading

I'm also seeing this very frequently, and it's getting worse. We have daily backups, and from January 1, 2020 to June 30, 2020 we had 88 failures. From July 1 to July 19, we've only had 2 backups succeed. Today, I've retried 4 times in a row and it has failed every time. I also ran chef-server-ctl restart before the last attempt just in case any services weren't running properly, even though the status command did show everything was up.

@stevendanna
Copy link
Contributor

stevendanna commented Jul 19, 2020 •
edited
Loading

A 504 error message typically means that the chef-server itself is having some sort of problem serving requests, either because of a problem with a particular service or because the server itself is overloaded.

The place to start investigating this would be to investigate the chef-server logs with chef-server-ctl tail or by creating a log bundle that you can share with Chef Support chef-server-ctl gather-logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@stevendanna @marcparadise @nathan-lochala @kishorerc @amcappelli @nicknameyu @mithujose @MichaelRolandD @karalov