I’m using a free InfluxDB cloud account and the officially supported node.js client library to insert data and perform queries. I get multiple 503 errors per day (service unavailable). This seems problematic to have a hosted service with these types of regular errors. Any insights as to causes/workarounds?
Anyone? I can’t be the only person experiencing this.
Wow. So much for “community support”. Doesn’t anyone from InfluxData monitor these discussions?
This is a community of volunteers with all sorts of different levels of
expertise and experience with InfluxDB, in many different environments.
Nobody is paid or obligated to respond to questions posted here, and it’s
unlikely that anyone will if they haven’t run into the same problem as you’re
seeing with the same or a similar setup.
So, I can understand your disappointment that nobody has been able to answer
your question, but please don’t make sarcastic remarks suggesting that the
community is not doing what you think it’s supposed to.
If someone can help, they generally will; if nobody does help, it’s usually
because no-one knows the answer to the question.
Antony.
Ha! You completely missed my point. Are you telling me that no one from InfluxData monitors these forums? And BTW, my issue has apparently been encountered often. If InfluxData is going to offer a free cloud account, they should also provide some level of support such that customers have a positive experience. There’s clearly a server-side issue (that’s the ONLY way a 503 error can occur), so only the InfluxData team can reliably troubleshoot or provide guidance.
Ha! You completely missed my point.
I think you may have misunderstood mine.
I was simply pointing out that everyone here is here of their own volition,
and contributes what they feel they can from their own ability. Nobody is
expected or obligated to respond if they don’t feel like it. That’s what
“community” means - people who are willing to help when they have the time,
and think they can positively contribute, but do so on a completely voluntary
basis.
Are you telling me that no one from InfluxData monitors these forums?
I have no idea, and since these are “community forums” there is no expectation
that anyone from InfluxData is involved. They may be, they may not be, but
certainly not in any official capacity.
If you want official support, then that is another available option:
https://support.influxdata.com/s/contactsupport
And BTW, my issue has apparently been encountered often. If InfluxData is
going to offer a free cloud account, they should also provide some level of
support such that customers have a positive experience.
I think it’s impressive enough that InfluxData (a) provides the software for
free under an Open Source licence to start with, and (b) offers a free-of-
charge cloud-hosted service for people to try it out.
If you expect free-of-charge professional support services on top, then you
might want to question your own business situation - I assume you do something
of value to people, and you get paid for it?
Why then do you expect to get free software, hosted for free, and with free
professional support? The line has to be drawn somewhere, and in this case
it’s free software, free hosting, and “community support” from volunteers who
help when they can and are able to do so.
Anything beyond that is a paid-for service, and is entirely justified in my
opinion - the people who are developing and publishing InfluxData for free have
to earn their money from somewhere, and professional support is one aspect.
There’s clearly a server-side issue (that’s the ONLY way a 503 error can
occur), so only the InfluxData team can reliably troubleshoot or provide
guidance.
So, maybe you should contact them, instead of expecting the community of
volunteers who simply happen to use InfluxDB to help you out?
I have no idea how commonplace your problem is (I don’t use InfluxDB in this
specific setup), and I’m not trying to put down your frustrations with
encountering a problem - I’m simply saying that it’s very likely that:
a) anyone here who thinks they can help with your problem will do so
b) if you don’t get a response it’s because nobody here is familiar with the
problem you’re running into.
If you think that “InfluxData the organisation” can help with your problem,
then https://support.influxdata.com/s/contactsupport is probably a good choice.
Antony.
Agreed. It is not necessary to pay for support to report bugs.
See Issues · influxdata/influxdb · GitHub and click on “New issue” to
report a new bug.
If you do not already have a Github account, creating one is free of charge
and is not associated with paying for an InfluxDB support contract.
Antony.
I have to wonder if you might be hitting free query and write limits?
Also can you please confirm this is the client library you are using?
And what version of influxdb you are running
Also another user solved this issue with
“I found a solution - I needed to add the “await” keyword on the async functions in the writeAPI (flush and close).”
Unlikely. Logging 3 values every 5 seconds, and querying at most every 5 seconds.
That other person was me. 
Fair enough lol
Sorry when people create new threads its hard to keep track, i dont pay attention to names, just issues lol
For docs - just to confirm it was the v2 version of the js library?
Correct. And that one thread was quite old, hoped that this one with more specifics could help towards a solution. And it did! Thank you.
