Section 1
Introduction

Section 2
Configuring for First Use

Section 3
Changing Admin Password

Section 4
Creating Accounts

Section 5
Global Component Settings

Section 6
Backups

Section 7
Log Files

Section 8
User Interface Settings

Section 9
Database Connections

Section 10
Non-Standard Ports

Section 11
Firewalls

Section 12
SSL

Section 13
Tracking and Recipient Profiles

Section 14
Editing INI Files

Section 15
Distributed Components

Section 16
User Interface Branding

Section 17
Evaluation Mode

Section 18
International Character Sets

Appendix A
Standard Default Ports

Section 7
Maestro Logs

LISTSERV Maestro has three levels of logging. In the Administrator User Interface, it is possible to choose the level of logging for each component. Click the radio button adjacent to the level of logging desired.

  • “Only log severe messages” – Logs only unexpected problems and errors.
  • “Log severe and standard operational messages” – Logs all severe messages and general informational messages about normal operations such as logins, or new jobs.
  • “Log all messages” – Logs all severe messages, all operational messages and additional detailed messages to describe the ongoing processes such as databases opened and closed, or files created or deleted. These messages are usually used for debugging, or finding problems.

LISTSERV Maestro log files are located in two places. Log files having to do with specific LISTSERV Maestro components are kept in a directory configured like the example below:

x:\Program Files\L-Soft\Application Server\XXX\log

"x:” is the drive where LISTSERV Maestro is installed and “XXX” is the component, either HUB, LUI, or TRK.

Log files for third party components like Tomcat are kept in a directory configured like the example below:

x:\Program Files\L-Soft\Application Server\logs

"x:” is the drive where Maestro is installed.

7.1 Remote Log Access

The three main LISTSERV Maestro components all write their own log files. These files can be found in the “logs” subfolder of each component’s home folder inside of the “Application Server” installation folder. In some situations the administrator may not have access to these folders, but still needs to access the log files. To solve this, LISTSERV Maestro offers remote log file access. The remote access allows an administrator to download the log files from the server, directly in the Web browser.

Before accessing the log files of a component, configure the component for remote log access first. To do so, edit the INI file of the component and add the following entry:

RemoteAdminPassword=PASSWORD

Replace “PASSWORD” with a password only known to authorized administrators. For security reasons, do not use the normal admin password from the Administration Hub. Because this password will later be used as a parameter in a URL, use only URL-safe characters in the password (alphanumeric characters).

Remember; add this entry to each component’s INI file; to lui.ini, hub.ini, and tracker.ini. For more information on editing INI files, see Section 14. If the entry is not added to one of the INI files, then it will not be possible to access the log files of that component (but it will still be possible to access logs of the other components where the entry has been added). To disable remote log access, simply remove the entry from the INI file(s) or comment it out. Whenever this entry is changed, the change will be effective immediately – The component will not have to restart.

Once the component(s) have been configured for remote log access, access their log files from any Web browser on any computer that has HTTP access to the particular component. The only requirements for access are the "PASSWORD" configured in the INI file(s) and the day of the log file to access.

To download a Maestro User Interface log file, access the following URL:

http://HOST:PORT/lui/downloadLog?pw=PASSWORD&day=DATE

To download an Administration Hub log file, access the following URL:

http://HOST:PORT/hub/downloadLog?pw=PASSWORD&day=DATE

To download a Maestro Tracker log file, access the following URL:

http://HOST:PORT/trk/downloadLog?pw=PASSWORD&day=DATE

Replace “HOST” with the host name of the server running the component to be accessed, “PORT” with the HTTP port on that server (“:PORT” can be left out if the HTTP-port is “80”), “PASSWORD” with the password configured in the INI file, and “DATE” with the date of the day of the log file to download. The date is formatted as “YYYYMMDD”, where “YYYY” is the year with 4 digits, “MM” is the month with 2 digits and “DD” is the day of the month with 2 digits.

7.2 Remote Version Query

The current version and build number of all components can be queried remotely. This is done with a simple HTTP-request - a URL typed into the address field of any browser. The result of the query will be displayed in the browser.

  • To query LUI: http://LUISERVER/lui/build
  • To query HUB: http://HUBSERVER/hub/build
  • To query TRK: http://TRKSERVER/trk/build