c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <824783@xxxxxxxxxxxxxxxxxx>]

Hello,

The usual cause for --stop-after-init failing to stop the process is
that other background threads are active in the server, and either
currently processing requests, or failing to appropriately react to the
shutdown procedure.

Looking at your startup logs, we can see at least 2 things that are starting background threads:
 - document_ftp modules starts at 11:00:16,412, but it fails to open the listening socket because the 8021 is already in use. This module normally uses timeout to react to shutdown events in a timely manner anyway.
 - pyro: the pyro module starts at 11:00:16,099 and it opens a listening socket on port 8072. Perhaps this service does not properly handling shutdown events?
- there are perhaps other custom modules in your database that run background threads as well...?

Some things you could do to narrow down the problem:
- make a copy of the database with the issue, then disable the pyro module or uninstall it temporarily, and see if that makes the problem go away. Do the same with any other suspected module
- alternatively, make a copy of a database that does not have the problem, then add the suspicious modules one by one, and see which one makes it fail the --stop-after-init

I suppose replacing the sys.exit() (graceful termination) with an
os._exit() (hard process kill) would be a valid way to make the problem
go away in the case of --stop-after-init. Normally only the
initialization of the server has been done, and it should not be
servicing requests, so a hard kill would not do much harm. But I'd like
to avoid such a solution, because it would only hide the issue in the
case of --stop-after-init, but still requiring a hard kill (or double
ctrl-c) every time to shutdown the server when it is running in normal
mode. I'd rather have all modules with background threads behave as good
citizens when it comes to background threads.

** Changed in: openobject-server
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/824783

Title:
  v6 stop_after_init does not exit

Status in OpenERP Server:
  Incomplete

Bug description:
  please see last comment on
  https://bugs.launchpad.net/openobject-server/5.0/+bug/574874
  can not change the status of the bug  there

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/824783/+subscriptions