[ClusterLabs] Error performing operation: Argument list too long

[Shane Lawrence]

I'm experiencing a strange issue with pacemaker. It is unable to check the
status of a systemd resource.

systemctl shows that the service crashed:
[root at xxxxxxxxxx ~]# systemctl status rsyslog
● rsyslog.service - System Logging Service
   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor
preset: enabled)
   Active: inactive (dead) since Mon 2016-12-05 07:41:11 UTC; 12h ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
 Main PID: 22703 (code=exited, status=0/SUCCESS)

Dec 02 21:41:41 xxxxxxxxxx.xxxx.xxxx.xx systemd[1]: Starting Cluster
Controlled rsyslog...
Dec 02 21:41:41 xxxxxxxxxx.xxxx.xxxx.xx systemd[1]: Started Cluster
Controlled rsyslog.
Dec 05 07:41:08 xxxxxxxxxx.xxxx.xxxx.xx systemd[1]: Stopping System Logging
Service...
Dec 05 07:41:11 xxxxxxxxxx.xxxx.xxxx.xx systemd[1]: Stopped System Logging
Service.
Dec 05 07:41:40 xxxxxxxxxx.xxxx.xxxx.xx systemd[1]: Stopped System Logging
Service.

Attempting to view the status through Pacemaker shows:
[root at xxxxxxxxxx ~]# crm_resource --force-check -V -r rsyslog
Error performing operation: Argument list too long
[root at xxxxxxxxxx ~]# pcs resource debug-monitor rsyslog --full
Error performing operation: Argument list too long

The problem seems to be resolved (temporarily) by restarting corosync and
then starting the cluster again.

Has anyone else experienced this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20161205/7c9f69ec/attachment-0002.html>