Note
This article applies only to standalone installations.
If users cannot access Lasernet Archive or the REST API is not responding, check the deployment status. This article explains how to check the deployment status and troubleshoot common startup issues for a standalone installation of Archive.
Check the Deployment Status
Archive is Java software running on a bundled Wildfly application server. After Wildfly starts, it completes the following deployment process that creates a running instance of the application:
Wildfly loads a
.earfile that contains the Archive software.Wildfly runs the software in that
.earfile.
If Archive is running and you can log in, it has been successfully deployed. However, if Wildfly cannot deploy Archive, the application will not run.
If you think Archive is not running, check its deployment status:
On the Archive server, navigate to:
<installation directory>\Wildfly-<version>\standalone\deployments. Appropriately substitute<installation directory>and<version>. The path to the<installation directory>varies depending on whether you chose the default installation.Locate
pdm_app_module.ear. This file contains the main Archive components.In the same directory, the extension of an accompanying file shows Archive’s deployment status. Locate this file and check the current deployment status. For example,
pdm_app_module.ear.deployed.
Archive deployment statuses:
.deployed: Archive was successfully deployed and is running..deploying: Wildfly is currently deploying the Archive application:If the deployment succeeds, the file’s extension changes to
.deployed.If the deployment fails, the extension changes to
.undeployedor.failed.
.undeployed: Wildfly has not deployed Archive. Before trying to restart Archive, you must complete further configuration steps. Check the Lasernet Archive logs for messages that identify the cause of the problem. Often, licensing issues cause this problem. If you require further assistance, contact Lasernet Support..failed: Wildfly failed to deploy Archive. See Troubleshoot Startup Issues to resolve common issues.
Troubleshoot Startup Issues
The following sections describe common startup issues and provide resolution steps:
Lasernet Archive Starts Before One or More of Its Dependencies
Lasernet Archive Startup is Affected by a Firewall or Local Security Policy
If none of these issues is the cause of deployment failure, check the Lasernet Archive logs for messages that identify the root cause. If the logs do not help you to identify the cause, contact Lasernet Support.
Lasernet Archive Starts Before One or More of Its Dependencies
If Archive depends on an external software component that has not yet started when the application starts up, Wildfly will fail to deploy Archive. This can happen when the server is restarted.
Try manually restarting Lasernet Archive to resolve this issue.
A Port Conflict Occurs
A port conflict can prevent Archive from starting.
Use your preferred tools and approach to investigate the current port allocation for Archive and other software. If a conflict is found, take appropriate steps.
Lasernet Archive Startup is Affected by a Firewall or Local Security Policy
Firewall configuration or a local security policy can prevent Archive from binding its configured port. This will prevent Archive from starting.
To resolve this issue, follow these steps:
Locate the Archive
standalone.xmlfile. It is in<installation directory>\Wildfly-<version>\standalone\configurationfile (appropriately substitute<installation directory>and<version>). Thestandalone.xmlfile is in the same directory asnode.properties.Open the file and locate the following lines:
<server name="default-server"> <http-listener name="default" socket-binding="http" max-post-size="${max.post.size}" max-parameters="15000" ... <https-listener name="default-https" socket-binding="https" max-post-size="${max.post.size}" max-parameters="15000" ... <host name="default-host" alias="localhost"> <location name="/" handler="welcome-content"/> ...In the
<host name="default-host" alias="localhost">line, changelocalhostto your server’s host name.Save
standalone.xml.
Manually Restart Lasernet Archive
After you have taken the recommended troubleshooting steps, restart Archive.
If Archive is running as a Windows service, follow these steps to restart it:
Open the Windows Services window.
Locate the Archive service. For example, Lasernet Archive Server 11.3 - Standalone [Production]. The service name contains the Archive version number and includes the corresponding Archive node name in square brackets. The node name is entered during installation and is typically the name of the relevant service.
Click Restart Service.
Note
The restart can take up to 10 minutes.