[gentoo-user] PostgreSQL with unknown message to starting

[gentoo-user] PostgreSQL with unknown message to starting

[Javier Uribe]

hi people.

I have compile PostgreSQL satisfactorily,  my doubt is when starting, it 
appears the next message

highwaystar ~ # /etc/init.d/postgresql start
 * Starting PostgreSQL ...
su: Authentication service cannot retrieve authentication info.
(Ignored)                                                               [ ok ]

any ideas?
it can be by change to the user postgres?

Best Regards
-- 
Javier Uribe
juribe at linuxchile dot cl 
Gentoo GNU/Linux User
jabber ID: whereismybrain@jabber.org
"Old at heart but I'm only 28  And I'm much too young 
 To let love break my heart" 
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: PostgreSQL with unknown message to starting

[Gabriel M. Beddingfield]

Javier Uribe wrote:

> hi people.
> 
> I have compile PostgreSQL satisfactorily,  my doubt is when starting, it
> appears the next message
> 
> highwaystar ~ # /etc/init.d/postgresql start
>  * Starting PostgreSQL ...
> su: Authentication service cannot retrieve authentication info.
> (Ignored)                                                               [
> ok ]
> 
> any ideas?
> it can be by change to the user postgres?

I have the same problem (see my post on 10/7).  It appears postgres works
OK, though.  If anyone knows how to put PAM in it's place, let me know!

-Gabriel

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: PostgreSQL with unknown message to starting

[Mariusz Pękala]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On 2005-10-08 19:51:16 -0500 (Sat, Oct), Gabriel M. Beddingfield wrote:
> Javier Uribe wrote:
> 
> > hi people.
> > 
> > I have compile PostgreSQL satisfactorily,  my doubt is when starting, it
> > appears the next message
> > 
> > highwaystar ~ # /etc/init.d/postgresql start
> >  * Starting PostgreSQL ...
> > su: Authentication service cannot retrieve authentication info.
> > (Ignored)                                                               [
> > ok ]
> > 
> > any ideas?
> > it can be by change to the user postgres?
> 
> I have the same problem (see my post on 10/7).  It appears postgres works
> OK, though.  If anyone knows how to put PAM in it's place, let me know!
> 

This time it's about no entry for postgres in /etc/shadow. :-)

This line, added to /etc/shadow, would be OK:
postgres:!:12654:0:99999:7:::

-- 
No virus found in this outgoing message.
Checked by 'grep -i virus $MESSAGE'
Trust me.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: PostgreSQL with unknown message to starting

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

Am Montag, 10. Oktober 2005 07:23 schrieb ext Mariusz Pękala:

> This time it's about no entry for postgres in /etc/shadow. :-)
>
> This line, added to /etc/shadow, would be OK:
> postgres:!:12654:0:99999:7:::

Better don't edit /etc/shadow manually, use pwconv.

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

[gentoo-user] Re: Re: PostgreSQL with unknown message to starting

[Gabriel M. Beddingfield]

Mariusz P?kala wrote:

> This time it's about no entry for postgres in /etc/shadow. :-)
> 
> This line, added to /etc/shadow, would be OK:
> postgres:!:12654:0:99999:7:::
> 

Hi Mariusz,

This is what I had:

postgres:!!:0:0:99999:7:::8021806

This is what I changed it to:

postgres:!!:13066:0:99999:7:::8021806

And the problem goes away.  But this doesn't make any sense.  According to
the man pages there should have been no problem to begin with (password
expiry was turned off.)

Before:
# chage -l postgres
Last password change                                    : never
Password expires                                        : never
Password inactive                                       : never
Account expires                                         : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 99999
Number of days of warning before password expires       : 7

After:
# chage -l postgres
Last password change                                    : Oct 10, 2005
Password expires                                        : never
Password inactive                                       : never
Account expires                                         : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 99999
Number of days of warning before password expires       : 7

Is this a bug or obscurely documented feature for PAM?

Thanks,
Gabriel



-- 
gentoo-user@gentoo.org mailing list