search for: 60999

Displaying 20 results from an estimated 21 matches for "60999".

Did you mean: 0999
2018 Jul 24
2
Bad zone problem after join, seize, demote
...dns service work again. Jul 24 08:19:21 dc4 named[1526]: loading configuration from '/etc/bind /named.conf' Jul 24 08:19:21 dc4 named[1526]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 24 08:19:21 dc4 named[1526]: using default UDP/IPv4 port range: [32768, 60999] Jul 24 08:19:21 dc4 named[1526]: using default UDP/IPv6 port range: [32768, 60999] Jul 24 08:19:21 dc4 named[1526]: listening on IPv6 interfaces, port 53 Jul 24 08:19:21 dc4 named[1526]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 24 08:19:21 dc4 named[1526]: listening on IPv4 interface enp...
2018 Jul 24
0
Bad zone problem after join, seize, demote
...t; Jul 24 08:19:21 dc4 named[1526]: loading configuration from > '/etc/bind /named.conf' > Jul 24 08:19:21 dc4 named[1526]: reading built-in trusted keys from > file '/etc/bind/bind.keys' > Jul 24 08:19:21 dc4 named[1526]: using default UDP/IPv4 port range: > [32768, 60999] > Jul 24 08:19:21 dc4 named[1526]: using default UDP/IPv6 port range: > [32768, 60999] > Jul 24 08:19:21 dc4 named[1526]: listening on IPv6 interfaces, port 53 > Jul 24 08:19:21 dc4 named[1526]: listening on IPv4 interface lo, > 127.0.0.1#53 > Jul 24 08:19:21 dc4 named[1526]: l...
2017 Jun 15
2
gluster peer probe failing
Thanks, but my current settings are: net.ipv4.ip_local_reserved_ports = 30000-32767 net.ipv4.ip_local_port_range = 32768 60999 meaning the reserved ports are already in the short int range, so maybe I misunderstood something? or is it a different issue? From: Atin Mukherjee [mailto:amukherj at redhat.com] Sent: Thursday, June 15, 2017 10:56 AM To: Guy Cukierman <guyc at elminda.com> Cc: gluster-users at gluster.org...
2016 Nov 24
1
samba_dnsupdate --verbose --all-names fails with kinit RuntimeError
...P AS (type 9) DB not available > Nov 24 11:36:51 addc01 named[30541]: GeoIP Domain (type 11) DB not > available > Nov 24 11:36:51 addc01 named[30541]: GeoIP NetSpeed (type 10) DB not > available > Nov 24 11:36:51 addc01 named[30541]: using default UDP/IPv4 port > range: [32768, 60999] > Nov 24 11:36:51 addc01 named[30541]: using default UDP/IPv6 port > range: [32768, 60999] > Nov 24 11:36:51 addc01 named[30541]: listening on IPv6 interfaces, port 53 > Nov 24 11:36:51 addc01 named[30541]: listening on IPv4 interface lo, > 127.0.0.1#53 > Nov 24 11:36:51 addc01...
2017 Jun 15
0
gluster peer probe failing
...urav, he is the author of the patch, can you please comment here? On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > Thanks, but my current settings are: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > net.ipv4.ip_local_port_range = 32768 60999 > > meaning the reserved ports are already in the short int range, so maybe I > misunderstood something? or is it a different issue? > > > > *From:* Atin Mukherjee [mailto:amukherj at redhat.com] > *Sent:* Thursday, June 15, 2017 10:56 AM > *To:* Guy Cukierman <guyc at...
2017 Jun 15
0
gluster peer probe failing
https://review.gluster.org/#/c/17494/ will it and the next update of 3.10 should have this fix. If sysctl net.ipv4.ip_local_reserved_ports has any value > short int range then this would be a problem with the current version. Would you be able to reset the reserved ports temporarily to get this going? On Wed, Jun 14, 2017 at 8:32 PM, Guy Cukierman <guyc at elminda.com> wrote: >
2018 Mar 15
0
DNS Updates fail with dns_tkey_gssnegotiate: TKEY is unacceptable
...566 GeoIP Org (type 5) DB not available 15-Mar-2018 12:29:13.566 GeoIP AS (type 9) DB not available 15-Mar-2018 12:29:13.566 GeoIP Domain (type 11) DB not available 15-Mar-2018 12:29:13.566 GeoIP NetSpeed (type 10) DB not available 15-Mar-2018 12:29:13.566 using default UDP/IPv4 port range: [32768, 60999] 15-Mar-2018 12:29:13.566 using default UDP/IPv6 port range: [32768, 60999] 15-Mar-2018 12:29:13.566 listening on IPv4 interface lo, 127.0.0.1#53 15-Mar-2018 12:29:13.567 listening on IPv4 interface enp0s3, 192.168.2.16#53 15-Mar-2018 12:29:13.567 generating session key for dynamic DNS 15-Mar-2018...
2020 Sep 30
6
Bind9 issue
Rowland, To answer you first, my "example.com" registered host is a wildcat " *. example.com". Everything example.com returns my external ip address. Both bind9 and samba are running. Might add your "options" but for now, solving my problem, first. Louis, your answer in a few minutes. On Wed, Sep 30, 2020 at 8:09 AM Rowland penny via samba < samba at
2017 Jan 26
3
CentOS 7 install on one RAID 1 [not-so-SOLVED]
In article <1485416344.2047.1.camel at biggs.org.uk>, Pete Biggs <pete at biggs.org.uk> wrote: > > > > > If you are using RAID 1 kernel mirroring, you can do that with /boot too, > > and Grub finds the kernel just fine. I've done it many times: > > > > > Hmm, OK. I wonder why anaconda doesn't do it then. > > Reading various
2013 Jan 31
0
samba4 as DC problems
...org Jan 31 09:25:48 EM-DC named[1481]: client 192.168.7.20#55001: request has invalid signature: TSIG 1136-ms-7.1-52ef.9f4ed036-6b6f-11e2-31a7-8c89a5ffcfe7: t$ Jan 31 09:26:53 EM-DC named[1481]: samba_dlz: starting transaction on zone em.org Jan 31 09:26:53 EM-DC named[1481]: client 192.168.7.13#60999: update 'em.org/IN' denied Jan 31 09:26:53 EM-DC named[1481]: samba_dlz: cancelling transaction on zone em.org Second question is about randomly appearing in the log message: ???: Jan 31 09:29:34 EM-DC smbd[2029]: [2013/01/31 09:29:34.640810, 0] ../source4/lib/messaging/messaging.c:633(i...
2017 Jun 16
2
gluster peer probe failing
...can you please comment here? > > > On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > >> Thanks, but my current settings are: >> >> net.ipv4.ip_local_reserved_ports = 30000-32767 >> >> net.ipv4.ip_local_port_range = 32768 60999 >> >> meaning the reserved ports are already in the short int range, so maybe I >> misunderstood something? or is it a different issue? >> >> >> >> *From:* Atin Mukherjee [mailto:amukherj at redhat.com] >> *Sent:* Thursday, June 15, 2017 10:56 AM >...
2021 Nov 29
1
Gluster 10 used ports
Hi all, Over the years I have been using the same ports in my firewall for gluster 49152-49251 ( I know a bit too many ports but local network with limited access) Today I upgraded from version 9 to version 10 and it finally went well until I ran: gluster volume heal my-vol info summary I got the answer: Status: Transport endpoint is not connected I realized that glusterfsd was using 50000+
2020 Oct 01
1
Bind9 issue
...> > Sep 30 07:19:21 dtdc1 named[395]: GeoIP Domain (type 11) DB > not available > > > > Sep 30 07:19:21 dtdc1 named[395]: GeoIP NetSpeed (type 10) > DB not available > > > > Sep 30 07:19:21 dtdc1 named[395]: using default UDP/IPv4 port range: > > [32768, 60999] > > > > Sep 30 07:19:21 dtdc1 named[395]: using default UDP/IPv6 port range: > > [32768, 60999] > > > > Sep 30 07:19:21 dtdc1 named[395]: listening on IPv4 interface lo, > > 127.0.0.1#53 > > > > Sep 30 07:19:21 dtdc1 named[395]: listening on IPv4 &g...
2023 Jul 21
3
cant start bind9 after dc upgrade 4.17 > 4.18
...ed.conf' Jul 21 23:49:14 dc-cloud named[637]: reading built-in trust anchors from file '/etc/bind/bind.keys' Jul 21 23:49:14 dc-cloud named[637]: looking for GeoIP2 databases in '/usr/share/GeoIP' Jul 21 23:49:14 dc-cloud named[637]: using default UDP/IPv4 port range: [32768, 60999] Jul 21 23:49:14 dc-cloud named[637]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 21 23:49:14 dc-cloud named[637]: listening on IPv4 interface eth0, 75.119.155.151#53 Jul 21 23:49:14 dc-cloud named[637]: listening on IPv4 interface eth1, 192.168.8.1#53 Jul 21 23:49:14 dc-cloud named[637]:...
2020 Sep 30
0
Bind9 issue
...> > Sep 30 07:19:21 dtdc1 named[395]: GeoIP Domain (type 11) DB > not available > > > > Sep 30 07:19:21 dtdc1 named[395]: GeoIP NetSpeed (type 10) > DB not available > > > > Sep 30 07:19:21 dtdc1 named[395]: using default UDP/IPv4 port range: > > [32768, 60999] > > > > Sep 30 07:19:21 dtdc1 named[395]: using default UDP/IPv6 port range: > > [32768, 60999] > > > > Sep 30 07:19:21 dtdc1 named[395]: listening on IPv4 interface lo, > > 127.0.0.1#53 > > > > Sep 30 07:19:21 dtdc1 named[395]: listening on IPv4 &g...
2017 Jun 20
2
gluster peer probe failing
...of the patch, can you please comment here? > > > > On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > > Thanks, but my current settings are: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > net.ipv4.ip_local_port_range = 32768 60999 > > meaning the reserved ports are already in the short int range, so maybe I > misunderstood something? or is it a different issue? > > > > *From:* Atin Mukherjee [mailto:amukherj at redhat.com] > *Sent:* Thursday, June 15, 2017 10:56 AM > *To:* Guy Cukierman <guyc at...
2017 Jun 18
0
gluster peer probe failing
...e is the author of the patch, can you please comment here? On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com<mailto:guyc at elminda.com>> wrote: Thanks, but my current settings are: net.ipv4.ip_local_reserved_ports = 30000-32767 net.ipv4.ip_local_port_range = 32768 60999 meaning the reserved ports are already in the short int range, so maybe I misunderstood something? or is it a different issue? From: Atin Mukherjee [mailto:amukherj at redhat.com<mailto:amukherj at redhat.com>] Sent: Thursday, June 15, 2017 10:56 AM To: Guy Cukierman <guyc at elminda.com&...
2017 Jun 20
0
gluster peer probe failing
...re? >> >> >> >> On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: >> >> Thanks, but my current settings are: >> >> net.ipv4.ip_local_reserved_ports = 30000-32767 >> >> net.ipv4.ip_local_port_range = 32768 60999 >> >> meaning the reserved ports are already in the short int range, so maybe I >> misunderstood something? or is it a different issue? >> >> >> >> *From:* Atin Mukherjee [mailto:amukherj at redhat.com] >> *Sent:* Thursday, June 15, 2017 10:56 AM >...
2017 Jun 20
1
gluster peer probe failing
...e is the author of the patch, can you please comment here? On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com<mailto:guyc at elminda.com>> wrote: Thanks, but my current settings are: net.ipv4.ip_local_reserved_ports = 30000-32767 net.ipv4.ip_local_port_range = 32768 60999 meaning the reserved ports are already in the short int range, so maybe I misunderstood something? or is it a different issue? From: Atin Mukherjee [mailto:amukherj at redhat.com<mailto:amukherj at redhat.com>] Sent: Thursday, June 15, 2017 10:56 AM To: Guy Cukierman <guyc at elminda.com&...
2017 Jun 14
2
gluster peer probe failing
Hi, I have a gluster (version 3.10.2) server running on a 3 node (centos7) cluster. Firewalld and SELinux are disabled, and I see I can telnet from each node to the other on port 24007. When I try to create the first peering by running on node1 the command: gluster peer probe <node2 ip address> I get the error: "Connection failed. Please check if gluster daemon is operational."