fail2ban fails to build (fwd)

[Dave Horsfall]

On Tue, 3 Nov 2015, Kubilay Kocak wrote:

> > OK, I did a bit more digging, and found that during one of my more 
> > desperate i.e. less lucid moments I had renamed /var/db/pkg to 
> > .../pkg.old in an attempt to load all of ports again, which I now 
> > remember was failing because of a FreeBSD version mismatch[*].  Looks 
> > like pkg got upset and crashed...
> > 
> > Anyway, here's what you wanted (after I renamed it back):
> > 
> > pkg-1.5.3                          >   succeeds port (port has 1.2.7)
> > 
> > So yeah, I'm outta date, so I have some work to do...
> 
> Definitely. What's not better is what you have installed is later than 
> what pkg thinks there is (db mismatch or out of sync)

Yeah, I was trying various things in order to get my ports area back into 
shape...

> > [*]
> > Because this is a binary-only system (as supplied to me), the script to 
> > bump the patch level is not present, but it gets incremented on a kernel 
> > update, thus we have:
> > 
> >     aneurin# uname -r
> >     9.3-RELEASE-p21
> 
> What script, freebsd-update?

Yes, I run "freebsd-update cron" each day.

> > but I know it's at p29 because I faithfully track all updates.
> 
> How are you tracking them?

See above.  I also pay attention to security announcements :-)

> > No matter what mirror or technique (FTP/HTTP) was used to load "ports" 
> > I get something like "not found on this server" or something, so I 
> > gave up; it was looking for -p21 but only say -p25 was available.
> > 
> > Does that make sense?
> 
> Kinda/Mostly :)
> 
> When you say "load ports", what do you mean and what method exactly are 
> you using to do it?

To restore /usr/ports to a known condition, by renaming it and then doing
a sysinstall (if I remember).

> You said earlier you're using binary packages only, but here you say 
> ports. Are we using these terms interchangeably here? If so, cool, if 
> not, confusing :)

Yeah, I meant "/usr/ports", as I prefer to compile from sources; that way, 
I get to play with the configuration options (important for OpenLDAP, with 
its zillions of tweaks) and use "-g" if I need the big guns.

> I'm not sure whether or to what extent your potential system 
> (mis?)configuration is contributing to these "not found on this server" 
> errors. What exactly is showing you this error?

I'll have to get back to that later; I've been side-tracked a lot lately 
(I had issues with my MacBook for a while).

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."