Skip to Content
Menu
This question has been flagged
1 Reply
2157 Views

Hi all,

I am having issues when making changes in studio. I have now had a "500 internal server error" which makes Odoo inaccessible the last 3-4 times I have been making changes in Studio. 


The last error that caused the crash starts with:


"RPC_ERROR

Odoo Server Error

Traceback (most recent call last):

  File "/home/odoo/src/odoo/odoo/api.py", line 989, in get

    cache_value = field_cache[record._ids[0]]

KeyError: 1 "


I can post the rest but don't want to clutter this question too much. 


What I think I have pin pointed is the crash happens when I am saving a change in studio and 2 otherusers simultaneously perform an action. In the most recent case I was changing a field label (not the technical name, just the label), and 2 users validated transfers at the same time. 


I tested with 1 user actioning a transfer at the same time as a studio save which caused the same type of error, but didn't crash the server. I was able to clear the error, but needed to re save the change.


What is unusual is we implemented Odoo in May and made many studio changes after go live with no issue. Users were working in the database as normal at the same time i was saving studio changes. Now it is almost every time i make a change.   ​  


Does anyone have experience of this? I cannot see how studio can be usable if you need to stop all users from working in the database while changes are being made.


Could it be to do with the size of our database now compared to after go live? more data = more strain on the server? we are using Odoo.SH hosting.


any help is appreciated


Graeme 

 

   


Avatar
Discard
Author Best Answer

I received a response from Odoo support:

"The error your client is facing is connected to a known issue on Odoo.SH. If you try to modify a model with studio that is used in parallel (by another user for instance), it sometimes corrupts the registry, which blocks the access to the records, which ends up corrupting the whole process of retrieving data from the database, thus making the instance inaccessible.

This is a current limitation, so it may happen to you again in the future if you do use Studio. To avoid this issue, here are some tips:

-avoid using Studio during strong activity hours. As explained earlier, the issue happens if there is a parallel activity on the same model, if you do Studio operations outside of activity hours, you reduce this risk.

-use custom Odoo.SH code to add fields rather than using Studio.

Finally, if the very same issue happen to you in the future, there is an "easy" way to solve it out. As the issue is caused by the registry being corrupted, if we reset it, the issue disappears with it. In order to do this you can either:

1.Open a webshell session or Editor > Console, then type the command: odoosh-restart http

2. Open the odoo.sh Editor in the menu go to Odoo > Restart

We are working to fix this issue entirely in future versions of Odoo, however for now this is the best solution."


Avatar
Discard
Related Posts Replies Views Activity
1
Jul 25
1131
2
Mar 25
1401
0
Feb 25
1075
0
Feb 25
1217
0
Feb 25
1201