was collected before with the same name and label values\n” source=“log.go:172”
What’s recomandations have you to fix it ?
Thank you in advance 🙂
---
### Author:  [@Stateros](https://forums.percona.com/u/Stateros)
#### Post date: [February 23, 2020, 1:21pm UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/2 "2020-02-23T13:21:27Z")
what version of pmm are you using?
---
### Author:  [@virgile](https://forums.percona.com/u/virgile)
#### Post date: [February 24, 2020, 3:38am UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/3 "2020-02-24T03:38:30Z")
Hello Stateros,
My pmm version server is 1.17.1 and 1.17.3 for client side.
---
### Author:  [@Stateros](https://forums.percona.com/u/Stateros)
#### Post date: [February 26, 2020, 9:43am UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/4 "2020-02-26T09:43:26Z")
Try to use the same version of client and server. Will be more predictable.
---
### Author:  [@gordan](https://forums.percona.com/u/gordan)
#### Post date: [June 11, 2020, 3:12pm UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/5 "2020-06-11T15:12:09Z")
I am having this exact same problem, and I don’t have a discrepancy between versions - 1.17.3 on both the server side and on the client side. Is there a cure? The log size gets unnecessarily big eventually and there is no log rotation by default that ships with the package.
---
### Author:  [@steffen](https://forums.percona.com/u/steffen)
#### Post date: [June 17, 2020, 10:43am UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/6 "2020-06-17T10:43:39Z")
Hi, I think “example.prom” is the sample file for the textfile collector. Are you actually using that sample file to collect data?
If not, have you checked if moving the file out of the textfile collector directory makes the error go away?If you are actually using it, is it possible that your textfile collector is trying to evaluate the file more than once, like maybe via different links to the same file?
---
### Author:  [@gordan](https://forums.percona.com/u/gordan)
#### Post date: [June 17, 2020, 10:49am UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/7 "2020-06-17T10:49:27Z")
@steffen
I removed example.prom file and that turns the message into this:
```auto
time="2020-06-17T16:18:08Z" level=error msg="error gathering metrics: collected metric node_textfile_scrape_error gauge:<value:0 > was collected before with the same name and label values\n" source="log.go:172"
```
This is a 100% vanilla setup, nothing was added or altered away from defaults. It is how pmm-admin created any and all configs.
---
### Author:  [@steffen](https://forums.percona.com/u/steffen)
#### Post date: [June 17, 2020, 11:31am UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/8 "2020-06-17T11:31:27Z")
@gordan
Yes, that’s really not a very helpful message. I’m out of ideas here, since I switched everything to PMM2 already.
Did you try restarting the pmm agent?
From what I see, “node\_textfile\_scrape\_error” indicates whether or not reading a textfile was successful (0) or not (1).
Unfortunately that metric doesn’t name the file(s) the collector has read or tried to read.
The agent process is not by any chance running twice or something like this?
---
### Author:  [@gordan](https://forums.percona.com/u/gordan)
#### Post date: [June 17, 2020, 12:10pm UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/9 "2020-06-17T12:10:38Z")
@steffen
Yes, restarting it makes no difference after removing the file.
There is only one instance of node\_exporter logging to /var/log/pmm-linux-metrics-42000.log
---
### Author:  [@gcarter](https://forums.percona.com/u/gcarter)
#### Post date: [July 7, 2020, 7:31am UTC](https://forums.percona.com/t/getting-error-who-fill-logs-every-second/7431/10 "2020-07-07T07:31:44Z")
I also have this problem with 1.17.3. I found that the systemd unit file for pmm-linux-metrics-42000 had textfile listed twice as a collectors.enabled. When i removed that, did a systemctl daemon-reload followed by a restart of pmm-linux-metrics-24000, the problem went away. So does “pmm-admin config” generate a broken unit file for linux?