This website uses cookies. By continuing to browse or login to this website, you consent to the use of cookies. Learn more.
OK
steve-m
Micro Focus Expert
Micro Focus Expert
‎2018-07-13 21:13
398 views

ArcSight Event Broker 2.21 - DNS and host setup and configuration - v1a

DNS is required with Event Broker. This document covers the proper DNS and host setup and configuration for nodes in an Event Broker deployment.

Reply
Report Inappropriate Content
4 Replies
steve-m
Micro Focus Expert
Micro Focus Expert
‎2018-07-16 20:10

This is a subset of the full build guide I posted: ArcSight Event Broker 2.20 from the ground up build guide

0 Likes
Reply
Report Inappropriate Content
steve-m
Micro Focus Expert
Micro Focus Expert
‎2018-08-10 00:02

Here is the full build guide for Event Broker 2.21: ArcSight Event Broker 2.21 from the ground up build guide

0 Likes
Reply
Report Inappropriate Content
steve-m
Micro Focus Expert
Micro Focus Expert
‎2018-08-20 09:35

v1a has a very minor update to the nslookup commands.

0 Likes
Reply
Report Inappropriate Content
steve-m
Micro Focus Expert
Micro Focus Expert
‎2018-11-07 15:28

Here are errors I've seen with Event Broker 2.21 (Installer 1.50.9) when an internal or external dns server is setup that cannot forward/reverse lookup based on hostname/fqdn/ip. For every node in the cluster, please check /etc/resolv.conf and make sure you can forward/reverse lookup for every server listed. Use the syntax of "nslookup [name] [server]" to check every entry in /etc/resolv.conf. For example, "nslookup eb1.example.com 192.168.0.53" is used to query the 192.168.0.53 DNS server for the entry eb1.example.com.

 

[FATAL] 2018-08-06 09:21:53 : Failed to get X-AUTH-TOKEN. Please make sure the inputted password is correct.

First deploy phase failed!

Error while deploying core services. Please see logs for more details. Installation will be aborted!

 

[FATAL] 2018-06-21 08:39:49 : Failed to store key [/suite-installer/v1.1/ca-external-host] value [investigate.arcsight.example.com]

First deploy phase failed!

Error while deploying core services. Please see logs for more details. Installation will be aborted!


/log/scheduler/hyperkube.ERROR

E0619 16:20:58.857550       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1.PersistentVolume: Get https://investigate.arcsight.example.com:8443/api/v1/persistentvolumes?resourceVersion=0: dial tcp 172.16.100.201:8443: getsockopt: connection refused

 

/log/controller/hyperkube.ERROR

E0619 16:20:58.618701       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://investigate.arcsight.example.com:8443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 172.16.100.201:8443: getsockopt: connection refused

 

/log/kubelet/kubelet.WARNING

E0619 09:20:09.319687    7784 eviction_manager.go:238] eviction manager: unexpected err: failed to get node info: node 'investigate.arcsight.example.com' not found

0 Likes
Reply
Report Inappropriate Content
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.