Messages

1

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 29, 2021, 08:28:09 am »

Hello,

Thanks for the feedback and comments. Zentyal 7.0 is now released, you can find all the information here: https://forum.zentyal.org/index.php/topic,35132.0.html

If you hit any issues, please report them through GitHub https://github.com/zentyal/zentyal/issues

Cheers!

Great! Do I need to do anything apart from apt upgrade to update my Beta installation to full release?

2

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 29, 2021, 08:26:17 am »

The Dynamic DNS Options can be setted on "webmin > DHCP >interface configuration > Dynamic DNS Options". Here you can enable or disable the DDNS.

I have disabled DHCP and the system seems to run properly (the DNS module shows the "Dynamic Domain" enabled though).

Could be your samba service was down when the system tried to update DNS?

Paste here the zentyal.log parts regarding network and samba errors if you need some help.

Cheers!

The samba was definitely running. Seems like the user and key for DDNS were not created because I never enabled DHCP and the option there.

3

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 25, 2021, 11:57:33 am »

Thanks.

Should I still do it when it started working without this? What I did is enable DHCP module and enabled Dynamic DNS in it.. It seems that the problem was using DNS without DHCP - though I am not sure what set the domain to dynamic - it happened on its own.

4

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 22, 2021, 12:16:41 pm »

Got another problem.. Any advice? Not sure what caused this.. I noticed problems when I changed interface address and it did not update in DNS (the realm is dynamic).

Code: [Select]

2021/01/21 16:11:23 INFO> DNS.pm:91 EBox::DNS::appArmorProfiles - Setting DNS apparmor profile
2021/01/21 16:12:01 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command nsupdate -g -t 10 /var/lib/zentyal/tmp/s9lkGpokAt failed.
Error output: tkey query failed: GSSAPI error: Major = Unspecified GSS failure.  Minor code may provide more information, Minor = Cannot contact any KDC for realm 'ZENTYAL.LAN'.

Command output: .
Exit value: 2 at root command nsupdate -g -t 10 /var/lib/zentyal/tmp/s9lkGpokAt failed.


5

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 15, 2021, 12:24:54 pm »

Another bug - cannot create configuration backup using Web interface.

Wanted to attach screenshot but it said that "upload folder is full" - it was small, 45 KB PNG. Here's copy of the error instead:

Code: [Select]

root command tar cf /var/lib/zentyal/conf//eboxbackup.tar -C /var/lib/zentyal/conf//backup.9Gbry1 eboxbackup --preserve-permissions --exclude eboxbackup/files.tgz 2>&1 failed. Error output: Command output: tar: The following options were used after any non-optional arguments in archive create or update mode. These options are positional and affect only arguments that follow them. Please, rearrange them properly. tar: --exclude ‘eboxbackup/files.tgz’ has no effect tar: Exiting with failure status due to previous errors . Exit value: 2

6

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 14, 2021, 03:06:25 pm »

Update: Disabling DNSSEC solved my issue (created modified stub for named.conf.options).

Not sure what is the cause of DNSSEC problem. My installation is on virtual machine (KVM), but has it's dedicated Ethernet (using passthrough) so acts just like ordinary server connected directly to LAN.

7

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 14, 2021, 01:34:17 pm »

Hi all,

The Zentyal Server 7.0 Beta version is now ready for testing. You can download it here:

http://download.zentyal.com/.beta/zentyal-7.0-development-amd64.iso

We are still polishing the Proxy and CA modules (we are aware that there are some minor issues). We are specially interested on receiving your feedback on the Samba module.

You can report any issues & bugs in this thread. All the feedback is much appreciated.

I have issues with DNS when I install AD. Before the initial Zentyal setup, "ping google.com" works (systemd-resolved takes care of the resolution). After installing the DNS in webadmin, same command won't work - "Temporary failure in name resolution".

Resolution of local names (in zentyal domain) seems to work ok.

Code: [Select]

$ dig google.com

; <<>> DiG 9.16.1-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25689
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: e3d826031e80fbfe0100000060003687fe9667feb69104e3 (good)
;; QUESTION SECTION:
;google.com. IN A

;; Query time: 24 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan 14 13:18:15 CET 2021
;; MSG SIZE  rcvd: 67

Interface is configured with DHCP, which has 192.168.1.1 set as both DNS and gateway. Connection to DNS on that host works:

Code: [Select]

