High Availability troubleshooting: Virtual IP not working
Issue description
The virtual IP does not function properly in the High Availability (HA) setup. This impacts EventLog Analyzer access and syslog log collection.
Possible causes
- Wrong interface name in StartHA.vbs or StopHA.vbs
- Virtual IP isn’t in the same network range or subnet
- Syslog devices are not set to use the virtual IP
- Missing license files on the secondary server
- Elasticsearch is not configured for HA
What to check first
- Is the interface name correct in StartHA.vbs and StopHA.vbs?
- Is the virtual IP in the same subnet?
- Were license files copied from primary to secondary?
Resolution steps
Step 1: Confirm the interface name in the scripts is correct.
Step 2: Make sure the virtual IP is in the same subnet.
Step 3: Verify syslog devices are sending logs to the virtual IP.
Step 4: Copy these files from primary to secondary:
- <EventLog Analyzer Home>\lib\petinfo.dat
- <EventLog Analyzer Home>\lib\AdventNetLicense.xml
Step 5: Check Elasticsearch is configured for HA.
Validation and testing
- Ping the virtual IP
- Open EventLog Analyzer using the virtual IP
- Check if syslog logs are received
Tips
- Make sure settings match on both servers
New to ADSelfService Plus?
Related Articles
Troubleshooting: Unable to Access EventLog Analyzer User Interface
Issue description You may not be able to access EventLog Analyzer user interface or web console in your browser or over multiple machines thou EventLog Analyzer is running as service/console mode. This article offers possible cause and step by step ...Troubleshooting: Disk space issues in EventLog Analyzer
Issue description EventLog Analyzer server might run out of storage due to misconfiguration and other known factors. This article offers troubleshooting steps to resolve when your disk or drive where the application is installed is full and help you ...Troubleshooting: No data in Microsoft SQL Server DDL/DML report
Issue description This article provides troubleshooting guidance for cases where no data appears under DDL/DML report in SQL Server auditing report. Possible cause Advance Auditing not enabled: This may occur if you have not enabled Advanced Auditing ...Troubleshooting guide: EventLog Analyzer UI is unresponsive
Overview This document outlines the common causes and recommended steps to resolve the issue when the EventLog Analyzer UI becomes unresponsive. Possible causes Insufficient system resources High CPU or memory usage on the server. Low disk space in ...Troubleshooting: Some events are not available in the Search tab | EventLog Analyzer
Issue description The user might not be able to see some events that happened natively within the EventLog Analyzer Search tab. This article offers steps to review and resolve this issue. Possible causes The event was not recorded natively due to ...