Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ggowins

Pages: [1]
1
Sorry for the delay.  I got sidetracked and wasn't able to come back to this until today.  I ran the commands on the upgraded server, created a new backup, and it successfully restored onto the DR system.  Thanks!

2
They should be in /var/lib/zentyal/conf/backups/


3
Hi Daniel,

Thanks for the information.  Just to be clear, I run the specified commands from the upgrade script on my main system, do a backup, then also run the scripts on the disaster recovery machine, then do the restore?  I'll give this a try over the weekend.

4
Hi Daniel,

Yes, this was an upgrade from 6.2. 

5
So in the commit you linked, I removed the trailing slash from the URLs in lines 84 and 85 in Samba.pm.  That got rid of the double slash in the path in the error.  But I'm continuing to get the error of no such file or directory.  There isn't a bind-dns subdir in /var/lib/samba.  I tried to manually create the whole path of bind-dns/dns/sam.ldb.d there, but it gets erased at some point of the restore process.  When I get the error in the restore, those subdirs do not exist anymore.

6
Just tried it again.  Both running system and backup are on 7.0.1 for Domain Controller.  Made a new backup, went to restore, and got the same message as I posted. 

7
As part of my testing, I do a backup of my live system, then try to restore to a standby system in case of a need for disaster recovery.   I made a post-upgrade backup of my 7.0 live system, and installed 7.0 from the ISO on a standby system.

However, I'm getting an error when it gets to the Samba restore part.   In the log it appears that there is an extra / being put into the path, but I can't figure out where that is coming from.  Here is the output of the zentyal.log file for the error:

Quote
2021/03/17 18:44:50 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command ln /var/lib/samba/private//sam.ldb.d/DC*FORESTDNSZONES* /var/lib/samba/bind-dns//dns/sam.ldb.d/ failed.
Error output: ln: target '/var/lib/samba/bind-dns//dns/sam.ldb.d/' is not a directory: No such file or directory

Command output: .
Exit value: 1 at root command ln /var/lib/samba/private//sam.ldb.d/DC*FORESTDNSZONES* /var/lib/samba/bind-dns//dns/sam.ldb.d/ failed.
Error output: ln: target '/var/lib/samba/bind-dns//dns/sam.ldb.d/' is not a directory: No such file or directory

Command output: .
Exit value: 1 at /usr/share/perl5/EBox/Sudo.pm line 240
EBox::Sudo::_rootError('/usr/bin/sudo -p sudo: /var/lib/zentyal/tmp/jwJ1aMsNvC.cmd 2> /var/lib/zentyal/tmp/stderr', 'ln /var/lib/samba/private//sam.ldb.d/DC*FORESTDNSZONES* /var/lib/samba/bind-dns//dns/sam.ldb.d/', 256, 'ARRAY(0x557b12d63088)', 'ARRAY(0x557b0de880a8)') called at /usr/share/perl5/EBox/Sudo.pm line 210
EBox::Sudo::_root(1, 'ln /var/lib/samba/private//sam.ldb.d/DC*FORESTDNSZONES* /var/lib/samba/bind-dns//dns/sam.ldb.d/') called at /usr/share/perl5/EBox/Sudo.pm line 153
EBox::Sudo::root('ln /var/lib/samba/private//sam.ldb.d/DC*FORESTDNSZONES* /var/lib/samba/bind-dns//dns/sam.ldb.d/') called at /usr/share/perl5/EBox/Samba.pm line 1954
EBox::Samba::restoreConfig('EBox::Samba=HASH(0x557b1179d9c8)', '/var/lib/zentyal/tmp//backup.bLiQqo/eboxbackup/samba.bak', 'installMissing', 0, 'progress', 'EBox::ProgressIndicator=HASH(0x557b10274448)', 'forceZentyalVersion', 0, 'continueOnModuleFail', 0, 'forceDependencies', 0, 'modsToExclude', 'ARRAY(0x557b0c978cb8)', 'dataRestore', 1, 'revokeAllOnModuleFail', 1, 'deleteBackup', 0) called at /usr/share/perl5/EBox/Module/Config.pm line 108
EBox::Module::Config::aroundRestoreConfig('EBox::Samba=HASH(0x557b1179d9c8)', '/var/lib/zentyal/tmp//backup.bLiQqo/eboxbackup/samba.bak', 'installMissing', 0, 'progress', 'EBox::ProgressIndicator=HASH(0x557b10274448)', 'forceZentyalVersion', 0, 'continueOnModuleFail', 0, 'forceDependencies', 0, 'modsToExclude', 'ARRAY(0x557b0c978cb8)', 'dataRestore', 1, 'revokeAllOnModuleFail', 1, 'deleteBackup', 0) called at /usr/share/perl5/EBox/Module/Base.pm line 420
EBox::Module::Base::restoreBackup('EBox::Samba=HASH(0x557b1179d9c8)', '/var/lib/zentyal/tmp//backup.bLiQqo/eboxbackup', 'forceZentyalVersion', 0, 'installMissing', 0, 'progress', 'EBox::ProgressIndicator=HASH(0x557b10274448)', 'modsToExclude', 'ARRAY(0x557b0c978cb8)', 'continueOnModuleFail', 0, 'forceDependencies', 0, 'dataRestore', 1, 'revokeAllOnModuleFail', 1, 'deleteBackup', 0) called at /usr/share/perl5/EBox/Backup.pm line 1338
EBox::Backup::_restoreModule('EBox::Backup', 'EBox::Samba=HASH(0x557b1179d9c8)', '/var/lib/zentyal/tmp//backup.bLiQqo', 'HASH(0x557b100fcd88)') called at /usr/share/perl5/EBox/Backup.pm line 1190
eval {...} at /usr/share/perl5/EBox/Backup.pm line 1189
eval {...} at /usr/share/perl5/EBox/Backup.pm line 1186
eval {...} at /usr/share/perl5/EBox/Backup.pm line 1164
EBox::Backup::restoreBackup('EBox::Backup', '/var/lib/zentyal/tmp/path', 'dataRestore', 1, 'revokeAllOnModuleFail', 1, 'installMissing', 0, 'forceZentyalVersion', 0, 'progress', 'EBox::ProgressIndicator=HASH(0x557b10274448)', 'forceDependencies', 0, 'continueOnModuleFail', 0, 'deleteBackup', 0) called at /usr/share/zentyal/restore-backup line 105
eval {...} at /usr/share/zentyal/restore-backup line 104
2021/03/17 18:44:50 ERROR> Backup.pm:1210 EBox::Backup::restoreBackup - Error while restoring: root command ln /var/lib/samba/private//sam.ldb.d/DC*FORESTDNSZONES* /var/lib/samba/bind-dns//dns/sam.ldb.d/ failed.
Error output: ln: target '/var/lib/samba/bind-dns//dns/sam.ldb.d/' is not a directory: No such file or directory

