# Win 2003 32 bit OS Period(Time) is not correct it is showing default **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [February 6, 2018, 8:22pm UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713 "2018-02-06T20:22:16Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dilip](https://avatars.discourse-cdn.com/v4/letter/d/47e85d/32.png) [@dilip](https://discuss.elastic.co/u/dilip)\ **Post date:** [February 6, 2018, 8:22pm UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/1 "2018-02-06T20:22:16Z")
Hi, I am using Metricbeat 6.0.0 on WIn 2003 OS 32 Bit .with System module to collect the performance data. everything is working fine except Period Interval .its taking default as 10s instead of custom like 2m. Please suggest is this a bug . example like this .it is not accepting period as a 2 minute instead it is counting as 10s. ```auto - module: system period: 2m metricsets: - cpu #- load - memory - network - process - process_summary ``` ---
**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\ **Post date:** [February 7, 2018, 10:11am UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/2 "2018-02-07T10:11:44Z")
Could you provide us the debug logs of metricbeat (output of `metricbeat -e -d "*"`)? ---
**Author:** ![dilip](https://avatars.discourse-cdn.com/v4/letter/d/47e85d/32.png) [@dilip](https://discuss.elastic.co/u/dilip)\ **Post date:** [February 12, 2018, 2:38pm UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/3 "2018-02-12T14:38:53Z")
Here is the debug output. 2018/02/12 13:54:18.033936 metrics.go:23: INFO Metrics logging every 30s 2018/02/12 13:54:18.033936 beat.go:426: INFO Home path: [C:\metricbeat] Config p ath: [C:\metricbeat] Data path: [C:\metricbeat\data] Logs path: [C:\metricbeat\l ogs] 2018/02/12 13:54:18.049561 beat.go:453: DBG Beat metadata path: C:\metricbeat\da ta\meta.json 2018/02/12 13:54:18.065187 helper\_windows.go:19: DBG delete old: remove C:\metri cbeat\data\meta.json.old: The system cannot find the file specified. 2018/02/12 13:54:18.065187 helper\_windows.go:23: DBG rotate to old: rename C:\me tricbeat\data\meta.json C:\metricbeat\data\meta.json.old: The system cannot find the file specified. 2018/02/12 13:54:18.065187 beat.go:433: INFO Beat UUID: 4c5fee84-fb18-424f-af12- 00207c23205d 2018/02/12 13:54:18.065187 beat.go:192: INFO Setup Beat: metricbeat; Version: 6. 0.0 2018/02/12 13:54:18.065187 beat.go:199: DBG Initializing output plugins 2018/02/12 13:54:18.065187 processor.go:49: DBG Processors: 2018/02/12 13:54:18.080812 logger.go:18: DBG start pipeline event consumer 2018/02/12 13:54:18.080812 module.go:80: INFO Beat name: NYBEAT1P 2018/02/12 13:54:18.080812 metricbeat.go:37: DBG Register [ModuleFactory:[docker , mongodb, mysql, postgresql, system], MetricSetFactory:[aerospike/namespace, ap ache/status, ceph/cluster\_disk, ceph/cluster\_health, ceph/monitor\_health, ceph/p ool\_disk, couchbase/bucket, couchbase/cluster, couchbase/node, docker/container, docker/cpu, docker/diskio, docker/healthcheck, docker/image, docker/info, docke r/memory, docker/network, dropwizard/collector, elasticsearch/node, elasticsearc h/node\_stats, golang/expvar, golang/heap, haproxy/info, haproxy/stat, http/json, jolokia/jmx, kafka/consumergroup, kafka/partition, kibana/status, kubernetes/co ntainer, kubernetes/event, kubernetes/node, kubernetes/pod, kubernetes/state\_con tainer, kubernetes/state\_deployment, kubernetes/state\_node, kubernetes/state\_pod , kubernetes/state\_replicaset, kubernetes/system, kubernetes/volume, memcached/s tats, mongodb/dbstats, mongodb/status, mysql/status, nginx/stubstatus, php\_fpm/p ool, postgresql/activity, postgresql/bgwriter, postgresql/database, prometheus/c ollector, prometheus/stats, rabbitmq/node, redis/info, redis/keyspace, system/co re, system/cpu, system/diskio, system/filesystem, system/fsstat, system/memory, system/network, system/process, system/process\_summary, vsphere/datastore, vsphe re/host, vsphere/virtualmachine, windows/perfmon, zookeeper/mntr]] 2018/02/12 13:54:18.080812 beat.go:260: INFO metricbeat start running. 2018/02/12 13:54:18.080812 cfgwarn.go:11: WARN BETA: Dynamic config reload is en abled. 2018/02/12 13:54:18.080812 reload.go:128: INFO Config reloader started 2018/02/12 13:54:18.080812 service\_windows.go:51: DBG Windows is interactive: tr ue 2018/02/12 13:54:19.237092 service.go:33: DBG Received sigterm/sigint, stopping 2018/02/12 13:54:19.237092 reload.go:148: INFO Dynamic config reloader stopped 2018/02/12 13:54:19.237092 service.go:39: DBG Received svc stop/shutdown request 2018/02/12 13:54:19.237092 metrics.go:51: INFO Total non-zero values: beat.mems tats.gc\_next=4473924 beat.memstats.memory\_alloc=2526960 beat.memstats.memory\_tot al=2526960 libbeat.config.module.running=0 libbeat.output.type=logstash libbeat. pipeline.clients=0 libbeat.pipeline.events.active=0 2018/02/12 13:54:19.237092 metrics.go:52: INFO Uptime: 2.7500704s 2018/02/12 13:54:19.237092 beat.go:268: INFO metricbeat stopped. ---
**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\ **Post date:** [February 13, 2018, 11:08am UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/4 "2018-02-13T11:08:01Z")
In this log, metricbeat ran for only one second. Can you send us a more complete log where metricbeat has been running for some 5 minutes? ---
**Author:** ![dilip](https://avatars.discourse-cdn.com/v4/letter/d/47e85d/32.png) [@dilip](https://discuss.elastic.co/u/dilip)\ **Post date:** [March 7, 2018, 5:06am UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/5 "2018-03-07T05:06:51Z")
Hi, Please find the below link for more logs. [https://pastebin.com/wRn17iYq](https://pastebin.com/wRn17iYq) ---
**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\ **Post date:** [March 8, 2018, 9:50am UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/6 "2018-03-08T09:50:02Z")
This log looks fine, the system module is reporting every 2 minutes, 16:09 and 16:11. Maybe the issue here is that you expect one event every 2 minutes, but the system module generates multiple events every interval, at least one per enabled metricset. In this case, the `process` metricset generates one event per process. ---
**Author:** ![dilip](https://avatars.discourse-cdn.com/v4/letter/d/47e85d/32.png) [@dilip](https://discuss.elastic.co/u/dilip)\ **Post date:** [March 12, 2018, 6:57am UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/7 "2018-03-12T06:57:10Z")
Thank you.. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 9, 2018, 6:57am UTC](https://discuss.elastic.co/t/win-2003-32-bit-os-period-time-is-not-correct-it-is-showing-default/118713/8 "2018-04-09T06:57:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.