Skip to Content
Menu
This question has been flagged
2 Replies
2355 Views

Hi,
 I get this 500:Internal server Error , I believe it happend after I uninstalled some third party module, service restart/Inkognito window did not help, accessing database selector doesnt work.

Log shows this (not sure what I am looking for)

Any ideas?

2023-06-09 09:20:12,250 1333 DEBUG ? odoo.sql_db: create serialized cursor to {'database': '*****', 'application_name': '*****', 'host': '192.168.1.7', 'port': 5555, 'user': '*****', 'password': '******', 'sslmode': 'prefer'} 
2023-06-09 09:20:12,267 1333 DEBUG ? odoo.sql_db.connection: ConnectionPool(used=2/count=2/max=64) Create new connection backend PID 78603 
2023-06-09 09:20:12,267 1333 DEBUG ? odoo.sql_db: query: select datname from pg_database where datdba=(select usesysid from pg_user where usename=current_user) and not datistemplate and datallowconn and datname not in ('postgres', 'template0') order by datname 
2023-06-09 09:20:12,272 1333 DEBUG ? odoo.sql_db: SQL LOG from: 
2023-06-09 09:20:12,272 1333 DEBUG ? odoo.sql_db: table: pg_user: 0:00:00.004273/1 
2023-06-09 09:20:12,272 1333 DEBUG ? odoo.sql_db: SUM from:0:00:00.004273/1 [24664] 
2023-06-09 09:20:12,273 1333 DEBUG ? odoo.sql_db: SUM into:0:00:00/1 [24664] 
2023-06-09 09:20:12,273 1333 DEBUG ? odoo.sql_db.connection: ConnectionPool(used=2/count=2/max=64) Give back connection to 'user=**** password=**** dbname=***** host=192.168.1.7 port=5555 application_name=odoo-1333 sslmode=prefer' 
2023-06-09 09:20:12,273 1333 DEBUG ? odoo.sql_db.connection: ConnectionPool(used=1/count=1/max=64) Forgot connection to 'user=***** password=**** dbname=****** host=192.168.1.7 port=5555 application_name=****** sslmode=prefer' 
2023-06-09 09:20:12,274 1333 DEBUG dev odoo.sql_db: create serialized cursor to {'database': 'dev', 'application_name': '******', 'host': '192.168.1.7', 'port': 5555, 'user': '*****', 'password': '*****', 'sslmode': 'prefer'} 
2023-06-09 09:20:12,289 1333 DEBUG dev odoo.sql_db.connection: ConnectionPool(used=2/count=2/max=64) Create new connection backend PID 78604 
2023-06-09 09:20:12,289 1333 DEBUG dev odoo.sql_db: query: 
SELECT latest_version
FROM ir_module_module
WHERE name='base'
 
2023-06-09 09:20:12,292 1333 DEBUG dev odoo.sql_db: query: 
SELECT *, cron_name->>'en_US' as cron_name
FROM ir_cron
WHERE active = true
AND numbercall != 0
AND (nextcall <= (now() at time zone 'UTC')
OR id in (
SELECT cron_id
FROM ir_cron_trigger
WHERE call_at <= (now() at time zone 'UTC')
)
)
ORDER BY priority


