Bug 1058601 - collectd doesn't write to RRD files after update
Summary: collectd doesn't write to RRD files after update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: collectd
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ruben Kerkhof
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 06:22 UTC by Timon
Modified: 2014-02-08 05:10 UTC (History)
4 users (show)

Fixed In Version: collectd-5.4.1-1.fc19
Clone Of:
Environment:
Last Closed: 2014-02-08 05:00:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Timon 2014-01-28 06:22:47 UTC
Description of problem:

some times ago collectd updated from 5.2.x version to 5.3.1, after that it stopped writing data to RRD files. yum downgrade resolves this problem

Version-Release number of selected component (if applicable):
collectd-5.3.1-1.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. yum update collectd 
2. systemctl restart collectd

Actual results:
rrd files doesn't update

Expected results:
rrd should update with new data

Additional info:
log files doesn't help too much
after restart service

Jan 28 10:18:03 vesta systemd[1]: Stopping Collectd...
Jan 28 10:18:03 vesta collectd[21387]: Exiting normally.
Jan 28 10:18:03 vesta collectd[21387]: collectd: Stopping 5 read threads.
Jan 28 10:18:03 vesta collectd[21387]: ping plugin: Shutting down thread.
Jan 28 10:18:03 vesta collectd[21387]: rrdtool plugin: Shutting down the queue thread. This may take a while.
Jan 28 10:18:03 vesta collectd[21387]: network plugin: Stopping receive thread.
Jan 28 10:18:03 vesta collectd[21387]: network plugin: Stopping dispatch thread.
Jan 28 10:18:03 vesta collectd[21387]: collectd: Stopping 5 write threads.
Jan 28 10:18:03 vesta systemd[1]: Starting Collectd...
Jan 28 10:18:03 vesta systemd[1]: Started Collectd.
Jan 28 10:18:03 vesta collectd[30613]: Initialization complete, entering read-loop.
Jan 28 10:18:03 vesta collectd[30613]: Successfully connected to database pgbouncer (user postgres) at server localhost:6432 (server version: 1.5.4, protocol version: 3, pid: 1565947460)
Jan 28 10:18:03 vesta collectd[30613]: Successfully connected to database sample (user postgres) at server localhost:5432 (server version: 9.2.4, protocol version: 3, pid: 30628)

Comment 1 Ruben Kerkhof 2014-01-28 12:43:55 UTC
I can't reproduce this based on your information.

Can you share your config?

Comment 2 Timon 2014-01-29 04:12:01 UTC
collectd.conf

Hostname     "vesta.example.com"
FQDNLookup   false
Include      "/etc/collectd.d"

LoadPlugin syslog

<Plugin syslog>
        LogLevel info
</Plugin>

LoadPlugin aggregation
LoadPlugin cpu
LoadPlugin disk
LoadPlugin interface
LoadPlugin load
LoadPlugin memory
LoadPlugin network
LoadPlugin protocols

<Plugin disk>
        Disk "/^sd[a-f]$/"
</Plugin>

<Plugin interface>
        Interface "em1"
        Interface "em2"
</Plugin>

<Plugin network>
        Listen "fc00::10:0:0:4" "25826"
</Plugin>

<Plugin protocols>
        Value "/^Tcp:/"
</Plugin>

LoadPlugin match_hashed
LoadPlugin match_regex
LoadPlugin match_value

LoadPlugin target_replace
LoadPlugin target_set

<Plugin "aggregation">
  <Aggregation>
    Plugin "cpu"
    Type "cpu"

    GroupBy "Host"
    GroupBy "TypeInstance"

    CalculateSum true
    CalculateAverage true
  </Aggregation>
</Plugin>

/etc/collectd.d/perl.conf 
LoadPlugin perl

/etc/collectd.d/ping.conf
LoadPlugin ping

<Plugin ping>
        Host "venus.example.com"
        Host "oberon.example.com"
        Host "eris.example.com"
        Host "aurora.example.com"
</Plugin>

/etc/collectd.d/postgresql.conf
LoadPlugin postgresql

<Plugin postgresql>
  <Query pgbouncer>
    Statement "show stats;"

    <Result>
      Type gauge
      InstancesFrom database
      InstancePrefix avg_request
      ValuesFrom avg_req
    </Result>
    <Result>
      Type gauge
      InstancesFrom database
      InstancePrefix avg_query
      ValuesFrom avg_query
    </Result>
  </Query>

  <Query pools>
    Statement "show pools;"

    <Result>
       Type gauge
       InstancesFrom database user
       InstancePrefix clients_active
       ValuesFrom cl_active
    </Result>

    <Result>
       Type gauge
       InstancesFrom database user
       InstancePrefix clients_waiting
       ValuesFrom cl_waiting
    </Result>

    <Result>
       Type gauge
       InstancesFrom database user
       InstancePrefix servers_active
       ValuesFrom sv_active
    </Result>

    <Result>
       Type gauge
       InstancesFrom database user
       InstancePrefix servers_idle
       ValuesFrom sv_idle
    </Result>
  </Query>

  <Database pgbouncer>
    Host "localhost"
    Port "6432"
    User "postgres"
    Query pgbouncer
    Query pools
  </Database>


  <Query replay_lag>
    Statement "SELECT pg_xlog_location_diff(pg_last_xlog_receive_location(), pg_last_xlog_replay_location()) as bytes_lag"

    <Result>
       Type gauge
       InstancePrefix bytes_lag
       ValuesFrom bytes_lag
    </Result>

  </Query>

  <Database sample>
    Host "localhost"
    Port "5432"
    User "postgres"
    Query replay_lag
  </Database>

</Plugin>

/etc/collectd.d/rrdtool.conf
LoadPlugin rrdtool
<Plugin rrdtool>
       DataDir "/opt/dev.example.com/collectd/rrd"
       CacheTimeout 30
       CacheFlush   60
</Plugin>

Comment 3 Ruben Kerkhof 2014-01-29 09:47:31 UTC
Can you reverse these lines?

Include      "/etc/collectd.d"

LoadPlugin syslog

<Plugin syslog>
        LogLevel info
</Plugin>

So first load the syslog plugin before loading the configs in the include directory. Hopefully this shows more output.

I also see that you don't have BaseDir and TypesDB defined, maybe that helps?

Comment 4 Timon 2014-01-29 11:08:03 UTC
hmm. seems that this bug has been fixed in git. 
https://github.com/collectd/collectd/issues/380
so, let's wait for 5.3.2 :)
thanks for help

Comment 5 Fedora Update System 2014-01-30 17:50:33 UTC
collectd-5.4.1-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/collectd-5.4.1-1.fc20

Comment 6 Fedora Update System 2014-01-30 17:59:00 UTC
collectd-5.4.1-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/collectd-5.4.1-1.fc19

Comment 7 Fedora Update System 2014-01-31 04:28:58 UTC
Package collectd-5.4.1-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing collectd-5.4.1-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1845/collectd-5.4.1-1.fc19
then log in and leave karma (feedback).

Comment 8 Timon 2014-01-31 11:50:30 UTC
updated package works fine

Comment 9 Fedora Update System 2014-02-08 05:00:53 UTC
collectd-5.4.1-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2014-02-08 05:10:01 UTC
collectd-5.4.1-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.