c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Monday 16 May 2011, you wrote:
> I had the same problem with OpenERP 6 on Ubuntu (11.04), and figured out
> what was wrong using strace:
> 
> openerp-server is trying to roll over an old /var/log/openerp-server.log
> to something with the date in the name, like /var/log/openerp-
> server.log.2011-05-12. It can't do this if the user the server is
> running as doesn't have appropriate permissions on /var/log, which it
> probably doesn't if you're running as openerp.
> 
There is another approach, done 2 years ago with commit:
http://git.hellug.gr/?p=xrg/openobject-server;a=commitdiff;h=deba425f4aa55449
(the commit is present on 6.0 branch)

setting "logrotate=False" in openerp-server.conf , will turn off that, and then 
you can use system's 'logrotate'. That one is safer.

-- 
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/329111

Title:
  OpenERP server stops logging

Status in OpenERP Server:
  Fix Released

Bug description:
  OpenERP server 5.0.0-2 stops logging after a specific (but possibly
  common) chain of events. There may be related problems, as it seems to
  be caused by a bad interaction between command line options and
  serverrc options.

  From a few experiments it seems to be a generic problem with options,
  but for completeness: I found this happening on a 64-bit Ubuntu 8.04
  LTS server with up to date packages, with the OpenERP server set up as
  running under a dedicated user/group ID, started from a customised
  init script. The  server is started using 'start-stop-daemon' which
  passes several options. (But the same thing seems to happen when
  starting the server from the commandline.)

  This is what happens: the server starts logging correctly (to a
  logfile specified with --logfile, but the same seems to happen when
  using syslog). Then, when changing the database admin password,
  .openerp_serverrc is written (which - redundantly - specifies several
  options including logging options). So far the server still writes to
  the log. However, when the server is restarted, it doesn't write to
  the log anymore.

  If the .openerp_serverrc is removed the server will start logging
  again on restart (but this obviously loses the database password).
  When .openerp_serverrc is created again, same problem will happen on
  server restart.

  So far I have been able to fix this by adding --log-level=info to the
  command line options. Maybe this overrides a broken log_level
  specification in the .openerp_serverrc?