Bug 44809 - The container for 4.1/tecart=4.5.1 could not be started!
The container for 4.1/tecart=4.5.1 could not be started!
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 18:54 CEST by Florian Best
Modified: 2020-07-03 20:51 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017061321000055
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2017-06-16 18:54:11 CEST
Version: 4.2-0 errata29 (Lesum)

The container for 4.1/tecart=4.5.1 could not be started!

docker logs 5896c3e6c48f7c5dd3a4bedbd772ba121a9c745002643d652750ee604df96d52:

dockerd logs:
-- Logs begin at So 2017-06-11 06:32:57 CEST, end at Di 2017-06-13 02:05:53 CEST. --
Jun 13 01:56:05 s1 dockerd[1112]: time="2017-06-13T01:56:05.01363005+02:00" level=warning msg="containerd: unable to save
5acfdce0c498ec2f9ce928d9247e0362b278c1e60720eb346b94e7c709675854:1237e30c9c01560c9d959c08e0dee353ae4122657cc5876a1e66e89394fe2b04 starttime: open /proc/31288/stat: no such file or
directory"
Jun 13 01:56:05 s1 dockerd[1112]: time="2017-06-13T01:56:05.135548462+02:00" level=info msg="containerd:
5acfdce0c498ec2f9ce928d9247e0362b278c1e60720eb346b94e7c709675854:1237e30c9c01560c9d959c08e0dee353ae4122657cc5876a1e66e89394fe2b04 (pid 31288) has become an orphan, killing it"
Jun 13 01:56:34 s1 dockerd[1112]: time="2017-06-13T01:56:34.047003125+02:00" level=info msg="Container 5acfdce0c498ec2f9ce928d9247e0362b278c1e60720eb346b94e7c709675854 failed to
exit within 10 seconds of signal 15 - using the force"
Jun 13 01:58:02 s1 dockerd[1112]: time="2017-06-13T01:58:02.684811016+02:00" level=error msg="Handler for POST
/v1.24/containers/cdb65483f3e69679765055cb62c3664e01da90d22051d9350720eb19ffc7a547/stop returned error: Container cdb65483f3e69679765055cb62c3664e01da90d22051d9350720eb19ffc7a547
is already stopped"

docker inspect:
{u'Status': u'created', u'Pid': 0, u'OOMKilled': False, u'Dead': False, u'Paused': False, u'Running': False, u'FinishedAt': u'0001-01-01T00:00:00Z', u'Restarting': False, u'Error':
u'', u'StartedAt': u'0001-01-01T00:00:00Z', u'ExitCode': 0}
{u'Data': {u'MergedDir': u'/var/lib/docker/overlay/5e798b4568117ff84b772d88f05a67bbb0e9b0a17d1278cc5f3e9e136723fa4f/merged', u'WorkDir':
u'/var/lib/docker/overlay/5e798b4568117ff84b772d88f05a67bbb0e9b0a17d1278cc5f3e9e136723fa4f/work', u'LowerDir':
u'/var/lib/docker/overlay/03567bff567f980fda7c404debdc83ebe574e3ee08f1420ea265eb8113e50655/root', u'UpperDir':
u'/var/lib/docker/overlay/5e798b4568117ff84b772d88f05a67bbb0e9b0a17d1278cc5f3e9e136723fa4f/upper'}, u'Name': u'overlay'}
Comment 1 Dirk Wiesenthal univentionstaff 2017-07-03 11:34:55 CEST
Unfortunately, this traceback is not useful. Closing it; instead we should improve the traceback further.
Comment 2 Florian Best univentionstaff 2017-11-10 15:37:04 CET
(In reply to Dirk Wiesenthal from comment #1)
> Unfortunately, this traceback is not useful. Closing it; instead we should
> improve the traceback further.

Then use this bug to do it.
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:51:54 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.