Skip to main content

Miata: Fluids & Filters

Really just noting these here for my reference.  I was at Tool Tyme in Whitby last night to get speaker wire (that was the place that initially got me into audio systems), but turns out they no longer do stereo stuff at all!!  So sad.  Just 'accessories' and whatnot.  Now they do stock Momo wheels, so got to feel what they were like.  Wow...ya a bazillion times nicer on the hands than the Mazda wheel.

Anywho, they also are able to get RedLine fluids (per order basis), and that is just fine by me.  Better than driving out to Concord on my lunch, at any rate.  I still need the diff oil, brake/clutch fluid, Shin Etsu grease, 303 stuff, and possibly something else I'm forgetting.

Fluids & Filters (redline)
Coolant 6.0L 1 17.99 17.99 Ethylene Glycol-based (55water:45coolant)
Transmission 3.0L 3 18 54 Ford Motorcraft MTF (XT-M5-QS), trans needs 2, a little more for shift turret
Diff 0.65L 1 16 16 Redline 75W90 gear oil
Engine 3.4L 2 54 108 5W30 for winter, 10W30 otherwise, Mobil 1 synthetic
Brake & Clutch 2.0L 2 19.99 39.98 ATE Super Blue Brake Fluid (1L)
Power steering 0.75L 1 15.99 15.99 Redline Power Steering Fluid
Oil Filter -extended length Fram PH7317 2 13 26 Or NAPA 1356, Bosch 3323
ShinEtsu grease for windows 1 16 16
Air filter Fram CA6828/NAPA6097 1 12 12
PB Blaster for rusty bolts 1 5 5
303 aerospace protectant for boot install 1 9 9 Vinyl protector  $     367.95


  1. Useful info. Fortunate me I discovered your web site by chance, and I am surprised why this accident did not took place in advance! I bookmarked it.
    Inland 705 silicone diffusion pump oil

  2. Ross, some of the info came from searches, some from here:

    For the Shin Etsu grease, go to and get their window kit - in fact, that's the only place I go to get Mazda parts (even after shipping/taxes they are cheaper than the local dealership).

    One last note - PB Blaster isn't that great - use Liquid Wrench at least. There is one penetrant better than LW, but the name escapes me.


Post a Comment

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…