On 25.09.05 17:12:56, Martin Pitt wrote: > Hi Andreas! > > Andreas Pakulat [2005-09-23 15:38 +0200]: > > As I said, the "2nd" start of PG now doesn't fail, but the one during > > boot-time does. > > > > If this really is a timeout-thing, I think I know why it might happen > > here: > > > > I changed kdm to start earlier as that takes some time, so kdm is > > started as 14th in runlevel 2, while PG is 20. So it could be that the > > startup of KDE (which is quite hdd-intensive) makes PG take quite some > > time to come up. (Did I tell you that this is a notebook hdd with only > > 4500 RPM?) > > > > If this is indeed the problem an option to increase this timeout in > > pg_ctlcluster would be really nice - for example in > > /etc/default/postgresql-server-8.0 or so. > > Ok, but to be sure that this is really the culprit, can you please > increase the timeout to 60 seconds (raise $attempt comparison to > "< 120") and check that indeed the slow startup is the reason, and not > something else?
60 Seconds doesn't work either, but 120 do:
for (my $attempt = 0; $attempt < 240; $attempt++) {
Now PG doesn't give an error anymore. I'll try with values of 120 and 40
there while removing kdm from the runlevel..
Andreas
--
You will pay for your sins. If you have already paid, please disregard
this message.
pgp20zh2rfn2w.pgp
Description: PGP signature
