Skip to main content
Nintex Community Menu Bar
Solved

Issue with Data Source (PostGreSQL)

D
Forum|alt.badge.img+13

HI Guys,

Not sure if any of you use skuid with External Data Sources, but i’ve been experiencing issues for past couple days where all pages using DSO give me one of those errors 95% of the time i try to load a page

  1. There was an error making a request against the database: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

or

  1. Error reaching datasource due to timeout: Post “http://seaquill-internal.app-proxy/api/v2/entity/load”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Any of you experiencing same issue or any advice for me? as nothing changed on DB side for weeks now, and all was working fine until recently.

Thx

Best answer by David.A

Thank you Jeremy,
Actually, your questions made me go over all with the Dev again, and it seems it was a proxy issue. Once we disabled it, everything went back to normal

We had set that proxy because of the limited # of simultaneous connections we could have, so we will work on fixing that.

Thank you for throwing us in the right direction!

View original
Translate

Q
Forum|alt.badge.img+11

Hey @Dave,

Just want to ask some basic questions here to cover our basis, but when you go to the DataSource(DS) details page, did you confirm(and double check) all the IP Addresses are allowed/trusted to access the database?

Cheers,

Translate
D
Forum|alt.badge.img+13
  • David.A
  • Scholar
  • July 12, 2024

Hi Germany, ty for your response, yes all this has been double-checked and DB has no Ip restrictions. And it works 5-10% of the time now with no error, so for sure not a credential /IP issue as this would never work,

From all the research i made into those errors, it seems to be on skuid’s side.

Translate
Q
Forum|alt.badge.img+11

Migrating to public thread for visibility and update.

After looking at our logs, we have a few ideas on what is going on, but to be sure, we need to verify the pool size and connection timeout to make sure it’s set properly for the amount of data he’s are querying.

Two things could be happening:

  1. The pool size may be too small for the amount of data being queried.
  2. Because of the amount of data being queried, the DB is timing out and not staying active, terminating the connection.
Translate
D
Forum|alt.badge.img+13
  • David.A
  • Scholar
  • July 12, 2024

Thank you Jeremy,
Actually, your questions made me go over all with the Dev again, and it seems it was a proxy issue. Once we disabled it, everything went back to normal

We had set that proxy because of the limited # of simultaneous connections we could have, so we will work on fixing that.

Thank you for throwing us in the right direction!

Translate
Q
Forum|alt.badge.img+11

That’s awesome, and I’m glad you were able to fix it!

Translate

Reply


Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
Terms & ConditionsCookie Settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings