localhost woes -- help requested

[Adam]

On Sat, Jun 15, 2019 at 12:54 AM Ronald F. Guilmette <rfg at tristatelogic.com>
wrote:

> I've recently completed a long overdue upgrade from FreeBSD 9.1 to
> 12.0.  And when I say "completed" that isn't 100% accurate, as there
> are still a couple of remaining things I can't quite seem to make
> work properly.
>
> Both of these, perhaps coincidentally, have to do with the magic
> name "localhost".
>
> I can't for the life of me figure out what I've done wrong so I am
> asking for help.
>
> First I should probably explain where I have been already, as that
> may help to shed light on the problem.
>
> I installed and configured my new 12.0 system on a different (Intel-
> based) machine at first.  Got almost everything I need installed and
> working on that hardware before, as a last step, pulling the hard
> drive out of that system and sticking in into the AMD-based system
> which will be its final home.  Two things that definitely worked
> before I swapped the hard drive to its new home were the Firefox and
> Opera browsers.  (I know.  I checked.)
>
> Once I had the drive installed on the AMD system, I had to make a
> small diddle to /etc/rc.conf to enable the AMD Kernel Mode Switching
> graphics driver.  But other than that, everything remained pretty
> much as it was.  The only other thing I did was to tun on ipfw.
> It took me awhile to get my ipfw rules all the way I want them,
> but now everything is running peachey again...
>
> ... except for the browsers, and also one other thing (nmh outbound
> email handling).  Now, both Firefox and Opera crash and burn, right
> out of the gate, when started from the command line.  In both cases
> thet do so both with entirely cryptic failure messages.
>
> But here's the kicker... I futzed around with this awhile and found
> out that if I just change the default value of the DISPLAY environment
> variable from "localhost:0.0" to ":0.0" then both browsers *do* then
> start up successfully from the command line.
>
> So, um, what the bleep did I do wrong?
>
> Here's the output of the command "getent hosts localhost":
>
> ::1               localhost
> 127.0.0.1         localhost  localhost.tristatelogic.com
>
>
> Any hints for how I can debug this mess would be appreciated.
>

Do you have local_unbound running?  It's probably caching the result.

/etc/rc.d/local_unbound stop

Then try your changes to /etc/hosts

fwiw, the default ipv6 line matches the ipv4 short then fqdn.

-- 
Adam