got /var/run/cri-resmgr/cri-resmgr-agent.sock no such file issue

[jongwu]

My cri-resmgr version is
cri-resmgr version information:

• version: 0.8.4
• build: acee70b

I always get journal log related with cri-resmgr:

cri-resmgr[196816]: W: [ grpc ] [core]grpc: addrConn.createTransport failed to connect to {/var/run/cri-resmgr/cri-resmgr-agent.sock /var/run/cri-resmgr/cri-resmgr-agent.sock 0 }. Err: connection error: desc = "transport: Error while dialing dial unix /var/run/cri-resmgr/cri-resmgr-agent.sock: connect: no such file or directory". Reconnecting...

Yeah, there is really no that agent socket and I have never saw it ever. I think cri-resmgr has not created it.
And cri-resmgr doesn't work. When I start it with topolgy-aware plocy, the pod won't bind to numa node.

How to resolve this?

[klihub]

That is a warning , not an error. Unless you explicitly tell it not to, cri-resmgr will always try to connect to the agent socket and log that warning if it can't. you can get rid of that warning by disabling the agent (socket). IIRC, you can do this by setting the agent socket (--agent-socket command line option) to distabled or the empty string.