Skip to main content

Miata: Wish list

Just a place to note what I'd like to do over the life of the car.  At the end of the car's life, would be a great deal of fun to convert it to a V8, but for the sake of fuel economy, a turbo-four will always do better.  L/100 is completely relevant and important since we have a car budget, not a money tree.

Phase 1
Make car reliable and safe, bring maintenance schedule into line.  Fix oil leaks.  Fix rust.

Phase 2
Go MS!!  Get MS3x incl. GM IAT, MAP, WBO2. ~$1000

Phase 3
Gauges, additional sensors. ~$500

Phase 4
Find a donor car - 2001-2005, swap over drivetrain! ~$1000-2000

Old ideas...
Phase 1
Make the car 100% reliable and safe, bring maintenance schedule into line.  Get a feel for what 'normal' is (compression test/leakdown test).  Fix the rust issues (DIY).  Additional undercoating?  Fix oil leaks. (Pretty sure rear main is leaking dye test)

Phase 2
Remove weak points such as the differential, ECU, injectors, MAF, coils (required only for turbo?).  Replace with 1.8 diff, MS ECU (IAT/MAP/WBO2), 550cc injectors, Coil-On-Plug.  LED dash conversion? (not expensive, just time-consuming)

Phase 3
Spend a calendar year learning the ins/outs of tuning the MS.  Add gauges - oil temp (& remote oil filter?), boost, WBO2 (Autometer Sport-CompII).

Phase 4
Debate about the 1.8 upgrade.  Debate about VVT.  Debate about built engine (rods/pistons/headwork).  Good time to pull engine and do a proper engine bay refresh.  Wire tuck?  Coolant re-route?  Radiator upgrade?  Debate 1.8 brake upgrade.

Phase 5
Debate about kit vs. DIY turbo solution.  Debate about 'just get a turbo' vs. 'build properly first time'.  V-band? Cast vs. mild vs. stainless manifold?


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…