Skip to main content

Miata: Parts are in!

Well, some of them, anyway.  Still waiting on all the phone bits, plugs/wires, and of course still have to order another Rosenthal chunk, Flyin Miata parts, and Moss Motors parts.  Yes, it's costing more than we'd expected...but darn it if the car won't drive like new when I'm done, should be good mechanically for the next 10-20 years.  :)  50k until I do timing belt (a little early, but will reset the maintenance cycle).  So 2-3 years.

The list is hooge, so I'll just post pics, cuz everyone loves pics.  Not pictured are the KYB shocks...I'm sure they'll crop up in the suspension post.

Rosenthal parts!
Quite impressed they got here so soon...I think less than 2 weeks from 'click to order' to pick up at the post office.  Definitely saved some dough, even after the import/shipping charges.  If nothing else, I saved a ton of time with their MOST EXCELLENT website:

Shifter refresh kit
Rosenthal Mazda has a number of these pre-packaged kits.  I also got their water hose refresh kit (9 hoses).  Will be getting their Teflon roller kit for the windows as well (seeing as how they only roll down half-way).

Moar parts.
I believe I still need more injector bits - just got 4 o-rings and 4 bushing thingies.  I think more o-rings required...more research, anyway.

Fat Cat Motorsports!!
Bumpstop kit - 58mm.  Even comes with a handwritten note thanking me for my purchase...THAT is customer service.  Very impressed.  I think this is the most anticipated part of the whole refresh project...but the proof is in the pudding, as they say.  A number of very positive reviews on and elsewhere.

The child in me is wishing I'd gotten the sportier set, and RED shock boots.  :)  The person who has to commute several hours a day in traffic is glad he didn't listen and got the 'comfort' suspension pack.

Their articles on suspension systems are very interesting:

$92 radiator


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…