Thread: iso-8859-1 log messages
Hi,
I’m getting the following error in my log file. Normally it’s every 10 minutes, but occasionally the frequency changes to 5min, 3,1,30sec, 10sec, 5sec and then every second. Weeks ago it took the db down with a disk full situation, but usually it clears after a few minutes of continuous errors.
Can anybody offer any thoughts for how to identify what this is, and how to correct the issue.
Thanks
Doug
Env: Greenplum 3.3.6(based on PG 8.2.13), Solaris 10u5, Sun X4540 (x86)
We are probing the machine with sitescope for cpu/mem/disk stats, but I don’t believe it’s connecting to the db.
2011-01-01 13:01:56.848368 CST,"root","root",p427,th1,"[local]",,2011-01-01 13:01:56 CST,0,,,seg-1,,,,,"FATAL","28000","no pg_hba.conf entry for host ""[local]"", user ""root"", database ""root"", SSL off",,,,,,,0,,"auth.c",369,"Traceback 0: a12ca6: /usr/local/greenplum-db-3.3.6.6/bin/postgres errstart+0x3e6
Traceback 1: 748915: /usr/local/greenplum-db-3.3.6.6/bin/postgres ClientAuthentication+0x4c5
Traceback 2: 84a4c0: /usr/local/greenplum-db-3.3.6.6/bin/postgres ClosePostmasterPorts+0x5610
Traceback 3: 84b789: /usr/local/greenplum-db-3.3.6.6/bin/postgres PostmasterMain+0x959
Traceback 4: 76bb84: /usr/local/greenplum-db-3.3.6.6/bin/postgres main+0x474
Traceback 5: 4dae6c: /usr/local/greenplum-db-3.3.6.6/bin/postgres _start+0x6c
"
Doug Little
Sr. Data Warehouse Architect | Enterprise Data Management | Orbitz Worldwide
500 W. Madison, Suite 1000 Chicago IL 60661| Office 312.260.2588 | Fax 312.894.5164 | Cell 847-997-5741
orbitz.com | ebookers.com | hotelclub.com | cheaptickets.com | ratestogo.com | asiahotels.com
Attachment
Env: Greenplum 3.3.6(based on PG 8.2.13), Solaris 10u5, Sun X4540 (x86)
We are probing the machine with sitescope for cpu/mem/disk stats, but I don’t believe it’s connecting to the db.
2011-01-01 13:01:56.848368 CST,"root","root",p427,th1,"[local]",,2011-01-01 13:01:56 CST,0,,,seg-1,,,,,"FATAL","28000","no pg_hba.conf entry for host ""[local]"", user ""root"", database ""root"", SSL off",,,,,,,0,,"auth.c",369,"Traceback 0: a12ca6: /usr/local/greenplum-db-3.3.6.6/bin/postgres errstart+0x3e6
No dbuser named Root. Don’t know who is the client, so having trouble identifying it.
So it sounds like the log messages are standard for a login attempt with unknown user.
I have a case open with GP.
Thanks for the thoughts.
Doug
From: bricklen [mailto:bricklen@gmail.com]
Sent: Wednesday, January 05, 2011 10:32 AM
To: Little, Douglas
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] unknown log messages
On Wed, Jan 5, 2011 at 7:16 AM, Little, Douglas <DOUGLAS.LITTLE@orbitz.com> wrote:
Env: Greenplum 3.3.6(based on PG 8.2.13), Solaris 10u5, Sun X4540 (x86)
We are probing the machine with sitescope for cpu/mem/disk stats, but I don’t believe it’s connecting to the db.
2011-01-01 13:01:56.848368 CST,"root","root",p427,th1,"[local]",,2011-01-01 13:01:56 CST,0,,,seg-1,,,,,"FATAL","28000","no pg_hba.conf entry for host ""[local]"", user ""root"", database ""root"", SSL off",,,,,,,0,,"auth.c",369,"Traceback 0: a12ca6: /usr/local/greenplum-db-3.3.6.6/bin/postgres errstart+0x3e6
Do you actually have a database named "root" and a db user named "root"? If not, I'd check your client connection details to ensure you pass in the database name and user.
Also, if you have a support contract, you could contact Greenplum -- I've generally found them to be pretty responsive. Barring that, you could also try posting to http://community.greenplum.com
Could it be an automatic process, kicked off by cron or some such, running as root, and not specifying the db or user, thereforedefaulting to root & root? -- Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice
On Jan 5, 2011, at 9:34 AM, Little, Douglas wrote: > No dbuser named Root. That's my point, you don't have a db user named root, but you do (maybe) have a process running as root trying to connectto the db. > So it sounds like the log messages are standard for a login attempt with unknown user. No, they are standard for root trying to connect to the database when you do not have a db user named root. -- Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice
On Wed, Jan 5, 2011 at 9:15 AM, Scott Ribe <scott_ribe@elevated-dev.com> wrote: > On Jan 5, 2011, at 9:34 AM, Little, Douglas wrote: > >> No dbuser named Root. > > That's my point, you don't have a db user named root, but you do (maybe) have a process running as root trying to connectto the db. > >> So it sounds like the log messages are standard for a login attempt with unknown user. > > No, they are standard for root trying to connect to the database when you do not have a db user named root. As Scott says, check your root crontab for any scripts that might connect to the db, and check the connection string. The "[local]" part means that the call is being initiated locally to that box, else it would should the IP.