Project

General

Profile

Actions
Copy link

Bug #5959

closed

Failed Jobs on 5/7 (Docker issues?)

Added by Bryan Cosca almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-

Description

From qr1hi-8i9sb-bfc0bxbl6tuyd1a, qr1hi-8i9sb-4jqk0i8zsma5sma

stderr time="2015-05-07T23:15:49Z" level=fatal msg="Post http:///var/run/docker.sock/v1.18/containers/cd335b5b7875ddb10ce64bbe2d099ad2db3ad408feb530ac6ea58631dc62f9cf/wait: write unix /var/run/docker.sock: broken pipe. Are you trying to connect to a TLS-enabled daemon without TLS?"

From qr1hi-8i9sb-k866luby319hnc1

It looked like it just released the job allocation with tasks still to do?

From qr1hi-8i9sb-qxh3vk1agmqe0mi

stderr run-command: terminating on signal 15
stderr time="2015-05-07T22:56:37Z" level=fatal msg="Error response from daemon: engine is shutdown"

Related issues

Is duplicate of Arvados - Bug #5956: [Deployment] Docker configuration changes restart Docker on compute nodes, interrupting running jobsDuplicate05/07/2015Actions
Actions
Copy link
 #1

Updated by Peter Amstutz almost 9 years ago

  • Target version set to Bug Triage
Actions
Copy link
 #2

Updated by Brett Smith almost 9 years ago

  • Status changed from New to Closed
  • Target version deleted (Bug Triage)

Duplicate of #5956.

Actions
Copy link

Also available in: Atom PDF