Command output: .
Exit value: 1

8
Installation and Upgrades / Re: upgrade 6.2 to 7.0 - CA problem
« on: March 17, 2021, 04:29:46 am »
I'm getting this as well post-upgrade.   I chown'd the .rnd to ebox:ebox and that seems to have resolved it. 

9
Installation and Upgrades / Possible to configure IPv6?
« on: March 05, 2017, 05:17:20 am »
Hello all,

I have a 4.2 installation, and was wondering if it is possible to use stubs to configure IPv6.  I realize that none of the GUI tools will work with IPv6, and everything will have to be done command-line.

I seem to have it working from the Zentyal instance itself out to the Internet.  But so far no luck with machines on the LAN segment behind the Zentyal box. 

I've used the interfaces.mas file in the stub directory to manually set the IPv6 addresses for eth0 and eth1.  I was delegated a /56 address, so I used one /64 subnet for the outside eth0 interface and another /64 for the inside.  I configured radvd to send info to the internal network on eth1.   I set sysctl.conf to forward ipv6, and there is a default route going out eth0.   I can successfully run the tests at test-ipv6.com from the browser of the Zentyal machine.  But on any LAN machine if I run a traceroute it ends at the link local address of eth1.

I've check ip6tables, and they are empty at the moment.  I'm sure I'm probably missing something simple and obvious, but I can't for the life of me figure out what it is.  Has anyone else had any luck getting native IPv6 (not tunneling) work when using a Zentyal box for internal machines?

10
Installation and Upgrades / Re: [FIXED] Zentyal 5.0 not booting
« on: March 02, 2017, 10:40:06 pm »
I too am having issues with 5.0 not booting after upgrading from 4.2.  It has happened to me twice now trying to upgrade.  After the upgrade completes, it reboots, then nothing.  I can hold the shift key down to get into the grub menu, but none of the kernels will start.  I don't think it is fsck causing the issue.  Even if it were, the drive is a 64GB SSD so it shouldn't take long to finish.  I let it sit overnight, and nothing ever came up.  Can't ping the machine, so it looks almost like a kernel panic, but there is no signal to the monitor so I can tell for sure.

11
I too am in the same boat.  An older machine (Celeron) just set up to be an AD server.   I see that the source code is available on the Zentyal Git repo for libsamba-perl, but am having all sorts of issues getting it to build.   Hopefully someone else will have better luck.

Another question on this, did the 4.2 install process make a backup of the 4.1 Samba config?  I can't seem to find the files if it did.

Pages: [1]