Bug 50029 - App Center should check availability of local port before configuring docker port forwarding
App Center should check availability of local port before configuring docker ...
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-20 08:58 CEST by Ingo Steuwer
Modified: 2019-08-20 08:58 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Steuwer univentionstaff 2019-08-20 08:58:29 CEST
In a customized environment the installation of the admin dashboard app fails. The error in the App Center UMC module is "Error: None".

Reading the logfiles my understanding is, that the app uses port 3000 for port forwarding between host and docker container. This port is already in use by a service that is not installed using the App Center (port 3000 is used by some GIT implementations, in this case it is used by "vdr").

The App Center should test whether ports are in used by other services and at least report a human readable error message.



From the logfiles:


# appcenter.log
  1470 actions.start                    19-08-20 08:32:38 [ WARNING]: Job for docker-app-admin-dashboard.service failed because the control process exited with error code.
  1470 actions.start                    19-08-20 08:32:38 [ WARNING]: See "systemctl status docker-app-admin-dashboard.service" and "journalctl -xe" for details.
  1470 actions.start                    19-08-20 08:32:38 [    INFO]: Starting docker-app-admin-dashboard (via systemctl): docker-app-admin-dashboard.service failed!
  1470 actions.start                    19-08-20 08:32:39 [   DEBUG]: /etc/init.d/docker-app-admin-dashboard returned with 1


# systemctl  status docker-app-admin-dashboard.service -l 20
Failed to get unit for PID 20: PID 20 does not belong to any loaded unit.
● docker-app-admin-dashboard.service
   Loaded: not-found (Reason: No such file or directory)
   Active: failed (Result: exit-code) since Tue 2019-08-20 08:32:38 CEST; 13min ago
      CPU: 856ms


# journalctl -xe
Aug 20 08:32:36 c3po systemd[1]: Starting LSB: Start the Container for admin-dashboard...
Aug 20 08:32:38 c3po docker-app-admin-dashboard[3490]: Starting admin-dashboard Container a2027d2230eb1b5206d5a5cf7e4fbc30e2901cd408f70055bdd3b7eda584f22f ...Error respons
Aug 20 08:32:38 c3po systemd[1]: docker-app-admin-dashboard.service: Control process exited, code=exited status=1
Aug 20 08:32:38 c3po systemd[1]: Failed to start LSB: Start the Container for admin-dashboard.
Aug 20 08:32:38 c3po systemd[1]: docker-app-admin-dashboard.service: Unit entered failed state.
Aug 20 08:32:38 c3po systemd[1]: docker-app-admin-dashboard.service: Failed with result 'exit-code'.






Aug 20 08:32:33 c3po dockerd[2158]: time="2019-08-20T08:32:33.658733099+02:00" level=warning msg="failed to retrieve docker-init version: unknown output format: tini version 0.13.0\n"
Aug 20 08:32:36 c3po systemd[1]: Starting LSB: Start the Container for admin-dashboard...
-- Subject: Unit docker-app-admin-dashboard.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker-app-admin-dashboard.service has begun starting up.
Aug 20 08:32:37 c3po kernel: docker0: port 3(veth18e8862) entered blocking state
Aug 20 08:32:37 c3po kernel: docker0: port 3(veth18e8862) entered disabled state
Aug 20 08:32:37 c3po kernel: device veth18e8862 entered promiscuous mode
Aug 20 08:32:37 c3po kernel: IPv6: ADDRCONF(NETDEV_UP): veth18e8862: link is not ready
Aug 20 08:32:37 c3po systemd-udevd[313]: Network interface NamePolicy= disabled on kernel command line, ignoring.
Aug 20 08:32:37 c3po systemd-udevd[3526]: Could not generate persistent MAC address for veth90c61f5: No such file or directory
Aug 20 08:32:37 c3po systemd-udevd[3527]: Could not generate persistent MAC address for veth18e8862: No such file or directory
Aug 20 08:32:37 c3po dockerd[2158]: time="2019-08-20T08:32:37.583817820+02:00" level=warning msg="Failed to allocate and map port 3000-3000: Error starting userland proxy: listen tcp 0.0.0.0:3000: bind: address already in use"
Aug 20 08:32:37 c3po kernel: docker0: port 3(veth18e8862) entered disabled state
Aug 20 08:32:37 c3po kernel: device veth18e8862 left promiscuous mode
Aug 20 08:32:37 c3po kernel: docker0: port 3(veth18e8862) entered disabled state
Aug 20 08:32:38 c3po check_nrpe[3591]: Remote 192.168.1.22 accepted a Version 3 Packet
Aug 20 08:32:38 c3po dockerd[2158]: time="2019-08-20T08:32:38.878893652+02:00" level=error msg="Handler for POST /v1.26/containers/a2027d2230eb1b5206d5a5cf7e4fbc30e2901cd408f70055bdd3b7eda584f22f/restart returned error: Cannot restart container a2027d2230eb1b5206d5a5cf7e4fbc30e2901
Aug 20 08:32:38 c3po docker-app-admin-dashboard[3490]: Starting admin-dashboard Container a2027d2230eb1b5206d5a5cf7e4fbc30e2901cd408f70055bdd3b7eda584f22f ...Error response from daemon: Cannot restart container a2027d2230eb1b5206d5a5cf7e4fbc30e2901cd408f70055bdd3b7eda584f22f: drive
Aug 20 08:32:38 c3po systemd[1]: docker-app-admin-dashboard.service: Control process exited, code=exited status=1
Aug 20 08:32:38 c3po systemd[1]: Failed to start LSB: Start the Container for admin-dashboard.
-- Subject: Unit docker-app-admin-dashboard.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker-app-admin-dashboard.service has failed.
-- 
-- The result is failed.