Messages

1

Other modules / Re: I did the 6.1 upgrade now anything added to DNS won't resolve

« on: November 24, 2019, 01:49:39 pm »

Thank you. I can confirm that I built a 6.0.1 VM and restored it from the backup I did before I clicked the upgrade button (fortunately) and then added the new entries. That all worked so as an experiment I upgraded the VM to 6.1. Upgrade worked without a problem, the entries I added before the upgrade resolve but anything else added doesn't resolve. It's definitely a 6.1 problem but I can't find anything helpful in the logs e.g. theres no "Unable to write /var/lib/bind/db.1.168.192" or anything that says "There was an error".

I'm now running a VM with 6.0.1 until someone confirms and fixes this. Or tells me what I'm doing wrong (for example, 6.1 might have new extra steps that are not obvious).

2

Other modules / I did the 6.1 upgrade now anything added to DNS won't resolve

« on: November 19, 2019, 11:20:52 pm »

I decided to do the 6.1 upgrade when the button appeared and the upgrade seemed to work fine. Everything appeared to have come up as it should.

However, I've discovered that if I add something to DNS in the same way I've done for loads of other devices I can't resolve it. To be clear, anything that was already on my server still works

Code: [Select]

dig +short odroid1.23wwc.io @192.168.6.1                           22:09:52
192.168.1.91
But anything added since the upgrade doesn't work

Code: [Select]

dig pdu1.23wwc.io @192.168.6.1                                     22:11:09

; <<>> DiG 9.10.6 <<>> pdu1.23wwc.io @192.168.6.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40328
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pdu1.23wwc.io. IN A

;; AUTHORITY SECTION:
23wwc.io. 3600 IN SOA zentyal.23wwc.io. hostmaster.23wwc.io. 2160 900 600 86400 3600

;; Query time: 82 msec
;; SERVER: 192.168.6.1#53(192.168.6.1)
;; WHEN: Tue Nov 19 22:11:15 GMT 2019
;; MSG SIZE  rcvd: 97

I can't see anything relevant in any log files so I went and did a bit of digging and found this (PDU1 is 192.168.1.31)

Code: [Select]

cat /var/lib/bind/db.1.168.192
$ORIGIN .
$TTL 259200 ; 3 days
1.168.192.in-addr.arpa IN SOA zentyal.23wwc.io. hostmaster.23wwc.io. (
2019111628 ; serial
28800      ; refresh (8 hours)
7200       ; retry (2 hours)
2419200    ; expire (4 weeks)
86400      ; minimum (1 day)
)
NS zentyal.23wwc.io.
$ORIGIN 1.168.192.in-addr.arpa.
1 PTR usg.23wwc.io.
10 PTR pve.23wwc.io.
12 PTR diskstation.23wwc.io.
13 PTR bigserver.23wwc.io.
14 PTR qnap.23wwc.io.
16 PTR netgear.23wwc.io.
196 PTR ups.23wwc.io.
25 PTR zabbix.23wwc.io.
26 PTR librenms.23wwc.io.
$TTL 3600 ; 1 hour
29 PTR minecraft.23wwc.io.
$TTL 259200 ; 3 days
3 PTR garageswitch.23wwc.io.
$TTL 3600 ; 1 hour
34 PTR docker.23wwc.io.
$TTL 259200 ; 3 days
4 PTR lrswitch.23wwc.io.
5 PTR loftswitch.23wwc.io.
$TTL 3600 ; 1 hour
51 PTR HS100.23wwc.io.
52 PTR HS100.23wwc.io.
$TTL 259200 ; 3 days
7 PTR lrap.23wwc.io.
8 PTR upstairsap.23wwc.io.
$TTL 3600 ; 1 hour
91 PTR odroid1.23wwc.io.
92 PTR odroid2.23wwc.io.
93 PTR odroid3.23wwc.io.

So these records haven't been created even though they're visible in the Admin UI


Anyone know what's going on?

Thanks

Steve

3

Directory and Authentication / Re: Struggling with LDAP authentication

« on: July 06, 2019, 12:50:32 am »

I read your response and I thought "That's a bit silly - it means Zentyal has LDAP in the interface but you can't query the LDAP using standard LDAP tools". But I did a bit of Googling and figured out how ldbsearch works and I found this

CN=Administrator Administrator,CN=Users,DC=23wwc,DC=io


