Skip to main content
  • EN

I wanted to post this for everyone who uses VB365 and PGBouncer with Postgres with the recent upgrade 8.1.2.180.

When trying to run this upgrade I ran in to an issue with the following error which was caused by connecting to Postgres via the PBBouncer 6432 port.  I had to stop services, modify the XML files back to 5432 (default PG port) and then run the upgrade.  Once complete I could then revert back to 6432 for PGBouncer and start up the services again.

Error seen during upgrade -

 

 
 
 

I’ve done some testing on this scenario and have some feedback, Chris.  With the pgbouncer config you have there definitely is something not working right.

I ran through Veeam’s recently released PGbouncer KB and the authentication method differs from what I had configured (same issue as you).  When following the KB everything worked as expected.  Upgrade from v8.1.1 to v8.1.2 worked as expected.  No issues.

I suspect the following issues from your config (same as mine ;) ):

  • No user lookup function
    • This step in the KB allows pgbouncer to look up default Postgres users
  •  HBA auth from the KB compared to MD5 in my first pgbouncer implementations
    • MD5 does a direct lookup to the userlist file
    • HBA should use the auth_query method configured in the KB which bypasses the userlist (of pgbouncer) and authenticates against Postgresql directly

The authentication differences from your setup to the KB are the likely issue here.  I suggest adjusting your config to align with the Veeam KB and you should be good to go for current usage of PGbouncer *and* for future upgrades.  Good luck out there!

I’ve done some testing on this scenario and have some feedback, Chris.  With the pgbouncer config you have there definitely is something not working right.

I ran through Veeam’s recently released PGbouncer KB and the authentication method differs from what I had configured (same issue as you).  When following the KB everything worked as expected.  Upgrade from v8.1.1 to v8.1.2 worked as expected.  No issues.

I suspect the following issues from your config (same as mine ;) ):

  • No user lookup function
    • This step in the KB allows pgbouncer to look up default Postgres users
  •  HBA auth from the KB compared to MD5 in my first pgbouncer implementations
    • MD5 does a direct lookup to the userlist file
    • HBA should use the auth_query method configured in the KB which bypasses the userlist (of pgbouncer) and authenticates against Postgresql directly

The authentication differences from your setup to the KB are the likely issue here.  I suggest adjusting your config to align with the Veeam KB and you should be good to go for current usage of PGbouncer *and* for future upgrades.  Good luck out there!

Hey ​@tim.hudson - thanks for this testing and work done.  I will review the KB again as I followed another document that I was sent which was probably “unofficial”.  😋

Let me go through the KB and fix the settings you mentioned then I will need to wait on the next update to release and then test.

Terms & Conditions