[ClusterLabs] Error performing operation: Argument list too long

[Jan Pokorný]

On 06/12/16 09:44 -0600, Ken Gaillot wrote:
> On 12/05/2016 02:29 PM, Shane Lawrence wrote:
>> 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?
> 
> That is odd behavior. You may want to open a bug report at
> bugs.clusterlabs.org and attach your configuration and logs.
> 
> On Linux, the system error number for "Argument list too long" is the
> same as the OCF monitor status "Not running", so I suspect that it's a
> display issue rather than an actual error, but I'm not sure.
> 
> Then the question would just be why is rsyslog stopping.

Even more that "Cluster Controlled rsyslog has been started" while
"System Logging Service" is being stopped.  Could it be a result
of a namespace/daemon/service clash of some kind?

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20161206/8619a66f/attachment-0003.sig>