Bug #17469: DSC agent reports may have incorrect timezone format making them not showing at top in technical logs - Rudder - Issue Tracker

Actions

Copy link

Bug #17469

open

DSC agent reports may have incorrect timezone format making them not showing at top in technical logs

Added by Félix DALLIDET over 4 years ago. Updated 5 months ago.

Status:

New

Priority:

N/A

Assignee:

Category:

Web - Compliance & node report

Target version:

7.3.17

Pull Request:

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

Name check:

To do

Fix check:

To do

Regression:

Description

This is the second time it happens to me.
I have an agent which is reporting, and suddenly the technical logs page does not update anymore. I can ctrl+f5, clear cache the page, it does not change anything.
A restart of the webapp or the web browser do not fix the issue.

The postgres is still ok and contains newer reports that are now shown on the webapp.
See attached screenshots. A sample of the database, which seems correct:

[root@server configuration-repository]# psql -U rudder -h localhost -c "select * from ruddersysevents where nodeid = '797c9215-d3c2-4c72-b8a3-6b1176f87d9f' order by executiontimestamp desc limit 10" 
  id   |     executiondate      |                nodeid                |  directiveid   |    ruleid     | serial |        component        |         keyvalue         |   executiontimestamp   
|   eventtype    |         policy          |                                                                                 msg                                                               

-------+------------------------+--------------------------------------+----------------+---------------+--------+-------------------------+--------------------------+------------------------
+----------------+-------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------
-------------------
 43790 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | run            | rudder        |      0 | start                   | 20200520-143253-248360b3 | 2020-05-20 14:40:00+00 
| control        | start                   | Start execution
 43791 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | Reporting configuration | nxlog                    | 2020-05-20 14:40:00+00 
| result_success | Reporting configuration | Managing nxlog configuration file
 43792 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | Service status          | nxlog                    | 2020-05-20 14:40:00+00 
| result_success | Service status          | Managing nxlog configuration file
 43793 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | System variables        | parameters               | 2020-05-20 14:40:00+00 
| result_success | System variables        | Defined Rudder global parameters
 43794 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | System variables        | properties               | 2020-05-20 14:40:00+00 
| result_success | System variables        | Defined Rudder properties
 43795 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | Agent Configuration     | Agent-Schedule           | 2020-05-20 14:40:00+00 
| result_success | Agent Configuration     | File C:\Program Files\Rudder\share\scheduler\Rudder-Agent.xml content already match template C:\Program Files\Rudder\policy\dsc-common\1.0\templat
e\Rudder-Agent.xml
 43796 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | Agent tasks             | Rudder-Agent             | 2020-05-20 14:40:00+00 
| result_success | Agent tasks             | The Rudder-Inventory task, scheduled to be run every night
 43797 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | Agent tasks             | Rudder-Inventory         | 2020-05-20 14:40:00+00 
| result_success | Agent tasks             | The Rudder-Inventory task, scheduled to be run every night
 43798 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | dsc-common-all | dsc-agent-all |      0 | Log system for reports  | None                     | 2020-05-20 14:40:00+00 
| result_na      | Log system for reports  | Reports forwarding to policy server
 43799 | 2020-05-20 07:40:03+00 | 797c9215-d3c2-4c72-b8a3-6b1176f87d9f | run            | rudder        |      0 | end                     | 20200520-143253-248360b3 | 2020-05-20 14:40:00+00 
| control        | end                     | End execution
(10 lignes)

Actions

Copy link

Updated by François ARMAND over 4 years ago

Subject changed from Technical logs page is stuck on the same logs forever to DSC agent logs may have incorrect timezone format making them not showing at top in technical logs

So it seems to be a problem with timezone or date/time of the node. The node reports were timestamped several hours before "now" and so weren't apperearing at the expected place.

https://issues.rudder.io/issues/17466 correction could solve that problem, too (not its root cause it the problem is date/time format on node, just the fact that we don't see pb).

Actions

Copy link

Updated by François ARMAND over 4 years ago

Subject changed from DSC agent logs may have incorrect timezone format making them not showing at top in technical logs to DSC agent reports may have incorrect timezone format making them not showing at top in technical logs

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.0~rc1 to 6.1.0~rc2

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.0~rc2 to 6.1.0~rc3

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.0~rc3 to 6.1.0~rc4

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.0~rc4 to 6.1.0

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.0 to 6.1.1

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.1.1 to 6.1.2

Actions

Copy link

#10

Updated by François ARMAND over 4 years ago

Severity set to Major - prevents use of part of Rudder | no simple workaround
User visibility set to Operational - other Techniques | Rudder settings | Plugins
Priority changed from 0 to 51