service start
Start a named service on the Luna Network HSM 7 appliance. Services usually need to be started only if they were stopped with a service stop command, or if the service stopped unexpectedly.
Use the service list command to display a list of services that you can stop.
User Privileges
Users with the following privileges can perform this command:
>Admin
>Operator
Syntax
service start <service_name>
| Argument(s) | Shortcut | Description |
|---|---|---|
| <service_name> |
Specifies the service to start. Valid values: cbs, cluster, clusteradmin, ctc, lsta, network, ntls, ntp, pedserver, snmp, ssh, stc, syslog, sysstat, webserver |
|
| -force | -f |
Applies to the cluster service only. Including this option will force the cluster service to start, regardless of whether other members of the cluster can be reached. Use only with the guidance of a Thales Support Engineer. CAUTION! Only use the -force option on the primary cluster member if you are prepared to factory reset the cluster service on all other members and re-add them to the cluster from scratch. When service start cluster -force is run, the internal Ignite configuration on that member is reconfigured to reflect a single-node cluster. This change is not reflected in the external configurations of other members. If those members are not factory reset (sysconf config factoryreset -service cluster) and re-joined to the cluster, hidden inconsistencies will exist between their internal and external Ignite configurations. These inconsistencies may not cause immediate problems, but can result in unpredictable cluster behavior in the future. |
Example
lunash:>service start syslog Starting syslog: [ OK ] Command Result : 0 (Success)
