Replies: 6 comments 11 replies
-
Hello team, I'm having the same problems and looking for the installation guide. I searched the logs and found the following. I was expecting Manageiq to manage this certificate issue. Jun 16 19:32:32 manageiq.test.info kafka-server-start.sh[1452]: [2024-06-16 19:32:32,879] INFO [Controller id=0, targetBrokerId=0] Client requested connection close from node 0 (org.apache.kafka.clients.NetworkClient) |
Beta Was this translation helpful? Give feedback.
-
The errors in the logs indicate that the hostname entered during messaging configuration does not match the hostname of the appliance. Have you set the hostname and added it to /etc/hosts on the appliance? |
Beta Was this translation helpful? Give feedback.
-
Appliance Hostname
|
Beta Was this translation helpful? Give feedback.
-
Hi @erwinb3 and @kodkurdu, messaging must be configured with a FQDN hostname that is not localhost/127.0.0.1. From the docs:
For example:
and I should be able to ping the ip/hostname
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I applied same config on manageiq-morphy and it runs. |
Beta Was this translation helpful? Give feedback.
-
First of all thanks for the work done to achieve the new update Quinteros-1.
Unfortunately we cannot get the new version Quinteros-1 to run on the VMware environment, the old version (manageiq-vsphere-petrosian) works without any problems.
Simple setup:
-1 Configure Network settings
-5 Configure application > 1. Create key > 1. Create Internal Database> 3. make no messaging changes> 1. Database disk /dev/sdb: 153600mb> Should run as standalone database? No
Region 44
After this the service should start but it gets stuck on starting manageiq
services:
kafka failed to start
"top(1) data collection" failed to start
https://www.manageiq.org/docs/reference/latest/installing_on_vmware_vsphere/
Beta Was this translation helpful? Give feedback.
All reactions