[Bug 207804] nscd negtive cache do not timeout for getaddrinfo:Non -recoverable failure in name resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207804 Bug ID: 207804 Summary: nscd negtive cache do not timeout for getaddrinfo:Non -recoverable failure in name resolution Product: Base System Version: 10.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: am...@amutu.com I met this bug several times for the last years，today I can reproduce it on a machine.I can always restart nscd or use nscd -i hosts to clear the nscd cache，but I think it is better to fix this bug. config: cat /etc/nsswitch.conf group: compat group_compat: nis hosts: cache files dns networks: files passwd: compat passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files cat /etc/nscd.conf threads 1 enable-cache passwd yes enable-cache group yes enable-cache hosts yes enable-cache services yes enable-cache protocols yes enable-cache rpc yes enable-cache networks yes positive-time-to-live hosts 30 negative-time-to-live hosts 1 on the first console : >pkg install bash postgresql95-client >bash >while true; do psql -p 80 -h www.google.com; sleep 50; done you will see psql: received invalid response to SSL... on the second console: edit the /etc/resolv.conf,comment all the nameserver using "#' now on the first console,you will see: psql: could not translate host name "www.google.com" to address: hostname nor servname provided,or not known psql: could not translate host name "www.google.com" to address: Non -recoverable failure in name resolution ...repeate the last message. you can ping www.google.com,but psql can not resolve the error.I read the psql code,and find it use getaddrinfo to resolve the addr. now even if you un-comment the servername in /etc/resolv.conf ,the "Non -recoverable failure in name resolution" still there,unless you restart nscd,or nscd -i hosts for that user. uname -a FreeBSD xx 10.1-RELEASE-p26 FreeBSD 10.1-RELEASE-p26 #0: Wed Jan 13 20:59:29 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207804] nscd negtive cache do not timeout for getaddrinfo:Non -recoverable failure in name resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207804 --- Comment #1 from Jov --- (In reply to Jov from comment #0) you can ping www.google.com after you recover the /etc/resolv.conf content,but psql can not resolve the error.I read the psql code,and find it use getaddrinfo to resolve the addr. this bug happened for my home router several times and one vps a a time. I have coredump for nscd,and I can gdb for the psql or nscd process for more info if some one need. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207783] OpenSSH client segfaults in 9.3-RELEASE-p37
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207783 Athanasios Douitsis changed: What|Removed |Added CC||aduit...@gmail.com --- Comment #6 from Athanasios Douitsis --- Same here, freebsd-update rollback or replacing libcrypto.so.6 with the previous one fixes the problem. As already reported, backtrace shows the problem being in BN_mod_exp_mont_consttime () from /lib/libcrypto.so.6. Maybe this has something to do with r296462 (https://svnweb.freebsd.org/base?view=revision&revision=296462). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207783] OpenSSH client segfaults in 9.3-RELEASE-p37
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207783 Ryan Frederick changed: What|Removed |Added Severity|Affects Only Me |Affects Many People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207807] mountd: mountd.pid file is not readable by normal users
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207807 Bug ID: 207807 Summary: mountd: mountd.pid file is not readable by normal users Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: ru...@rubenkerkhof.com I have a daemon running as a normal user, that runs /etc/rc.d/mountd status once in a while to check if mountd is running. /var/run/mountd.pid is only readable by root however: % ls -l /var/run/mountd.pid -rw--- 1 root wheel 5 Mar 8 14:33 /var/run/mountd.pid It's not that it contains secret information ;) Can those permissions please be changed? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207807] mountd: mountd.pid file is not readable by normal users
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207807 --- Comment #1 from Ruben Kerkhof --- Created attachment 167853 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167853&action=edit Change permissions of mountd.pid to 0644 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207811] service -e doesn't show all enabled services
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207811 Bug ID: 207811 Summary: service -e doesn't show all enabled services Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: 000.f...@quip.cz CC: freebsd-am...@freebsd.org CC: freebsd-am...@freebsd.org I have seen this few times before on another machines. This time I came to file a PR for it. I have isc-dhcp41-server-4.1.e_10,2 installed and enabled in rc.conf but service -e doesn't show it: root@xyza ~/# service -e | grep local /usr/local/etc/rc.d/proftpd /usr/local/etc/rc.d/smartd /usr/local/etc/rc.d/rsyncd /usr/local/etc/rc.d/amavis-p0fanalyzer /usr/local/etc/rc.d/mysql-server /usr/local/etc/rc.d/amavisd /usr/local/etc/rc.d/courier-authdaemond /usr/local/etc/rc.d/postfix /usr/local/etc/rc.d/courier-imap-pop3d-ssl /usr/local/etc/rc.d/courier-imap-pop3d /usr/local/etc/rc.d/courier-imap-imapd-ssl /usr/local/etc/rc.d/courier-imap-imapd /usr/local/etc/rc.d/bsdstats /usr/local/etc/rc.d/apache24 The rc file is there root@xyza ~/# /usr/local/etc/rc.d/isc-dhcpd Usage: /usr/local/etc/rc.d/isc-dhcpd [fast|force|one|quiet](start|stop|restart|rcvar|enabled|uninstall|configtest|status|poll) It can be started, I can request status etc. root@xyza ~/# service isc-dhcpd start Starting dhcpd. root@xyza ~/# service isc-dhcpd status dhcpd is running as pid 74802. rc.conf contains these lines ## ISC-DHCPd dhcpd_enable="YES" dhcpd_flags="-q" dhcpd_ifaces="nfe0" dhcpd_chroot_enable="YES" All listed services on this machine root@xyza ~/# service -e /etc/rc.d/hostid /etc/rc.d/hostid_save /etc/rc.d/cleanvar /etc/rc.d/ip6addrctl /etc/rc.d/devd /etc/rc.d/pf /etc/rc.d/newsyslog /etc/rc.d/syslogd /etc/rc.d/ntpdate /etc/rc.d/nfsclient /etc/rc.d/dmesg /etc/rc.d/virecover /etc/rc.d/motd /etc/rc.d/ntpd /usr/local/etc/rc.d/proftpd /etc/rc.d/sshd /usr/local/etc/rc.d/smartd /usr/local/etc/rc.d/rsyncd /usr/local/etc/rc.d/amavis-p0fanalyzer /usr/local/etc/rc.d/mysql-server /usr/local/etc/rc.d/amavisd /usr/local/etc/rc.d/courier-authdaemond /usr/local/etc/rc.d/postfix /etc/rc.d/bsnmpd /usr/local/etc/rc.d/courier-imap-pop3d-ssl /usr/local/etc/rc.d/courier-imap-pop3d /usr/local/etc/rc.d/courier-imap-imapd-ssl /usr/local/etc/rc.d/courier-imap-imapd /usr/local/etc/rc.d/bsdstats /usr/local/etc/rc.d/apache24 /etc/rc.d/cron /etc/rc.d/jail /etc/rc.d/mixer /etc/rc.d/gptboot /etc/rc.d/bgfsck root@xyza ~/# uname -srmi FreeBSD 10.2-RELEASE-p10 amd64 GENERIC I don't know why some services (isc-dhcpd in this case) are not shown. How can I track it down? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207783] OpenSSH client segfaults in 9.3-RELEASE-p37
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207783 --- Comment #7 from Athanasios Douitsis --- Some more info, in case it helps: - Everything using libcrypto.so.6 can be affected. I've noticed problems with ssh server (ssh child dies with segfault), cyrus-imapd and check-imaps from nagios plugins. - Ssh'ing from another FreeBSD to a system with the problematic sshd is successful, but ssh'ing using openssh client e.g. from a linux box is not. Some clients do work, some do not. So some care must be taken to reproduce the problem, as not all clients trigger the problem. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207714] [zfs] send/receive does not recreate holes correctly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207714 --- Comment #4 from Martin Birgmeier --- Created attachment 167864 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167864&action=edit patch applicable to releng/10.3 The attached patch combines the three commits which correct the problem from https://github.com/ahrens/illumos/commits/recv-hole. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207783] OpenSSH client segfaults in 9.3-RELEASE-p37
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207783 Alexandros Kosiaris changed: What|Removed |Added CC||akosia...@gmail.com --- Comment #8 from Alexandros Kosiaris --- Just reporting I 've been having the same issue. ssh to the 9.3 box from a recently installed 10.2 succeeded, ssh from a Debian Jessie failed. Version is: $ ssh -V OpenSSH_6.7p1 Debian-5+deb8u1, OpenSSL 1.0.1k 8 Jan 2015 A freebsd-update rollback fixed the issue for me. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207714] [zfs] send/receive does not recreate holes correctly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207714 --- Comment #5 from Steven Hartland --- We should wait till this has finished review and gets unstreamed, the current PR is here: https://github.com/openzfs/openzfs/pull/37 This may be too late for 10.3 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207783] OpenSSH client segfaults in 9.3-RELEASE-p37
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207783 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org, ||j...@freebsd.org, ||security-offi...@freebsd.or ||g Status|New |Open Assignee|freebsd-bugs@FreeBSD.org|delp...@freebsd.org --- Comment #9 from Xin LI --- Take. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202135] nscd does not accept a value of zero for negative-time-to-live for passwd nor group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202135 Jov changed: What|Removed |Added CC||am...@amutu.com --- Comment #1 from Jov --- Created attachment 167900 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167900&action=edit patch for check nscd configuration value I make a patch for checking the value for nscd config. the patch check if the config value valid as follows when parse the /etc/nscd.conf,the condition value come from assert statement in various place from nscd code. positive-time-to-live > 0 negative-time-to-live > 0 negative-confidence-threshold > 0 suggested-size > 0 keep-hot-count >= 0 the patch against HEAD. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207804] nscd negtive cache do not timeout for getaddrinfo:Non -recoverable failure in name resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207804 Jov changed: What|Removed |Added CC||am...@amutu.com --- Comment #2 from Jov --- Created attachment 167901 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167901&action=edit fix nscd negtive ttl bug I find PR 181586 and try the patch,it fix the bug. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181586 the origin patch is trimed，and I rework the patch. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207831] r293311 breaks OpenVPN routing using pf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831 Bug ID: 207831 Summary: r293311 breaks OpenVPN routing using pf Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Keywords: regression Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: daniel.engberg.li...@pyret.net CC: freebsd-am...@freebsd.org, melif...@freebsd.org CC: freebsd-am...@freebsd.org Hi, I have a box that acts as a firewall (pf), gateway and VPN gateway running OpenVPN. Upgrading from -CURRENT r290676 to r295667 broke some of the functionality namely the ability to route traffic from the VPN to other networks. The network setup looks like this: Network A (AMD64) - 192.168.20.0/24 (VPN: 10.0.9.1) Network B - 192.168.40.0/24 (VPN: 10.0.9.240) Network C (AMD64) - 192.168.1.0/24 (VPN: 10.0.9.253) Network B and C connects to Network A and accesses both devices on Network A but also between each others network, Network A (the box itself) works in that regard as a hub. This is setup using tunneling (tun interfaces). Upgrading to r295667 (including rebuilding everything) brakes this completely (you cannot ping the other nodes either), so I decided to do some backtracking to see where it stopped working. This is tested using full rebuilds (world, kernel, ports) no partial ones. r290676 - OK r290866 - OK r291136 - OK r291262 - OK r291465 - OK r291855 - OK r292004 - OK r292019 - OK r292158 - OK r292483 - OK r292626 - OK r293017 - OK r293108 - OK r293313 - Broken The only related commit I can find is r293311 which seems very resonable. However it's not completely broken as Network C (client) can connect to other networks via VPN running r295667 which seems a bit weird to me (if the hub is working that is). Network B is a Linux client which also works but I don't think that's relevant in this case. Both Network A and Network C have no blocking filtering on the tun interfaces. pass in quick on tun0 all pass out quick on tun0 all Unfortunately I'm not a developer so I can't really tell what's really broken but I'm willing to test patches etc. If there's anything else you need or have questions just fire off a mail and I'll try to respond as useful as possible. Keep up the good work! Best regards, Daniel Engberg -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
