PLANTA Server Service (PLANTA Service)

Error rendering macro 'fontawesome-macro' : Page loading failed

For information

The PLANTA Server service is automatically set up during installation under both Windows and Linux.
At the same time, the name of the service will be allocated as well.

For the administration of the PLANTA Server service, there are batch scripts (for Windows installations) and shell scripts (for Linux installations) each in the server directory under yajsw/bat.

Error rendering macro 'fontawesome-macro' : Page loading failed

Scripts

Linux	Windows	Function
`installDaemon.sh`	`installService.bat`	For a one-time installation of the PLANTA Server service. Usually it does not have to be run manually, since it is run during automatic installation.
`uninstallDaemon.sh`	`uninstallService.bat`	For a one-time installation of the PLANTA Server service. Should be carried out if you carry out a reinstallation (e.g. in the case of installation errors), PLANTA is uninstalled, or you change to another Java version (see above).
`startDaemon.sh`	`startService.bat`	Starts the PLANTA Server service. Error rendering macro 'fontawesome-macro' : Page loading failed Even if the script outputs that the service has been started, it will still take about one minute until the server can accept the new connection.
`stopDaemon.sh`	`stopService.bat`	Shuts down the PLANTA Server service. Error rendering macro 'fontawesome-macro' : Page loading failed All clients that are still connected to the server will lose their connection. The PLANTA Server service can be restarted immediately afterwards.
`queryDaemon.sh`	`queryService.bat`	Informs on the current status of the PLANTA Server service. Error rendering macro 'fontawesome-macro' : Page loading failed `Installed` must be set to "true" in order for the PLANTA Server service to be bootable. If `Running` is set to "true", the PLANTA Server service is running.

Logging

Error rendering macro 'fontawesome-macro' : Page loading failed

For information

In the log/ directory at the installation site, log files will be created.
They are configured with a preconfigured warn log threshold value with daily rotation.
If the operation of the monitoring component causes problems, these log files are to be checked, since they can show hints to the root of such problems.
A comprehensive output of log messages can be achieved as described in the Logging configuration section.