Announcements
This site is in read only until July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Another edgemicro.sock 'no such file or directory' microgateway docker question

adeger
New Member

I'm hoping someone here has seen or can otherwise help me with this problem. When we try to start a version of the microgateway we get no functionality due to the problem "no such file or directory, access '/home/node/edgemicro.sock'" (the stack trace is below).

My understanding is that this directory is really only used in clustered container setups so I'm first wondering if we even need this (now) and if there's a way to not require it.

My understanding is that this directory is really only used in clustered container setups so I'm first wondering if we even need this (now) and if there's a way to not require it.

Note that I don't know if the message about not having access to apigee-access is a root cause, nor the messages about unset environment variables EDGEMICRO_LOCAL and EDGEMICRO_LOCAL_PROXY nor how or where they should be set.

Things I've tried:

1) Reinstallations of the docker image and

2) Restarting Docker (then restarting container)

3) Creating the 'node' user on the host and chown-ing the directory to that user

4) Starting container as root and another user in the docker group

4a) In all cases above the directory edgemicro.sock is not created

5) Creating an external docker volume mapping (outside->inside) /home/user/edgemicro.sock -> /home/node/edgemicro.sock The directory edgemicro.sock is always created but the app in the contaner fails to start and the 'docker logs' command for the container shows messages like:

Edgemicro seems to be already running.

If the server is not running, it might because of incorrect shutdown of the prevous start.

Try removing /home/node/edgemicro.sock and start again

6) Reinstallations of the docker image and container re-running 🙂

7) Finding and grokking as much salient documentation as seems related...and this forum

Here are some environment facts:

Microgateway version: latest

Docker version 1.13.1, build 07f3374/1.13.1

CentOS Linux release 7.5.1804 (Core), selinux running in Permissive mode

Note that I know just enough Docker to be dangerous and am pretty new to the microgateway too so I have no ego on this matter.

======================== Output from 'docker logs <microgateway container name>' command: ===================

Tue, 05 Feb 2019 15:32:34 GMT apigee Operating without access to apigee-access
2019-02-05T15:32:34.406Z start EDGEMICRO_LOCAL: undefined
2019-02-05T15:32:34.407Z start EDGEMICRO_LOCAL_PROXY: undefined
2019-02-05T15:32:34.408Z microgateway Error: ENOENT: no such file or directory, access '/home/node/edgemicro.sock'
    at Object.fs.accessSync (fs.js:301:11)
    at Gateway.start (/home/node/edgemicro-oneapi/node_modules/edgemicro/cli/lib/gateway.js:28:12)
    at Command.commander.command.option.option.option.option.option.option.option.option.option.option.option.option.option.description.action (/home/node/edgemicro-oneapi/node_modules/edgemicro/cli/cmd.js:243:21)
    at Command.listener (/home/node/edgemicro-oneapi/node_modules/commander/index.js:315:8)
    at emitTwo (events.js:126:13)
    at Command.emit (events.js:214:7)
    at Command.parseArgs (/home/node/edgemicro-oneapi/node_modules/commander/index.js:654:12)
    at Command.parse (/home/node/edgemicro-oneapi/node_modules/commander/index.js:474:21)
    at setup (/home/node/edgemicro-oneapi/node_modules/edgemicro/cli/cmd.js:564:15)
    at Object.<anonymous> (/home/node/edgemicro-oneapi/node_modules/edgemicro/cli/edgemicro:49:21)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Function.Module.runMain (module.js:694:10)
0 21 1,152
21 REPLIES 21