| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Denis BUCHER <dbucherml(at)hsolutions(dot)ch>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unable to stop postgresql ("failed") -> [SOLVED] |
| Date: | 2010-08-06 17:25:57 |
| Message-ID: | 6702.1281115557@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thom Brown <thom(at)linux(dot)com> writes:
> On 6 August 2010 17:49, Denis BUCHER <dbucherml(at)hsolutions(dot)ch> wrote:
>> I was unable to stop postgres, I always got "[FAILED] :
>> * /etc/init.d/postgresql stop
>> * service postgresql stop
>> * /sbin/service postgresql stop
> Surely it depends what the packager put into the init.d script? Plus
> there's the "zap" option for some setups if you're desperate, although
> I don't know if that issues a SIGINT or a SIGQUIT. Hopefully the
> former. But really your init.d script should be issuing that pg_ctl
> stop command anyway, so don't know why you're getting failed messages.
I'm wondering about permissions problems. initscripts normally only
work when called by root. Being able to call pg_ctl directly suggests
he was logged in as the postgres user.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gordon Shannon | 2010-08-06 17:56:33 | Re: Need help understanding vacuum verbose output |
| Previous Message | Thom Brown | 2010-08-06 17:14:43 | Re: Unable to stop postgresql ("failed") -> [SOLVED] |