Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session
| От | Cristian Bittel |
|---|---|
| Тема | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| Дата | |
| Msg-id | AANLkTi=-H6Ud8es4Q-kTAECf2VpbWKxvjsTGYz5eawRa@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session (Dave Page <dpage@pgadmin.org>) |
| Список | pgsql-hackers |
I am the "remote" support guy for a web developed application (Apache+PHP+Pg. Postgres is isolated on a server, Apache runs on another server), and installed at our client, our client is the Administrator user on Windows Server, I just have a limited privileges Windows user for monitoring. I have my own "support" superuser (not "postgres" user) for Postgres database to monitor the status, logs and to perform stats queries.
To Windows Server I just can login using remote desktop, my interactive user cannot start or stop the PostgreSQL service or other services, just Administrators users can do it.
From inside my underprivileged session on the Windows server I can open pgAdmin and connect to Postgres service. When I left the pgAdmin connected to Postgres service opened into the Windows session (session connected or disconnected) and I or someone else (Administrators) "close" my session, then is when PostgreSQL service crash. If inside the remote session I normally close pgAdmin using the "X" button or File>Exit or "Ctrl+Q", that not affect PostgreSQL service.
This is the major reason to think is pgAdmin.exe when forced shutdown by terminating Windows session which sends abnormal signal to PostgreSQL service.
Besides the abnormal signal that pgAdmin forced shutingdown could being send to PostgreSQL service, the service itself also could catch that behavior in any of the aproaches you are discussing for the service itself to ignore that signal.
To Dave's question, this behavior occurs on all Windows Server interactive sessions, no matter if Administrators or underpriviledge users, but is related to closing Windows interactive session while pgAdmin window is opened and connected to service. Nobody logon to Windows using "postgres" service user.
Regards,
Cristian.
To Windows Server I just can login using remote desktop, my interactive user cannot start or stop the PostgreSQL service or other services, just Administrators users can do it.
From inside my underprivileged session on the Windows server I can open pgAdmin and connect to Postgres service. When I left the pgAdmin connected to Postgres service opened into the Windows session (session connected or disconnected) and I or someone else (Administrators) "close" my session, then is when PostgreSQL service crash. If inside the remote session I normally close pgAdmin using the "X" button or File>Exit or "Ctrl+Q", that not affect PostgreSQL service.
This is the major reason to think is pgAdmin.exe when forced shutdown by terminating Windows session which sends abnormal signal to PostgreSQL service.
Besides the abnormal signal that pgAdmin forced shutingdown could being send to PostgreSQL service, the service itself also could catch that behavior in any of the aproaches you are discussing for the service itself to ignore that signal.
To Dave's question, this behavior occurs on all Windows Server interactive sessions, no matter if Administrators or underpriviledge users, but is related to closing Windows interactive session while pgAdmin window is opened and connected to service. Nobody logon to Windows using "postgres" service user.
Regards,
Cristian.
2010/8/31 Dave Page <dpage@pgadmin.org>
This behaviour, no - but desktop heap exhaustion is very easy toOn Sun, Aug 29, 2010 at 12:05 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Thu, Aug 26, 2010 at 22:59, Cristian Bittel <cbittel@gmail.com> wrote:
>> I still believe this "exit code 128" is related to pgAdmin opened during the
>> clossing session on Remote Desktop. I have a Windows user login wich is not
>> administrator just no privileged user, it cannot start/stop services, just
>> monitoring. With pgAdmin window opened inside my disconected session, as
>> Administrator if I "close" the another disconnected session, Postgres exit
>> with 128 code.
>
> If the closing of a session on the remote desktop can affect a
> *service* then frankly that sounds like a serious isolation bug in
> Windows itself. The postmaster grabs the handle of the process when
> it's started and waits on that - that should never be affected by
> something in a different session.
>
> I think it's more likely that Windows just looses track when you
> terminate a lot of processes at once, and randomly kills off something
> - or at least *indicates* that something has been killed off.
>
>> Did you reproduce this behavior?
>
> No, AFAIK nobody has managed to reproduce this behavior in any kind of
> consistent way. It's certainly been seen more than once in many
> places, but not consistently reproducible.
reproduce. That's because the heap usage is caused by user32.dll which
uses a consistent amount with each process started, which is allocated
as the process is created. When I was working on the issue a couple of
years ago, it was entirely predictable - user32.dll allocates N bytes
and as soon as N * numbackends exceeds the allocated heap size, we
fall over.
It shouldn't matter as desktop heap is allocated on a per-session
basis, but are you logging on using the service account to run your
admin tasks Cristian? If so, do you see the problem if you login
interactively using a different account?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления:
Предыдущее
От: Bruce MomjianДата:
Сообщение: Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!)
Следующее
От: Dave PageДата:
Сообщение: Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session