gt; On Fri, Aug 16, 2013 at 9:45 AM, Jeff Janes wrote:
> > On Thu, Aug 15, 2013 at 1:28 PM, Andrew Berman
> wrote:
> >> Hi Jeff,
> >>
> >> Here is the full process list at the time it stopped working (I have
> changed
> >> the actual username, db and
Awesome, I'll give that a shot John.
On Fri, Aug 16, 2013 at 8:39 AM, John DeSoi wrote:
>
> On Aug 15, 2013, at 1:07 PM, Andrew Berman wrote:
>
> > I'm having an issue where streaming replication just randomly stops
> working. I haven't been able to find an
db x.x.x.x(64431) idle
root 21529 0.0 0.0 103240 844 pts/0S+ 10:33 0:00 grep
--color postgres
**
Thanks,
Andrew
On Thu, Aug 15, 2013 at 1:20 PM, Jeff Janes wrote:
> On Thu, Aug 15, 2013 at 11:07 AM, Andrew Berman wrote:
> > Hello,
> >
> > I&#x
EOF' errors.
>
> On Thu, Aug 15, 2013 at 12:22 PM, Andrew Berman wrote:
> > The only thing I see that is a possibility for the issue is in the slave
> > log:
> >
> > LOG: unexpected EOF on client connection
> > LOG: could not receive data from client: Con
n Thu, Aug 15, 2013 at 11:51 AM, Lonni J Friedman wrote:
> Are you certain that there are no relevant errors in the database logs
> (on both master & slave)? Also, are you sure that you didn't
> misconfigure logging such that errors wouldn't appear?
>
> On Thu, Aug 15, 20
ms (like the NIC dying, or dropping packets)?
>
>
> On Thu, Aug 15, 2013 at 11:07 AM, Andrew Berman wrote:
> > Hello,
> >
> > I'm having an issue where streaming replication just randomly stops
> working.
> > I haven't been able to find anything in the logs wh
Hello,
I'm having an issue where streaming replication just randomly stops
working. I haven't been able to find anything in the logs which point to
an issue, but the Postgres process shows a "waiting" status on the slave:
postgres 5639 0.1 24.3 3428264 2970236 ? Ss Aug14 1:54 postgres:
