Thread: yast sles9.3 stopped all postgres instance

yast sles9.3 stopped all postgres instance

From

dx k9

Date:

28 April 2009, 20:47:31

Just as a follow up.. The same thing happened again after just going into yast and viewing the run level services. After I exit'd yast, ALL instances of postgres went down on the server.

.hmmessage P { margin:0px; padding:0px } body.hmmessage { font-size: 10pt; font-family:Verdana } Hi,

I wanted to report a new way to shut down a postgres instance. I was troubleshooting a PAM-warning message in syslog and decided to restart slpd /etc/init.d/slpd, since I made a small change in ldap.conf, the OpenSLP daemon for the Service Location Protocol. It caused both instances of postgres ( i have 2 running a one system one 8.24 and one 8.36) to stop with a fast shutdown by admin(see below). The first time it happened right after I re-started slpd and the second time there was a 2 hour delay, then it shut down both instances. Has anyone ever seen that happen before or know why that could have caused postgres to shut down. I was troubleshooting a PAM-warn message with SLES 9 2.6.5-7.308-smp, sp4 and thought it would be worth a shot. It did stop those PAM-warnings for a while, since the instance was down. :)

~DjK

< % %2009-04-17 10:22:32 EDT>LOG: received fast shutdown request

< % %2009-04-17 10:22:32 EDT>LOG: aborting any active transactions

<t_server %system %2009-04-17 10:22:32 EDT>FATAL: terminating connection due to administrator command

<bb %ce %2009-04-17 10:22:32 EDT>FATAL: terminating connection due to administrator command

17 10:03:04 pa PAM-warn[20051]: function=[pam_sm_acct_mgmt] service=[postgresql] terminal=[<unknown>] user=[postgres] ruser=[<unknown>] rhost=[<unknown>]
Apr 17 10:03:39 pa PAM-warn[20387]: function=[pam_sm_authenticate] service=[postgresql] terminal=[<unknown>] user=[postgres] ruser=[<unknown>] rhost=[<unknown>]
Apr 17 10:03:39 pa PAM-warn[20387]: function=[pam_sm_acct_mgmt] service=[postgresql] terminal=[<unknown>] user=[postgres] ruser=[<unknown>] rhost=[<unknown>]

pam_radius-1.3.16-65.1
pam-0.77-221.11
pam-modules-9-18.19
pam_ldap-169-28.7
spamassassin-3.1.9-0.3
pam-32bit-9-200710171330
pam_ldap-32bit-9-200610241503
pam_smb-2.0.0rc5-38.3
yast2-pam-2.9.15-0.1
pam-devel-0.77-221.11
pam_krb5-1.3-201.12
perl-spamassassin-3.1.9-0.3
pam-modules-32bit-9-200711021346

Windows Live™ Hotmail®:…more than just e-mail. Check it out.

Re: yast sles9.3 stopped all postgres instance

From

Michael Monnerie

Date:

29 April 2009, 04:28:16

On Dienstag 28 April 2009 dx k9 wrote:
> with SLES 9

I'd believe your start/stop scripts are not original, but anyway with
SLES 9, you should contact Novell support. That's what you pay for ;-)

mfg zmi
--
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

Attachment

signature.asc