Skip to main content

Miata 1.8 swap done - next steps

To keep it short...

  • Swap went well
  • Managed to snap some key coolant piece was the only issue at the time, decided to do the coolant re-route
  • Also managed to incorrectly assume that the clutch would not need re-adjusting because...hey I haven't changed clutch components or drained the fluid or anything...
  • The above caused me to run for 2 weeks on a misadjusted clutch, so the shiny FM Stage1 clutch is now pretty much toast - we played with the adjustment afterwards to try and salvage luck
  • I've decided to get off the 'because racecar' bandwagon - ordered the OEM-level value clutch, and I'll get the 1.8 flywheel I have resurfaced
  • The de-powered steering thing has become a saga...continue to have 'stiction' issues
Had the bushings done (IL Motorsports rubber ones), only the mechanic didn't replace the rear bushings due to some miscommunication.  The good news is that alignments are now holding, the bad news is that 1 week after the fronts were done (and rears not), I started getting noises in the rears.

Also getting a clunk noise that I'm hoping is the hard top being slightly loose (latches didn't really 'pull' shut)

Anywho, list of stuff to do...
  1. Get flywheel resurfaced
  2. Engine out, but this time not a weekend blitz
  3. Replace clutch/flywheel/clutch fork
  4. Install coolant re-route & front block-off
  5. Install 1.8 crank pulley, 1.8 WP pulley, 1.8 alternator
  6. Put on replacement hood hinges
  7. FM front sway
  8. Maybe going to try out a thicker trans fluid (suspect the 'exhaust' noise I have is gear lash...?)
  9. Need to do BG oil flush & BG injector flush
  10. REALLY REALLY REALLY clean the engine/trans/everything - suspect oil leaks but can't really tell if it's oversprayed penetrant from the mechanic, spills from filling shift turret, or what
  11. Time available for rear bushing install?
  12. Stop by a body shop and see what rust repair & paint will actually cost


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…