- the script itself is wrong, there's a typo in it (missing "$" in the "for" loop)
- apparently something is preventing lsof to know about the unix sockets used by the ovn-northd service
While the first issue is easy to correct, the second one is a bit trickier.
We can see the following lsof output:
()[root@undercloud /]# lsof -c ovn-northd -Ua
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ovn-north 8 root 4u unix 0xffff9ac671751c00 0t0 753132 socket
ovn-north 8 root 8u unix 0xffff9ac671752000 0t0 753134 /var/run/openvswitch/ovn-northd.8.ctl
ovn-north 8 root 9u unix 0xffff9ac671750400 0t0 753135 socket
ovn-north 8 root 10u unix 0xffff9ac671756000 0t0 753136 socket
This shows some "socket", but without pointing to the actual files.
All the pipe and socket are in red, usually meaning "broken symlink", although for this kind of things I'm not sure it's the same meaning.
Is there a way to ensure that ovn-northd thingy is actually working as expected? The running command is pointing the sockets, but lsof doesn't show that:
/usr/bin/ovn-northd -vconsole:emer -vsyslog:err -vfile:info --ovnnb-db=unix:/run/openvswitch/ovnnb_db.sock --ovnsb-db=unix:/run/openvswitch/ovnsb_db.sock [...]
Soooo. I've taken some more time into this issue.
There are a couple of things:
- the script itself is wrong, there's a typo in it (missing "$" in the "for" loop)
- apparently something is preventing lsof to know about the unix sockets used by the ovn-northd service
While the first issue is easy to correct, the second one is a bit trickier.
We can see the following lsof output: openvswitch/ ovn-northd. 8.ctl
()[root@undercloud /]# lsof -c ovn-northd -Ua
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ovn-north 8 root 4u unix 0xffff9ac671751c00 0t0 753132 socket
ovn-north 8 root 8u unix 0xffff9ac671752000 0t0 753134 /var/run/
ovn-north 8 root 9u unix 0xffff9ac671750400 0t0 753135 socket
ovn-north 8 root 10u unix 0xffff9ac671756000 0t0 753136 socket
This shows some "socket", but without pointing to the actual files.
I tried to go directly for the /proc/, and here's the thing: openvswitch/ ovn-northd. log h/ovn-northd. pid
()[root@undercloud /]# ls /proc/8/fd -l
total 0
lrwx------. 1 root root 64 Apr 16 09:18 0 -> /dev/null
l-wx------. 1 root root 64 Apr 16 09:18 1 -> pipe:[759993]
lrwx------. 1 root root 64 Apr 16 09:18 10 -> socket:[753136]
l-wx------. 1 root root 64 Apr 16 09:18 2 -> pipe:[759994]
l-wx------. 1 root root 64 Apr 16 09:18 3 -> /var/log/
lrwx------. 1 root root 64 Apr 16 09:18 4 -> socket:[753132]
lrwx------. 1 root root 64 Apr 16 09:18 5 -> /run/openvswitc
lr-x------. 1 root root 64 Apr 16 09:18 6 -> pipe:[753133]
l-wx------. 1 root root 64 Apr 16 09:18 7 -> pipe:[753133]
lrwx------. 1 root root 64 Apr 16 09:18 8 -> socket:[753134]
lrwx------. 1 root root 64 Apr 16 09:18 9 -> socket:[753135]
All the pipe and socket are in red, usually meaning "broken symlink", although for this kind of things I'm not sure it's the same meaning.
Is there a way to ensure that ovn-northd thingy is actually working as expected? The running command is pointing the sockets, but lsof doesn't show that: db=unix: /run/openvswitc h/ovnnb_ db.sock --ovnsb- db=unix: /run/openvswitc h/ovnsb_ db.sock [...]
/usr/bin/ovn-northd -vconsole:emer -vsyslog:err -vfile:info --ovnnb-
Cheers,
C.