pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedFailed to set up event for socket: error code 10038
3+ messages / 3 participants
[nested] [flat]
* Failed to set up event for socket: error code 10038
@ 2017-01-27 10:23 Ertan Küçükoðlu <ertan.kucukoglu@1nar.com.tr>
0 siblings, 1 reply; 3+ messages in thread
From: Ertan Küçükoðlu @ 2017-01-27 10:23 UTC (permalink / raw)
To: pgsql-admin
Hi,
Using PostgreSQL 9.6.1, compiled by Visual C++ build 1800, 64-bit on a
Laptop running Windows 10 64bit OS with pro series SSD and 8GB RAM. Setup is
fetched from EnterpriseDB. I am a software developer and this is a system is
only used by me.
Goolge searches were not helpful for the log message I receive.
I have below postgresql.conf parameters (only listing some of them):
max_connections = 100
shared_buffers = 512MB
work_mem = 87381kB
maintenance_work_mem = 512MB
dynamic_shared_memory_type = Windows
wal_buffers = 16MB
max_wal_size = 100MB
min_wal_size = 100MB
checkpoint_completion_target = 0.5
effective_cache_size = 2GB
default_statistics_target = 100
When establishing a connection to the database, I frequently get error
messages in my application log saying:
2017-01-27 12:47:41.908 *** (10054) Error on data reading from the
connection: An existing connection was forcibly closed by the remote host.
Socket Error Code: 10054($2746)
I read a FATAL marked line in postgresql log file at exact same second:
2017-01-27 12:47:41 +03 FATAL: failed to set up event for socket: error
code 10038
Application is self-closing upon receiving such error. I instantly re-run it
(to continue my code tests) and sometimes it is 3-4 times until I can get my
application running.
I am using latest version of Devart Universal Database Access Components
(UniDAC) for performing database operations. As far as I know, these
components make direct connection to PostgreSQL. Nothing in between like
ODBC or anything. If that is relevant.
When I was investigating my problem, I also read following lines in the
postgresql log file:
2017-01-27 12:22:34 +03 LOG: using stale statistics instead of current ones
because stats collector is not responding
2017-01-27 12:27:35 +03 LOG: using stale statistics instead of current ones
because stats collector is not responding
2017-01-27 12:29:51 +03 LOG: using stale statistics instead of current ones
because stats collector is not responding
2017-01-27 12:30:51 +03 LOG: using stale statistics instead of current ones
because stats collector is not responding
2017-01-27 12:32:35 +03 LOG: using stale statistics instead of current ones
because stats collector is not responding
My questions are:
1- I understand that PostgreSQL is closing the connection. What may cause
for such a connection error, and how to solve it?
2- These "stale statistics" messages in log file, are they anything
important? Is there a way to stop them being logged because they seem to
grow log file.
Thanks.
Ertan Küçükoðlu
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Failed to set up event for socket: error code 10038
@ 2017-01-27 11:02 Thomas Kellerer <spam_eater@gmx.net>
parent: Ertan Küçükoðlu <ertan.kucukoglu@1nar.com.tr>
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Kellerer @ 2017-01-27 11:02 UTC (permalink / raw)
To: pgsql-admin
Ertan Küçükoğlu schrieb am 27.01.2017 um 11:23:
> I read a FATAL marked line in postgresql log file at exact same second:
> 2017-01-27 12:47:41 +03 FATAL: failed to set up event for socket: error
> code 10038
>
> Application is self-closing upon receiving such error. I instantly re-run it
> (to continue my code tests) and sometimes it is 3-4 times until I can get my
> application running.
>
> I am using latest version of Devart Universal Database Access Components
> (UniDAC) for performing database operations. As far as I know, these
> components make direct connection to PostgreSQL. Nothing in between like
> ODBC or anything. If that is relevant.
>
> When I was investigating my problem, I also read following lines in the
> postgresql log file:
> 2017-01-27 12:22:34 +03 LOG: using stale statistics instead of current ones
> because stats collector is not responding
> 2017-01-27 12:27:35 +03 LOG: using stale statistics instead of current ones
> because stats collector is not responding
> 2017-01-27 12:29:51 +03 LOG: using stale statistics instead of current ones
> because stats collector is not responding
> 2017-01-27 12:30:51 +03 LOG: using stale statistics instead of current ones
> because stats collector is not responding
> 2017-01-27 12:32:35 +03 LOG: using stale statistics instead of current ones
> because stats collector is not responding
>
> My questions are:
> 1- I understand that PostgreSQL is closing the connection. What may cause
> for such a connection error, and how to solve it?
> 2- These "stale statistics" messages in log file, are they anything
> important? Is there a way to stop them being logged because they seem to
> grow log file.
Try to disable your Anti-Virus for a test.
If things then work, configure your Anti-Virus to not scan the Postgres data directory and to not check postgres.exe
Thomas
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Failed to set up event for socket: error code 10038
@ 2017-01-27 12:51 Ertan Küçükoğlu <ertan.kucukoglu@1nar.com.tr>
parent: Thomas Kellerer <spam_eater@gmx.net>
0 siblings, 0 replies; 3+ messages in thread
From: Ertan Küçükoğlu @ 2017-01-27 12:51 UTC (permalink / raw)
To: 'Thomas Kellerer' <spam_eater@gmx.net>; pgsql-admin
> > Ertan Küçükoğlu schrieb am 27.01.2017 um 11:23:
> > I read a FATAL marked line in postgresql log file at exact same second:
> > 2017-01-27 12:47:41 +03 FATAL: failed to set up event for socket:
> > error code 10038
> >
> > Application is self-closing upon receiving such error. I instantly
> > re-run it (to continue my code tests) and sometimes it is 3-4 times
> > until I can get my application running.
> >
> > I am using latest version of Devart Universal Database Access
> > Components
> > (UniDAC) for performing database operations. As far as I know, these
> > components make direct connection to PostgreSQL. Nothing in between
> > like ODBC or anything. If that is relevant.
> >
> > When I was investigating my problem, I also read following lines in
> > the postgresql log file:
> > 2017-01-27 12:22:34 +03 LOG: using stale statistics instead of
> > current ones because stats collector is not responding
> > 2017-01-27 12:27:35 +03 LOG: using stale statistics instead of
> > current ones because stats collector is not responding
> > 2017-01-27 12:29:51 +03 LOG: using stale statistics instead of
> > current ones because stats collector is not responding
> > 2017-01-27 12:30:51 +03 LOG: using stale statistics instead of
> > current ones because stats collector is not responding
> > 2017-01-27 12:32:35 +03 LOG: using stale statistics instead of
> > current ones because stats collector is not responding
> >
> > My questions are:
> > 1- I understand that PostgreSQL is closing the connection. What may
> > cause for such a connection error, and how to solve it?
> > 2- These "stale statistics" messages in log file, are they anything
> > important? Is there a way to stop them being logged because they seem
> > to grow log file.
>
>
> Try to disable your Anti-Virus for a test.
>
> If things then work, configure your Anti-Virus to not scan the Postgres data directory and to not check postgres.exe
>
> Thomas
Disabling Anti-Virus did not work for me. I continue to have connection problems.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-01-27 12:51 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-01-27 10:23 Failed to set up event for socket: error code 10038 Ertan Küçükoðlu <ertan.kucukoglu@1nar.com.tr>
2017-01-27 11:02 ` Thomas Kellerer <spam_eater@gmx.net>
2017-01-27 12:51 ` Ertan Küçükoğlu <ertan.kucukoglu@1nar.com.tr>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox