Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some random measurements stop working after some time #298

Open
andreasbehnke opened this issue Oct 3, 2022 · 9 comments
Open

Some random measurements stop working after some time #298

andreasbehnke opened this issue Oct 3, 2022 · 9 comments

Comments

@andreasbehnke
Copy link

andreasbehnke commented Oct 3, 2022

Describe the bug
After running a setup of iobroker.influxdb with about 70 measurements, some of these measurements stop working.
Restarting iobroker or the iobroker.influxdb adapter solves the issue. Which measurements stop working is random.

To Reproduce
Steps to reproduce the behavior:

  1. configure your measurements
  2. run for at least 3 days
  3. check if all measurements are working

Expected behavior
Measurements should not be dropped or ignored

Screenshots & Logfiles
There is no information in the logs. iobroker.influxdb reports no errors nor warnings.

Versions:

  • Adapter version: v3.1.8
  • JS-Controller version:
  • Node version: v16.16.0
  • Operating system: Linux/Debian
@Apollon77
Copy link
Contributor

Hm ... No idea how to solve that ... noone else did report something like this so far.

The only idea would be to enable the debug logging for instance and also the enhanced datapointlogging for relevant (or all) datapoints. Then you should see in the logs why he do not log anymore. Infact will be a lot logging ....

We need more details ...

@TbsJah
Copy link

TbsJah commented Nov 1, 2022

I have unfortunately the same problem
Saving the values stops every night. The values are saved only after the influxdbinstance is restarted.
I have now changed the log level from warning to debug. Maybe there is something to see about it

image

Node.js v16.18.0
NPM 8.19.2
iob 6.2.23

@Apollon77
Copy link
Contributor

Please provide more log.It is not normal that the instance terminates daily unless you have set a restart Schedule, so there should be more log - also from the host/js-controller maybe.

@Draygv2
Copy link

Draygv2 commented Jan 17, 2023

Same problem here. Last entry 18.12.2022 after that just one remains and none of them are active in iob.
grafik
unfortunally I have no logs from this time anymore.

@Apollon77
Copy link
Contributor

Is a restart helping? Was there an issue? But yes you most likely will have mo logs from 1 month ago anymore ... so no idea what could be the reason

@Draygv2
Copy link

Draygv2 commented Jan 17, 2023

Restart was not helping. I noted nothing special but I'm not daily active on my iob. In my case it's always with DS data and no other ones.
I will send now all errors according to influxdb to telegram. Maybe I get the log with it.

@Apollon77
Copy link
Contributor

DS data aka DigitalStrom? or what you mean? Is the logging still activated on the mentioned states? maybe it got inacrtive because the adapter deleted objects?

@Draygv2
Copy link

Draygv2 commented Jan 17, 2023

Sorry yes I mean Digitalstrom. In IOB/Object was nothing activated. I don't know how I find it in influxDB. That could be, sometimes some devices disappear and after a reset they appear again.

@stale
Copy link

stale bot commented May 9, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

@stale stale bot added the wontfix label May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants