Open Stack

On Jun 30, 2016, at 4:07 PM, Turbo Fredriksson wrote:

Stracing the running process, I noticed this:

connect(8, {sa_family=AF_LOCAL, sun_path="/var/lib/neutron/metadata_proxy"}, 33) = -1 ENOENT (No such file or directory)

Creating the socket manually, I instead get "Connection refused".
So whatever is/was supposed to create that socket, isn't running.

What else than the neutron-ns-metadata-proxy are supposed to create
this?

bladeA01:~# ps | grep meta
 4946 ?        S      0:00 /usr/bin/python2.7 /usr/bin/neutron-ns-metadata-proxy --pid_file=/var/lib/neutron/external/pids/39c01b3c-7709-4e4b-9455-60daf31f2b1e.pid --metadata_proxy_socket=/var/lib/neutron/metadata_proxy --router_id=39c01b3c-7709-4e4b-9455-60daf31f2b1e --state_path=/var/lib/neutron --metadata_port=80 --metadata_proxy_user=120 --metadata_proxy_group=125 --verbose --log-file=neutron-ns-metadata-proxy-39c01b3c-7709-4e4b-9455-60daf31f2b1e.log --log-dir=/var/log/neutron
-- 
Att tänka innan man talar, är som att torka sig i röven
innan man skiter.
- Arne Anka