nmap -p 53 192.168.1.1
Starting Nmap 7.80 ( https://nmap.org ) at 2021-01-14 13:24 CET
Nmap scan report for 192.168.1.1
Host is up (0.0011s latency).

PORT   STATE SERVICE
53/tcp open  domain

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds

Directing dig @192.168.1.1 works as well.

Adding 192.168.1.1 to Forwarders has no effect.

Code: [Select]

● named.service - BIND Domain Name Server
     Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2021-01-14 13:32:02 CET; 1s ago
       Docs: man:named(8)
   Main PID: 4155 (named)
      Tasks: 26 (limit: 9459)
     Memory: 65.2M
     CGroup: /system.slice/named.service
             └─4155 /usr/sbin/named -f -u bind -4

Jan 14 13:32:03 adc named[4155]: managed-keys-zone: DNSKEY set for zone '.' could not be verified with current keys
Jan 14 13:32:03 adc named[4155]: validating ./NS: no valid signature found
Jan 14 13:32:03 adc named[4155]: validating ./NS: no valid signature found

If any logs or more info helps, I'll be happy to provide it.

8

Installation and Upgrades / Re: Zentyal 7 release date?

« on: January 11, 2021, 05:49:21 pm »

Hi all,

The Zentyal Server 7.0 Beta version is now ready for testing. You can download it here:

http://download.zentyal.com/.beta/zentyal-7.0-development-amd64.iso

We are still polishing the Proxy and CA modules (we are aware that there are some minor issues). We are specially interested on receiving your feedback on the Samba module.

You can report any issues & bugs in this thread. All the feedback is much appreciated.

Will it be possible to keep using beta installation after full release (updating to the official release) or will I have to do fresh installation?

9

Directory and Authentication / up-to-date Samba on Zentyal?

« on: December 03, 2020, 02:15:54 pm »

Is there a reasonable way to run more up-to-date Samba on Zentyal? the LTS version is very old..

It would probably mean importing some custom repository and web admin might not work at all..

10

Directory and Authentication / Re: Folder Redirection to limit profile size

« on: October 26, 2019, 08:31:54 am »

Just a quick note: keeping a lot of documents on the desktop is a very dangerous habit.

Apart from the sync + roaming profiles issue, the documents can get often damaged and lost in case of profile corruption (and slow logins/logouts may cause corruption if the user does not wait for the process to complete correctly).

One workaround that I have used for my users is creating links on the desktop to some local folder elsewhere: if they save stuff using that "desktop folder" they are actually saving in C:/Documents or other, or on the file server if they are not supposed to save on the local disk.

Yeah, I did that for principal - moved stuff to network drive and created links.. She doesn't care as long as the links have same names as the folders

But it's not a permanent, automatic solution..

11

Installation and Upgrades / New systemd update conflicts with upstart

« on: October 20, 2019, 04:18:13 pm »

On my Ubuntu Server 18.04 (originally installed as 14.04 and upgraded to 18.04 few months ago), systemd update has now been "kept back".

I looked at it in aptitude and it says that dependencies are not satisfied:

• systemd(upgrade, 237-3ubuntu10.29 -> 237-3ubuntu10.31) conflicts with upstart

I know Ubuntu used to use upstart but have no idea if my installation still uses it or if it's safe to remove it. It's a production server. I can have down time only during weekend. I would very much like to avoid breaking it by messing with the boot process.

What should I do and how?

12

Directory and Authentication / Re: Folder Redirection to limit profile size

« on: October 20, 2019, 04:16:34 pm »

Windows 10 roaming profiles has lots of issues. It isn't a Samba4 problem (Some Windows Server seems to have this problem too).

If you enables roaming profiles only as consequence of  backup reasons, I think that you could simply disable roaming profiles as far as you would need to configure a system backup able to manage the local folders of the user on each one of the client machines, isn't it?.

I'll try to configure a folder redirection and I will give you my results in a few days.

Cheers!

How did it go?

As for the reason, it's also handy that users have same setting and stuff across different machines. The policy is to use network share for storing stuff but you know how well users actually follow instructions..

13

Directory and Authentication / Re: Folder Redirection to limit profile size

« on: August 22, 2019, 06:58:04 pm »

No one?   

14

Directory and Authentication / Folder Redirection to limit profile size

« on: July 23, 2019, 10:58:39 pm »

My users tend to store lot of things on Desktop and in User Shell folders (documents, etc.). For backup reasons, I have roaming profiles enabled so all these files are saved on server as well.

Problem is that these profiles often have size of several gigabytes and the log in and log out times are very long (minutes, sometimes even more than 10 minutes). I wanted to do Folder redirection of large folders to their home shares as per https://wiki.samba.org/index.php/Configuring_Windows_Profile_Folder_Redirections. Sadly, this does not work well on my Windows 10 clients. Values in registry get changed to correct ones, but doesn't really work. Some folders (desktop and AppData) did get redirected, but clicking on Documents in Explorer still lead to old C:\Users\xx\Documents location.

Any experiences/tips on what to do about this? Feel free to offer different solution than Folder redirection. Thanks.