Birger Krägelin - Tue, 2018/12/18 - 20:01

Just checked all my servers. One of them (test installation) did not run tklbam-backup since some days.

I get the following errors:

Traceback (most recent call last):
  File "/usr/bin/tklbam-backup", line 510, in <module>
    main()
  File "/usr/bin/tklbam-backup", line 443, in main
    opt_resume, True, dump_path if dump_path else "/")
  File "/usr/lib/tklbam/backup.py", line 238, in __init__
    backup_conf.tofile(extras_paths.backup_conf)
  File "/usr/lib/tklbam/backup.py", line 81, in tofile
    simplejson.dump(dict(self), file(path, "w"))
IOError: [Errno 2] No such file or directory: '/TKLBAM/backup-conf'

Is there any way to get it working again?

Just to run tklbam-backup and do tklbam-restore to a new 15.1 system.

Thanks,
Birger
 

Forum: 
Support
Tags: 
tklbam
Jeremy Davis's picture

Jeremy Davis - Tue, 2018/12/18 - 21:30

I'm only guessing, but it seems that it may be trying to resume an interrupted backup, but it can't find one of the files.

Probably the first thing to do is to make sure that you have the latest version of TKLBAM (you probably do, but just in case):

apt update
apt install tklbam

Then I suggest you try forcing it to do a new full backup manually. You can do that like this:

tklbam-backup --disable-resume --full-backup now

Hopefully that should get you going. Please let me know how you go.

Birger Krägelin - Wed, 2018/12/19 - 09:24

this hint took me to the solution...

Some time ago I changed my database configuration. I now have a dedicated DB cluster.
Turnkey MySQL as MariaDB Galera Cluster ;-)

So I disabled MySQL and installed pen-proxy and socat to redirect localhost DB access to my new cluster.

Running tklbam-backup in the foreground gave additional output:

Serializing MySQL database to /TKLBAM/myfs
------------------------------------------
Traceback (most recent call last):
  File "/usr/bin/tklbam-backup", line 510, in <module>
    main()
 

tklbam-backup throws this traceback error, if it tries to backup databases but there is no mysql daemon.

--skip-database does the trick.

Thumbs up for your work!!!
Birger

Jeremy Davis's picture

Jeremy Davis - Wed, 2018/12/19 - 23:55

Great to hear that my input helped you find the issue (despite my guess being totally off the mark).

I'm guessing that you adjusted the cron job to '--skip-database' to get your automated backups working again? That's certainly an effective way of doing it, although FWIW another alternative would be to add an override (to the overrides file: '/etc/tklbam/overrides'). Although OTTOMH I'm not 100% sure what you would need to do to skip all databases?! And the docs aren't explicit on that count either. Perhaps simply '-mysql:'? When I get a chance, I might test it out and add an explicit note to the docs.

Add new comment