adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-10-31 01:32:02 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Timestamps suddenly change #151

New Issue
Closed
opened 2026-10-05 04:01:23 +02:00 by adam · 6 comments
adam commented 2026-10-05 04:01:23 +02:00
Owner
Copy link
Copy source

Hello,

I'm running the current stable build of znc for now and there is something weird that happend while running the bouncer for some weeks:

The timestamps shown during a playback are suddenly two hours offset.
I haven't changed the system time or the time on my client system while running the bouncer. Also, I haven't changed the user offset or anything else.

Is this a known problem?

Regards,

Hello, I'm running the current stable build of znc for now and there is something weird that happend while running the bouncer for some weeks: The timestamps shown during a playback are suddenly two hours offset. I haven't changed the system time or the time on my client system while running the bouncer. Also, I haven't changed the user offset or anything else. Is this a known problem? Regards, <!-- github-sync-id:7029204 -->
adam closed this issue 2026-10-05 04:01:23 +02:00
adam commented 2026-10-05 04:01:24 +02:00
Author
Owner
Copy link
Copy source

Current stable build = which exact version? 0.206?
ZNC didn't restart?
What modules are loaded?

Current stable build = which exact version? 0.206? ZNC didn't restart? What modules are loaded? <!-- github-comment-id:8765913 -->
adam commented 2026-10-05 04:01:25 +02:00
Author
Owner
Copy link
Copy source

Hello.
Yes, the current stable build which is 0.206 on Debian 6.0.5 using a chroot-environment as explained in the wiki.
ZNC is now running for weeks without a restart.

The following modules have been loaded:
Webadmin (listening on localhost only)
adminlog
awaynick
fail2ban
nickserv
simple_away

All other modules have been deactivated by moving the shared object files.

Regards,

Hello. Yes, the current stable build which is 0.206 on Debian 6.0.5 using a chroot-environment as explained in the wiki. ZNC is now running for weeks without a restart. The following modules have been loaded: Webadmin (listening on localhost only) adminlog awaynick fail2ban nickserv simple_away All other modules have been deactivated by moving the shared object files. Regards, <!-- github-comment-id:8766242 -->
adam commented 2026-10-05 04:01:26 +02:00
Author
Owner
Copy link
Copy source

Probably you had wrong time on the system, and then someone else executed ntpdate? Or maybe it's somehow related to switch from summer-time? What timezone is set on server?
You have only 1 user in ZNC?
Anyway, now (in 0.207/1.0) time offsets are handled differently, it sets TZ env variable while stringifying the timestamp instead of using offsets.

Probably you had wrong time on the system, and then someone else executed ntpdate? Or maybe it's somehow related to switch from summer-time? What timezone is set on server? You have only 1 user in ZNC? Anyway, now (in 0.207/1.0) time offsets are handled differently, it sets TZ env variable while stringifying the timestamp instead of using offsets. <!-- github-comment-id:8767008 -->
adam commented 2026-10-05 04:01:26 +02:00
Author
Owner
Copy link
Copy source

Hello,

ntpdate is being autoexecuted - the difference is always a few milliseconds - nothing special.
The timezone on the server is the CEST (GMT+1 +Summertime = 2) - like on my client with the znc user difference set to none.
The time hasn't changed since the last switch to summer time (I compiled and installed znc after that) accoring to the system logs.
And yes, there is one znc user only.
That's really odd.

Hello, ntpdate is being autoexecuted - the difference is always a few milliseconds - nothing special. The timezone on the server is the CEST (GMT+1 +Summertime = 2) - like on my client with the znc user difference set to none. The time hasn't changed since the last switch to summer time (I compiled and installed znc after that) accoring to the system logs. And yes, there is one znc user only. That's really odd. <!-- github-comment-id:8767415 -->
adam commented 2026-10-05 04:01:27 +02:00
Author
Owner
Copy link
Copy source

Btw, it's better to setup ntpd instead of autoexecute ntpdate... But it shouldn't matter for this.
So, if you change the znc user time offset by 2, it becomes good again?

Btw, it's better to setup ntpd instead of autoexecute ntpdate... But it shouldn't matter for this. So, if you change the znc user time offset by 2, it becomes good again? <!-- github-comment-id:8865053 -->
adam commented 2026-10-05 04:01:28 +02:00
Author
Owner
Copy link
Copy source

If you have more details, or can reproduce it, etc, reopen it

If you have more details, or can reproduce it, etc, reopen it <!-- github-comment-id:9639397 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#151