Bug #17469
openDSC agent reports may have incorrect timezone format making them not showing at top in technical logs
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)
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).
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
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0~rc1 to 6.1.0~rc2
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0~rc2 to 6.1.0~rc3
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0~rc3 to 6.1.0~rc4
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0~rc4 to 6.1.0
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0 to 6.1.1
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.1 to 6.1.2
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
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.2 to 6.1.3
Updated by François ARMAND over 4 years ago
- Target version changed from 6.1.3 to 6.1.4
- Priority changed from 51 to 50
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.4 to 6.1.5
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.5 to 6.1.6
- Priority changed from 50 to 49
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.1.7
- Priority changed from 49 to 48
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.7 to 6.1.8
- Priority changed from 48 to 47
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.8 to 6.1.9
- Priority changed from 47 to 46
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.9 to 6.1.10
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.10 to 6.1.11
- Priority changed from 46 to 45
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.11 to 6.1.12
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.12 to 6.1.13
- Priority changed from 45 to 44
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.13 to 6.1.14
- Priority changed from 44 to 43
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by Alexis Mousset 8 months ago
- Target version changed from old 6.1 issues to relocate to 7.3.15
- Priority changed from 43 to 0
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 7.3.15 to 7.3.16
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 7.3.16 to 7.3.17