Project

General

Profile

Bug #25008

An error is returned by rrdtool when updating Log_Counts.rrd

Added by Bruno Coimbra 7 months ago. Updated about 1 month ago.

Status:
Remission
Priority:
Normal
Assignee:
-
Category:
-
Target version:
v3_9_2
Start date:
09/23/2020
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

The factory monitoring (glideFactoryMonitoring) fails to update the Log_Counts.rrd file with an error returned by rrd_tools.

Steps to reproduce:
- Stop the factory
- Remove a Log_Counts.rrd file (e.g. /var/lib/gwms-factory/work-dir/monitor/entry_ITB_FC_SIN_CE2/total/Log_Counts.rrd)
- Upgrade the factory
- Start the factory

Error:

[2020-09-21 10:27:12,157] ERROR: glideFactoryMonitoring:249: Failed to update /var/lib/gwms-factory/work-dir/monitor/entry_ITB_FC_SIN_CE2/total/Log_Counts.rrd:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/glideinwms/factory/glideFactoryMonitoring.py", line 247, in write_rrd_multi_hetero
    self.rrd_obj.update_rrd_multi(fname, time, val_dict)
  File "/usr/lib/python3.6/site-packages/glideinwms/lib/rrdSupport.py", line 183, in update_rrd_multi
    self.rrd_obj.update(*args)
  File "/usr/lib/python3.6/site-packages/glideinwms/lib/rrdSupport.py", line 543, in update
    outstr = subprocessSupport.iexe_cmd(cmdline)
  File "/usr/lib/python3.6/site-packages/glideinwms/lib/subprocessSupport.py", line 101, in iexe_cmd
    raise CalledProcessError(exitStatus, cmd, output="".join(stderrdata))
subprocess.CalledProcessError: Command '/bin/rrdtool update "/var/lib/gwms-factory/work-dir/monitor/entry_ITB_FC_SIN_CE2/total/Log_Counts.rrd" "-t" "EnteredCom
pleted:EnteredHeld:EnteredIdle:EnteredRemoved:EnteredRunning:EnteredWait:ExitedHeld:ExitedIdle:ExitedRunning:ExitedWait:StatusHeld:StatusIdle:StatusRunning:Sta
tusWait" "1600702031:0:0:0:0:0:0:0:0:0:0:0:0:0:0"' returned non-zero exit status 1.

History

#1 Updated by Bruno Coimbra 2 months ago

  • Status changed from New to Remission

I couldn't reproduce this error in any of my recent deployments of GWMS 3.9.1 factory.
It might have been a glitch with my environment at the time. I'll keep this issue open in case we ever find it again.

#2 Updated by Marco Mambelli about 1 month ago

  • Target version changed from v3_9_1 to v3_9_2

Also available in: Atom PDF