# update\_every stuck at 1s, ignored for go.d.plugin for apache

**URL:** <https://community.netdata.cloud/t/update-every-stuck-at-1s-ignored-for-go-d-plugin-for-apache/5290>\
**Category:** Help\
**Tags:** agent\
**Created:** [March 28, 2024, 9:20pm UTC](https://community.netdata.cloud/t/update-every-stuck-at-1s-ignored-for-go-d-plugin-for-apache/5290 "2024-03-28T21:20:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aimpink](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@aimpink](https://community.netdata.cloud/u/aimpink)\
**Post date:** [March 28, 2024, 9:20pm UTC](https://community.netdata.cloud/t/update-every-stuck-at-1s-ignored-for-go-d-plugin-for-apache/5290/1 "2024-03-28T21:20:17Z")

</div>

**Suggested template:**

## Problem/Question

I see the go.d plugin for apache is hitting the URL [HTTP://localhost/server-status?auto](HTTP://localhost/server-status?auto) every 1 second, as is the default. I’ve updated the netdata global config to use “update every = 10” in netdata.config, and also added “update\_every: 10” in /opt/netdata/usr/lib/netdata/conf.d/go.d/apache.conf. Neither change appears to take effect. I completely restarted the netdata service after each change.

## Relevant docs you followed/actions you took to solve the issue

I researched the community forum and the netdata docs, none of which provided a satisfactory answer  
I also ran the collector in debug mode, and observed the collection triggering every 1 second. The apache access\_log also shows the status URL being hit every 1 second.

## Environment/Browser/Agent’s version etc

I am running an Amazon Linux 2 server in AWS. go.d.plugin, version: 1.45.1.0

## What I expected to happen

I expecting the plug to hit the URL every 10 seconds, as configured.

---

<div class="post-metadata">

**Author:** ![aimpink](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@aimpink](https://community.netdata.cloud/u/aimpink)\
**Post date:** [March 28, 2024, 9:36pm UTC](https://community.netdata.cloud/t/update-every-stuck-at-1s-ignored-for-go-d-plugin-for-apache/5290/2 "2024-03-28T21:36:15Z")

</div>

SOLVED: After changing the correct config file, it now appears to be working properly.

I had re-installed the netdata agent using a static build, so I initially changed /etc/netdata/netdata.conf instead of /opt/netdata/etc/netdata/netdata.conf.

Rookie error, I guess.