Project

General

Profile

Actions

Bug #4406

closed

Strange warning about Store Agent Run Times

Added by Dennis Cabooter about 10 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In the webapp logs I get the following warning:

[2014-01-27 10:16:35] WARN  application - [Store Agent Run Times] Task frequency is set too low! Last task took 8818 ms but tasks are scheduled every 5000 ms. Adjust rudder.batch.storeAgentRunTimes.updateInterval if this problem persists.

What can I do to resolve this?

Actions #1

Updated by Nicolas CHARLES about 10 years ago

  • Category set to Web - Compliance & node report
  • Status changed from New to Discussion
  • Target version set to 2.8.3

Hi Dennis,

Is this message constantly appearing (every 5 secondes), or is it only from time to time ?

Actions #2

Updated by Dennis Cabooter about 10 years ago

It's from time to time:

# grep rudder.batch.storeAgentRunTimes.updateInterval /var/log/rudder/webapp/2014_01_27.stderrout.log | awk -F ] '{ print $1"]" }'
[2014-01-27 01:21:46]
[2014-01-27 02:01:57]
[2014-01-27 03:37:03]
[2014-01-27 03:41:32]
[2014-01-27 04:11:40]
[2014-01-27 05:06:53]
[2014-01-27 05:31:39]
[2014-01-27 05:36:30]
[2014-01-27 09:11:57]
[2014-01-27 10:16:35]
[2014-01-27 10:31:55]
[2014-01-27 10:47:31]
[2014-01-27 11:01:32]
[2014-01-27 11:01:42]
[2014-01-27 13:01:15]
[2014-01-27 13:01:52]
[2014-01-27 16:11:39]
[2014-01-27 16:12:11]
Actions #3

Updated by Nicolas CHARLES about 10 years ago

  • Assignee set to Dennis Cabooter

There is no definitive pattern in these dates.
This warning means that the actor that detects when the agent was executed last on the nodes needed more than 5 secondes to run, while is should really take less than one second.
You also say you have issues with slowness in the webapp. Could it be that you have issues with your database ?
Could you run the following command in Postgres:

\d ruddersysevents

and past the result here ?

Actions #4

Updated by Dennis Cabooter about 10 years ago

Yes sire, of course I could. :)

rudder=> \d ruddersysevents
                                Table "public.ruddersysevents" 
       Column       |           Type           |                  Modifiers                   
--------------------+--------------------------+----------------------------------------------
 id                 | integer                  | not null default nextval('serial'::regclass)
 executiondate      | timestamp with time zone | not null
 nodeid             | text                     | not null
 directiveid        | text                     | not null
 ruleid             | text                     | not null
 serial             | integer                  | not null
 component          | text                     | not null
 keyvalue           | text                     | 
 executiontimestamp | timestamp with time zone | not null
 eventtype          | character varying(64)    | 
 policy             | text                     | 
 msg                | text                     | 
Indexes:
    "ruddersysevents_pkey" PRIMARY KEY, btree (id)
    "component_idx" btree (component)
    "composite_node_execution_idx" btree (nodeid, executiontimestamp)
    "executiondate_idx" btree (executiondate)
    "executiontimestamp_idx" btree (executiontimestamp)
    "keyvalue_idx" btree (keyvalue)
    "nodeid_idx" btree (nodeid)
    "ruleid_idx" btree (ruleid)
Check constraints:
    "ruddersysevents_component_check" CHECK (component <> ''::text)
    "ruddersysevents_directiveid_check" CHECK (directiveid <> ''::text)
    "ruddersysevents_nodeid_check" CHECK (nodeid <> ''::text)
    "ruddersysevents_ruleid_check" CHECK (ruleid <> ''::text)

rudder=>
Actions #5

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.8.3 to 2.8.4
Actions #6

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.8.4 to 133
Actions #7

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 133 to 2.9.5
Actions #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.9.5 to 2.9.6
Actions #9

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.9.6 to 2.9.7
Actions #10

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.9.7 to 150
Actions #11

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 150 to 2.10.4
Actions #12

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.10.4 to 2.10.5
Actions #13

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions #14

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions #15

Updated by Fabrice FLORE-THÉBAULT over 9 years ago

i have the exact same issue, every 5 seconds.

Actions #16

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions #17

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions #18

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions #19

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions #20

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions #21

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions #22

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions #23

Updated by Benoît PECCATTE almost 9 years ago

  • Assignee changed from Dennis Cabooter to Nicolas CHARLES
Actions #24

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions #25

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions #26

Updated by Nicolas CHARLES almost 9 years ago

As a rule of thumb, this message should not appear. It means the database is probably not properly configured (see http://www.rudder-project.org/rudder-doc-3.0/rudder-doc.html#_application_tuning ), with default settings

Do you still have all these messages ?

Actions #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions #28

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions #29

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions #30

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #31

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 2.11.18
Actions #32

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #33

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #34

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #35

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #36

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #37

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #38

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions #39

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions #40

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #41

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #42

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #43

Updated by François ARMAND over 7 years ago

  • Status changed from Discussion to Rejected

Closing this as the correct answer is with a FAQ entry summarising the comments.

Actions

Also available in: Atom PDF