Layer7 API Management

When i run portal.sh, i see following error below. Please advice how this solved regarding docker.

=============================================================================

bash-4.2$ sudo ./portal.sh

Found docker version 17.09.0

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

===============================================

-bash-4.2$ systemctl status docker.service â docker.service - Docker Application Container Engine

   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

   Active: failed (Result: start-limit) since Wed 2018-01-03 20:21:49 PST; 1min 38s ago

     Docs: https://docs.docker.com

  Process: 4559 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)  Main PID: 4559 (code=exited, status=1/FAILURE)

Jan 03 20:21:49 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

Jan 03 20:21:49 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service failed.

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service holdoff time over, scheduling restart.

Jan 03 20:21:49 localhost.localdomain systemd[1]: start request repeated too quickly for docker.service Jan 03 20:21:49 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

Jan 03 20:21:49 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service failed.

====================================================================

-bash-4.2$ journalctl -xe

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service holdoff time over, scheduling restart.

Jan 03 20:21:49 localhost.localdomain systemd[1]: start request repeated too quickly for docker.service Jan 03 20:21:49 localhost.localdomain audispd[686]: node=localhost.localdomain type=SERVICE_START msg=audit(1515039709.24 Jan 03 20:21:49 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

-- Subject: Unit docker.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit docker.service has failed.

--

-- The result is failed.

Jan 03 20:21:49 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service failed.

Jan 03 20:21:49 localhost.localdomain audispd[686]: node=localhost.localdomain type=SERVICE_STOP msg=audit(1515039709.245 Jan 03 20:22:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=SYSCALL msg=audit(1515039737.725:2967 Jan 03 20:22:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=PROCTITLE msg=audit(1515039737.725:29 Jan 03 20:22:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=EOE msg=audit(1515039737.725:29679):

Jan 03 20:23:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=SYSCALL msg=audit(1515039797.726:2968 Jan 03 20:23:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=PROCTITLE msg=audit(1515039797.726:29 Jan 03 20:23:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=EOE msg=audit(1515039797.726:29680):

Jan 03 20:24:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=SYSCALL msg=audit(1515039857.727:2968 Jan 03 20:24:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=PROCTITLE msg=audit(1515039857.727:29 Jan 03 20:24:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=EOE msg=audit(1515039857.727:29681):

lines 1125-1147/1147 (END)

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service holdoff time over, scheduling restart.

Jan 03 20:21:49 localhost.localdomain systemd[1]: start request repeated too quickly for docker.service Jan 03 20:21:49 localhost.localdomain audispd[686]: node=localhost.localdomain type=SERVICE_START msg=audit(1515039709.245:29677): pid=1 uid=0 auid=4294967295 ses=42949 Jan 03 20:21:49 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

-- Subject: Unit docker.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit docker.service has failed.

--

-- The result is failed.

Jan 03 20:21:49 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Jan 03 20:21:49 localhost.localdomain systemd[1]: docker.service failed.

Jan 03 20:21:49 localhost.localdomain audispd[686]: node=localhost.localdomain type=SERVICE_STOP msg=audit(1515039709.245:29678): pid=1 uid=0 auid=4294967295 ses=429496 Jan 03 20:22:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=SYSCALL msg=audit(1515039737.725:29679): arch=c000003e syscall=159 success=yes exit= Jan 03 20:22:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=PROCTITLE msg=audit(1515039737.725:29679): proctitle="/usr/bin/vmtoolsd"

Jan 03 20:22:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=EOE msg=audit(1515039737.725:29679):

Jan 03 20:23:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=SYSCALL msg=audit(1515039797.726:29680): arch=c000003e syscall=159 success=yes exit= Jan 03 20:23:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=PROCTITLE msg=audit(1515039797.726:29680): proctitle="/usr/bin/vmtoolsd"

Jan 03 20:23:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=EOE msg=audit(1515039797.726:29680):

Jan 03 20:24:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=SYSCALL msg=audit(1515039857.727:29681): arch=c000003e syscall=159 success=yes exit= Jan 03 20:24:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=PROCTITLE msg=audit(1515039857.727:29681): proctitle="/usr/bin/vmtoolsd"

Jan 03 20:24:17 localhost.localdomain audispd[686]: node=localhost.localdomain type=EOE msg=audit(1515039857.727:29681):

Hello there. Are you running the Portal OVA, AWS instance or regular ESXi VM?

Can you send the output of these two commands:

• lsblk
• sudo cat /etc/docker/daemon.json

Regards,

ac

Hi Alan,

This is OVA 4.2 and uses ESXi VM.

-bash-4.2$ lsblk

NAME             MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT

fd0                2:0    1     4K  0 disk

sda                8:0    0 195.3G  0 disk

ââsda1             8:1    0     1G  0 part /boot

ââsda2             8:2    0    76G  0 part

â ââvg00-lv_root 253:0    0    40G  0 lvm  /

â ââvg00-lv_swap 253:1    0     4G  0 lvm 

â ââvg00-lv_var  253:2    0    16G  0 lvm  /var

â ââvg00-lv_tmp  253:3    0    16G  0 lvm  /tmp

ââsda3             8:3    0 118.3G  0 part

  ââappvg-apps   253:4    0   300G  0 lvm  /apps

sdb                8:16   0   200G  0 disk

ââsdb1             8:17   0   200G  0 part

  ââappvg-apps   253:4    0   300G  0 lvm  /apps

sr0               11:0    1  1024M  0 rom

-bash-4.2$ sudo cat /etc/docker/daemon.json

password for portal:

{

        "storage-driver": "devicemapper",

        "storage-opts": [

                "dm.directlvm_device=/dev/sda3",

                "dm.directlvm_device_force=true"

        ],

        "log-driver": "journald"

Regards

Karthik C

817-967-1383

Well, if this is the OVA then you shouldn't be having any Docker issue. Have you tried to restart docker several times or just once?

Yes, I have restarted several times but still I see the issue.

-bash-4.2$ systemctl restart docker.service

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to manage system services or units.

Authenticating as: portal

Password:

==== AUTHENTICATION COMPLETE ===

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

-bash-4.2$ systemctl restart docker.service

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to manage system services or units.

Authenticating as: portal

Password:

==== AUTHENTICATION COMPLETE ===

Job for docker.service failed because start of the service was attempted too often. See "systemctl status docker.service" and "journalctl -xe" for details.

To force a start use "systemctl reset-failed docker.service" followed by "systemctl start docker.service" again.

-bash-4.2$ systemctl restart docker.service

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to manage system services or units.

Authenticating as: portal

Password:

==== AUTHENTICATION COMPLETE ===

Job for docker.service failed because start of the service was attempted too often. See "systemctl status docker.service" and "journalctl -xe" for details.

To force a start use "systemctl reset-failed docker.service" followed by "systemctl start docker.service" again.

-bash-4.2$ systemctl reset-failed docker.service

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to manage system services or units.

Authenticating as: portal

Password:

==== AUTHENTICATION COMPLETE ===

Failed to reset failed state of unit docker.service: No such device or address

-bash-4.2$ systemctl start docker.service

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to manage system services or units.

Authenticating as: portal

Password:

==== AUTHENTICATION COMPLETE ===

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

Regards

Karthik C

817-967-1383

Looking at /etc/daemon.json, and the lsblk output, device /dev/sda3 does not exist.

I have come across this a number of times in my installations.  The easiest workaround is to allocate a new disk to the VM, use fdisk to create a primary partition on it, and then use lsblk to find the device (most likely /dev/sdb1).  Then change the content of daemon.json to match.  

If all is well, docker should now start.