Skip to main content

Miata: Maintenance update

Got word from the distributor that the Flyin Miata/Moss parts have shipped, guessing they'll be here in a few days.  Heated seat kit also shipped the other day, although it probably won't get much use.  Nice to have, just in case.  (in retrospect, a wind blocker would have been a better investment)

Also did some reading on, and turns out that the method I initially read about to do the clutch (drop trans out the bottom) is a complete nightmare versus pulling the engine and trans together out the top with a shop crane.  Kinda ironic that I helped my friend offload his (was being stored in my garage).  At the time the decision made sense.

Handily (providentially?) enough, PA's hoist is on sale right now, so I put one of them on reserve (along with a leveler bar).  Another $300 or so after taxes, but if it's the difference between getting the job done (quickly) and not, not much choice.  Also, I needed one anyway for when the foundry furnace is built, so not like it's a waste.

This is somewhat of a relief, as my jack stands offer 16" full travel, meaning to get the required 18" if doing the trans removal only, I'd either need larger stands, or to prop them up on wood - not ideal.

At this point this is the most expensive car maintenance project I've ever done, but I suppose it's also as close to a full overhaul as I've ever done as well (haha, on my own coin).

Engine hoist

Leveler bar

It's also apparent the maintenance is not happening this week, unfortunate as we have nice weather at the moment, but for the best...a lot going on otherwise. week.

One last note - for the money we've spent so far, yes, entirely possible we could have paid someone to do it.  However:

  1. No experience gained.
  2. Pay money, no tools to show for it.
  3. Sub-standard or bog-standard parts would probably have been used - nicer parts cost the same, but mechanics usually won't install non-OEM bits.
  4. If something doesn't go right, could cost more money/time to get them to do over.
So ya.  Expense is there, but worth it in the end.


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…