Topic: Affa is broken - while I fix it, how do you use it?

[vassili]

Hi, team, any news or updates on affa development ?

[ReetP]

Slow as I keep getting interrupted.

I think there is a v4.01 now in smedev but we know it still has some issues.

I think basic backup/restore works but some of the trickier stuff like restore a specific set - which was broken - still has some issues.

Please get a copy and test.

[vassili]

Sure, I will set up some test systems, test and report back the result

Slow as I keep getting interrupted.

I think there is a v4.01 now in smedev but we know it still has some issues.

I think basic backup/restore works but some of the trickier stuff like restore a specific set - which was broken - still has some issues.

Please get a copy and test.

[ReetP]

If you DM or email me your name and an email address I can set you up on my Rocket instance and you can chat to us directly for testing.......

We know you'll find a few bugs and it will be easier to explain to you there how and what to test methodically.

[Gary Douglas]

Way back on rocket one of my first comments was 'affa --rise is god'. I have tested and used AFFA4 extensively since then and this is still true. The RPM affa-4.0-1 in SMETEST has one small issue that affa --rise does not use hardlinks. It will still RISE if you have sufficient disk space. An earlier version 4.0-1a does RISE using hardlinks. The difference between 4.0-1a and SMETEST 4.0-1 is 4.0-1 has line 3852 commented, replaced with line 3853. 4.0-1a uses "--link-dest=$archive$src",
3852            # "--link-dest=$archive$src",
3853            ( $linkDest ? "--link-dest='$job{'RootDir'}/$jobname/$linkDest'" : '' ),
There may be other issues with affa4, there are many variables, undo RISE fails, restore old archive works but not tested recently.
My use and testing AFFA4 now includes RISE of several production servers, and other various purposes, i.e. saving my bacon.
An important Include if using i.e. MariaDB105 is; Include=/var/opt/rh/rh-mariadb105/lib/mysql
My sincere thanks to the dev team... my other gods!

[ReetP]

It's my fault - just overwhelmed with life   

I know where the issue is but it's linked to something else.

Just need to get my head back into it.

I haven't forgotten. Just time......

[Gary Douglas]

not your fault !!! Affa just saved my bacon to fix a 4month old problem, and now going to look at another nasty one which can't be fixed on the live box. Sync a copy minus data to a VM here, rise, then play.

[ReetP]

Thanks but I still feel guilty.

I haven't forgotten it........

[Gary Douglas]

thanks John. my other issue now fixed thanks to rise and play, in fact issue had disappeared on VM so updated live box

[bugzilla]

So following on from the thread opened by Gary:

https://forums.koozali.org/index.php/topic,54879.0.html

A recent update to rsync that fixed a number of security holes in it broke Affa backup.

For anyone in ~Aug 2024, with SMEServer 10, who accidentally ran "yum update" ...


I test this by having two terminals open - one ssh'd to the affa server, the other ssh'd to the production server.
On the production server;

Code: [Select]

watch -n1 "ps aux|grep rsync"

On the affa server;

Code: [Select]

affa --run my_server_job

If the rsync appears on the production server, affa at least started. If it goes away in about 4 seconds, something crashed it, check your logs to see more info

To see if its the bad rsync version that is tripping up affa ...

First, confirm you have the bad rsync version;

Code: [Select]

rpm -qa|grep rsync
rsync-3.1.2-12.el7.x86_64

We are looking at the number after "3.1.2-"
"12" is bad. "11" is bad. "10" is good.

If you have 12 ...

Code: [Select]

yum downgrade rsync
This gets  you back to 11 ( rsync-3.1.2-11.el7_9.x86_64 )

Then downgrade again;

Code: [Select]

yum downgrade rsync

This should get you back to v10; confirm this;

Code: [Select]

rpm -qa|grep rsync
rsync-3.1.2-10.el7.x86_64

Now you should be good to go.

Now ... to stop it happening again;

Code: [Select]

yum install yum-plugin-versionlock
yum versionlock rsync-*

# check this at any time ...
yum versionlock status
# or
cat /etc/yum/pluginconf.d/versionlock.list

"yum update" will also warn you each time you run it that versionlock is holding a/some packages, and also remind you of the command to see those packages. Very handy!
D