Project

General

Profile

Actions
Copy link

Bug #1751

closed

counters not working

Added by Anonymous almost 15 years ago. Updated over 14 years ago.

Status:
Missing Feedback
Priority:
Normal
Category:
mod_status
Target version:
1.5.0
ASK QUESTIONS IN Forums:

Description


[root@ sbin]# while true; do curl http://localhost/server-status?auto ; sleep 5;done
Total Accesses: 9465710
Total kBytes: 20287193749
Uptime: 966704
BusyServers: 658
Total Accesses: 9465747
Total kBytes: 20287307159
Uptime: 966709
BusyServers: 671
Total Accesses: 9432979
Total kBytes: 20197886814
Uptime: 966714
BusyServers: 677
Total Accesses: 9472926
Total kBytes: 20292078638
Uptime: 966719
BusyServers: 655

See how both Total Accesses and Total kBytes go up and down all the time around that limit.

Actions
Copy link
 #1

Updated by icy almost 15 years ago

mod_status uses the double type as counter which has limits, you will never reach (1.8 * 10^19 for 64bit doubles). An overflow is out of question.

May I guess: you are using multiple workers, right? That would explain why you get seemingly random numbers that float around some value which gets increased as time passes.
If so: there are big warnings for using multiple workers. Doing so breaks counters and other stuff.
Do this only if you exactly know what you are doing.

Actions
Copy link
 #2

Updated by stbuehler almost 15 years ago

  • Status changed from New to Fixed
  • Resolution set to worksforme
Actions
Copy link
 #3

Updated by stbuehler over 14 years ago

  • Status changed from Fixed to Missing Feedback
Actions
Copy link

Also available in: Atom