openerp-india team mailing list archive

[Carsten Schipke <carsten.schipke@xxxxxxxxxxxxx>]

** Description changed:

  I did now several clean OpenERP 7.0 installations from the debian / squeeze package repository with clean database etc.
- As soon as I install the "Payroll" module, I get following the exception & stack trace displayed in attached screenshot.
- Existing modules at this time are CRM and Timesheet.
+ As soon as I install the "Payroll" addon, I get the exception & stack trace displayed in attached screenshot.
  
- So the stack trace tells me it is related to the timesheet module, but
- the exception is triggered by the installation of Payroll module.
+ Existing installed addons at this time were CRM and Timesheet.
  
- Main issue here is that as soon as the system reached this state, it
- shows the same exception everytime I want to add/remove a module or do
- certain other actions. Only solution so far seems to be a reset of the
- whole system...
+ The stack trace tells me it seems to be related to the timesheet addon,
+ but the exception is actually triggered by the installation of Payroll
+ addon (I also had other actions triggerering the same issue - but
+ nothing I could remember clearly for this ticket).
+ 
+ Main issue here is that as soon as the system reaches this state, it
+ shows the same exception everytime I want to add/remove an addon. Only
+ solution so far seems to be a reset of the whole system...
  
  Unfortunately I can not find any useful information about architecture
  or runtime environment of the system to reason about its behavior and
  expectations myself.
  
- So most important for me would be some information about how to recover
+ Most important for me would be some information about how to recover
  from such states, since we really would like to evaluate the 7.0 release
- of openerp for our internal requirements.
+ of openerp for our internal requirements and reliability seems rather
+ important for a ERP system.
+ 
+ Being a developer myself (though zero python experience) I understand
+ that total reliability is impossible for a system that is openly
+ developed and anyway just released, so again, most important for me
+ would be some troubleshooting information / hints where to look etc.
+ 
+ I guess there is an internal job queue and/or some kind of  transactional processing etc. which makes the system try to finish what it started - which again put the system permanently infront of failed procedure. So how can I convince it to forget about this task? And/or how can I add/remove addons manually?
+ Also are there any maintenance features/scripts for validating and/or repairing data/system consistency etc. that might be helpful in such situations?

** Description changed:

  I did now several clean OpenERP 7.0 installations from the debian / squeeze package repository with clean database etc.
  As soon as I install the "Payroll" addon, I get the exception & stack trace displayed in attached screenshot.
  
  Existing installed addons at this time were CRM and Timesheet.
  
  The stack trace tells me it seems to be related to the timesheet addon,
  but the exception is actually triggered by the installation of Payroll
  addon (I also had other actions triggerering the same issue - but
  nothing I could remember clearly for this ticket).
  
  Main issue here is that as soon as the system reaches this state, it
  shows the same exception everytime I want to add/remove an addon. Only
  solution so far seems to be a reset of the whole system...
  
  Unfortunately I can not find any useful information about architecture
  or runtime environment of the system to reason about its behavior and
  expectations myself.
  
  Most important for me would be some information about how to recover
  from such states, since we really would like to evaluate the 7.0 release
  of openerp for our internal requirements and reliability seems rather
  important for a ERP system.
  
- Being a developer myself (though zero python experience) I understand
- that total reliability is impossible for a system that is openly
- developed and anyway just released, so again, most important for me
- would be some troubleshooting information / hints where to look etc.
+ I guess there is an internal job queue and/or some kind of
+ transactional processing etc. which makes the system try to finish what
+ it started - which again puts the system permanently in-front of failed
+ procedure. So how can I convince it to forget about this task? And/or
+ how can I add/remove addons manually?
  
- I guess there is an internal job queue and/or some kind of  transactional processing etc. which makes the system try to finish what it started - which again put the system permanently infront of failed procedure. So how can I convince it to forget about this task? And/or how can I add/remove addons manually?
- Also are there any maintenance features/scripts for validating and/or repairing data/system consistency etc. that might be helpful in such situations?
+ Are there any maintenance features/scripts for validating and/or
+ repairing data/system consistency etc. that might be helpful in such
+ situations?

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1101044

Title:
  Permanent crashing system - apparently related to timesheet module

Status in OpenERP Addons (modules):
  New

Bug description:
  I did now several clean OpenERP 7.0 installations from the debian / squeeze package repository with clean database etc.
  As soon as I install the "Payroll" addon, I get the exception & stack trace displayed in attached screenshot.

  Existing installed addons at this time were CRM and Timesheet.

  The stack trace tells me it seems to be related to the timesheet
  addon, but the exception is actually triggered by the installation of
  Payroll addon (I also had other actions triggerering the same issue -
  but nothing I could remember clearly for this ticket).

  Main issue here is that as soon as the system reaches this state, it
  shows the same exception everytime I want to add/remove an addon. Only
  solution so far seems to be a reset of the whole system...

  Unfortunately I can not find any useful information about architecture
  or runtime environment of the system to reason about its behavior and
  expectations myself.

  Most important for me would be some information about how to recover
  from such states, since we really would like to evaluate the 7.0
  release of openerp for our internal requirements and reliability seems
  rather important for a ERP system.

  I guess there is an internal job queue and/or some kind of
  transactional processing etc. which makes the system try to finish
  what it started - which again puts the system permanently in-front of
  failed procedure. So how can I convince it to forget about this task?
  And/or how can I add/remove addons manually?

  Are there any maintenance features/scripts for validating and/or
  repairing data/system consistency etc. that might be helpful in such
  situations?

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