Re: postgres sometimes returns no data

On 11/13/2015 07:56 AM, db042190 wrote:
> pls remember that since the switches didn't run, this all (or mostly) could
> be related to an unknown process.  My bad component appears to have started
> around 54 seconds into nov 10.  The overall job appears to have ended around

Actually 54 minutes, which makes the below occur over a roughly 7 minute
time frame.

> 01:01:44 which makes me wonder if a lot of the EOFs are related to some sort
> of cleanup effort between pentaho and postgres.  I'm poking around for info

Well without an indication of what the actual commands are that are
being run, this is going to be difficult to troubleshoot from this end.

What needs to be sorted out(besides increasing checkpoint_segments) is
the source of this:

unexpected EOF on client connection
could not receive data from client: No
connection could be made because the target machine actively refused it.

I would spend some time here:

http://www.postgresql.org/docs/9.4/interactive/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT

Enable log_connections and log_disconnections.

Look at log_line_prefix and add at least %u and %p

Look at log_statement. Though this can fill up a log in a hurry,
especially if you do all.

You will need to reload(not restart) the server to have the settings
changes take effect.

> on how to run perfmon unattended, how big its footprint would be if
> monitoring for an extended period of time unattended , and how to look at
> what the os might have told me that day at that time.  I took a peek at
> available disk space, and while I don't know what postgres might be allowed
> to take, there is a ton of available space.  I closed out about a handful of
> idle queries on pg admin iii left by programmers.  I'll post more soon.
>
> 2015-11-10 00:54:03 EST LOG:  checkpoints are occurring too frequently (116
> seconds apart)
> 2015-11-10 00:54:03 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:54:24 EST LOG:  checkpoints are occurring too frequently (21
> seconds apart)
> 2015-11-10 00:54:24 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:54:46 EST LOG:  checkpoints are occurring too frequently (22
> seconds apart)
> 2015-11-10 00:54:46 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:55:11 EST LOG:  checkpoints are occurring too frequently (25
> seconds apart)
> 2015-11-10 00:55:11 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:55:36 EST LOG:  checkpoints are occurring too frequently (25
> seconds apart)
> 2015-11-10 00:55:36 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:56:07 EST LOG:  checkpoints are occurring too frequently (31
> seconds apart)
> 2015-11-10 00:56:07 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:56:38 EST LOG:  checkpoints are occurring too frequently (31
> seconds apart)
> 2015-11-10 00:56:38 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:57:15 EST LOG:  checkpoints are occurring too frequently (37
> seconds apart)
> 2015-11-10 00:57:15 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:57:53 EST LOG:  checkpoints are occurring too frequently (38
> seconds apart)
> 2015-11-10 00:57:53 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:58:35 EST LOG:  checkpoints are occurring too frequently (42
> seconds apart)
> 2015-11-10 00:58:35 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:59:12 EST LOG:  checkpoints are occurring too frequently (37
> seconds apart)
> 2015-11-10 00:59:12 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 00:59:34 EST LOG:  checkpoints are occurring too frequently (22
> seconds apart)
> 2015-11-10 00:59:34 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 01:00:15 EST LOG:  checkpoints are occurring too frequently (41
> seconds apart)
> 2015-11-10 01:00:15 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 01:00:46 EST LOG:  checkpoints are occurring too frequently (31
> seconds apart)
> 2015-11-10 01:00:46 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 01:01:15 EST LOG:  checkpoints are occurring too frequently (29
> seconds apart)
> 2015-11-10 01:01:15 EST HINT:  Consider increasing the configuration
> parameter "checkpoint_segments".
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
> 2015-11-10 01:01:44 EST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>
> 2015-11-10 01:01:44 EST LOG:  unexpected EOF on client connection
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/postgres-sometimes-returns-no-data-tp5873720p5873824.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com