Figure: The Daemons View
The Daemons view in the Stardust Administration Portal shows the five daemons used in the Stardust context:
For detailed information on these daemons, please refer to the chapter Daemons in the Administrative Concepts section of the Stardust Online Documentation - Concepts. Daemons in the Administrative Concepts of the Concepts part.
This table displays the following information about these daemons:
Figure: The Daemons View
You have the option to select the columns to be displayed in
the table and reorder them. Click the Select Columns
icon 
to open
the Select Columns dialog, which is described
in detail in the section Column Selection and Reordering
of the chapter Stardust Portal Components.
Figure: Select Columns Dialog
The data in the table may be exported to an Excel or CSV file. To export
to a file, click 
to export to Excel or
to export to a CSV file.
Please refer to the section Exporting Table Content of the chapter Stardust Portal Components for detailed information.
The table may be sorted by any sortable column by clicking the sort icon
in the column header. The table data can be toggled
between ascending and descending order when the sort icon is clicked.
Please refer to the section Sorting of the chapter Stardust Portal Components for detailed information.
To start a daemon, select the Start Daemon button in the Actions column of the according daemon.
Figure: Starting a Daemon
After a daemon has been started, the entries in the corresponding row in the Daemons view must change accordingly, displaying a new start time and status set to Running.
Figure: Daemon changed to Running State.
To stop a daemon, select the Stop Daemon button in the Actions column of the according daemon.
Figure: Stopping a Daemon
After a daemon has been stopped, the entries in the corresponding row of the Daemons view must change accordingly, clearing the start and last execution times and displaying the status set to Stopped.
It could be necessary to stop the daemon to avoid problems during deployment or cleaning up the audit trail, even though it is displayed as Stopped. This is the case when the acknowledge state is not displayed as OK at the same time.
The Acknowledge State reflects the communication capability of the daemons. An OK message means that the daemon was able to perform the command, while a Failure message means that the daemon has received the command, but was unable to successfully execute it. A Response Requested message in most of the cases reflects a "zombie" daemon, i.e. the daemon was started but the process executing it terminated without updating the audit trail.
You have the option to adjust the number of retries to get a daemon operation acknowledgment. Set the property <daemon_name>.AckRetries in your carnot.properties file to a number of retries you would like to be used. The default value is 10 retries.
To change the number of seconds to wait between two daemon operation acknowledgments, set the property <daemon_name>.AckWait in your carnot.properties file accordingly. The default value is 2 seconds.
The Execution State shows the execution result of the daemon. An OK message shows that the daemon executed without problems, a Warning message specifies that a problem occurred during daemon run but the daemon could continue to run, while a Fatal message specifies that the daemon has stopped due to a fatal execution error.