Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0016172
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 01. General setupminoralways2011-03-08 17:342011-06-20 10:23
ReporterxabiermerinoView Statuspublic 
Assigned Tojpabloae 
PriorityhighResolutionfixedFixed in Version3.0MP0
StatusclosedFix in branchpiFixed in SCM revisiona
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version3.0RC4SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0016172: It is not possible to delete a client

DescriptionAccording this configuration, http://wiki.openbravo.com/wiki/ERP/2.50/Openbravo_environment_installation [^]

It is not possible to delete a client. This error appears:

Error:
out of shared memory
Steps To Reproduce- As System Administrator create a client
- Login as admin of the new client.
- Create 5 organizations
- As System Administrator try to delete the new client
- Realize that the error appears
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
depends on backport 0017654 closedgorka_gil It is not possible to delete a client 
has duplicate defect 0016550 closedjpabloae Delete Client runs out of memory in community appliance 

-  Notes
(0034733)
jpabloae (reporter)
2011-03-10 16:21

 Xabi,

Where have you reproduced this? Cloud Appliance? Community Appliance? Ubuntu?
(0034736)
xabiermerino (reporter)
2011-03-10 16:34

 Hi Juan Pablo,

it is reproducible in ubuntu stack and also at live.builds.openbravo.com.

Could be a problem with share buffer memory on Postgre?
(0035462)
egoitz (developer)
2011-04-01 13:28

 The kernel.shmmax parameter on ubuntu stack and appliance should have a higher value, and it should be possible to modifiy the shared_buffer propoery
on postgresql.conf file to use more memory.

With 256MB the performance is improved
(0035529)
jpabloae (reporter)
2011-04-04 12:35

 From 0016550:

This is related to the PostgreSQL memory allocation. It is necessary to increase it to remove this error. We'll deploy a fix for the appliance, but meanwhile you can apply it yourself in your current running ones:

1) Increase the kernel limits:

echo >> /etc/sysctl.conf
echo "# Openbravo - PostgreSQL" >> /etc/sysctl.conf
echo "kernel.shmmax = 268435456" >> /etc/sysctl.conf
sysctl -p /etc/sysctl.conf

2) Increase the PostgreSQL memory allocation:

Edit /srv/pgsql/8.4/postgresql.conf and set "shared_buffers" to 128MB.

3) Restart PostgreSQL:

/etc/init.d/tomcat stop
/etc/init.d/postgresql restart
/etc/init.d/tomcat start
(0035530)
jpabloae (reporter)
2011-04-04 12:39

 Note: we'll fix in the appliances. But we cannot fix it in Ubuntu, because it's not allowed for a package to change the kernel memory parameters:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/264336 [^]

So for Ubuntu we'll document it and state it clearly in the installation guide. And perhaps also with a message at the end of the installation process.
(0037304)
jpabloae (reporter)
2011-05-23 10:26

 Fix included in the RC7 appliance.
(0037902)
gorka_gil (administrator)
2011-06-02 00:56

 The problem is in the max_locks_per_transaction parameter, since the delete client touch in the same transaction more tables than the default configuration allows.

Increasing the max_locks_per_transaction in postgresql.conf from (64 standard) to 200, solves the problem.

Note: the max locks per transaction uses shared memory, so if your configuration of shared buffers is very low, increasing this parameter can make necessary to increase also the shared buffers parameter.
(0037906)
gorka_gil (administrator)
2011-06-02 10:29

 This fix will be included in MP0 appliances, except in Ubuntu since it is not allowed that an application modify the kernel parameters.

The default configuration included will be:
* (postgresql.conf) max_locks_per_transaction = 200
* (postgresql.conf) shared_buffers = 128MB
* (kernel) kernel.shmmax = 167772160 (160MB)

Also, starting from MP0 appliances, it is included a script that make these changes and restart postgresql:
  # /etc/init.d/tomcat stop
  # /usr/share/ops-base/bin/pgsql-tune
  # /etc/init.d/tomcat start
(0037907)
gorka_gil (administrator)
2011-06-02 10:30

 Verified

- Issue History
Date Modified Username Field Change
2011-03-08 17:34 xabiermerino New Issue
2011-03-08 17:34 xabiermerino Assigned To => adrianromero
2011-03-08 17:34 xabiermerino Modules => Core
2011-03-08 17:34 xabiermerino Issue Monitored: networkb
2011-03-08 17:49 adrianromero Assigned To adrianromero => jpabloae
2011-03-08 17:49 adrianromero Issue Monitored: adrianromero
2011-03-10 16:20 jpabloae Status new => acknowledged
2011-03-10 16:21 jpabloae Note Added: 0034733
2011-03-10 16:34 xabiermerino Note Added: 0034736
2011-04-01 13:28 egoitz Note Added: 0035462
2011-04-04 12:19 rafademiguel Issue Monitored: rafademiguel
2011-04-04 12:35 jpabloae Note Added: 0035529
2011-04-04 12:39 jpabloae Note Added: 0035530
2011-04-04 12:40 jpabloae Relationship added has duplicate 0016550
2011-05-23 10:25 jpabloae Status acknowledged => scheduled
2011-05-23 10:25 jpabloae fix_in_branch => pi
2011-05-23 10:26 jpabloae Note Added: 0037304
2011-05-23 10:26 jpabloae Status scheduled => resolved
2011-05-23 10:26 jpabloae Fixed in Version => 3.0MP7
2011-05-23 10:26 jpabloae Fixed in SCM revision => n/a
2011-05-23 10:26 jpabloae Resolution open => fixed
2011-06-02 00:56 gorka_gil Note Added: 0037902
2011-06-02 10:29 gorka_gil Note Added: 0037906
2011-06-02 10:30 gorka_gil Note Added: 0037907
2011-06-02 10:30 gorka_gil Status resolved => closed
2011-06-02 10:30 gorka_gil Fixed in Version 3.0MP7 => 3.0MP0
2011-06-17 10:27 maite Relationship added related to 0017654
2011-06-20 10:23 gorka_gil Relationship replaced depends on 0017654

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker