Skip to main content

Miata: New wheels

Picked these up from a guy in Bradford who had them listed on Kijiji.  Turns out he's a long-time Mazda mechanic who for many years did runs down to the southern states to get Miata parts rust-free.  However, since the economy went bad and people driving Miatas up here tended to be cheapskates (his opinions), he's sold off all his parts - these were the last set of wheels he had.  They're in pretty nice shape, just slight curb rash on one or two, easily remedied.

I initially thought they were the hollow-spoke wheels, but turns out they are 'semi-hollow'.  These came on the 94-97 automatic Miatas.  BTW, the weights for hollow/semi-hollow/solid spoke wheels are 10.8/11.2/11.5lbs each.  Still a heck of a lot lighter than the 16" NB wheels Mia is currently rockin', at 15.3lbs each.

The unsprung weight reduction should lead to a number of benefits:

  1. Better mileage (less weight for the drivetrain to spin)
  2. Better ride quality (less work for the suspension to travel up/down, so easier to traverse bumps)
  3. Better handling (same reason above)
  4. Narrower than the 16", so better in the winter
Now, it'll be a little less fancy-lookin', but I believe I can help that cause.  (I do really like the look of the NB wheels, kinda like the Porsche Turbo-twist wheels)  Enter the 7-spoke wheels, some abrasive pads, sandpaper, paint, and clearcoat.  That's the theory, anyway.  I've always had a soft spot for bronze wheels (from my days at WheelsDirect, and the early Rota selections), and bronze w. polished lip = nom.

Something to do once all the maintenance is up to spec.



Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…