🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Error while running the VMR using docker on Ubuntu 18
Hi,
I am facing this issue while starting up the VMR on Ubuntu 18.
Has anyone faced and fixed this issue?
Starting VMR Docker Container: Wed Oct 9 06:48:32 UTC 2019
SolOS Version: soltr_9.3.0.22
ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA ED25519
** Unable to raise event; rc(would block)**
Best Answer
-
Thanks for the info.
The second "docker ps -a" shows that the docker container started 15 minutes before, and exited 4 minutes before the docker ps command, with exit status 2. Exit status 2 is a general purpose error code for our product.
Please run the following to retrieve the shutdown message from the container:docker cp solace:/var/lib/solace/diags/shutdownMessage .
Please run the following to get another log file:
docker cp solace:/usr/sw/loads/currentload/.lastRespawnsAction .
Please return those files. Thanks!
Because you are running Ubuntu, with AppArmor, try adding the following to the
docker runcommand, to give your container more privileges--security-opt apparmor:unconfined
Some errors related to Solace are generated by the Linux kernel in the regular log files in
/var/log. Look for things that happen at the time of the exit, approximately.
Examples:/var/log/syslog- general errors/var/log/kern.log- various kernel errors, including Out Of Memory (OOMkills) where the kernel killed the process, rather than something inside the container if it ran out of memory.
Some processes that run in our container, and might show up in log files, are:
- multipathd
- solsyslogtee
- solacedaemon
- watchdog
- dataplane
- controlplane
- smrp
- trmmanager
- msgbusadapter
- solcachemgr
Of course 10-50 lines of context before and after is always helpful.
We aren't sure what specific errors to look for here, sorry. However, those logs should help.6
![[Deleted User]](https://w1.vanillicon.com/v2/13b3b02c82d9a93ae3f4f73efc1e4034.svg)
Answers
-
Thanks for asking.
I am checking with some people with experience in this area.0 -
Are you installing a Docker image directly, the QCOW image, the OVA image, or something else?
Also, if you have a longer log file of the output, please attach it as a file.0 -
I am told that "Unable to raise event; rc(would block)" is an error message from something that runs in the startup phase before it is ready. It is run again later, so that error does not indicate a problem.
Can you please post, preferably as an attached file:
- The output of:
docker ps - The output of:
docker inspect (container name) - The output of:
docker logs (container name) - The actual command line you used to create the container, if you have it.
Thanks!
0 - The output of:
-
docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
57e182ada568 solace/solace-pubsub-standard "/usr/sbin/boot.sh" 7 minutes ago Up 6 minutes 0.0.0.0:8080->8080/tcp, 2222/tcp, 0.0.0.0:55555->55555/tcp solacedocker logs -f solace
Host Boot ID: 36e65621-a5da-430b-88df-1d360b3cb64a
Starting VMR Docker Container: Thu Oct 10 00:26:25 UTC 2019
SolOS Version: soltr_9.3.0.22
ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA ED25519
Unable to raise event; rc(would block)docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
57e182ada568 solace/solace-pubsub-standard "/usr/sbin/boot.sh" 15 minutes ago Exited (2) 4 minutes ago solacedocker run -d -p 8080:8080 -p 55555:55555 --shm-size=3g --env username_admin_globalaccesslevel=admin --env username_admin_password=admin --name=solace solace/solace-pubsub-standard
0 -
Thanks for the info.
The second "docker ps -a" shows that the docker container started 15 minutes before, and exited 4 minutes before the docker ps command, with exit status 2. Exit status 2 is a general purpose error code for our product.
Please run the following to retrieve the shutdown message from the container:docker cp solace:/var/lib/solace/diags/shutdownMessage .
Please run the following to get another log file:
docker cp solace:/usr/sw/loads/currentload/.lastRespawnsAction .
Please return those files. Thanks!
Because you are running Ubuntu, with AppArmor, try adding the following to the
docker runcommand, to give your container more privileges--security-opt apparmor:unconfined
Some errors related to Solace are generated by the Linux kernel in the regular log files in
/var/log. Look for things that happen at the time of the exit, approximately.
Examples:/var/log/syslog- general errors/var/log/kern.log- various kernel errors, including Out Of Memory (OOMkills) where the kernel killed the process, rather than something inside the container if it ran out of memory.
Some processes that run in our container, and might show up in log files, are:
- multipathd
- solsyslogtee
- solacedaemon
- watchdog
- dataplane
- controlplane
- smrp
- trmmanager
- msgbusadapter
- solcachemgr
Of course 10-50 lines of context before and after is always helpful.
We aren't sure what specific errors to look for here, sorry. However, those logs should help.6 -
This one made the trick: --security-opt apparmor:unconfined
Thanks a lot0 -
Hi Thierry,
Happy to help.
We have a bug to fix some things in those docs, and this info for Ubuntu will go in there.
Thanks for letting us know. And I think I will ask IT for an extra machine with Ubuntu on it. (grin)0 -
Actually, kudos to the team in Solace Singapore!
0
