Get-PveNodesServicesState
Read service properties
API: GET /nodes/{node}/services/{service}/state, Proxmox VE API viewer
Syntax
Section titled “Syntax”Get-PveNodesServicesState [-PveTicket <PveTicket>] -Node <string> -Service <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Node |
string |
Yes | The cluster node name. |
-Service |
string |
Yes | Service ID. Values: chrony, corosync, cron, ksmtuned, lxcfs, postfix, proxmox-firewall, pve-cluster, pve-firewall, pve-ha-crm, pve-ha-lrm, pve-lxc-syscalld, pvedaemon, pvefw-logger, pveproxy, pvescheduler, pvestatd, qmeventd, spiceproxy, sshd, syslog, systemd-journald, systemd-timesyncd. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
