Hello,
When starting HiveMQ service (/etc/init.d/hivemq restart), I see an error in the log file regarding the s3 bucket:
2023-03-17 13:32:44,163 ERROR - Configured bucket ‘hivemq’ doesn’t exist. Skipping initial discovery.
My bucket name is ‘hivemq-demo-rajiv’ but somehow picking up ‘hivemq’ - not sure why? Attached error log and s3 configuration files.
Appreciate any help - Thanks.
Best,
Rajiv
[root@ip-10-10-1-14 ~]# cat /opt/hivemq/extensions/hivemq-s3-cluster-discovery-extension/hivemq-s3-cluster-discovery-extension.xml
############################################################
S3 Bucket
############################################################
Region for the S3 bucket used by hivemq
see AWS service endpoints - AWS General Reference for a list of regions for S3
example: us-west-2
s3-bucket-region:us-east-1
Name of the bucket used by HiveMQ
s3-bucket-name:hivemq-demo-rajiv
[root@ip-10-10-1-14 ~]#
[root@ip-10-10-1-14 ~]# cat /opt/hivemq/log/hivemq.log
2023-03-17 13:32:40,219 INFO - Starting HiveMQ Enterprise Server
2023-03-17 13:32:40,222 INFO - HiveMQ version: 4.12.0
2023-03-17 13:32:40,222 INFO - HiveMQ home directory: /opt/hivemq
2023-03-17 13:32:40,223 INFO - Log Configuration was overridden by /opt/hivemq/conf/logback.xml
2023-03-17 13:32:40,557 INFO - Successfully loaded configuration from ‘/opt/hivemq/conf/config.xml’.
2023-03-17 13:32:40,615 WARN - Soft limit for open files (500000) is lower than the recommended limit (1000000). Please increase the open file limit to at least the recommended limit.
2023-03-17 13:32:40,615 WARN - Hard limit for open files (500000) is lower than the recommended limit (1000000). Please increase the open file limit to at least the recommended limit.
2023-03-17 13:32:40,618 INFO - This node’s ID is he9gs
2023-03-17 13:32:40,743 INFO - Clustering is enabled
2023-03-17 13:32:42,815 INFO - No valid license file found. Using trial license, restricted to 25 connections.
2023-03-17 13:32:43,254 INFO - This node uses ‘4’ CPU cores.
2023-03-17 13:32:43,258 INFO - Starting HiveMQ extension system.
2023-03-17 13:32:43,300 INFO - Starting extension with id “hivemq-allow-all-extension” at /opt/hivemq/extensions/hivemq-allow-all-extension
2023-03-17 13:32:43,316 WARN -
################################################################################################################
This HiveMQ deployment is not secure! You are lacking Authentication and Authorization.
Right now any MQTT client can connect to the broker with a full set of permissions.
For production usage, add an appropriate security extension and remove the hivemq-allow-all extension.
You can download security extensions from the HiveMQ Marketplace (HiveMQ Extensions Marketplace: Integrate HiveMQ into your business).
################################################################################################################
2023-03-17 13:32:43,317 INFO - Extension “Allow All Extension” version 1.0.0 started successfully.
2023-03-17 13:32:43,317 INFO - Starting extension with id “hivemq-s3-cluster-discovery-extension” at /opt/hivemq/extensions/hivemq-s3-cluster-discovery-extension
2023-03-17 13:32:43,328 INFO - Extension “S3 Cluster Discovery Extension” version 4.0.1 started successfully.
2023-03-17 13:32:43,431 INFO - Using TCP cluster transport on address 10.10.1.14 and port 7800
2023-03-17 13:32:43,437 INFO - Using extension cluster discovery
2023-03-17 13:32:44,163 ERROR - Configured bucket ‘hivemq’ doesn’t exist. Skipping initial discovery.
2023-03-17 13:32:46,164 INFO - he9gs: no members discovered after 2628 ms: creating cluster as first member
2023-03-17 13:32:46,171 INFO - Cluster nodes found by discovery: [he9gs|0] (1) [he9gs].
2023-03-17 13:32:46,186 INFO - No user for HiveMQ Control Center configured. Starting with default user
2023-03-17 13:32:46,186 INFO - Starting HiveMQ Control Center on address 0.0.0.0 and port 8080
2023-03-17 13:32:46,366 INFO - Control Center Audit Logging started.
2023-03-17 13:32:46,366 INFO - Started HiveMQ Control Center in 180ms
2023-03-17 13:32:46,381 INFO - Starting TCP listener on address 0.0.0.0 and port 1883
2023-03-17 13:32:46,401 INFO - Started TCP Listener on address 0.0.0.0 and on port 1883.
2023-03-17 13:32:46,401 INFO - Started HiveMQ in 6189ms
2023-03-17 13:33:44,454 ERROR - Configured bucket ‘hivemq’ doesn’t exist. Skipping reload callback.
[root@ip-10-10-1-14 ~]#