Обсуждение: BUG #14423: Fail to connect to DB
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDQyMwpMb2dnZWQgYnk6ICAg ICAgICAgIE1pa2FlbCBXYWxsZW4KRW1haWwgYWRkcmVzczogICAgICBtaWth ZWwud2FsbGVuQHNwYXJrLXZpc2lvbi5jb20KUG9zdGdyZVNRTCB2ZXJzaW9u OiA5LjQuMTAKT3BlcmF0aW5nIHN5c3RlbTogICBXaW5kb3dzIDEwIChWZXJz aW9uIDE2MDcgT1MgQnVpbGQgMTQzOTMuNDQ3KQpEZXNjcmlwdGlvbjogICAg ICAgIAoKQWZ0ZXIgcmVjZW50IFdpbmRvd3MgdXBkYXRlcyB3ZSBhcmUgZ2V0 dGluZyBjb25uZWN0aW9uIGVycm9ycyBhbmQgdGhlIGxvZ3MKYXJlIGZ1bGwg b2YgdGhlIGZvbGxvd2luZyBlcnJvcnM6DQoyMDE2LTExLTE0IDEwOjAwOjQz IENFVCBMT0c6ICBjb3VsZCBub3QgcmVzZXJ2ZSBzaGFyZWQgbWVtb3J5IHJl Z2lvbgooYWRkcj0wMDAwMDAwMDAyMkMwMDAwKSBmb3IgY2hpbGQgMDAwMDAw MDAwMDAwMEZFMDogZXJyb3IgY29kZSA0ODcNCjIwMTYtMTEtMTQgMTA6MDA6 NDMgQ0VUIExPRzogIGNvdWxkIG5vdCBmb3JrIGF1dG92YWN1dW0gd29ya2Vy IHByb2Nlc3M6IE5vCmVycm9yDQoNCldlIGFyZSBhbHNvIHNlZWluZyB0aGUg c2FtZSBpc3N1ZSBvbiBXaW5kb3dzIDcgeDY0IGFuZCB3aXRoIFBvc3RncmVT UUwKdmVyc2lvbnMgOS40LjgsIDkuNS4yIGFuZCA5LjUuNS4NCg0KRXJyb3Jz IHNheWluZyAiY291bGQgbm90IGZvcmsgbmV3IHByb2Nlc3MgZm9yIGNvbm5l Y3Rpb246IE5vIGVycm9yIiBhcmUgYWxzbwpvY2N1cnJpbmcgd2hlbiB1c2lu ZyBwZ2FkbWluSUlJIGFzIHdlbGwgYXMgcHNxbC4gRXZlcnl0aGluZyB3b3Jr ZWQgd2VsbApiZWZvcmUgdGhlIHJlY2VudCBXaW5kb3dzIHVwZGF0ZXMuIElz IHRoaXMgc29tZWhvdyByZWxhdGVkIHRvIGNoYW5nZXMgaW4KQVNMUiAoYWRk cmVzcyBzcGFjZSBsYXlvdXQgcmFuZG9taXphdGlvbikgYW5kIGlmIHNvLCBp cyB0aGVyZSBhbnkKd29ya2Fyb3VuZD8KCg==
On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.com> wrote: > Errors saying "could not fork new process for connection: No error" are also > occurring when using pgadminIII as well as psql. Everything worked well > before the recent Windows updates. Is this somehow related to changes in > ASLR (address space layout randomization) and if so, is there any > workaround? Let me guess: you are seeing that since you updated to Win7 SP1? That's not the first complain in the area... -- Michael
Not exactly. We are seeing this on both Windows 7 SP1 and Windows 10 and it started after recent Windows security updates. If we manually restart the PostgreSQL service it starts working again but the problem usually comes back after a day or two. /Mikael -----Original Message----- From: Michael Paquier [mailto:michael.paquier@gmail.com] Sent: den 15 november 2016 04:10 To: Mikael Wallén <Mikael.Wallen@spark-vision.com> Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org> Subject: Re: [BUGS] BUG #14423: Fail to connect to DB On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.com> wrote: > Errors saying "could not fork new process for connection: No error" > are also occurring when using pgadminIII as well as psql. Everything > worked well before the recent Windows updates. Is this somehow related > to changes in ASLR (address space layout randomization) and if so, is > there any workaround? Let me guess: you are seeing that since you updated to Win7 SP1? That's not the first complain in the area... -- Michael
Some additional info. It seems as if this is related to F-Secure and/or anti-virus software in general. A colleague tried to temporarily disableF-Secure and then the errors stopped. However as soon as he enabled F-Secure again the error messages started fillingthe PostgreSQL logs. However I have also seen the same error messages on a virtual machine running Windows 10 Pro with the latest Windows updatesand there I am not running F-Secure. I am running Windows Defender though. /Mikael -----Original Message----- From: Michael Paquier [mailto:michael.paquier@gmail.com] Sent: den 15 november 2016 04:10 To: Mikael Wallén <Mikael.Wallen@spark-vision.com> Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org> Subject: Re: [BUGS] BUG #14423: Fail to connect to DB On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.com> wrote: > Errors saying "could not fork new process for connection: No error" > are also occurring when using pgadminIII as well as psql. Everything > worked well before the recent Windows updates. Is this somehow related > to changes in ASLR (address space layout randomization) and if so, is > there any workaround? Let me guess: you are seeing that since you updated to Win7 SP1? That's not the first complain in the area... -- Michael
On Wed, Nov 16, 2016 at 1:48 AM, Mikael Wall=C3=A9n <Mikael.Wallen@spark-vision.com> wrote: > Some additional info. > It seems as if this is related to F-Secure and/or anti-virus software in = general. A colleague tried to temporarily disable F-Secure and then the err= ors stopped. However as soon as he enabled F-Secure again the error message= s started filling the PostgreSQL logs. > However I have also seen the same error messages on a virtual machine run= ning Windows 10 Pro with the latest Windows updates and there I am not runn= ing F-Secure. I am running Windows Defender though. Interesting. So would Windows 10 be enforcing Windows Defender or a virus scanner to be enabled? This OS shines a lot in updating settings forcibly with its automatic updates, sometimes without caring about what the user may have changed in the past. --=20 Michael