Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collector/Kafka communication issue ? #85

Open
monimail opened this issue Apr 25, 2018 · 0 comments
Open

Collector/Kafka communication issue ? #85

monimail opened this issue Apr 25, 2018 · 0 comments

Comments

@monimail
Copy link

Hello everyone,

I have set up a test of SNAS on my server using the multi-container approach. I followed all the steps on the website, even copy/pasting the commands to run all docker containers.

However, while the router and the collector can communicate without problem, the collector seems to be unable to contact the kafka container. I am getting the following log entries on the collector container after a while :

2018-04-25T12:16:38.280170 | ERROR    | produce            | rtr=xx.xx.xx.xx: Failed to produce message: Local: Queue full
2018-04-25T12:16:38.380402 | ERROR    | send_bmp_raw       | rtr=xx.xx.xx.xx: Failed to produce bmp raw message: Local: Queue full

Again I did no specific configuration. I just ran the following commands in this order :

docker run -d --name=openbmp_mysql -e KAFKA_FQDN=localhost -e MEM=15 \
     -v /var/openbmp/mysql:/data/mysql -v /var/openbmp/config:/config \
     -p 3306:3306 -p 8001:8001 \
     openbmp/mysql

docker run -d \
     --name=openbmp_kafka \
     -e KAFKA_FQDN=localhost \
     -v /var/openbmp/kafka:/data/kafka \
     -p 2181:2181 -p 9092:9092 \
     openbmp/kafka

docker run -d --name=openbmp_collector -e KAFKA_FQDN=localhost \
     -v /var/openbmp/config:/config \
     -p 5000:5000 \
     openbmp/collector

All the directory structure is created as written on SNAS website.

I have checked the logs of all other containers and no one seems to complain about anything.
Thus I’m quite out of ideas to fix this issue.

Any help will be greatly appreciated.

Thanks in advance !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant