Search results

Thanks all. There is also a good treasure trove of information at Brendan's site (http://www.brendangregg.com/index.html). It's well worth bookmarking that site. Atsuri, I went ahead and marked this "solved" for you.

The altq man page and a search for mentions of "altq" and "ALTQ" in pf.conf is a good start.

hwpmc or dtrace. See also https://wiki.FreeBSD.org/DTrace.

Wow. I forgot all about this. I fixed this as part of 203059 in commit https://svnweb.FreeBSD.org/changeset/ports/397925. The issue was needing ldconfig and can be seen in the linked changeset.

That port is marked BROKEN. sysutils/ncdu is what I have used before that seems similar.

There is probably an underlying FreeBSD issue but however you replicated the issue from the GUI would likely be required to troubleshoot it. Your best bet is to report it through the pfSense bug tracker with the GUI steps you did that caused it and let the underlying caused be filtered up to...

Thanks Dan. Is there a bug report in for this yet?

"Someone" has to be "somebody" or else the issue may not be fixed.

You could try lang/clang37 to see if the behavior is improved there. It sounds though as you have a reproducible error that should be reported to the LLVM folks so that it could get fixed in the upstream.

freebsd-update is not an automated process. It is interactive and the user must remove those merge markers as they update.

Ah. Yes when freebsd-update is used the merge markers must be removed.

The above mentioned reviewed was closed in commit: https://reviews.FreeBSD.org/rS287099 on head. The corresponding stable/10 commit was https://reviews.FreeBSD.org/rS287665 two months ago.

So this address is not your home address so it's not your ISP responsibility. I also see this fail using the command mentioned above to a public DNS server. Does a reverse DNS lookup of your home IP address work? That will at least rule out local issues with your ISP's DNS.

drill -x @8.8.8.8 66.237.94.160 for a query to Google fails. It works for a reverse DNS lookup of my home router IP address. I think the issue with with the ISP.

Can you post the contents of /etc/resolv.conf?

On 9.x and earlier, ISC's dig was part of the base system along with BIND. On 10.x and later, NLnet labs Unbound suite and drill are included instead. This certainly does look to be some changes to DNS resolution somewhere in the network that are causing issues.

drill and dig are tools for DNS lookup. An example would be drill -x 8.8.8.8. Sendmail is sensitive to DNS issues so if things like that are failing then DNS needs to be looked at.

Thanks! I should have searched for this before posting. Yes. You'll want to apply all the errata beforehand as there was a few for freebsd-update that addressed upgrades to 10.x. Since the finance/electrum is already in the ports collection we've covered the topic of this thread. If you have...

It looks like this was just addressed in commit https://svnweb.FreeBSD.org/changeset/base/291657 as part of work on 204968. Raf, thanks for reporting the bug!

If anybody did the port for Electrum then it can certainly get added if a PR was created for it. It may be some time before it gets reviewed as there is a rather large backlog of PRs and I'll contribute as much as my time and sanity allow. FreeBSD 8.4 is no longer supported as of earlier this...