reassign 224047 postgresql severity 224047 normal retitle 224047 postgresql: restarts postmaster after upgrade even when disabled thanks, control, and have a nice day On Sat, Dec 13, 2003 at 09:23:59PM +0100, Marko@Thetaworld.Net wrote: > Package: general > Version: 20031213 > Severity: critical This is not a critical bug, nor is it general. Reassigning and lowering the severity. Keeping info inline for the postgresql maintainer. > > After running apt-get upgrade, here is what happens: > ---------------------------------------------------- > > Setting up postgresql (7.2.1-2woody4) ... > Restarting PostgreSQL database: postmaster > No /usr/lib/postgresql/bin/postmaster found running; none killed. > Starting PostgreSQL postmaster. > pg_ctl: Another postmaster may be running. Trying to start postmaster anyway. > postmaster successfully started > ---------------------END OF REPORT------------------ > > We have an additional runlevel /etc/rc7.d and there is postgresql script > marked as NO START, like: /etc/rc7.d/K20postgresql -> ../init.d/postgresql > > Thus such daemons should not start. But the upgrade scripts of a daemon > forces it to start, which we consider not OK for our systems. I can immagine > that the same happens with other daemons as well. > > We have additional runlevel, which is OK to have as far we know and runlevel > says it is N 7. > > > -- System Information > Debian Release: 3.0 > Kernel Version: Linux perlbroker.kosmos 2.2.19-udma100-ext3 #1 SMP Sat Oct 20 18:53:37 CEST 2001 i486 unknown -- Brian M. Carlson <sandals@crustytoothpaste.ath.cx> 0x560553e7
Attachment:
signature.asc
Description: Digital signature