Yes it is.
You should simply set enabled=1 under [nethserver-testing] section.
Take your time, there is no rush: in the meanwhile we are testing the fix internally ![]()
Yes it is.
You should simply set enabled=1 under [nethserver-testing] section.
Take your time, there is no rush: in the meanwhile we are testing the fix internally ![]()
Thanks form reporting it. I hit the same problem today, and this confirm my thoughts. I’ll work on this tomorrow!
It could be a firewall cfg issue. Run
shorewall stop
Yes, you’re correct, sshd was not dead, stopping shorewall gave me access with putty from another machine.
@davidep
fyi, I just got an email from this server that a backup completed… so I logged into the web gui… successfully, though the domain, users, etc, are broken, some modules were restored like nextcloud, others not like the php scl… maybe that repo wasn’t restored, perhaps killing shorewall gave access to the admin-httpd. That also means I have to remember to get a good backup before I try another restore test.
A new set of RPMs is ready for testing! /cc @quality_team
Two issues should now be fixed
Note that to restore the configuration, the backup must be fixed, too! In other words, existing cfg backups are incomplete in systems where nethserver-samba is not installed. The complete procedure is
Then in another system
To update from testing run
yum --enablerepo=nethserver-testing update
We’re fixing another bug affecting restore-config when network cards are different. @giacomo is investigating it! FIXED See NethServer/nethserver-base#75
Just to clarity, I have a populated snapshot, it’s an ad, with nextcloud, etc… therefore, I do not need to install testing packages into that before a backup… correct?
You need the fix before backup-config if nethserver-samba is not installed.
See… this was bothering me… now I know why, I’m not entirely stupid… just slow… I was thinking that ad dc was samba… but it’s nethserver-dc, and since I don’t have file server installed in that vm, nethserver-samba is not installed.
The bug is finally closed, maybe we will find some corner case in the future, but for now everything seem to work as expected.
To fix the issue we had to update 6 packages!
I would really say my thank you to @fasttech for this hunt and the hard (and boring testing)!
Big thank you also to @filippo_carletti for testing in a complex scenario, and of course thank you to @davidep who found a fix and implemented the working code!