- Related Products
- ADManager Plus
- ADAudit Plus
- ADSelfService Plus
- Exchange Reporter Plus
- AD360
- Log360
Once you have successfully installed EventLog Analyzer, start the EventLog Analyzer server by following the steps below.
During installation, you would have chosen to install EventLog Analyzer as an application or a service. If you installed it as an application, you can carry out the procedure to convert the software installation to a Windows Service.
Once the software is installed as a service, follow the steps given below to start EventLog Analyzer as a Windows Service:
Installed in | Users who can start | How to Start |
Top level directories like /opt/, /home , /, and others | Root User: Yes Other User: Yes | Root user: Navigate to the <Eventlog Analyzer>/bin directory and execute the configureAsService.sh file with root user privileges. Then restart the server using the shutdown.sh and service start commands to start using service. Other users: * Open a terminal.* Navigate to the <Eventlog Analyzer>/ES/bin directory, run sudo initES.sh. Alternatively, you can also run initES.sh using root.* Navigate to the <Eventlog Analyzer>/bin directory and execute the run.sh file or start using service. |
Home of a user For example, /home/testuser/Eventlog or /home/Admin/Eventlog or any other directory that comes under a user's home directory | User who owns the home directory: Yes Root user: No (Because in redhat & centos a user can't access files of another user since an Elasticsearch user is created when a user is running the application with root. The Elasticsearch user wont be able access their home directory as it's part of another home directory. | Root user: Should not run Other users: * Open a terminal. * Navigate to the <Eventlog Analyzer>/ES/bin</Eventlog> directory, run sudo initES.sh. Alternatively, you can also run initES.sh using root. |
Server started.
Please connect your client at http://localdevice:8400
Note: If the default syslog listener port of EventLog Analyzer is not free then EventLog Analyzer displays "Can't Bind to Port <Port Number>" when logging in to the UI.
During installation, you would have chosen to install EventLog Analyzer as an application or a service. If you installed it as an application, follow the procedure given below to convert the software installation to a Linux Service. Navigate to the bin folder and execute the following command:
/bin$ ./configureAsService.sh -i
/etc/init.d/eventloganalyzer start
/etc/init.d/eventloganalyzer status
ManageEngine EventLog Analyzer 11.0 is running (<Process ID>).
Follow the steps below to shut down the EventLog Analyzer server. Note that once the server is successfully shut down, the PostgreSQL/MySQL database connection is automatically closed, and all the ports used by EventLog Analyzer are freed.
To stop a Windows service, follow the steps given below.
Execute the commands given below to stop the Linux service (sample outputs are given):
/etc/init.d/eventloganalyzer stop
Stopping ManageEngine EventLog Analyzer <version number>...
Stopped ManageEngine EventLog Analyzer <version number>
/etc/init.d/eventloganalyzer status
ManageEngine EventLog Analyzer <version number> is not running.
Note: You can also execute run.bat but this is not preferred.
For the service mode:Copyright © 2020, ZOHO Corp. All Rights Reserved.