Collecting Logs of Server Components

Logging Levels

Depending on how detailed the information about the component's operation needs to be, different logging levels can be set. They determine how important and detailed the information will be recorded in log files. This allows for more efficient filtering and analysis of logs.

It is recommended to use the Trace logging level as the most detailed.

Logging Levels

Logging Level	Sequential Number	Description
Trace	0	Most detailed level. All information about the component's operation processes is recorded, including details about API method calls.
Debug	1	Details about the component's operation progress, significant variables, and other data that may be useful in detecting and fixing errors are recorded.
Info	2	Informational messages are recorded that notify about normal component functioning. They may include events such as starting or stopping processes, editing user profiles, and others.
Warn	3	Warnings and notifications about potential errors and abnormal situations are recorded. Events are not critical but require attention. At the same time, the component can continue operating.
Error	4	Errors that have led to incorrect component operation or the occurrence of serious problems are recorded. Logs indicate problems that require intervention and correction.
Fatal	5	The least detailed logging level. Only the most critical errors and problems that lead to immediate termination of the component or other serious consequences are recorded. Logs usually indicate serious failures that require immediate intervention and correction.

Collecting installation script logs

The installation script  run-deploy.sh  may terminate with an error. In this case, you need to send the log files to technical support.

Path to log files: AxidianPAM_3.2/axidian-pam/logs/web-wizard/

Example

Failed: Anable playbook returned error code: 2

Axidian Privilege Core

Windows

Enabling Logging

1. Open the configuration file C:\inetpub\wwwroot\core\appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart the application pool:

1. Run PowerShell as administrator.

2. Execute the command:

   C:\Windows\System32\inetsrv\appcmd.exe recycle apppool Axidian.Privilege.Core

Collecting Logs

1. Clear the existing Privilege Core server logs in the folder C:\inetpub\wwwroot\core\Logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Linux

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/core/appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
     }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh core

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/core
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege Idp

Windows

Enabling Logging

1. Open the configuration file C:\inetpub\wwwroot\idp\appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart the application pool:

1. Run PowerShell as administrator.

2. Execute the command:

   C:\Windows\System32\inetsrv\appcmd.exe recycle apppool Axidian.Privilege.Idp

Collecting Logs

1. Clear existing logs in the folder C:\inetpub\wwwroot\idp\Logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Linux

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/idp/appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh idp

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/idp
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege Management Console

Windows

Enabling Logging

1. Open the configuration file C:\inetpub\wwwroot\mc\assets\config\config.prod.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart the application pool:

1. Run PowerShell as administrator.

2. Execute the command:

   C:\Windows\System32\inetsrv\appcmd.exe recycle apppool Axidian.Privilege.ManagementConsole

Collecting Logs

1. Clear existing logs in the folder C:\inetpub\wwwroot\mc\Logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Linux

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/mc/config.prod.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh mc

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/mc
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege User Console

Windows

Enabling Logging

1. Open the configuration file C:\inetpub\wwwroot\uc\assets\config\config.prod.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart the application pool:

1. Run PowerShell as administrator.

2. Execute the command:

   C:\Windows\System32\inetsrv\appcmd.exe recycle apppool Axidian.Privilege.UserConsole

Collecting Logs

1. Clear existing logs in the folder C:\inetpub\wwwroot\uc\Logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Linux

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/uc/config.prod.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh uc

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/uc
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege Log Server

Windows

Enabling Logging

1. Open the configuration file C:\inetpub\wwwroot\ls\appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart the application pool:

1. Run PowerShell as administrator.

2. Execute the command:

   C:\Windows\System32\inetsrv\appcmd.exe recycle apppool Axidian.Privilege.LS

Collecting Logs

1. Clear existing logs in the folder C:\inetpub\wwwroot\ls\Logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Linux

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/ls/appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh ls

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/ls
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege Gateway Service

Windows

Enabling Logging

1. Open the configuration file C:\Program Files\Axidian\Axidian Privilege\Gateway\Pam.Gateway.Service\appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart Pam.Gateway.Service:

1. Open the Services.
2. Find Pam.Gateway.Service in the services list.
3. Right-click the service and select Restart.

Collecting Logs

1. Clear existing logs in the folder C:\Program Files\Axidian\Axidian Privilege\Gateway\Pam.Gateway.Service\logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Linux

Enabling Logging

1. Open the configuration file etc/axidian/axidian-privilege/gateway-service/appsettings.json

2. Edit the NLog section:

   • set the minlevel parameter to Trace
   • set the dbMinLevel parameter to Trace
     
     
   Example

   "NLog": {
     "variables": {
       "minLevel": "Trace",
       "dbMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh gw-service

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/gateway-service
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege ProxyApp

Enabling Logging

1. Open the configuration file C:\Program Files\Axidian\Axidian Privilege\Gateway\ProxyApp\appsettings.json

2. Set the defaultMinLevel parameter to Trace.
   

   Example

   "NLog": {
     "variables": {
       "defaultMinLevel": "Trace",
       "maxArchiveFilesPerCategory": 23
   }

3. Save the file.

After editing the configuration file, restart Pam.Service:

1. Open the Services.
2. Find Pam.Service in the services list.
3. Right-click the service and select Restart.

Collecting Logs

1. Clear existing logs in the folder C:\Program Files\Axidian\Axidian Privilege\Gateway\ProxyApp\logs
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Privilege SSH Proxy

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/ssh-proxy/appsettings.json

2. Set the LogLevel parameter to Trace.
   

   Example

   "LogLevel": "TRACE",
   "LogStream": "FILE",
   "MaxLogFiles": 100,
   "MaxLogFileSize": 10000000,

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh ssh-proxy

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/ssh
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege PostgreSQL Proxy

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/sql-proxy/appsettings.json

2. Set the LogLevel parameter to Trace.
   

   Example

   "LogLevel": "TRACE",
   "LogStream": "FILE",
   "MaxLogFiles": 100,
   "MaxLogFileSize": 10000000,

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh sql-proxy

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/sql
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.

Axidian Privilege RDP Proxy

Enabling Logging

1. Open the configuration file /etc/axidian/axidian-privilege/rdp-proxy/appsettings.json

2. Set the LogLevel parameter to Trace.
   

   Example

   "LogLevel": "TRACE",
   "LogStream": "FILE",
   "MaxLogFiles": 100,
   "MaxLogFileSize": 10000000,

3. Save the file.

4. Navigate to the folder with PAM scripts and restart the component:

   cd /etc/axidian/axidian-privilege/scripts/

   bash restart-pam.sh rpd-proxy

Collecting Logs

1. Clear existing logs in the folder /etc/axidian/axidian-privilege/logs/rdp
2. Reproduce the problem.
3. Collect an archive with logs and send it to technical support. Describe the user's actions and specify the exact time when the problem occurred.