[bitnami/odoo] Odoo 17 Bitnami-GCP Discus Not Realtime Error #1357
Comments
Cristianfllc3
added
the
tech-issues
javsalgar
changed the title
|
Hi! Could you confirm that you are using the Bitnami Odoo Helm chart or a Bitnami Odoo Cloud Image? |
|
Hi, |
|
Support for VMs/Cloud Images is provided at https://github.com/bitnami/vms. We'll transfer this issue there so the proper team can check it |
I execute ( sudo /opt/bitnami/bndiagnostic-tool )
|
|
Hi @Cristianfllc3, Thanks for using Bitnami. All I can see in the bndiagnostic bundle is that your virtual machine is running out of free memory, which can affect the real time service you mentioned. Your instance has little available RAM memory. Can you try to increase the memory available as explained in the next guide? https://docs.bitnami.com/virtual-machine/faq/administration/increase-memory/ |
|
Thanks for the support, I increased the RAM to 4GB and I still have the scenario where there is no real-time communication.
Thank you very much in advance. ===== Begin of bndiagnostic tool output ===== [Apache] Please check the following guide to troubleshoot server issues: Press [Enter] to continue: cf0b72fb-f2c9-8f7a-b074-79a53d3dac39 And paste it in your Bitnami Support ticket. tail -n 20 /opt/bitnami/odoo/log/odoo-server.log |
|
Hi @Cristianfllc3, According to the latest bndiagnostic tool I'd say all services are running fine on your machine, but the bndiagnostic tool doesn't get any info from Odoo's logs nor config file. Can you check them? Apart from the above, it seems to me this issue is more related to Odoo itself (to its config file probably) than to our installation, so I think it is a good idea to open a new question in the official support forums. |
|
Hi, In the previous message I attached the parts of the Odoo and Apache logs!, I also added several questions?
I don't think I should open another incident, it would be ideal to save the log history for reference, |
|
Hi, Is there any response to this incident? Thanks in advance |
|
Hi @Cristianfllc3, Sorry for the delay. There seems to be an issue in Odoo 17 itself with this realtime feature as mentioned in the following thread from the official forums. We recommend you to get more information on how to configure Odoo from there, as they are the experts in using the application. We would be glad to help you configure the required settings on the Bitnami machine if you have any questions. https://www.odoo.com/forum/help-1/no-real-time-update-in-discuss-241137 Regarding your other questions, find my comments inline
I suppose your question is related to these messages from Apache trying to connect with Odoo. Is that correct? If so, you don't have to worry, it is normal to get them while the Odoo app is starting and your web server is getting requests.
I don't fully understand this question. Can you elaborate? |
|
Hi, 1 - Before writing the incident, I have verified a few threads from forums and Odoo communities about the irregularity of communication in real time, and most remain at a conceptual level in the solution, like the one you refer to me and in another case the majority proposes a solution for ngixn and not in Apache.
2 - About my question > "In my current case, I present the errors that could be solved, what would be the ideal configurations for the .conf files odoo-http-vhost.conf? bitnami-ssl.conf? or others?" It is related to the same solution proposal thread that is discussed in the link you sent me > I have verified several files and several configuration parameters without a solution.
Verified configuration files: 3 - My premise, if I install a bitnami odoo image in GCP, all its modules should work since you are the one who configures that image, right? And given my case that I already have installed when I see that it does not work, I should find instructions on their support page for scenarios that involve extra configuration. I would be grateful if you could guide me on how to proceed, in case you can help define the correct configuration for the proper functioning of odoo's real-time communication. THanks in advance |
|
I add 2 points I attach some of the solutions that I have been collecting in the forum threads, several comment that these configurations should be added to nginx and there is no detailed reference on how to adjust it to Apache, and I repeat in the case of the Bitnami configuration it is particular. 1 - They do not detail in which configuration file and in which these parameters should be adjusted. ProxyRequests Off ProxyPass / http://127.0.0.1:8069/ retry=0 ProxyPass /longpolling/ http://localhost:8072/longpolling/ retry=0 ProxyPass /longpolling/poll/ wss://127.0.0.1:8072/longpolling/poll/ <Location /longpolling/poll/> Add these lines for WebSocket 2 - Verificando los workers y conection WebSocket
|
|
Hi, Is there any response to this incident? Thanks in advance |
|
Hi @Cristianfllc3, Thanks for your message. I understand you should add the mentioned config in both Odoo files under the |
|
Thank you for the message, If a module, in this case the communication module, does not work, it allows real-time communication, I assume that bitnami should propose a solution, right? I understand the added value of bitnami, since it has several shortcuts at other points. In this case, what bitnami can do to find a solution to: "When installing an instance of odoo-bitnami the communication module MUST be able to communicate in real time." In the forums there are many messages that are not oriented to the bitnami architecture (GCP-Odoo-Apache) and I trust that you have the ability to provide a solution. Thanks in advance, |
|
Hi @Cristianfllc3, We provide thirdparty applications in ready-to-use formats, but we configure those applications as per the official upstream recommendations. You can find the full Odoo application data under the Regarding your issue, and according to official forums mentioned in previous messages, there seems to be a bug or a misconfiguration in the Odoo application itself not related to our installation. Because of that, you will have to check the official forums for help on how to solve that issue and apply the required changes in your server. All we can do here is to help you update the Apache or Odoo configuration in case you have any questions, but we can't provide you with the required changes for the fix because we don't have enough knowledge on how Odoo works internally (that's why we recommend you to ask the official developers, as they are the experts here). Sorry for the inconveniences you are facing. I really hope you can find a fix for those issues. |
|
Hi @gongomgra Thanks for all the detailed explanation. I understand that you are not experts in every tool you support. The Odoo error of lack of real-time communication is discussed in several forums, videos, etc., as I have mentioned in other messages as well, I have tried several solutions myself. What I do not agree with is that it says that it is a particular bad configuration, if I am using by DEFAULT the image that BITNAMI created or is it that this error comes by default! It may be that I misunderstand Bitnami's service/support, More than an incident, it is a process issue. Is it that in the image they should clarify that in version 17 the communication module does not work correctly?, and thus the client, me in this case, is prepared and knows that he is going to use Odoo with that irregularity. I hope it is not seen as a negative debate, I repeat, I like Bitnami's tools, which surprises me that something does not work correctly by default without prior notice. I imagine they can close the incident if there is no proposed solution to have an image that does not have that Odoo bug. Thanks for the support! |
|
Hi @Cristianfllc3, Thanks for your message. As mentioned previously, we offer upstream applications configured with the official instructions and recommendations from its developers without further modifications. In case there is an issue in an upstream application or a plugin, we can only wait for them to publish a new version solving the problem by default, and/or wait for them to provide end users with instructions on how to remediate it in their currently published versions. However, it looks like the application has an issue not related to Bitnami, but no official instructions on how to fix it are provided from upstream project yet, so I'm afraid there's nothing we can do here at this moment. We recommend you to keep asking for help in the official forums. Sorry for the inconveniences. |
|
Hello @gongomgra , I ended up installing a version of odoo17 with the Nginx server and after several configurations, the messaging system works real time. There is some hope!, that given the Nginx parameters, Bitnami can make the adaptations (AS YOU MAKE IT FROM NGINX TO APACHE IN YOUR IMAGE) and identify where its need to adjust these parameters in the Odoo bitnami Apache configuration! To fix this chat real time in your image! Thanks in advance #odoo/odoo#106339 map $http_upgrade $connection_upgrade { server { proxy_read_timeout 720s; logaccess_log /var/log/nginx/odoo.access.log; Redirect requests to odoo backend serverlocation / { location /websocket { common gzipgzip_types text/css text/less text/plain text/xml application/xml application/json application/javascript; client_body_in_file_only clean; |
|
Hi @Cristianfllc3, Sorry for the delay. I have been checking the Odoo 17 official configuration and I think I know what's happening. By default, we configure our Odoo instances in multi-threaded mode, while the LiveChat module seems to need Odoo running in multi-process mode. We enable multi-thread by default for simplicity and testing purposes, but you can configure multi-process on your side by following the official Odoo guides on this. Regarding the LiveChat module, we recommend you to check the official docs for further configuration requirements. About the NGINX configuration you shared, I found it in the Odoo docs as well, although they do not mention Apache web server is not supported. Checking the recommended setup, I understand the only change required in our Apache configuration is to add similar |
|
Hi @gongomgra Thanks for the message and the support. I will check the documentation that iu send me, and with the community . Have a nice day. |
|
Hello, here is how I proceeded to make the websocket service work correctly with Apache on Odoo 16 and Odoo 17. This solution works 100% on Odoo 16. On Odoo 17, the websocket service works correctly except with OdooBot onboard (there seems to be an issue with the CSRF token). Installation of the Bitnami Odoo image on an EC2 instance T3 small (2vCPU + 2GB RAM + 30GB HDD). Security group with these inbound rules: HTTPS TCP 443 0.0.0.0/0 Create an Elastic IP address 1- Verify if a swap is activated :
If result is empty, swap is not enabled, create a swap (e.g., 2GB)
Verify if a swap is activated :
Permanent swap configuration:
Add the following line at the end of the file and then save:
2- Update your system : Update your server timezone : e.g Europe/Paris httpd.conf configuration : Update this lines with your info (on lines 196 and 205): ServerAdmin [email protected]
Update your domain on line 2: ServerName www.mydomain.com
ServerName www.mydomain.com
3- Install letsencrypt SSL certificate :
4- Modify your odoo.conf
modify your email on line 17 : disabled longpolling line 30 with ; ;longpolling_port = 8072 and add a line 31 for gevent_port :
change workers on line 46 end remove the ; : workers = 2 5- Modify your odoo-https-vhost.conf
Add the following lines like this : 6- Allow traffic from websocket port 8072 :
7- Connect to Odoo at your URL with your account [email protected] and your password (to see your password use this command) 8- Go to Apps menu and activate discuss module 9- Modify your web.base.url At the key web.base.url change http to https:// 10- Restart all services |
|
@Nextcom-NC, Thank you very much for your time and your contribution. Without a doubt, the solution proposal is better documented than on the official bitanmi page 🪬 |
|
Hi @Cristianfllc3, @Nextcom-NC, Thanks for your message and for sharing your solution. We have an internal task open to update the |
gongomgra
added
on-hold
|
Hi @Cristianfllc3 @Nextcom-NC, Thanks for your help on reporting and checking this issue. We have released a new revision of our images including the updated Apache and Odoo configuration for this to work. You can find the new AWS AMI IDs in our website https://bitnami.com/stack/odoo/cloud/aws/amis Hope it helps! |
gongomgra
added
triage
|
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
|
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitname/odoo17
What architecture are you using?
None
What steps will reproduce the bug?
I installed the latest version of odoo bitnami in GCP (17), after the base configurations, the internal chat communication is not updated in real time, you have to refresh the page for the messages to load.
What is the expected behavior?
That communication in the disk module is carried out in real time and does not have to refresh the browser to see the messages.
What do you see instead?
I get the browser notification but the message is not displayed in the discuss module.
Additional information
I have invented several parameter settings in odoo.config and bitnami.confg but I still get the same error.
The text was updated successfully, but these errors were encountered: