{"message":"not able to send command"} about bngblaster-controller HOT 8 CLOSED

This means that socket communication between Blaster and Controller failed but I'm actually unable to reproduce this with those version. You can enter the test directory manually and execute the command to see if the issue is here:

cd /var/bngblaster/start-single-dualstack-iana-dhcp-iapd-dhcp-ipoe-dhcpv4-nat-qinq-qinq/
sudo bngblaster-cli run.sock session-counters

from bngblaster-controller.

Which BNG Blaster version is used?

from bngblaster-controller.

Which BNG Blaster version is used?

bngblaster-0.8.41-ubuntu-22.04_amd64.deb

from bngblaster-controller.

Just a quick ping! Any thing can be done from my side to identify what could be wrong here?

from bngblaster-controller.

In the cases where this error happens the directory listing is as follows:

# ls
config.json  run.json  run.log  run.pcap  run.pid  run.s  run.stderr  run.stdout

The socket name is just run.s. I can use the command given on run.s and getting expected output. In the cases where it's working as expected, the name is run.sock:

# ls
config.json  run.json  run.log  run.pcap  run.pid  run.sock  run.stderr  run.stdout

from bngblaster-controller.

What is your base operating system (ubuntu 22.04, ...)?

The file is actually handover as argument -S run.sock to the BNG Blaster:

The BNG Blaster is than using this filename here to open the socket:

https://github.com/rtbrick/bngblaster/blob/3b9bf5657355f53e6ee0e523a305f736ee3cd658/code/bngblaster/src/bbl_ctrl.c#L510

You should see a log message to verify the path is given correctly.

https://github.com/rtbrick/bngblaster/blob/3b9bf5657355f53e6ee0e523a305f736ee3cd658/code/bngblaster/src/bbl_ctrl.c#L541C1-L542C1

I never seen such an issue, but may be caused by your long instance name. Maybe you can try with a much shorter instance name:

start-single-dualstack-iana-dhcp-iapd-dhcp-ipoe-dhcpv4-nat-qinq-qinq <<<< maybe to long

from bngblaster-controller.

What is your base operating system (ubuntu 22.04, ...)?

Yes, Ubuntu 22.04.4 LTS

start-single-dualstack-iana-dhcp-iapd-dhcp-ipoe-dhcpv4-nat-qinq-qinq <<<< maybe to long

Yes, will attempt that and let you know.

from bngblaster-controller.

After reducing the instance name to short string, this issue has not been reproduced so far. I think this ticket can be closed. I will get back if this happens again in future.

Thanks for your support!

from bngblaster-controller.