The System Health module provides an overview of the "health" of the system. If the system detects discrepancies at various points, such as duplicate numbers, errors when executing process starters, a full memory, etc., a warning or error message is generated in the System Health overview.
In the overview, all messages about the health status of the system can be seen at a glance. Warnings are displayed in orange, error messages in red.
The messages shown are created at different intervals and at different times.
As described below, the supplied process starter regularly (typically once a day) performs detailed check routines to evaluate the system state. Some of the regularly executed checks are executed again when the System Messages module is called. So, in case of doubt, it is worth calling the module again after a problem has been solved. However, repeated execution of the process starter is not recommended due to the possibly long runtime. The system would be more heavily loaded and the informative value of the messages would be impaired by time overlaps.
Messages such as connectivity to online stores or APIs, Transfer. Modules, etc. are logged at the time they are detected and held in the display until they are reset. It is possible that successful connections have already taken place in the meantime. In this case, the message is outdated, but still indicates at least one failed connection.
The System Health process starter is required for the functionality of the System Health module. This can be set under Administration > Settings > System > Process starter according to this pattern:
For the verification of duplicate numbers, the process starter "Verify duplicate numbers" is also required.
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 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.
It is strongly discouraged to work directly at the database level in Xentral. The data integrity can be endangered by such interventions. In any case, a database snapshot must be taken in advance to fall back to a running previous state of the system if necessary.
Duplicate part numbers, customer numbers, supplier numbers
This notification message arises due to manual editing, a change in the number range definition or project settings are different records of items or addresses with the same numbers. The item numbers, customer numbers and supplier numbers can be changed by entering a new number. It is possible to jump to the Duplicate numbers module by clicking on the message text. There the elements with the same numbers are displayed and can be easily edited from there.
Blank item numbers
This notification indicates that items do not have an item number. Items with blank item numbers can be supplemented by entering a new item number. Items are usually addressed by their technical ID, so it is possible to add missing item numbers.
Invoice numbers, credit numbers
This warning means that at least 2 invoices or at least 2 credit notes have the same number. Duplicate document numbers for invoices and credit notes should not occur as a rule. However, this can happen if, for example, the set global or project-specific number range has been reset/changed or if documents have been loaded into the system via the document importer.
Initially, the message must be processed on the basis of our helpdesk entry for the Duplicate Numbers module
If the errors were caused by an import (e.g. via the document importer), the last database snapshot may have to be imported again. Before the next import, the number range definitions may need to be changed or the import data edited
If this did not work, contact our support or a technical partner to clean up the database entries
Ensure that the definition of number ranges is not changed during operation. If projects have their own number ranges, this setting should be retained as a matter of urgency. Deactivating a project's own number range can "create" duplicate numbers, as these are now no longer regarded as project-specific.
Display of remaining storage space.
For technical reasons, this value cannot be queried on all systems (e.g. shared hosting).
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.
Under certain circumstances, a message indicating an expired license may be displayed for cloud licenses after a longer period of inactivity (longer than 30 days). This notice can be removed by a renewed check (e.g. by the checking process launcher or by calling the System messages module). If the notice cannot be removed despite a valid cloud license, contact Xentral support.
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".
Alternatively, the userdata directory can also be moved to "above" the docroot and then the path can be adjusted in the userinc.php file
Depending on the web server (usually apache or nginx), access protection to the userdata directory can also be removed via .htaccess
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)
Use vector data for logos and other graphic elements
Always set text as font, not as image
Do not rasterize PDF file and save it to save space
A good file size for deposited stationery PDF files is 50 kB.
This notification appears when one of your Amazon shop interfaces has been deactivated due to an empty token. The affected shop ID is displayed in square brackets, e.g., Sales channel .
This notification gives you information about the current state of your account in Amazon Seller Central. Every marketplace ID will get its own entry that will look similar to this: Amazon_1_A1PA6795UKMFR9 with different values for the shop and marketplace ID.
The notification is structured like this: [Marketplace ID] from sales channel [x] is [Status].
The [Marketplace ID] lets you recognize which of your marketplaces is affected. The Marketplace for Germany is, e.g., A1PA6795UKMFR9.
The [x] after sales channel displays the ID of the affected shopimporter in Xentral. All shop IDs are displayed in the leftmost column in the overview table of the Online shops app.
There are three possible states the [Status] field can be in:
Status in Xentral
Status in Amazon API
If you get a notification other than "ok", please check your Amazon Seller Central to identify the issue. Your account may be flagged as at risk if you, for example, fall below Amazons' performance guidelines due to a negative customer review.
The System Health module is currently in beta stage. Therefore, false positive messages may occur, i.e. errors are displayed that do not exist. In addition, errors are displayed that have already been in the system for some time (such as inconsistent data).
Please feel free to report these errors to us so that Xentral can fix the cause. Please check the error against the following list in advance to avoid multiple reports.
(as of 20/02/2020)
VAT message: link broken
Message data inconsistency: workpackage.project > project.id
Message "Duplicate customer numbers" is displayed, module Duplicate numbers does not show any errors
Message "Duplicate supplier numbers" is displayed, link refers to module Duplicate numbers /Duplicate customer numbers and shows no errors
Message Data inconsistency: documente_send.address > address.id
Message Data inconsistency: production_send.production > production.id
Message data inconsistency: file_version.file > file.id and file_stichwoerter.file > file.id
Message data inconsistency: pdfarchive.table_id > invoice.id, pdfarchive.table_id > order.id, pdfarchive.table_id > order.id, pdfarchive.table_id > offer.id
Message data inconsistency: sale_prices.item > item.id
Message data inconsistency: purchase_prices.item > item.id and sale_prices.item > item.id
Message data inconsistency: pdfarchiv.table_id > lieferschein.id and voucher_chargesnmhd.doctypeid > lieferschein.id
Warning message regarding duplicate numbers behaves inversely to Administration > Settings > Basic settings > Duplicate serial numbers
Message duplicate serial numbers: Link to serial number module does not work