System Health

There are at least 2 identical items with identical serial numbers. With the help of the "Duplicate numbers" module, the serial numbers can be identified and the entries can be corrected manually.

This lists notes if active process starters could not be executed correctly or could not be terminated correctly.

Process starters that are not needed can simply be deactivated under Administration > Settings > System > Process starter. This is especially useful if a process starter is running but you do not own or use the associated module.

If a process starter is really needed but not terminated correctly, it can be manually triggered again under Administration > Settings > System > Process starter, which is often sufficient.

If the process starter does not run even after several attempts, it is recommended to look for the cause on the server, i.e. contact the server hoster or administrator. Customers whose systems are hosted on the Xentral Cloud can contact Xentral via the support ticket system.

The last execution of the system process starter is logged here. A regular execution leads to a regular update of the displayed date and time.

Reference to the maximum runtime of the process starters configured on the system side. A minimum of 30 seconds is recommended. An unlimited runtime is ideal.

Reference to the maximum memory usage of the process starters configured on the system side. A minimum of 128 MB is recommended. Ideally, at least 512 MB per process.

This message appears when the server memory is full.

This message appears if the database version is outdated. DB version as of 20.2

The cause is that as of Xentral version 20.2, MySQL database version 5.7 or higher functions are required. The solution is to make sure in time that the system administrator or hosting provider updates to database version 5.7. SQL error

An error related to SQL queries has been detected.

The cause here is that "orphaned" database entries exist. As a rule, these are entries for which the parent reference (parent node) no longer exists. The main cause for this is incomplete or incorrectly manually deleted data, e.g. test data. To solve the problem, first click on the message text. A page appears on which the database can be tested by clicking on the "Test" button. Afterwards a list of the found integrity errors can be seen. Here some can be fixed by clicking in the Action column. All other errors can be checked by a technician by looking at the database. A technician is usually required to resolve them. If necessary, Xentral can put you in contact with one of our IT partners.

Display of remaining storage space.

For more information about your cloud storage, please refer to About the AWS Cloud .

Indicates a license that may be about to expire (for monthly payment in the rental model) or expiring support (for purchase licenses). A warning appears (from 14 days before the license expires) or an error after the license expires To resolve, contact Xentral Sales for clarification or to extend the license.

To ensure that calculations in process starters that last longer can be executed correctly and finally, the length of the allowed script runtime, a setting of the server configuration, is important. By default, 30 seconds is set for CLI. However, depending on the size of the organization, it may be appropriate for times to be increased. The same applies to upload capacity.

To ensure that files and transferred form data can be transferred to the server correctly, the upload capacity, a setting of the server configuration, is important.

PHP is a server software (more precisely: an interpreter) that is necessary to run Xentral. Since this software can exist in different versions on the server side, which offer different functionality, the correct minimum version is relevant for running Xentral ERP.

If the message "Userdata directory not writable" appears, the following applies: This critical error must be urgently corrected by the system administrator or hosting provider. It must be ensured that the userdata directory and all subdirectories are writable by the user running the web server and the cronjobs (e.g. starterX.php). Without fixing this error no files can be saved, no PDF archives can be created or snapshots of the database can be saved.

If the message "Userdata directory can be viewed from outside" appears, the following applies: This error should be corrected by the system administrator or hosting provider for reasons of data protection.

This can be done either by changing the DocRoot in the web server configuration (to the directory ""www"", which in the standard case is parallel to the directory userdata), so that the userdata directory is no longer "open".

If there are problems with the verification of the stored company data, this message will become active.

The use of excessively large PDF background files or a very high-resolution logo quickly leads to unnecessarily high memory requirements on the server when there are a large number of documents. In this case, the templates used (stationery PDF or logo file) should be reduced in size as a matter of urgency. To find a solution, contact the graphics agency or recreate the background files yourself, taking into account the following tips:- do not store full-format scans but only areas that are necessary (e.g. head and foot area)

A good file size for deposited stationery PDF files is 50 kB.

These notifications appear when there are errors in the connection to online stores.