Attaching to docker_openbmp_kafka_1, docker_openbmp_mysql_1, docker_openbmp_collector_1
openbmp_kafka_1 | rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
openbmp_kafka_1 | rsyslogd: activation of module imklog.so failed [v8.31.0 try http://www.rsyslog.com/e/2145 ]
openbmp_kafka_1 | sed: /usr/local/kafka/config/server.properties: No such file or directory
openbmp_collector_1 | /usr/sbin/run: line 35: /etc/default/openbmpd: No such file or directory
openbmp_kafka_1 | sed: /usr/local/kafka/config/server.properties: No such file or directory
openbmp_collector_1 | * Starting enhanced syslogd rsyslogd
openbmp_kafka_1 | /usr/sbin/run: line 55: bin/zookeeper-server-start.sh: No such file or directory
openbmp_mysql_1 | Installing MariaDB/MySQL system tables in '/data/mysql' ...
openbmp_collector_1 | ...done.
openbmp_collector_1 | sed: can't read /usr/etc/openbmp/openbmpd.conf: No such file or directory
openbmp_collector_1 | sed: can't read /usr/etc/openbmp/openbmpd.conf: No such file or directory
openbmp_collector_1 | /usr/sbin/run: line 73: /usr/bin/openbmpd: No such file or directory
docker_openbmp_collector_1 exited with code 127
openbmp_mysql_1 | OK
openbmp_mysql_1 |
openbmp_mysql_1 | To start mysqld at boot time you have to copy
openbmp_mysql_1 | support-files/mysql.server to the right place for your system
openbmp_mysql_1 |
openbmp_mysql_1 |
openbmp_mysql_1 | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
openbmp_mysql_1 | To do so, start the server, then issue the following commands:
openbmp_mysql_1 |
openbmp_mysql_1 | '/usr/bin/mysqladmin' -u root password 'new-password'
openbmp_mysql_1 | '/usr/bin/mysqladmin' -u root -h 8496e6cd7948 password 'new-password'
openbmp_mysql_1 |
openbmp_mysql_1 | Alternatively you can run:
openbmp_mysql_1 | '/usr/bin/mysql_secure_installation'
openbmp_mysql_1 |
openbmp_mysql_1 | which will also give you the option of removing the test
openbmp_mysql_1 | databases and anonymous user created by default. This is
openbmp_mysql_1 | strongly recommended for production servers.
openbmp_mysql_1 |
openbmp_mysql_1 | See the MariaDB Knowledgebase at http://mariadb.com/kb or the
openbmp_mysql_1 | MySQL manual for more instructions.
openbmp_mysql_1 |
openbmp_mysql_1 | You can start the MariaDB daemon with:
openbmp_mysql_1 | cd '/usr' ; /usr/bin/mysqld_safe --datadir='/data/mysql'
openbmp_mysql_1 |
openbmp_mysql_1 | You can test the MariaDB daemon with mysql-test-run.pl
openbmp_mysql_1 | cd '/usr/mysql-test' ; perl mysql-test-run.pl
openbmp_mysql_1 |
openbmp_mysql_1 | Please report any problems at http://mariadb.org/jira
openbmp_mysql_1 |
openbmp_mysql_1 | The latest information about MariaDB is available at http://mariadb.org/.
openbmp_mysql_1 | You can find additional information about the MySQL part at:
openbmp_mysql_1 | http://dev.mysql.com
openbmp_mysql_1 | Consider joining MariaDB's strong and vibrant community:
openbmp_mysql_1 | https://mariadb.org/get-involved/
openbmp_mysql_1 |
openbmp_mysql_1 | * Starting MariaDB database server mysqld
openbmp_mysql_1 | ...done.
openbmp_kafka_1 | /usr/sbin/run: line 57: bin/kafka-server-start.sh: No such file or directory
docker_openbmp_kafka_1 exited with code 127
openbmp_mysql_1 | * Stopping MariaDB database server mysqld
openbmp_mysql_1 | ...fail!
openbmp_mysql_1 | * Starting MariaDB database server mysqld
openbmp_mysql_1 | ...done.
openbmp_mysql_1 | -----| RUNNING |------
openbmp_mysql_1 | Error: Unable to access jarfile /usr/local/openbmp-mysql-consumer.jar
openbmp_mysql_1 | Error: Unable to access jarfile /usr/local/openbmp-mysql-consumer.jar
openbmp_mysql_1 | Error: Unable to access jarfile /usr/local/openbmp-mysql-consumer.jar
openbmp_mysql_1 | Error: Unable to access jarfile /usr/local/openbmp-mysql-consumer.jar
openbmp_mysql_1 | Error: Unable to access jarfile /usr/local/openbmp-mysql-consumer.jar
openbmp_mysql_1 | Error: Unable to access jarfile /usr/local/openbmp-mysql-consumer.jar
