similar to: dovecot[1511]: auth-worker: Fatal: master: service(auth-worker): child 17009 killed with signal 11

Displaying 20 results from an estimated 1000 matches similar to: "dovecot[1511]: auth-worker: Fatal: master: service(auth-worker): child 17009 killed with signal 11"

2019 Feb 28
0
dovecot[1511]: auth-worker: Fatal: master: service(auth-worker): child 17009 killed with signal 11
Is is possible for you to try https://github.com/dovecot/core/commit/3c5101ffdd2a8115e03ed7180d53578765dea4c9.patch Aki > On 28 February 2019 18:03 Patrik via dovecot <dovecot at dovecot.org> wrote: > > > This bug report is similar to this issue: > https://www.dovecot.org/list/dovecot/2017-May/108116.html (https://www.dovecot.org/list/dovecot/2017-May/108116.html) >
2019 Aug 05
9
samba dlz. bind9 nslookup is wrong
On 05/08/2019 11:53, Patrik wrote: > the ?? file "/etc/bind/zones/enp1s0f3/patrikx3.com > <http://patrikx3.com/>"; are my domain names A, AAAA, CNAME-s, that is > where i store then, there is know AD records at all. it is all DLZ. > *_ > _* If 'patrikx3.com' is a registered dns domain name, then you should have used a subdomain of this for the AD dns
2019 Aug 05
6
samba dlz. bind9 nslookup is wrong
... From your output below.. >> Uncomment only single database line, depending on your BIND version << Then tell uss, why are 3 lines uncommented? I suggest, run : https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Anonimize it where needed, and show me your server setup. Greetz, Louis > -----Oorspronkelijk bericht----- > Van:
2019 Aug 05
5
samba dlz. bind9 nslookup is wrong
On 05/08/2019 09:55, Patrik via samba wrote: > the dig is wrong as well, it adds an additional ip address, which i have > not request to use other interfaces: > root at server:/# dig p3x-dc.patrikx3.com > Patrik, I have told you what your problem is, refusing to accept that you have setup Bind9 incorrectly is no reason for opening a new thread. Just in case you missed it, or
2019 Aug 03
2
Samba generating wrong ipv6 and ipv4 address
Hey! How are you? I have two interfaces (192.168.78.20 / *2001:470:1f1b:5b3:21b:21ff:fea6:ce93* and 192.168.81.20 / *2001:470:1f1b:5b5:21b:21ff:fea6:ce92*) I have interfaces disabled i mean that i bind on everything on samba ac-dc... What here is what is weird, (via bind9 DLZ i am using it and is working), but on my clients i am getting some weird ipv6 addresses: patrikx3 at bitang:~$ ping
2019 Aug 05
2
samba dlz. bind9 nslookup is wrong
samba generates an unknown ip4 and ip6 address. here is my settings: root at server:/# ifconfig enp1s0f2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.81.20 netmask 255.255.255.0 broadcast 192.168.81.255 inet6 fe80::21b:21ff:fea6:ce92 prefixlen 64 scopeid 0x20<link> inet6 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 prefixlen 64 scopeid
2019 Aug 05
2
samba dlz. bind9 nslookup is wrong
On 05/08/2019 12:50, L.P.H. van Belle via samba wrote: > That is because your resolving setup is wrong. > > You problem starts here. > Checking file: /etc/resolv.conf > > search patrikx3.com > search corifeus.com > search p3x-dc.patrikx3.com > > The first 2 will do nothing, only last will be used that setup. > > You want : > search p3x-dc.patrikx3.com
2019 Aug 05
2
samba dlz. bind9 nslookup is wrong
what is weird is that i have not changed it for about 2 years, only apt update, upgrade. no other change, ipv4 and ipv6 address working correctly. now there is this bug, that i have not changed anything and suddenly, DLZ generates an unknown not connected , working, live ip4 and ip6. and all because it tried an nslookup p3x-dc.patrikx3.com that was the correct for over 2 years. the only thing that
2019 Aug 05
3
samba dlz. bind9 nslookup is wrong
On 05/08/2019 12:33, Patrik wrote: > the patrikx3.com <http://patrikx3.com> is my domain > my AD DC domain is p3x-dc.patrikx3.com <http://p3x-dc.patrikx3.com>, > you can see: > Unless you have done something strange like using 'p3x-dc' as the subdomain of 'patrikx3.com', that isn't your AD dns domain, it the FQDN of your AD DC. Rowland
2019 Aug 03
2
Samba generating wrong ipv6 and ipv4 address
On 03/08/2019 11:17, Patrik wrote: > the problem is that dnsupdate is not working becuase i use dlz. i > cannot use dbsupdate with dnsupdate it fails. > *_ > _* What is 'dbsupdate' ? I can assure you that dnsupdate does work with dlz. I think you need to give us more info. Rowland
2019 Aug 03
2
Samba generating wrong ipv6 and ipv4 address
On 03/08/2019 03:01, Patrik via samba wrote: > My config is this: > # Global parameters > [global] > # bind interfaces only = Yes > # if this is turned on, always perfect > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 > #
2019 Aug 05
6
samba dlz. bind9 nslookup is wrong
On 05/08/2019 10:14, Patrik wrote: > I am not using flatfiles and i using BIND_DLZ it shows in my log and i > do not use flatfiles. BIND_DLZ only. Oh yes you are, you have this in your /etc/bind/named.conf.local : ??? zone "patrikx3.com" { ??????? type master; ??????? file "/etc/bind/zones/enp1s0f3/patrikx3.com"; ??????? include
2019 Aug 05
2
samba dlz. bind9 nslookup is wrong
I suggest, read : https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-1.0.txt https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-1.1-checkup.txt https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-2.0-samba-minimal-ad.txt https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-2.1-samba-minimal-ad-checks.txt Alsmost anything is in the samba
2019 Aug 05
1
samba dlz. bind9 nslookup is wrong
On 05/08/2019 11:54, Patrik wrote: > my problem is that this is a simple config, i have 2 subnets on 1 > server (business? ISP with static ip / home for downloading and > dynamic ip) > *_ > _* No, your problem is that you do not understand AD DNS ;-) Your Samba AD DC is authoritative for the AD dns domain and should only know about the AD domain, it should forward anything
2019 Aug 05
2
samba dlz. bind9 nslookup is wrong
On 05/08/2019 10:29, Patrik wrote: > ok, so i remove that nemd.conf.update, but the rest it looks good? > *_ > _* These are my 'named.conf' files, used since 2012 with only minor changes: /etc/bind/named.conf include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones";
2017 Feb 10
2
/usr/sbin/samba_dnsupdate: ERROR: Record already exist
Thanks so much! I will deal with the user home folders later! *Here is the DNS:* options { directory "/var/cache/bind"; dnssec-validation auto; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { any; }; }; zone "patrikx3.tk" { type master; file "/etc/bind/zones/db.patrikx3.tk"; }; zone "corifeus.tk" { type master; file
2019 Aug 05
1
samba dlz. bind9 nslookup is wrong
but as i shown in my config i use bind9, why do you say i am using BIND9_FLATFILE DNS? root at server:/# cat etc/bind/named.conf.local // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; // the order is important!!!! first internal, then external!!! view "internal-enp1s0f3" { match-clients {
2017 Feb 10
2
/usr/sbin/samba_dnsupdate: ERROR: Record already exist
*Not entirely sure which of your 'named' files the above are in, but youshould remove them, they are your problem.* Where is the named files?? You mean the zone/patrikx3.tk? *You shouldn't have the 'patrikx3' zone in a conf file, it is in AD anddlz will connect Bind to Samba**You shouldn't have any other forward zone in Bind.* How can I add in other in the patrikx3.tk
2019 Aug 03
0
Samba generating wrong ipv6 and ipv4 address
My config is this: # Global parameters [global] # bind interfaces only = Yes # if this is turned on, always perfect # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 # interfaces = lo 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 # if all interfaces
2019 Aug 05
0
samba dlz. bind9 nslookup is wrong
the dig is wrong as well, it adds an additional ip address, which i have not request to use other interfaces: root at server:/# dig p3x-dc.patrikx3.com ; <<>> DiG 9.11.5-P4-5.1-Debian <<>> p3x-dc.patrikx3.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11190 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0,