Now, this is not some essential problem since logrotate is in place and the
file is not getting that big, but still it kind of makes reading the file
difficult since I have to scroll through thousands of unnecessary lines.
--
Amar Prasovic
Gaißacher Straße 17
D - 813
Thank you all for tips and suggestions. I managed to configure postgres so
it actually starts.
First, I updated resource-agents (Florian thanks for the tip, still don't
know how did I manage to miss that :) )
Second, I deleted postgres primitive, cleared all failcounts and configure
it again like
> >What version of resource-agents package do you use? Old version of pgsql
> >depended on fuser tool installed, otherway it could fail with that error
> >code.
>
Hello Serge,
thank you for your answer.
I don't have any resource-agents installed. The system is Debian Squeeze
6.0.3 and it automa
crmd: [921]: info: do_lrm_rsc_op: Performing
key=4:97:0:933bf2ab-00d0-435c-a24f-85897e0c9725 op=postgres_res_stop_0 )
Oct 11 11:39:50 webnode01 lrmd: [914]: info: rsc:postgres_res:40: stop
Oct 11 11:39:50 webnode01 crmd: [921]: info: process_lrm_event: LRM
operation postgres_res_stop_0 (call=40,
