Message;Resolution ERROR: Application failed with error ${status_code} ${app}:${process};If this is an unexpected event call VOSS Support for further investigation. This trap can also be triggered as expected when app stop or system reboot is run. ERROR: Automate License Service Error;Check licenses with vendor. See: Product Licensing in Platform Guide. ERROR: Backup failed .;Check the backup including connectivity to backup server. There may have been some form of corruption during the time that the backup was run. Run backup manually and see whether the same failure is detected. If it is the case investigate. Otherwise contact VOSS Support to investigate. ERROR: cannot compute children counts for: {resource.path};Possible issue with the resource hierarchy or metadata structure. Contact VOSS Support or try these steps: (1) Ensure the resource path specified in the error message is correct and exists in the hierarchy. (2) In case the error is due to a corrupt resource metadata structure verify that the metadata structure for the resource is intact and correctly defined. (3) Ensure the resource has a valid parent hierarchy. (4) Verify that resource relations are correctly defined and that there are no missing or corrupt references. (5) Review error codes and messages. ERROR: cannot create HTML application. + traceback.format_exc();Possible issue with creating an HTML application. The traceback provides more details. Contact VOSS Support or try these steps: (1) Check error message and traceback. (2) Ensure the request format is correct. (3) Verify that all required attributes and fields are provided and correctly formatted. (4) Ensure settings and configurations are properly set up. (5) Ensure that the hierarchy context is not None and is correctly selected. (6) Verify that the import file and export URL are valid. ERROR: Can not create symbolic link : A required privilege is not held by;Contact VOSS Support or try these steps: Ensure the user attempting to create the symbolic link has the necessary privileges (typically admin). Grant the privilege. If you are running a script or command that requires creating symbolic links ensure that you run it with administrative privileges. Ensure the user has access to the necessary hierarchy and resources. ERROR: Can not execute `setup.py` since setuptools is not available in ;Contact VOSS Support or try these steps: Ensure that setuptools is installed in your environment. If working in a virtual environment ensure the virtual environment is activated and that setuptools is installed within it. Ensure the Python path is correctly set and that it includes the directory where setuptools is installed. If setuptools is already installed but you are still encountering the error try updating it to the latest version. ERROR: could not contact server $TIMESERVER after three tries giving up;The system may be unable to synchronize time with the specified time server after multiple attempts. Contact VOSS Support or try these steps: (1) Ensure the time server address ($TIMESERVER) is correct and reachable from the VOSS Automate system. (2) Verify there are no network issues preventing the VOSS Automate system from reaching the time server. (3) Ensure the NTP (Network Time Protocol) configuration is correctly set up on the VOSS Automate system. (4) Restart the time synchronization service to attempt to re-establish contact with the time server. (5) Check system logs for additional error messages or clues about why the time server cannot be contacted. ERROR: Could not read $TEMPLATE;Possible issue with accessing or reading specified template. Contact VOSS Support or try these steps: (1) Ensure the template path specified in the error message ($TEMPLATE) is correct and accessible. (2) Verify that file permissions for the template allow reading by the user or process attempting to access it. (3) Confirm that the template file exists at the specified path. (4) Ensure the template file is not corrupted and is in the correct format. (5) If you're using a default template ensure it is cloned and customized correctly (default templates are read-only and need to be cloned to your hierarchy for customization). (6) Review error codes and messages. ERROR: Database maintenance not scheduled... ;Contact VOSS Support or try these steps: Create schedule and time: With for example a schedule name dbtxn: schedule add dbtxn voss transaction archive or schedule add dbtxn voss transaction delete schedule time dbtxn weekly 0 ERROR: Data loaded from JSON: no file scan options can be ;Possible issue with loading data from a JSON file which may be due to missing or incorrect file scan options. Contact VOSS Support or try these steps: (1) Ensure the JSON file is correctly formatted and adheres to the expected schema. (2) Ensure the JSON file is encoded correctly (e.g. UTF-8). (3) Verify that all required fields and data are present in the JSON file. (4) Follow the guidelines for exporting and importing JSON data as specified in the VOSS Automate documentation and ensure the JSON file format is compatible with the system's requirements. (4) Ensure there are no errors during the file upload process. ERROR: Disk full;Contact VOSS Support or try these steps: It depends on which disk is full: * If it is the media or backup disks then clean up the disk space. * If it is any other disk then contact VOSS Support immediately. ERROR: Disk slow;Contact VOSS Support or try these steps: This trap indicates that there is heavy disk activity. This will be normal in many situations and should not always require immediate action. The one reason for this is that there are many transactions spawned at the same time. The disk utilization can be relieved by cancelling a few current transactions or by rescheduling some others. However this should be monitored closely and should it persist over several hours then VOSS Support should be contacted to investigate. ERROR: Excessive load;The system load average is too high over a specified interval. Contact VOSS Support or try these steps: (1) Use system monitoring tools to identify processes that are consuming excessive CPU or memory resources. (2) Check the load average over different intervals (1 minute 5 minutes 15 minutes) to understand the load pattern. (3) Identify and optimize or terminate resource-intensive processes that are contributing to the high load. (4) If the system consistently experiences high load consider increasing the available CPU and memory resources. This may involve upgrading the hardware or adjusting the virtual machine settings. (5) Check system logs for any errors or warnings that might indicate underlying issues contributing to the high load. (6) Distribute the load across multiple servers or instances to prevent any single system from becoming overloaded. This may involve setting up a load balancer and configuring it to distribute traffic evenly. ERROR: Extracted source still exists for %s' % target out=True);Possible issue that the extracted source directory or file still exists when it should have been removed or moved. Contact VOSS Support or try these steps: (1) Verify the target path specified in the error message is correct and accessible. (2) Verify if the extracted source directory or file still exists at the target path. (3) Remove or move existing files or directories. If the extracted source still exists remove or move it to avoid conflicts. (4) Ensure that the extraction process includes proper cleanup steps to remove or move the extracted source after use. (5) Review backup and restore procedures. If error occurs during a backup or restore process review the procedures to ensure that the extracted files are handled correctly. ERROR: Failed package source list exists in ipcentral root dir. ;Possible issue with the package source list in the root directory of the ipcentral. Contact VOSS Support or try these steps: (1) Ensure that the package source list in the ipcentral root directory is correct and not corrupted. (2) Verify if the package source list file still exists in the ipcentral root directory. (3) If the package source list still exists remove or move it to avoid conflicts. (4) Ensure that the package management process includes proper cleanup steps to remove or move the package source list after use. (5) If the error occurs during a package management process review the procedures to ensure that the package source list is handled correctly. ERROR: Failed to archive %s % target out=True);Possible issue with archiving the specified target. Contact VOSS Support or try these steps: (1) Ensure the target path specified in the error message is correct and accessible. (2) Verify if the target directory or file still exists and is not corrupted. (3) Ensure there is enough disk space available to create the archive. (4) Verify that the file permissions for the target directory or file allow for reading and writing. (5) Ensure the command used to create the archive is correct and includes all necessary options. (6) Check system logs for any additional error messages or clues about why the archiving process failed ERROR: failed to collect resource_attributes for plugin: ;Possible issue with collecting resource attributes for a specific plugin. Contact VOSS Support or try these steps: (1) Ensure the plugin configuration is correct and all required parameters are specified. (2) Verify that the resource meta structure is not missing or corrupt. (3) Verify that all required resources are available and accessible. (4) Ensure that there are no duplicate resources that might be causing conflicts. (5) Check system logs for any additional error messages or clues about why the resource attributes collection failed. (6) Restart the plugin to ensure that it is properly initialized and can collect resource attributes ERROR: failed to download source for %s package %s' % (pkg['from'] pkg['name']) out=True);Possible issue with downloading the source for a specified package. Contact VOSS Support or try these steps: (1) Ensure that the URL specified for the package source is correct and accessible. (2) Ensure that the system has network connectivity and can reach the package source URL. (3) Ensure there is enough disk space available to download the package. (4) Check file permissions for the target directory allow for writing. (5) Ensure the package management process is correctly configured and includes all necessary options. (6) Check system logs for any additional error messages or clues about why the package download failed. ERROR: Failed to download source package {} for package {}.format(source_package_name ;Possible issue with downloading the source package for a specified package. Contact VOSS Support or try these steps: (1) Ensure the URL specified for the source package is correct and accessible. (2) Ensure the system has network connectivity and can reach the package source URL. (3) Ensure there is enough disk space available to download the package. (4) Check that file permissions for the target directory allow for writing. (5) Ensure the package management process is correctly configured and includes all necessary options. (6) Check system logs for any additional error messages or clues about why the package download failed ERROR: failed to load codebase from scan file at: %(input)r;Possible issue with loading the codebase from a specified scan file. Contact VOSS Support or try these steps: (1) Ensure the path specified for the scan file is correct and accessible. (2) Check that file permissions for the scan file allow for reading. (3) Verify the scan file is not corrupted and is in the expected format. (4) Ensure that all required dependencies for loading the codebase are installed and available. (5) Check system logs for any additional error messages or clues about why the codebase loading failed. (6) Retry the operation to load the codebase from the scan file ERROR: failed to load resource from cached location: {cache_location} ;Possible issue with loading a resource from a specified cached location. Contact VOSS Support or try these steps: (1) Check that the path specified for the cache location is correct and accessible. (2) Check that file permissions for the cache location allow for reading. (3) Ensure the cache file is not corrupted and is in the expected format. (4) Clear the existing cache and rebuild it to ensure that it is up-to-date and not corrupted. (5) Ensure that all required dependencies for loading the resource are installed and available. (6) Check system logs for any additional error messages or clues about why the resource loading failed ERROR: failed to run %(stage)s plugin: %(name)s:' % locals();Possible issue with running a specific plugin at a particular stage. Contact VOSS Support or try these steps: (1) Ensure that the plugin configuration is correct and all required parameters are specified. (2) Verify that the resource meta structure is not missing or corrupt. (3) Verify that all required resources are available and accessible. (4) Ensure that there are no duplicate resources that might be causing conflicts. (5) Check system logs for any additional error messages or clues about why the plugin execution failed. (6) Restart the plugin to ensure that it is properly initialized and can run without issues ERROR: failed to setup plugin: %(stage)s:%(name)s:' % locals();Possible issue with setting up a specific plugin at a particular stage. Contact VOSS Support or try these steps: (1) Ensure the plugin configuration is correct and all required parameters are specified. (2) Verify that the resource meta structure is not missing or corrupt. Verify that all required resources are available and accessible. (4) Ensure that there are no duplicate resources that might be causing conflicts. (5) Check system logs for any additional error messages or clues about why the plugin setup failed. (6) Restart the plugin to ensure that it is properly initialized and can run without issues ERROR: Failed to write output for: + repr(template_chunk);Possible issue with processing a template chunk. Contact VOSS Support or try these steps: (1) Ensure that the template syntax is correct and that there are no missing or extra characters that could cause parsing issues. (2) Verify that the data being passed to the template is in the expected format and type. Incorrect data types or malformed data can cause this error. (3) Review error codes related to template processing ERROR: Failure installing ${APPNAME} not running clean-up;Contact VOSS Support or try these steps: (1) Check the installation logs to identify the specific cause of the failure. The logs provide detailed information about what went wrong during the installation process. (2) Check that the application you're installing is compatible with your current system version. Incompatibility can cause install failures. (3) Make a system backup before installation so that you can restore the system in case of a failure. (4) If an application URI is specified as a parameter ensure it is correctly downloaded. If the application is already installed it will be skipped with a message. (5) If an application with more than one version is found in the media directory the latest version is installed. Ensure that the correct version is being installed. (6) In an application in the list fails to install the installation is terminated. Refer to the install logs for more details. (7) If the delete-on-success parameter is set to yes the manifest file and application files are removed after successful installation. (8) If system settings have changed reboot the system ERROR: File warning fileErrorFlag != 0;Possible issue with file processing. Contact VOSS Support or try these steps: (1) Ensure that the file being processed is in the correct format. (2) Verify that the file encoding is correct. Incorrect file encoding can cause errors during file processing. (3) Ensure that the file size does not exceed the maximum permitted size. Large files may need to be split into smaller parts. (4) Check that the file has a valid and VOSS Supported file extension. (5) Validate the content of the file to ensure it conforms to the expected schema. Discrepancies in the data structure can lead to errors. (6) Refer to the VOSS Automate documentation for specific error codes related to file processing ERROR: for scanner: + scanner.name + : + error;Contact VOSS Support, or try these steps: (1) Inspect the system resources to ensure there are no issues with disk, memory, or CPU usage. (2) Review the error message and return code displayed in the browser for information to determine the cause of the problem. ERROR: for scanner: + scanner.name + : + traceback.format_exc();Contact VOSS Support, or try these steps: (1) Inspect the system resources to ensure there are no issues with disk, memory, or CPU usage. (2) Review the error message and return code displayed in the browser for information to determine the cause. (3) Inspect the traceback.format_exc() function for a detailed traceback of the error. Review the traceback to identify the specific point of failure in the code. ERROR: High memory usage Memory activity: ...;This should be monitored closely and should it persist over several hours then VOSS Support should be contacted to investigate. Monitor and make adjustments to the VM memory if the condition persists. ERROR: invalid date '{}': expected date format YYYY-MM-DD[_hh:mm:ss].format(date));Contact VOSS Support, or try these steps: (1) Check the date format and ensure that the date string you are providing matches the expected format. (2) Validate the input. If the date is being input by a user or coming from an external source, validate the input to ensure it conforms to the expected format before processing it. (3) Review the documentation to understand the expected date format and any additional requirements. Consider also the context in which the error occurs, such as the specific operation or API call being made. ERROR: License file generation failed ;The system runs an internal schedule to generate monthly license reports. For details on license reports and how to generate these manually refer to the Licensing Guide. This internal schedule cannot be disabled. The schedule is configured to run at 3AM UTC on the first day of the month. The date cannot be changed but the time can. Please contact your VOSS account manager if a schedule time change is required. After the monthly schedule is run a check is carried out for the generated report. If the report was generated successfully no messages are sent and no notifications are generated. If the report was not generated successfully a message shows on the CLI console when logging in or when typing the health command: LICENSE REPORT: FAILED - Please run 'voss export type license_initial_audit' This message will continue to show until the report is generated successfully by running the command shown in the message. ERROR: Log files larger than 1Gig found in /var/log ...;The system will automatically trigger a cleanup. Check the log partition after some time. ERROR: Log processing failure ;If the remote syslog server stops receiving logs the local disk space of the queue of logs can grow to a maximum of 1GB before logs are not queued and log messages are discarded. ERROR: `max_depth` must be a positive integer or 0.);Contact VOSS Support, or try these steps: (1) Ensure that the max_depth parameter is set to a valid value. The valid values for max_depth are positive integers or 0. (2) If the max_depth value is being input by a user or coming from an external source, validate the input to ensure it conforms to the expected format before processing it. (3) Refer to the relevant documentation to understand the expected values for max_depth and any additional requirements. ERROR: Memory swap error;"Contact VOSS Support, or try these steps: (1) Ensure that the system has sufficient swap space available. Running out of swap space can cause memory swap errors. (2) Use diagnostic commands to inspect the overall system resources, including disk, memory, and CPU usage. (3) If you are using SNMP for monitoring, review the SNMP trap logs for any memory-related errors. For example, an SNMP trap log might indicate running out of swap space Running out of swap space (4) If the system is running out of swap space, consider increasing the swap space. (5) Continuously monitor memory usage to ensure that the system does not run out of memory or swap space." ERROR: Missing output option(s): at least one output ;Ensure that at least one output option is specified in your configuration or function call. You can contact VOSS Support, or try these steps: (1) Ensure that you have specified at least one output option in your configuration or function call. For example, if you are using a macro function, make sure to include the necessary output parameters. (2) Review relevant documentation to understand the required output options for the function or operation you are performing. (3) Check your configuration to ensure that all required output options are included. If you are using a template or script, verify that the output parameters are correctly defined. ERROR: Missing source directory %s % target out=True);Contact VOSS Support, or try these steps: (1) Ensure that the source directory specified in your configuration or command exists and is accessible. The error indicates that the system is unable to find the specified source directory. (2) Double-check the directory path for any typos or incorrect formatting. Ensure that the path is correctly specified and points to the intended directory. (3) Verify that the user or process running the command has the necessary permissions to access the source directory. Lack of permissions can cause the system to be unable to read the directory. (4) Review your configuration settings to ensure that the source directory is correctly specified. If you are using a script or template, make sure the directory paths are correctly defined. (5) Review any additional logs or error messages that might provide more context about the issue. ERROR: Network Failures. The following network failures occurred:;Contact VOSS Support, or try these steps: (1) Ensure that the network connections between the VOSS Automate system and other network components are stable and functioning correctly. This includes checking cables, switches, routers, and firewalls. (2) If SNMP traps are configured, review the SNMP trap logs for any network-related errors. The logs can provide detailed information about the specific network failures that occurred. (3) Use network monitoring tools to continuously monitor the network status. (4) Review the system logs for any network-related error messages. The logs can provide additional context and details about the network failures. (5) Ensure that the network configuration settings in VOSS Automate are correct. This includes verifying IP addresses, DNS settings, and network routes. (6) If necessary, restart the network services on the VOSS Automate system to resolve any temporary network issues. ERROR: nginx upstream failure upstream %s server %s failed: %s;Check that the file has a valid extension. Unsupported file extensions can cause this error. ERROR: No ntp configured for %s ...;Possible issue with Network Time Protocol (NTP) configuration. Contact VOSS Support, or try these steps: (1) Ensure the NTP server is properly configured for the specified server. (2) Restart the NTP Daemon. (3) Ensure that the NTP offset is within acceptable limits. If the offset exceeds 1 second, it may indicate synchronization issues. ERROR: Operation cancelled by user in output;Typically, a user-initiated action results in this error rather than a system issue. Contact VOSS Support, or try these steps: (1) Check with the user who initiated the action to understand why it was cancelled. This may have been intentional, or an issue prompted the user to cancel the operation. (2) Re-initiate the operation, ensuring all conditions are met before restarting the operation. (3) The user may have cancelled the operation due to an underlying issue, such as slow performance or other errors. Investigate and resolve before re-iniating the operation. ERROR: Processes cannot log because /var/log is full - run 'log purge' ;Validate the content of the file to ensure it conforms to the expected schema. Any discrepancies in the data structure can lead to errors. ERROR: Processing interrupted: timeout after %(timeout)d seconds.;"Processing may have been interrupted because it exceeded the allowed time limit, which may be due to network issues, server performance, or configuration settings. Contact VOSS Support, or try these steps: (1) Increase timeout settings for the specific process. (2) Ensure that server and network performance are optimized. For example, check for bottlenecks, ensure sufficient resources (CPU, memory), and optimize database queries, if applicable. (3) Verify if there are any transactions stuck in the ""Queued"" or ""Processing"" state for too long. (4) Ensure session timeouts are appropriately configured, both idle timeout (the number of minutes a session remains active when there is no activity) and absolute timeout (the maximum number of minutes a session can be active. " ERROR: provided end date '{}' is earlier than the start date '{}'.format(end start));Possible issue is that the end date provided is earlier than the start date, and thus not a valid date range. Contact VOSS Support, or try these steps: (1) Ensure that the end date is later than the start date. Double-check the date values you're entering to ensure they're in the correct order. (2) Ensure date values are in the correct format. (3) Adjust the date range, end date must be after start date. ERROR: provided start date '{}' is in the future.format(start));Possible issue related to invalid start and end date range. Contact VOSS Support, or try these steps: (1) Ensure the start date you're providing is not set in the future. Start date should be past or current date. (2) Verify the date format is as expected in VOSS Automate. (3) If you're using a filter, ensure the start and end dates are within a valid range and that start date is not after end date. ERROR: Service Failures ...;"Issues with one or more services. Contact VOSS Support, or try these steps: (1) Check the status the services to ensure they're running correctly. Check the service logs or use the platform's monitoring tools. (2) Restart any services that aren't running. (3) Check the detailed logs for any specific error messages that can provide more insight into what caused the service failure. (4) Ensure that all dependencies required by the services are available and functioning correctly. This includes network connectivity, database connections, and other required services. Update Software: Make sure that your VOSS Automate software is up to date. Sometimes, service failures can be due to bugs that have been fixed in newer versions." ERROR: SNMP trap send failed trap:;Issue with sending a SMTP trap. Contact VOSS Support, or try these steps: (1) Ensure SNMP is correctly configured, verify SNMP settings, including the trap destination, community strings, and SNMP version. (2) Ensure the trap destination (the IP address or hostname of the SNMP manager) is correctly configured and reachable from the VOSS Automate system. (3) Check network connectivity between the VOSS Automate system and the SNMP manager. Ensure that there are no network issues or firewalls blocking the SNMP traffic. (4) Ensure that the SNMP service is running on both the VOSS Automate system and the SNMP manager. Restart the SNMP service if necessary. (5) Review the detailed logs for any specific error messages that can provide more insight into what caused the SNMP trap send failure. (6) Ensure that the corresponding SNMP MIBs are loaded on the SNMP manager. If the MIBs are not loaded, the SNMP manager may not correctly interpret the traps. ERROR: Some services failed to start during installation. System provisioning deferred.;May indicate that certain services did not start successfully during the installation process, causing the system provisioning to be deferred. Contact VOSS Support, or try these steps: (1) Check the status of services to ensure they're running correctly. Check the service logs or using the platform's monitoring tools. (2) Restart any services that aren't running. (3) Review the detailed logs for any specific error messages that can provide more insight into what caused the service failure. (4) Ensure all dependencies required by the services are available and functioning correctly. This includes network connectivity, database connections, and other required services. (5) If you're using a clustered environment, you may need to run cluster provisioning to mitigate the failure. (6) Ensure that the installation process is completed correctly. ERROR: System unable to send {} messages to {}... ;May indicate that the system encountered an issue while trying to send messages to a specified destination. Contact VOSS Support, or try these steps: (1) Ensure there is proper network connectivity between the VOSS Automate system and the destination. Verify that there are no network issues or firewalls blocking the communication. (2) Ensure that the destination address (IP address or hostname) is correctly configured and reachable. Double-check the configuration settings for any typos or errors. (3) Review the detailed logs for any specific error messages that can provide more insight into what caused the failure. (4) Ensure any message queues (if available) are functioning correctly and that there are no issues with message processing. (5) Restart relevant services to resolve any temporary issues. (6) Check disk usage to ensure there is sufficient disk space available on the system. High disk usage can sometimes cause issues with message processing and logging. ERROR: Template path must be a directory;May indicate that the specified template path is not recognized as a directory. Contact VOSS Support, or try these steps: (1) Ensure the path you specified for the template is indeed a directory. Double-check the path for any typos or errors. (2) If the specified path does not exist, create the directory at the specified location. Ensure that the directory has the correct permissions for the VOSS Automate system to access it. (3) Ensure that the directory structure is maintained correctly. (4) Use relative paths. (5) Avoid leading slashes in the path name. ERROR: The db is failing over constantly within 5 min ...;Create schedule and time: With for example a schedule name dbtxn: schedule add dbtxn voss transaction archive or schedule add dbtxn voss transaction delete schedule time dbtxn weekly 0 ERROR: The last backup was more than 2 days ago ...;Indicates that the system has not performed a backup in the last two days. Contact VOSS Support, or try these steps: (1) Ensure that the backup schedule is correctly configured and that backups are set to run at the desired intervals. Check the backup configuration settings to confirm the schedule. (2) If the automated backup did not run, you can manually trigger a backup to ensure that the system is backed up. (3) Review the backup logs to identify any issues that may have prevented the backup from running. Look for any error messages or warnings that can provide more insight into the problem. (4) Ensure there is sufficient disk space on the system to perform the backup. (5) Ensure the backup destination (e.g., local storage, remote server) is accessible and has enough space to store the backup files. (6) If necessary, restart backup services to resolve any temporary issues that may be preventing the backup from running. ERROR: The selected protocol is already disabled.);"May indicate that you're trying to disable a protocol that is already in a disabled state. Contact VOSS Support, or try these steps: (1) Check the current protocol status before attempting to enable or disable a protocol. (2) Use the appropriate commands to enable or disable the desired protocol. Note that enabling or disabling a protocol that is already in that state will raise an error message. (3) Restart the web server. (4) Avoid redundant commands, for example, you're trying to disable an already disabled protocol, or enable an already enabled protocol. " ERROR: Transaction archive files older than 30 days...;May indicate that there are transaction archive files in the system that are older than 30 days. Contact VOSS Support, or try these steps: (1) Check the Transaction Archive Directory to identify any files that are older than 30 days. (2) Manually delete old archive files. (3) Consider setting up a scheduled task or script to automatically delete transaction archive files that are older than a certain number of days. This will help prevent the accumulation of old files in the future. (4) Use the VOSS Automate commands to manage transaction archives. (5) Regularly monitor the transaction archive files to ensure that they are being managed properly and that old files are being removed as needed. ERROR: Transaction export failed;Possible issue with exporting transaction data. Contact VOSS Support or try these steps: (1) Review system logs for any additional error messages or clues about the cause of the transaction export failure. (2) Ensure all database connections are properly configured and accessible. (3) Check for any unhandled errors in the logs or error messages. (4) Ensure all queries and data operations are correctly formed and executed. (5) Ensure all foreign keys are correctly resolved and not causing conflicts. (6) Verify that all configuration files are correctly set up and do not contain any errors. (7) Replay or rerun failed transactions to ensure they are processed correctly ERROR: Trouble sending health email;Email failure (if a monitoring email was set up and system cannot reach it) ERROR: Unable to copy license file for %s' % pkg['name'] out=True);Possible issue with copying the license file for a specified package. Contact VOSS Support or try these steps: (1) Ensure that the path specified for the license file is correct and accessible. (2) Verify that the file permissions for the license file allow for reading and writing. (3) Ensure sufficient disk space available to copy the license file. (4) Verify that the license file is not corrupted and is in the expected format. (5) Check system logs for any additional error messages or clues about why the license file copying failed. (6) Retry the operation to copy the license file after verifying the above steps ERROR: Unknown error: ;Contact VOSS Support or try these steps: (1) Check system logs for any additional error messages or clues about the cause of the unknown error. (2) Ensure all database connections are properly configured and accessible. (3) Check for any unhandled errors in the logs or error messages. (4) Ensure all queries and data operations are correctly formed and executed. (5) Ensure that all foreign keys are correctly resolved and not causing conflicts. (6) Verify all configuration files are correctly set up and do not contain any errors ERROR: upgrade failed ;Script install failures ERROR: upgrade failed upgrade failed as other activity is in progress ...;Script install failures ERROR: user missing or not specified. USAGE: mailxfwd.py );The user parameter may be missing or not correctly specified when running the mailxfwd.py script. Contact VOSS Support or try these steps: (1) Ensure that the user parameter is correctly specified when running the mailxfwd.py script. (2) Ensure that the specified user exists and has the necessary permissions. (3) Verify that all required user parameters are provided and not missing. (4) Verify that the specified user exists in the system. (5) Ensure that the user has the necessary permissions to perform the requested operation. (6) Check system logs for any additional error messages or clues about why the user specification failed ERROR: user not specified);A user-related parameter may be missing or not correctly specified. Contact VOSS Support or try these steps: (1) Ensure the user details are correctly specified in the request or configuration. (2) Verify that all required user parameters are provided and not missing. (3) Verify that the specified user exists in the system. (4) Ensure that the user has the necessary permissions to perform the requested operation. (5) Check system logs for any additional error messages or clues about why the user specification failed. (6) Update user configuration to ensure that all required parameters are correctly specified ERROR: Web certificate about to expire..;Trap is generated when the nginx web certificate is about to expire. Three intervals are checked which will return a result: 30 days prior to expiry 14 days prior to expiry 1 day prior to expiry. After expiry an alert is sent every day. ERROR: You may not disable the only enabled SSL protocol!);Ensure that at least one SSL protocol remains enabled. If you want to disable the currently enabled protocol (e.g. TLSv1.2) you must first enable another supported protocol (e.g. TLSv1.3). Once another protocol is enabled you can disable the previously enabled protocol. ERROR: You may only enable a supported protocol.);Ensure the protocol is one supported in Automate. See the list of supported SSL ciphers, which may change and ciphers are added or existing ones are found to be insecure. For the most up-to-date information you can refer to the VOSS Automate documentation on supported SSL ciphers. INFO: All notify levels is now configured with an external email address ..; INFO: Application has changed its PID from %s to %s - %s:%s; INFO: Application has changed its state from %s to %s - %s:%s; INFO: Application start command completed $APP; INFO: Application was killed ${app}:${process}; INFO: Backup completed...; INFO: Backups now runs regularly ; INFO: Database maintenance is scheduled ...; INFO: Database %s returned to normal ...; INFO:default_text ; INFO: DISK STATUS: Disk {} is now running below {} percent. Disk %s cleared Disk status after it was cleared; INFO: DISK STATUS: Disk {} is now running below {} percent'.format(disk_path limit) ; INFO: dns is now configured for %s ...; INFO: domain is now configured for %s...; INFO: EXTERNSHEET needs %d bytes have %d; INFO: Health emails is now being sent; INFO: License file generated ; INFO: Memory usage returned to normal Memory more than 1024MB; INFO: Messages for %s auto archived as it reached more than 500...; INFO: Network failures resolved ...; INFO: nginx upstreams OK nginx upstream servers returned to normal; INFO: ntp is now configured for %s ...; INFO: Restore successful...; INFO: Security Updates applied ...; INFO: Services started successfully ...; INFO: System taken out of maintenance mode; INFO: Test notifications; INFO: The db failover status returned to normal ...; INFO: The disk latency returned to normal ; INFO: The ntp daemon is now running on %s ...; INFO: The ntp offset restored to normal on %s ...; INFO: The total local messages for %s is now under 200...; INFO: Transaction archive files OK... ; INFO: Trying to access sector %d but only %d available; INFO: /var/log rotated ...; INFO: Web certificate has been renewed ...; WARNING: {} API Request Limit Exceeded; WARNING: {} Exceeded Threshold; WARNING: {} Session Limit Exceeded; WARNING: A CSR private key file exists which does not have a valid correspoding CA signed certificate.; WARNING: Applications are restarting $APP; WARNING: Applications are stopping${APP:+ }${APP}; WARNING: Automate License Expired; WARNING: Automate License Expiry; WARNING: Autopurging /var/log due to extremely high disk usage. [platform_mon.py] Usage {}: {}.format(use_limit message); WARNING: Autopurging /var/log due to extremely high disk usage. Usage $USAGE: $message; WARNING: Auto-reloading does not work with Fapws3. ); WARNING: Backup maintenance of this location is not scheduled fg='yellow'); WARNING: Certificate_Maintenance; WARNING: Continuing with this command will render this node destroyed Do you want to continue? ; WARNING: Database %s exceeded threshold; WARNING: DB Index Size Exceeded Threshold; WARNING: DB Size Exceeded Threshold; WARNING: Device Change Notification; WARNING: Device Change Notification Collector; WARNING: Device Change Notification Collector data/CallManager; WARNING: Device Change Notification Collector is disabled for device {}; WARNING: DISK ALMOST FULL: Disk {} is more than {} percent full; WARNING: DISK ALMOST FULL: Disk /var/log is more than {} percent full; WARNING: failed to contact server: $TIMESERVER - retrying; WARNING: Files are missing a SHA1 attribute.; WARNING: Forcing log rotation as /var/log is at $USAGE usage: $message; WARNING: Forcing log rotation as /var/log is at {} usage. [platform_mon.py] {}.format(use_limit message); WARNING: For performance reasons 'iop' is not bounds-checked ; WARNING: gevent: Error when handling error; WARNING: gevent: running prepare callbacks from a destroyed handle: ; WARNING: gevent: Unable to dereference handle; WARNING: gevent: Unhandled error with no watcher; WARNING: Global Administration Session Limit Exceeded ; WARNING: hyperlink at R%dC%d has %d extra data bytes: %s ; WARNING: No dns configured for %s...; WARNING: No domain configured for %s...; WARNING: Not all notify levels is configured with an external email address ...; WARNING: not saving as location + is not a local file reference; WARNING: object in expression is not renderable: ; WARNING: Previous backups created in locations {} cannot be restored unless the passphrase is reverted .format(' '.join(relevent_locations))); WARNING: Removing file and re-downloading %s as SHA checksum is mismatched' % os.path.basename(outfile) fg='yellow'); WARNING: Running IDLE without a Subprocess is deprecated +; WARNING: Security Updates available ...; WARNING: System going into maintenance mode; WARNING: The easy_install command is deprecated ; WARNING: The filename %r CAN be encoded by the filesystem encoding (%s). ; WARNING: The function doesn't check string content the result may not be a; WARNING: The ntp daemon has stopped on %s ...; WARNING: The ntp offset exceeds 1 second on %s ..; WARNING: The system preference Prefer tabs when opening; WARNING: The total messages in the local mailbox for %s has reached in excess of 200..; WARNING: The values for DNS email and URI are WRONG. OpenSSL; WARNING: Transaction Completed with {}; WARNING: Transaction Completed with Fail; WARNING: Transaction Completed with Mock-Fail; WARNING: Transaction Queue Size Exceeded Threshold; WARNING: Unknown usernames may become world readable.; WARNING: You are about to upgrade the system which will cause the system to restart. Do you wish to continue? ;