Enketo cannot connect with server after upgrade to v1.5.1

I have a similar issue where Enketo fails to connect to the server even after having succeeded with upgrade to v1.5.1.

By reviewing posts and the documentation, I think its possible to solve the issue by running these steps rightly (I could have done it wrongly);

Now, run nano /etc/docker/daemon.json to make those nameservers and, optionally, the Google DNS (8.8.8.8) as a fallback available to Docker. Put the following in the daemon.json file.

{
"dns": ["", "", "8.8.8.8"]
}

Kindly guide me on the directory I have to be to run nano /etc/docker/daemon.json ?

No need to change directories. The nano /etc/docker/daemon.json command will automatically open the file in the /etc/docker/ directory.

1 Like

Dear @yanokwa ,

Thank you very much for the guidance.
I have run the command and succeeded saving the daemon.json file. I also ran docker-compose stop from the central directory where it succeeds.

But on running systemctl restart docker, I get an error message below;
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

This is the point where I have always failed to continue to the final command.
Kindly advise.

I ran systemctl restart docker from the central directory. Was this right?

Were you able to get the IP addresses in the first step and actually put them in quotes?

Have you tried running those commands? What do they tell you?

1 Like

Yes @LN ,

I was able to get the IP addresses and put them in quotes;

{
"dns": ["67.207.67.2", "67.207.67.3", "8.8.8.8"]
}

The file was also successfully saved.

I have just tried those now; systemctl status docker.service returns the following:

● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2022-07-01 01:13:05 UTC; 13h ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 60320 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, sta>
   Main PID: 60320 (code=exited, status=1/FAILURE)

Jul 01 01:13:03 chanjooo systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 01 01:13:03 chanjooo systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 01 01:13:03 chanjooo systemd[1]: Failed to start Docker Application Container Engine.
Jul 01 01:13:05 chanjooo systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jul 01 01:13:05 chanjooo systemd[1]: Stopped Docker Application Container Engine.
Jul 01 01:13:05 chanjooo systemd[1]: docker.service: Start request repeated too quickly.
Jul 01 01:13:05 chanjooo systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 01 01:13:05 chanjooo systemd[1]: Failed to start Docker Application Container Engine.

--> It also does not hand back the control to enter more commands. I have to close console and come back

And journalctl -xe returns the following;

-- The job identifier is 2.
Jul 01 14:25:21 chanjooo systemd[1]: Started User Manager for UID 0.
-- Subject: A start job for unit user@0.service has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit user@0.service has finished successfully.
-- 
-- The job identifier is 2362.
Jul 01 14:25:21 chanjooo systemd[1]: Started Session 58 of user root.
-- Subject: A start job for unit session-58.scope has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit session-58.scope has finished successfully.
-- 
-- The job identifier is 2444.
Jul 01 14:25:21 chanjooo systemd[68045]: Reached target Main User Target.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 1.
Jul 01 14:25:21 chanjooo systemd[68045]: Startup finished in 146ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The user manager instance for user 0 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
-- 
-- Startup of the manager took 146444 microseconds.
lines 1499-1533/1533 (END)

--> Also does not hand back control

What could be the next step?

The reason Docker was not start was that the daemon.json had this in it:

{
    "dns": ["<1.2.3.4>", "<4.5.6.7>", "8.8.8.8"]
}

It should instead have

{
    "dns": ["1.2.3.4", "4.5.6.7", "8.8.8.8"]
}

I will update the docs to make this more clear.

1 Like

Thanks very much.
The issue is well solved.

Continually grateful for the support on this forum.
And thank you core team.

Thanks @yanokwa and @LN
Joseph

2 Likes