The admin account's DN is 'Administrator Administrator'. And now, using that account, I can do queries. I would never have guessed that so thank you for pointing me in the right direction.

Steve

4

Directory and Authentication / Struggling with LDAP authentication

« on: July 03, 2019, 08:53:54 am »

Hi all,

I've spent way too much time trying to understand what I'm doing wrong. I have searched these forums and Google in general, tried all the suggestions and still can't figure out which bit is incorrect. I'm using an up-to-date "Zentyal Development Server 6.0"

Just to clarify it's not anything "obvious", I can:

○ → ssh steve@zentyal.23wwc.io
steve@zentyal.23wwc.io's password:
Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-54-generic x86_64)


And I can even

○ → kinit steve@23WWC.IO
steve@23WWC.IO's password:

○ → klist
Credentials cache: API:2A75BED1-1C30-4585-991E-6681BEC9CB99
        Principal: steve@23WWC.IO

  Issued                Expires               Principal
Jul  3 07:30:46 2019  Jul  3 17:30:43 2019  krbtgt/23WWC.IO@23WWC.IO

But no matter what I try, doing anything with LDAP fails

○ → ldapsearch -h zentyal.23wwc.io  -b dc=23wwc,dc=io -D CN=steve,CN=Users,DC=23wwc,DC=io -W
Enter LDAP Password:
ldap_bind: Invalid credentials (49)
   additional info: 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1

And the Zentyal Samba logs show

Auth: [LDAP,simple bind/TLS] user [(null)]\[CN=steve,CN=Users,DC=23wwc,DC=io] at [Wed, 03 Jul 2019 07:35:10.123764 BST] with [Plaintext] status [NT_STATUS_NO_SUCH_USER] workstation [(null)] remote host [ipv4:192.168.3.50:63405] mapped to [(null)]\[(null)]. local host [ipv4:192.168.2.1:389]



My main path of testing has been that the DN CN=steve,CN=Users,DC=23wwc,DC=io is wrong so I've tried 23WWC/Steve and uid= and samAccountName= and other variations but I get the same result. I did notice in my searching that in screenshots for 5.0 the LDAP page used to display the bind user and bind password. In 6.0 it only shows the base DN. This also made me wonder if there's another step I have to do to "activate" LDAP

Can anyone point out what I'm missing or doing wrong?

Thanks

Steve

5

Installation and Upgrades / Re: Repeatable networking problem after apt update on 6.0

« on: June 08, 2019, 11:54:23 pm »

I've tried both. I can't repeat it if I install Zentyal on a fresh Ubuntu 18.04 install. This only happens on installs from the ISO.

6

Installation and Upgrades / Re: Repeatable networking problem after apt update on 6.0

« on: May 31, 2019, 09:49:03 am »

Hi,

Thanks for your reply but this isn't what is happening. The machine I'm setting it up on has one network interface. It works until an apt upgrade is performed whether I do it or it's done through the GUI. Upon restart /etc/network/interfaces is replaced with

# ifupdown has been replaced by netplan(5) on this system.  See
# /etc/netplan for current configuration.
# To re-enable ifupdown on this system, you can run:
#    sudo apt install ifupdown

But netplan isn't installed. just the default YAML file. For clarity, editing /etc/network/interfaces to put a network definition in doesn't help as I cant restart networking because the service has been moved. And because this has happened the computer doesn't even know where 127.0.0.1 is so I can't make changes locally through anything other than the command line.

This appears to be an apt manifest error.

7

Installation and Upgrades / Repeatable networking problem after apt update on 6.0

« on: May 30, 2019, 11:51:43 am »

Hi,

I've been having problems with installing Zentyal 6.0 and then performing an apt upgrade. I have tried this on an i5 machine and a couple of VMs and get the same result every time.

1) Install Zentyal
2) Go through the initial setup
3) Run

Code: [Select]

sudo apt update4) Run

Code: [Select]

sudo apt upgrade
Result:

Network configuration disappears and a /etc/netplan/01-netcfg.yaml appears but netplan isn't installed

I've searched the forums and found https://forum.zentyal.org/index.php/topic,32523.msg109278.html#msg109278 that might be the same problem but it's partly in Russian and the given fix - apt purge ubuntu-minimal - doesn't work.

Because I've lost the network connection I can't easily copy and paste logs to this post. apt/history.log does say it's installed netplan.io

Anyone know why this keeps happening? Not upgrading packages seems to be the only fix.