The installer displays the following message if you try to upgrade from complete syslog-ng PE to client setup syslog-ng PE with .run package.
This version of syslog-ng Premium Edition doesn't support storing messages in SQL servers, while the installed one did.
If you need to uninstall syslog-ng PE for some reason, you have the following options:
If you have installed syslog-ng PE using the .run installer: Execute the uninstall.sh script located at /opt/syslog-ng/bin/uninstall.sh. The uninstall script will automatically restore the syslog daemon used before installing syslog-ng. To completely remove syslog-ng PE, including the configuration files, use the uninstall.sh --purge command.
If you have installed syslog-ng PE from a .deb package: Execute the dpkg -r syslog-ng
If you have installed syslog-ng PE from an .rpm package: Execute the rpm -e syslog-ng
If you have installed syslog-ng PE from a .pkg package: Execute the pkgrm BBsyslng command to remove syslog-ng PE. Note that removing syslog-ng PE does not restore the syslog daemon used before syslog-ng.
For automatic uninstall (answering y to all questions): Execute the yes | pkgrm BBsyslng command.
The following files have to be deleted manually:
anything else under the <syslog-ng path>/var directory
The following describes how to configure your Microsoft SQL Server to enable remote logins and accept log messages from syslog-ng.
To configure your Microsoft SQL Server to enable remote logins and accept log messages from syslog-ng
Start the SQL Server Management Studio application. Select Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.
Create a new database.
Figure 20: Creating a new MSSQL database 1.
In the Object Explorer, right-click on the Databases entry and select New Database.
Figure 21: Creating a new MSSQL database 2.
Enter the name of the new database (for example syslogng) into the Database name field and click OK.
Create a new database user and associate it with the new database.
Figure 22: Creating a new MSSQL user 1.
In the Object Explorer, select Security, right-click on the Logins entry, then select New Login.
Figure 23: Creating a new MSSQL user 2.
Enter a name (for example syslog-ng) for the user into the Login name field.
Select the SQL Server Authentication option and enter a password for the user.
In the Default database field, select the database created in Step 2 (for example syslogng).
In the Default language field, select the language of log messages that you want to store in the database, then click OK.
Incorrect language settings may result in the database converting the messages to a different character-encoding format. That way the log messages may become unreadable, causing information loss.
In the Object Explorer, select Security > Logins, then right-click on the new login created in the previous step, and select Properties.
Figure 24: Associating database with the new user
Select User Mapping. In the Users mapped to this login option, check the line corresponding to the new login (for example syslogng). In the Database role membership field, check the db_owner and public options.
Figure 25: Associating database with the new user
Enable remote logins for SQL users.
In the Object Explorer right-click on your database server, and select Properties > Security, and set the Server Authentication option to SQL Server and Windows Authentication mode.
This chapter provides a very brief introduction into configuring the syslog-ng PE application. For details on the format of the configuration file and how to configure sources, destinations, and other features, refer to the subsequent chapters.
To configure syslog-ng PE as a client that sends log messages to a central logserver, see Configuring syslog-ng on client hosts.
To configure syslog-ng PE as a server that receives log messages from client hosts, see Configuring syslog-ng on server hosts.
To configure syslog-ng PE as a relay that receives log messages from client hosts and forwards them to a central logserver, see Configuring syslog-ng on server hosts.