On Wed, Nov 23, 2011 at 2:14 PM, Pongrácz István <[email protected]> wrote: > ----------------eredeti üzenet----------------- > Feladó: "Chris Travers" [email protected] > Címzett: [email protected] > Dátum: Wed, 23 Nov 2011 06:34:03 -0800 > ------------------------------------------------- > > This should not be happening. The question is why. Anything in the >> logs (http and postgresql) to suggest what's wrong? > > Hi, > > I only found these messages in the postgresql log file: > > 2011-11-23 14:19:51 UTC FATAL: password authentication failed for user "xxxx" > 2011-11-23 14:19:51 UTC FATAL: password authentication failed for user "xxxx" > 2011-11-23 14:20:15 UTC FATAL: password authentication failed for user "yyyyy" > 2011-11-23 14:20:15 UTC FATAL: password authentication failed for user "yyyyy" > Hi.
The above messages tell me PostgreSQL is refusing to authenticate the user here. There is really very little room for the upgrade script to cause an issue like this. Is it possible the passwords expired? You can test this temporarily by setting authentication (on a test db) to trust, and logging in, though I don't recommend this on a production server. The upgrade scripts in no way touch the user, and the auth routines have been unchanged since 1.3.0, and so the cause must be elsewhere. I will be happy to troubleshoot with you over IRC Best Wishes, Chris Travers ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Ledger-smb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
