Bind 9.16 port error still lingers
May 1 21:29:00 gallifrey named[3026]: invalid command from 127.0.0.1#16349: bad auth May 1 21:29:00 gallifrey named[3026]: stopping command channel on 127.0.0.1#953 May 1 21:29:02 gallifrey named[3026]: exiting May 1 21:29:02 gallifrey named[90441]: starting BIND 9.16.2 (Stable Release) May 1 21:29:02 gallifrey named[90441]: running on FreeBSD amd64 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 GENERIC May 1 21:29:02 gallifrey named[90441]: built with '--disable-linux-caps' '--localstatedir=/var' '--sysconfdir=/usr/local/etc/namedb' '--with-dlopen=yes' '--with-libxml2' '--with-openssl=/usr/local' '--with-readline=-L/usr/local/lib -ledit' '--with-dlz-filesystem=yes' '--enable-dnstap' '--enable-fixed-rrset' '--enable-geoip' '--with-maxminddb' '--without-gssapi' '--with-libidn2=/usr/local' '--with-json-c' '--enable-largefile' '--with-lmdb=/usr/local' '--disable-native-pkcs11' '--without-python' '--enable-querytrace' 'STD_CDEFINES=-DDIG_SIGCHASE=1' '--enable-tcp-fastopen' '--with-tuning=default' '--disable-symtable' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/share/info/' '--build=amd64-portbld-freebsd12.1' 'build_alias=amd64-portbld-freebsd12.1' 'CC=/usr/local/bin/clang10' 'CFLAGS=-O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing ' 'LDFLAGS= -L/usr/local/lib -ljson-c -Wl,-rpath,/usr/local/lib -fstack-protecto r-strong ' 'LIBS=-L/usr/local/lib' 'CPPFLAGS=-DLIBICONV_PLUG -isystem /usr/local/include' 'CPP=/usr/local/bin/clang-cpp10' 'PKG_CONFIG=pkgconf' May 1 21:29:02 gallifrey named[90441]: running as: named -u bind -c /usr/local/etc/namedb/named.conf May 1 21:29:02 gallifrey named[90441]: compiled by CLANG Clang 10.0.0 May 1 21:29:02 gallifrey named[90441]: compiled with OpenSSL version: OpenSSL 1.1.1g 21 Apr 2020 May 1 21:29:02 gallifrey named[90441]: linked to OpenSSL version: OpenSSL 1.1.1g 21 Apr 2020 May 1 21:29:02 gallifrey named[90441]: compiled with libxml2 version: 2.9.10 May 1 21:29:02 gallifrey named[90441]: linked to libxml2 version: 20910 May 1 21:29:02 gallifrey named[90441]: compiled with json-c version: 0.13.1 May 1 21:29:02 gallifrey named[90441]: linked to json-c version: 0.13.1 May 1 21:29:02 gallifrey named[90441]: compiled with zlib version: 1.2.11 May 1 21:29:02 gallifrey named[90441]: linked to zlib version: 1.2.11 May 1 21:29:02 gallifrey named[90441]: May 1 21:29:02 gallifrey named[90441]: BIND 9 is maintained by Internet Systems Consortium, May 1 21:29:02 gallifrey named[90441]: Inc. (ISC), a non-profit 501(c)(3) public-benefit May 1 21:29:02 gallifrey named[90441]: corporation. Support and training for BIND 9 are May 1 21:29:02 gallifrey named[90441]: available at https://www.isc.org/support May 1 21:29:02 gallifrey named[90441]: May 1 21:29:02 gallifrey named[90441]: Required root permissions to open '/var/run/named.pid'. May 1 21:29:02 gallifrey named[90441]: Please check file and directory permissions or reconfigure the filename. May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != ((void *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace May 1 21:29:02 gallifrey named[90441]: #0 0x2d26c5 in ?? May 1 21:29:02 gallifrey named[90441]: #1 0x4b44aa in ?? May 1 21:29:02 gallifrey named[90441]: #2 0x4a7d68 in ?? May 1 21:29:02 gallifrey named[90441]: #3 0x2e6fe5 in ?? May 1 21:29:02 gallifrey named[90441]: #4 0x2e2dc1 in ?? May 1 21:29:02 gallifrey named[90441]: #5 0x2d3ff8 in ?? May 1 21:29:02 gallifrey named[90441]: #6 0x4d90da in ?? May 1 21:29:02 gallifrey named[90441]: #7 0x800a7d736 in ?? May 1 21:29:02 gallifrey named[90441]: exiting (due to assertion failure) May 1 21:29:02 gallifrey doctor[90442]: /usr/local/etc/rc.d/named: WARNING: failed to start named May 1 21:29:02 gallifrey kernel: pid 90441 (named), jid 0, uid 0: exited on signal 6 Since bind914 is not available I had to revert to bind911 . Why this error? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism One kind word can warm three winter months. -Japanese proverb ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > Subject: Bind 9.16 port error still lingers "Still"? > May 1 21:29:02 gallifrey named[90441]: Required root permissions to open > '/var/run/named.pid'. > May 1 21:29:02 gallifrey named[90441]: Please check file and directory > permissions or reconfigure the filename. Did you? BTW the default location for named's pidfile on FreeBSD is /var/run/named/pid. > May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != ((void > *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace Some (configuration) value should be an integer, but isn't. Regards, Christoph -- Spare Space ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: > ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > Subject: Bind 9.16 port error still lingers > > "Still"? > > > May 1 21:29:02 gallifrey named[90441]: Required root permissions to open > > '/var/run/named.pid'. > > May 1 21:29:02 gallifrey named[90441]: Please check file and directory > > permissions or reconfigure the filename. > > Did you? > BTW the default location for named's pidfile on FreeBSD is > /var/run/named/pid. > > > May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != ((void > > *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace > > Some (configuration) value should be an integer, but isn't. > cat /var/run/named.pid 15640 running bind911 and ls -Fail /var/run/named.pid -rw-r--r-- 1 root wheel 6 May 1 21:38 /var/run/named.pid > Regards, > Christoph > > -- > Spare Space > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism One kind word can warm three winter months. -Japanese proverb ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
On 2020-05-02 17:16, The Doctor via freebsd-ports wrote: On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): Subject: Bind 9.16 port error still lingers "Still"? May 1 21:29:02 gallifrey named[90441]: Required root permissions to open '/var/run/named.pid'. May 1 21:29:02 gallifrey named[90441]: Please check file and directory permissions or reconfigure the filename. Did you? BTW the default location for named's pidfile on FreeBSD is /var/run/named/pid. May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != ((void *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace Some (configuration) value should be an integer, but isn't. cat /var/run/named.pid 15640 running bind911 and ls -Fail /var/run/named.pid -rw-r--r-- 1 root wheel 6 May 1 21:38 /var/run/named.pid I think what The Doctor tried to point out is that the pid file needs to be owned by the named user, normally "bind". If named is started the "normal" wai, i.e. "service named start" it should create this file with "bind" as owner. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
On Sat, May 02, 2020 at 05:20:27PM +0200, Per olof Ljungmark wrote: > On 2020-05-02 17:16, The Doctor via freebsd-ports wrote: > > On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: > >> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > >> > >>> Subject: Bind 9.16 port error still lingers > >> > >> "Still"? > >> > >>> May 1 21:29:02 gallifrey named[90441]: Required root permissions to open > >>> '/var/run/named.pid'. > >>> May 1 21:29:02 gallifrey named[90441]: Please check file and directory > >>> permissions or reconfigure the filename. > >> > >> Did you? > >> BTW the default location for named's pidfile on FreeBSD is > >> /var/run/named/pid. I'm running bind916-9.16.2: albert(12.1-S)[3] pkg info -o dns/bind\* bind-tools-9.16.2 dns/bind-tools bind916-9.16.2 dns/bind916 Here's what I have in /etc/rc.conf about it: albert(12.1-S)[5] egrep 'bind|named' /etc/rc.conf rpcbind_enable="YES" named_enable="YES" named_program="/usr/local/sbin/named" and the pidfile is in /var/run/named/: albert(12.1-S)[4] ls -lT /var/run/named/ total 8 -rw-r--r-- 1 bind bind6 May 1 05:03:40 2020 pid -rw--- 1 bind bind 102 May 1 05:03:40 2020 session.key No issues. > Peace, david -- David H. Wolfskill da...@catwhisker.org "I believe the people of this country are smart. And I don't think that they will put a man in who's incompetent." -- Donald J. Trump, who apparently missed the irony, 29 Apr 2020. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: Bind 9.16 port error still lingers
On 5/2/20 11:16 AM, The Doctor via freebsd-ports wrote: > On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: >> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): >> >>> Subject: Bind 9.16 port error still lingers >> >> "Still"? >> >>> May 1 21:29:02 gallifrey named[90441]: Required root permissions to open >>> '/var/run/named.pid'. >>> May 1 21:29:02 gallifrey named[90441]: Please check file and directory >>> permissions or reconfigure the filename. >> >> Did you? >> BTW the default location for named's pidfile on FreeBSD is >> /var/run/named/pid. >> >>> May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != ((void >>> *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace >> >> Some (configuration) value should be an integer, but isn't. >> > > cat /var/run/named.pid > 15640 > > running bind911 > > and ls -Fail /var/run/named.pid > > -rw-r--r-- 1 root wheel 6 May 1 21:38 /var/run/named.pid By default, you need 'root' permissions to write to the /var/run directory. As the port is configured on FreeBSD, BIND drops privileges as soon as practical to that of the 'bind' user and group. For example: imb@sarah:/home/imb> ls -l /var/run/named/ total 8 -rw-r--r-- 1 bind bind4 Apr 30 21:05 pid -rw--- 1 bind bind 102 Apr 30 21:05 session.key It seems you have incorrectly changed the configuration by not taking these permissions into account. Check your named.conf for the incorrect definition of pid-file - it should be "/var/run/named/pid", imb ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > Subject: Bind 9.16 port error still lingers > > > > "Still"? You seemed to imply that there was a known problem in our bind port. While I doubt the existence of a problem with this severity (at least my and other people's bind instances are happily serving away), a pointer to that previous description could still be quite helpful. > > > May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != > > > ((void *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace > > > > Some (configuration) value should be an integer, but isn't. Have you checked your configuration for that type of problem? Even a simple named-checkconf could go a long way here. > and ls -Fail /var/run/named.pid > > -rw-r--r-- 1 root wheel 6 May 1 21:38 /var/run/named.pid And that's still not the default location, and again the pid file was created via the workaround code - else that file would have been written as user "bind" - which only works at the default location, which is why we have that default location. Your configuration differs from the default configuration in more than "local addresses and zones", but you have given neither details nor rationale on your changes - all we have is some deductions from error messages. That might make for a good detective story, but does not really expedite technical analysis. Regards, Christoph -- Spare Space ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote: > ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > > > Subject: Bind 9.16 port error still lingers > > > > > > "Still"? > > You seemed to imply that there was a known problem in our bind port. > While I doubt the existence of a problem with this severity (at least > my and other people's bind instances are happily serving away), a pointer > to that previous description could still be quite helpful. > > > > > May 1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != > > > > ((void *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace > > > > > > Some (configuration) value should be an integer, but isn't. > > Have you checked your configuration for that type of problem? > Even a simple named-checkconf could go a long way here. > > > and ls -Fail /var/run/named.pid > > > > -rw-r--r-- 1 root wheel 6 May 1 21:38 /var/run/named.pid > Even with the changes still the parser error exists. > And that's still not the default location, and again the pid file was > created via the workaround code - else that file would have been written > as user "bind" - which only works at the default location, which is why > we have that default location. > > Your configuration differs from the default configuration in more than > "local addresses and zones", but you have given neither details nor > rationale on your changes - all we have is some deductions from error > messages. That might make for a good detective story, but does not > really expedite technical analysis. > Then let's look at the file: //Use with the following in named.conf, adjusting the allow list as needed: key "rndc-key" { algorithm hmac-md5; secret "7ZbGK94NdSa2WACxx72W1w=="; }; controls { inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "rndc-key"; }; }; acl loclnetworks{ 127.0.0.1; ::1; 10.8.0.0/24; 204.209.81.0/24; }; // generated by named-bootconf.pl options { directory "/usr/local/etc/namedb"; pid-file "/var/run/named/pid"; dump-file "/usr/local/etc/namedb/named.core"; max-ncache-ttl 86400; recursive-clients 100; //recursive no; reserved-sockets 32; tcp-clients 40; tcp-listen-queue 14; zone-statistics yes; //forwarders { 208.67.222.222; 208.67.220.220; }; blackhole { 65.94.172.87; 67.68.204.41; 74.15.184.13; 65.94.173.208; }; allow-transfer { 204.209.81.1; 204.209.81.14; }; allow-notify { 204.209.81.1; 204.209.81.14; }; also-notify { 204.209.81.1 port 53; 204.209.81.14 port 53; }; query-source address 204.209.81.3 port 53; version "no"; listen-on {204.209.81.3; 127.0.0.1; }; disable-algorithms . { DSA; }; }; // directory where cache files are stored // type domain source (ip/file) backup file // - -- zone "." { type hint; file "root.cache"; }; And the rest zone files. > Regards, > Christoph > > -- > Spare Space > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism One kind word can warm three winter months. -Japanese proverb ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
On 2020-05-02 19:29, The Doctor via freebsd-ports wrote: On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote: ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): [snip] //Use with the following in named.conf, adjusting the allow list as needed: key "rndc-key" { algorithm hmac-md5; secret "7ZbGK94NdSa2WACxx72W1w=="; I suggest you change this ^ rather quickly, especially if it is a public name server. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
03.05.2020 1:13, Per olof Ljungmark wrote: > On 2020-05-02 19:29, The Doctor via freebsd-ports wrote: >> On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote: >>> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > [snip] > >> //Use with the following in named.conf, adjusting the allow list as needed: >> key "rndc-key" { >>algorithm hmac-md5; >> secret "7ZbGK94NdSa2WACxx72W1w=="; > > I suggest you change this ^ rather quickly, especially if it is a public > name server. This is a key for local (over 127.0.0.1) connections for rndc, it can be abused by local users only, or if there is remotely expoitable vulnerability for running shell code. Still, should not be published so easily but no direct harm when system has no untrusted local users. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Bind 9.16 port error still lingers
03.05.2020 0:29, The Doctor via freebsd-ports wrote: > Then let's look at the file: [skip] Quickest way to unbreak your server: take default named.conf from the installation of version 9.16 and add your changes to it manually but keep default paths within lines "pid-file" and alike. That is, keep changes to default file as small as possible. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: reccomendations of conference / party audio video softwar
To: "https://lists.freebsd.org/mailman/listinfo/freebsd-ports"; + BCC Bernhard & Astrid Jitsi Meet & Server now in FreeBSD ports/ www/jitsi-meet net-im/jitsi-videobridge (Bernhard, might make NetBSD easier too ?) https://svnweb.freebsd.org/ports/head/www/jitsi-meet/pkg-descr?view=markup https://svnweb.freebsd.org/ports/head/net-im/jitsi-videobridge/pkg-descr?view=markup More links: http://www.berklix.org/meet/#jitsi Cheers -- Julian Stacey, Consultant Systems Engineer, BSD Linux http://berklix.com/jhs/ http://www.berklix.org/corona/#masks Tie 2 handkerchiefs. http://www.bbc.com/news/business-52304821 Brexit Dec. 2020 will hit UK more. https://www.bestforbritain.org/transition-coronavirus ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/eric6 | 19.04 | 20.5 +-+ devel/es-eric6 | 19.04 | 20.5 +-+ german/eric6| 19.04 | 20.5 +-+ russian/eric6 | 19.04 | 20.5 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"