2023-06-09 09:20:20,190 60292 INFO ? odoo: Odoo version 16.0 
2023-06-09 09:20:20,191 60292 INFO ? odoo: Using configuration file at /etc/odoo/odoo_demo.conf 
2023-06-09 09:20:20,191 60292 INFO ? odoo: addons paths: ['/opt/odoo/odoo_test/odoo/odoo/addons', '/opt/odoo/.local/share/Odoo/addons/16.0', 
'/opt/odoo/odoo_test/odoo/addons', 
'/opt/odoo/odoo_test/odoo/addons_custom', '/opt/odoo/odoo_test/odoo/addons_demo', '/opt/odoo/odoo_test/odoo/addons_enterprise'] 
2023-06-09 09:20:20,191 60292 INFO ? odoo: database: odoo2@192.168.1.7:5555 
2023-06-09 09:20:20,410 60292 INFO ? odoo.addons.base.models.ir_actions_report: Will use the Wkhtmltopdf binary at /usr/local/bin/wkhtmltopdf 
2023-06-09 09:20:20,815 60292 INFO ? odoo.service.server: HTTP service (werkzeug) running on 0.0.0.0:8169 
2023-06-09 09:20:20,823 60311 INFO ? odoo.service.server: Worker WorkerHTTP (60311) alive 
2023-06-09 09:20:20,825 60312 INFO ? odoo.service.server: Worker WorkerHTTP (60312) alive 
2023-06-09 09:20:20,828 60313 INFO ? odoo.service.server: Worker WorkerHTTP (60313) alive 
2023-06-09 09:20:20,831 60314 INFO ? odoo.service.server: Worker WorkerHTTP (60314) alive 
2023-06-09 09:20:20,833 60315 INFO ? odoo.service.server: Worker WorkerHTTP (60315) alive 
2023-06-09 09:20:20,836 60318 INFO ? odoo.service.server: Worker WorkerHTTP (60318) alive 
2023-06-09 09:20:20,848 60324 INFO ? odoo.service.server: Worker WorkerCron (60324) alive 
2023-06-09 09:20:20,852 60324 DEBUG ? odoo.sql_db: create serialized cursor to {'database': 'postgres', 'application_name': 'odoo-60324', 'host': '192.168.1.7', 'port': 5555, 'user': '*****', 'password': '*****', 'sslmode': 'prefer'} 
2023-06-09 09:20:20,851 60325 INFO ? odoo.service.server: Worker WorkerCron (60325) alive 
2023-06-09 09:20:20,854 60325 DEBUG ? odoo.sql_db: create serialized cursor to {'database': 'postgres', 'application_name': 'odoo-60325', 'host': '192.168.1.7', 'port': 5555, 'user': 'u*****', 'password': '******', 'sslmode': 'prefer'} 
2023-06-09 09:20:20,877 60324 DEBUG ? odoo.sql_db.connection: ConnectionPool(used=1/count=1/max=64) Create new connection backend PID 78612 
2023-06-09 09:20:20,877 60325 DEBUG ? odoo.sql_db.connection: ConnectionPool(used=1/count=1/max=64) Create new connection backend PID 78613 
2023-06-09 09:20:20,878 60324 DEBUG ? odoo.sql_db: query: SELECT pg_is_in_recovery() 
2023-06-09 09:20:20,878 60325 DEBUG ? odoo.sql_db: query: SELECT pg_is_in_recovery() 
2023-06-09 09:20:20,882 60325 DEBUG ? odoo.sql_db: query: LISTEN cron_trigger 
2023-06-09 09:20:20,882 60324 DEBUG ? odoo.sql_db: query: LISTEN cron_trigger 
2023-06-09 09:20:22,083 60321 WARNING ? py.warnings: /opt/odoo/odoo_test/odoo/odoo/tools/config.py:565: DeprecationWarning: The longpolling-port is a deprecated alias to the gevent-port option, please use the latter.
File "/opt/odoo/odoo_test/odoo/odoo-bin", line 8, in
odoo.cli.main()
File "/opt/odoo/odoo_test/odoo/odoo/cli/command.py", line 56, in main
o.run(args)
File "/opt/odoo/odoo_test/odoo/odoo/cli/server.py", line 179, in run
main(args)
File "/opt/odoo/odoo_test/odoo/odoo/cli/server.py", line 127, in main
odoo.tools.config.parse_config(args)
File "/opt/odoo/odoo_test/odoo/odoo/tools/config.py", line 378, in parse_config
self._warn_deprecated_options()
File "/opt/odoo/odoo_test/odoo/odoo/tools/config.py", line 565, in _warn_deprecated_options
warnings.warn(

Thank you

Avatar
Discard
Best Answer

Hi Jozef,

Try upgrading your base module. Since you are not able to access the application, try upgrading using the service startup parameters. First find the service file location, Modify the 'ExecStart' option under the 'Service' directive to update the base module on server startup and then restart the service/server.

  • SSH into your Server
  • Open the Service File
  • Add the following flags to ExecStart "-d database_name -u base --stop-after-init" replace the database_name with your actual database name
  • Restart Service (sudo systemctl restart service)

Final Execstart should look something like:

ExecStart=/odoo-bin --config=/odoo-conf --addons-path=/addons -d database_name -u base --stop-after-init

--stop-after-init flag stops the server once the upgrade process is finished. Depending on the server upgrading base module can take sometime, make sure to wait sometime before restarting the server after the upgrade process has finished.

Remove the "-d database_name -u base --stop-after-init" flags to start the server normally.

Make sure to vote and mark this as the best answer if this helps you

cheers!

Avatar
Discard
Best Answer

Hi,

Try upgrading the base module in the corresponding db from the command line and see if the issue get resolved or not.

upgrade module from terminal:   https://www.youtube.com/watch?v=c7QL1X3-Zlc

Thanks

Avatar
Discard
Related Posts Replies Views Activity
1
Aug 23
2528
0
Aug 23
2130
1
Aug 23
1263
2
May 15
8371
1
Mar 15
6149