auto back up make zero size .zip backup file
zeintiz opened this issue · 6 comments
hello
We have Odo 13. We have several databases in different sizes. We installed auto backup module , and worked fine until 10 days. It has been taking backups without error , but the backup size of our large database is zero. All our database backups are working properly (small size) , but the largest database( is around 1.7 gig) has zero size, and it is getting bigger day by day. Until last week, there have 15 concurrent users, and since last week, it has become 18 users.
I will send the specifications of the config file and automatic backup settings. I will also send the odoo server log. its our production server. that we don't have debug tools on it.
any idea. any help. please.
tankx in advance
configuration page:
odoo.conf:
[options]
addons_path = /usr/lib/python3/dist-packages/odoo/addons,/usr/lib/python3/dist-packages/odoo/addons-custom
admin_passwd = 92Bs3rg
csv_internal_sep = ,
data_dir = /var/lib/odoo/.local/share/Odoo
db_host = False
db_maxconn = 64
db_name = False
db_password = False
db_port = False
db_sslmode = prefer
db_template = template0
db_user = odoo
dbfilter =
demo = {}
email_from = False
geoip_database = /usr/share/GeoIP/GeoLite2-City.mmdb
http_enable = True
http_interface =
http_port = 8069
import_partial =
limit_memory_hard = 2684354560
limit_memory_soft = 2147483648
limit_request = 8192
limit_time_cpu = 60
limit_time_real = 120
limit_time_real_cron = -1
list_db = True
log_db = False
log_db_level = warning
log_handler = :INFO
log_level = info
logfile = /var/log/odoo/odoo-server.log
longpolling_port = 8072
max_cron_threads = 2
osv_memory_age_limit = 1.0
osv_memory_count_limit = False
pg_path =
pidfile =
proxy_mode = False
reportgz = False
screencasts =
screenshots = /tmp/odoo_tests
server_wide_modules = base,web
smtp_password = False
smtp_port = 25
smtp_server = localhost
smtp_ssl = False
smtp_user = False
syslog = False
test_enable = False
test_file =
test_tags = None
translate_modules = ['all']
unaccent = False
upgrade_path =
without_demo = False
workers = 0
here is my odoo server log
2022-07-03 13:30:17,626 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:30:17,629 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:30:17] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.003 0.011
2022-07-03 13:30:34,620 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:30:34,623 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:30:34] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.005 0.013
2022-07-03 13:30:41,752 1581 INFO dbssfit odoo.addons.base.models.ir_cron: Starting job Backup scheduler
.
2022-07-03 13:30:41,789 1581 INFO dbssfit odoo.addons.auto_backup.models.db_backup: DUMP DB: dbssfit format zip
2022-07-03 13:30:50,629 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:30:50,634 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:30:50] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.003 0.015
2022-07-03 13:30:59,304 1581 INFO dbssfit odoo.addons.base.models.ir_cron: Job Backup scheduler
done.
2022-07-03 13:31:14,619 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:31:14,624 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:31:14] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.004 0.015
2022-07-03 13:31:44,622 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:31:44,626 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:31:44] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.004 0.015
2022-07-03 13:31:58,132 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:31:58,135 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:31:58] "POST /longpolling/im_status HTTP/1.1" 404 - 1 0.004 0.013
2022-07-03 13:32:00,212 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:32:00] "POST /web/webclient/version_info HTTP/1.1" 200 - 1 0.004 0.015
2022-07-03 13:32:01,683 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:32:01,687 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:32:01] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.004 0.013
2022-07-03 13:32:16,731 1581 WARNING ? odoo.http: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
2022-07-03 13:32:16,734 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:32:16] "POST /longpolling/poll HTTP/1.1" 404 - 1 0.005 0.014
2022-07-03 13:32:31,221 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:32:31] "GET /web?db%3Ddbssfit HTTP/1.1" 303 - 2 0.009 0.022
2022-07-03 13:32:31,438 1581 INFO ? werkzeug: 192.168.65.125 - - [03/Jul/2022 13:32:31] "GET /web/database/selector HTTP/1.1"
@zeintiz I have the same problem
Same problem on v.16, but all logs are fine. This module works fine on all my instances except one, that have the same configuration as worked ones, but generate 0-bytes .zip archives in manual and auto mode. I've tried to reinstall this module many times, down/up my container, have checked read/write to /tmp and /mnt, but result is the same.
I have the same problem with Odoo 16 in docker. I can generate pg_dump file correctly but zip file is created with 0 bytes size.
I have the same issue with odoo 14.
Before it was working fine, but now I have the 0 bytes zip backups.
I found an issue in my case (odoo 14, OS debian 10), the host system is CentOS 7 with PG 13.
The version of the Postgres client in our docker container was updated from 15 to 16.
This is the root cause of the issue.
I made the following change in my Dockerfile:
&& apt-get install --no-install-recommends -y postgresql-client
to
&& apt-get install --no-install-recommends -y postgresql-client-15 \
Also, I made some additional changes in the forked version of backup addon, like:
- log.error() instead of log.debug() if there are any issues with backup
- in the first place we are dumping DB, because issues will likely be with it, but not with the filestore backup.
Side notes:
- if Backup Type is "Dump", then
.dump
backup made just fine (it usesodoo.tools.exec_pg_command_pipe
instead ofexec_pg_command
) - if make a backup manually in the CLI of a container using pg_dump from PG client 16, then it works just fine
(pg_dump -h 172.17.0.1 -d myDB -U odoo --no-owner --file=/tmp/dump.sql
)
Same problem on v.16, but all logs are fine. This module works fine on all my instances except one, that have the same configuration as worked ones, but generate 0-bytes .zip archives in manual and auto mode. I've tried to reinstall this module many times, down/up my container, have checked read/write to /tmp and /mnt, but result is the same.
I have just need to rebuild docker container, and this problem were gone.
Seems like one of the component in docker-container was updated and not working properly, then were fixed by developer, but I'm not sure.