Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

On Oct 4 07:02, Patrick Samson wrote: > --- Corinna Vinschen wrote: > > I'm still hoping for a simple testcase... > > I'm still working on it (the problem, not the > testcase, as it is probably a race condition). Too bad. I've checked in a patch to cygserver a few minutes ago. Since you're set

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Corinna Vinschen wrote: > On Oct 1 07:24, Patrick Samson wrote: > > > > --- Corinna Vinschen wrote: > > > > > On Sep 30 23:41, Patrick Samson wrote: > > > > Now, when it's wrong, I can see: > > > > good morning (error=4)! > > > > Error 4 is EINTR on the return of msleep(). > > > > Subseque

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

On Oct 1 07:24, Patrick Samson wrote: > > --- Corinna Vinschen wrote: > > > On Sep 30 23:41, Patrick Samson wrote: > > > Now, when it's wrong, I can see: > > > good morning (error=4)! > > > Error 4 is EINTR on the return of msleep(). > > > Subsequently semop() returns with this EINTR. > > > >

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Corinna Vinschen wrote: > On Sep 30 23:41, Patrick Samson wrote: > > Now, when it's wrong, I can see: > > good morning (error=4)! > > Error 4 is EINTR on the return of msleep(). > > Subsequently semop() returns with this EINTR. > > Are you set up to build cygwin? If so, could you > please

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Corinna Vinschen wrote: > On Oct 1 06:05, Patrick Samson wrote: > > > > --- Corinna Vinschen wrote: > > > > > On Sep 30 23:41, Patrick Samson wrote: > > > > Now, when it's wrong, I can see: > > > > good morning (error=4)! > > > > Error 4 is EINTR on the return of msleep(). > > > > Subseq

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

On Oct 1 06:05, Patrick Samson wrote: > > --- Corinna Vinschen wrote: > > > On Sep 30 23:41, Patrick Samson wrote: > > > Now, when it's wrong, I can see: > > > good morning (error=4)! > > > Error 4 is EINTR on the return of msleep(). > > > Subsequently semop() returns with this EINTR. > > > >

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Corinna Vinschen wrote: > On Sep 30 23:41, Patrick Samson wrote: > > Now, when it's wrong, I can see: > > good morning (error=4)! > > Error 4 is EINTR on the return of msleep(). > > Subsequently semop() returns with this EINTR. > > Are you set up to build cygwin? If so, could you > please

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

On Sep 30 23:22, Patrick Samson wrote: > --- Corinna Vinschen wrote: > > On Sep 30 00:12, Patrick Samson wrote: > > > I built the DLL another way, and now have: > > > $ cygcheck ./dp40.dll > > > .\dp40.dll > > > D:\cygwin\bin\cygwin1.dll < > > > C:\WINNT\System32\ADVAPI32.DLL

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

On Sep 30 23:41, Patrick Samson wrote: > Now, when it's wrong, I can see: > good morning (error=4)! > Error 4 is EINTR on the return of msleep(). > Subsequently semop() returns with this EINTR. Are you set up to build cygwin? If so, could you please test the following patch to cygserver and if

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Patrick Samson wrote: > With the third condition (pgAdmin) everything was > fine the whole night. And there is only 4 > "good night!" messages in the middle of the night. > I guess this is because of one of the cron tasks > scheduled around 3AM to do maintenance tasks such > as VACUUM, pg_dump

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Corinna Vinschen wrote: > On Sep 30 00:12, Patrick Samson wrote: > > I built the DLL another way, and now have: > > $ cygcheck ./dp40.dll > > .\dp40.dll > > D:\cygwin\bin\cygwin1.dll < > > C:\WINNT\System32\ADVAPI32.DLL > > C:\WINNT\System32\ntdll.dll > > C:\W

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

On Sep 30 00:12, Patrick Samson wrote: > I built the DLL another way, and now have: > $ cygcheck ./dp40.dll > .\dp40.dll > D:\cygwin\bin\cygwin1.dll < > C:\WINNT\System32\ADVAPI32.DLL > C:\WINNT\System32\ntdll.dll > C:\WINNT\System32\KERNEL32.dll > C:\WINNT\S

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

Sigh, Just after this post, I ran into the hang. So pgAdmin II is no better, may be just a little more difficult to fire the hang. Still searching ... --- Patrick Samson wrote: > > > Special note for Postgresql users: > > So far I can only reproduce this problem if these > > 3 conditions are met

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

> Special note for Postgresql users: > So far I can only reproduce this problem if these > 3 conditions are met: > - many connections (20, 25, 27) doing a simple > SELECT > - a script running SELECT, CREATE/DROP TABLE/INDEX > ... > - a pgAdmin III connected (but without activity) > (Postgresql ver

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Patrick Samson wrote: > > --- Patrick Samson wrote: > > Since my post I found a way to reproduce on > > development the problem I have on production. > > At some point cygserver hits 100%CPU and Postgres > > backends are no more able to serve requests. > > Now I must narrow the number of comp

Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl

--- Patrick Samson wrote: > > --- Igor Pechtchanski wrote: > > On Mon, 27 Sep 2004, Patrick Samson wrote: > > > > > I use a dll which have references to both > > > cygwin and m$: > > > $ cygcheck /usr/share/tcl8.4/dp4.0/win/dp40.dll > > > D:/cygwin/usr/share/tcl8.4/dp4.0/win/dp40.dll > > > D:\