Source:FAQ - Notifications and Logging

From SEPsesam
Other languages:

What does the notification "Disk space for listings and logging below critical threshold" mean?

In the Newday event, SEP sesam Server checks the free disk space on the partition where the log files and listings are stored.

<SESAM_ROOT>\var\log
<SESAM_ROOT>\var\lis

If free space falls below the critical threshold value, the server sends an email notification and the SEP sesam Server is shut down.

In SEP sesam version 5.1.0.14 Apollon V2, the threshold value for managing free disk space is now defined using system settings, which can be accessed and modified in Web UI ( navigation menu -> System Configuration -> System Settings).

To control the SEP sesam server's behavior when free disk space falls below a critical threshold, two key variables are used:

  • gv_conf_minfree_var: This variable determines the critical space threshold. The default setting is 5000 (measured in MB).
  • gv_conf_shutdown_minfree: This variable defines whether the SEP sesam Server is shut down when the free disk space falls below the critical threshold. The default setting is 1, indicating that the server will shut down.

In SEP sesam versions preceding 5.1.0 Apollon V2, the threshold value was specified in the <SESAM_ROOT>\var\ini\sm.ini file under the [Params] section. The parameter gv_min_free was used to define the threshold, with a default value of 5000 MB.

[Params]
gv_min_free= 5000
SEP Warning.png Attention

If there is no more disk space available on the partition, the server cannot write additional logs and listings. This can result in critical errors and lead to data loss. This error should be addressed at the earliest possible opportunity.

How do I set a higher logging level?

You can increase the logging level for specific backup or restore task in the GUI: Main selection -> Tasks -> By Clients -> double-click the backup or restore task to open the Properties. There you can adjust the logging level in the field 'Backup options' with -v <LOGLEVEL>. For details, see Setting Log Level. You can also set the logging level globally for SEP sesam kernel modules, as described in Setting log level globally for SEP sesam kernel modules in debug.ini. Note that running SEP sesam with a higher logging level than default (0 for backup and restore) increases the amount of information being logged and may negatively affect the performance of SEP sesam. For details, see Setting Log Level.

Is it possible to generate audit logs?

It is possible to use the sm_gui_server_requests.log as a source for audit logs by generating a more readable version of the log file with evidence of each action that was triggered by a user. Audit trail records may contain the following details:

  • date and time
  • API request for the executed action
  • user associated with the activity
  • user IP address

The below example shows that the restore task was deleted by the user Administrator.

2021-02-03 10:55:08,592 - [GET] /sep/api/restoreTasks/rs_task01/forceRemove [User: Administrator, IP: 192.168.21.12:59111]

For detailed procedure, see Audit Logging.

Why do the request status or daily protocol (log files) return "Host SEP sesam is not allowed to connect or security problem for user"?

Typically, there is an issue with client's access privileges:

scd-1136: Error: Host [{SEPsesam}] is not allowed to connect or security problem for user: [{user}].

There is a problem with the RMI GUI Server on the SEP sesam Server. The system requires CTRL or SMSSH privileges to complete the SEP sesam commands. On the backup client add permission for the SEP sesam Server so the server is allowed to connect to the client.

Execute the following command on the client:

 sm_setup set_client <SEP sesam Server hostname>

For example, if the SEP sesam Server hostname is backup01:

  • On Microsoft Windows, in the directory C:\Program Files\SEPsesam\bin\sesam, specify:
 sm_setup set_client backup01
  • On Linux, enter:
 /opt/sesam/bin/sesam/sm_setup set_client backup01

How can I create a LOG archive?

The LOG archive for backups, restores and migrations can be created very easily since SEP sesam version 4.4.3.86.

Proceed as follows:

  • In the GUI Main Selection - > Job Status - > click the desired <ACTION>: Backups, Restores or Migrations and Replications.
  • In the list of tasks, right-click the desired task to open the context menu, and then click the last menu item Download archive with all LOG files.
  • Select a directory where the LOG archive will be saved.

This archive contains the most important logs that can be used by SEP support to perform an initial analysis of the problem. Among others, these include the NOT and BCK logs, the daily log and, in the case of backups, the LIS file.

Information sign.png Note
Please attach this LOG archive to the support ticket.

In case of migration, create the archive once from the 'parent process' of the migration and also for the actual migration 'child process', i.e. attach both archives to the support ticket.

Copyright © SEP AG 1999-2024. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.