Subject | Re: [firebird-support] Re: sweep is running for more than 7 days now :( |
---|---|
Author | Dmitry Kuzmenko |
Post date | 2012-02-06T14:01:29Z |
Hello, nathanelrick!
Monday, February 6, 2012, 5:38:42 PM, you wrote:
n> by kill mean
n> NET STOP "Firebird Server - DefaultInstance"
If this is Classic, you will just stop "listener" process,
and it will not stop sweeping. Maybe you have some fb_inet_server process
that "locks" sweeping.
If this is SuperServer, this will stop sweep, i.e.
this will stop FB completely, and yes, sweep to.
I suggest you, in both cases, to save output of fb_lock_print.exe
before you will try to stop anything.
This output can help to understand what caused sweep to lock.
n> this is not safe too do to this during a sweep ?
depends on what happened. If sweep is stalled, then it can
be safe to stop server. If sweep is working, stopping it usually dangerous.
--
Dmitry Kuzmenko, www.ib-aid.com
Monday, February 6, 2012, 5:38:42 PM, you wrote:
n> by kill mean
n> NET STOP "Firebird Server - DefaultInstance"
If this is Classic, you will just stop "listener" process,
and it will not stop sweeping. Maybe you have some fb_inet_server process
that "locks" sweeping.
If this is SuperServer, this will stop sweep, i.e.
this will stop FB completely, and yes, sweep to.
I suggest you, in both cases, to save output of fb_lock_print.exe
before you will try to stop anything.
This output can help to understand what caused sweep to lock.
n> this is not safe too do to this during a sweep ?
depends on what happened. If sweep is stalled, then it can
be safe to stop server. If sweep is working, stopping it usually dangerous.
--
Dmitry Kuzmenko, www.ib-aid.com