Skip to main content

Miata: Door speaker cabling

Wow.  That was the closest I've come to outright profanity in a long time.  For whatever reason the door grommet/gasket thingy in the Miata is an 'S' shape, and makes routing cabling through it nigh impossible.

Also, I had the choice between 18- and 14-gauge wiring for the speakers, not the 16- I wanted.  Probably should have gone with 18-gauge, as the 14- is rather chunky.  I was barely able to route the two runs of it through the door grommet, but it is done.  If you're curious, you must remove the grommet from the door and body - otherwise it's impossible to run.  I tried for an hour with various methods, ended up having to use a rod with the cabling taped to it even with the grommet removed.

I only got the one door done.  Between the high winds (media calling it a hurricane) and my wife wanting to watch Castle with me (who am I kidding, Nathan Fillion is witty and charming), didn't have time to do the passenger side.

Tomorrow hopefully will see the speaker wiring done (assuming I bought enough!!!) and amplifier power/remote wiring completed as well.  Still haven't thought about how I'll switch the amp on/off, or how I'll cover the old double-din location.

Stock speaker is actually decent.  Too bad one is blown.

I zip-tied the old wiring to itself, hopefully shouldn't rattle.

Naked doors.

I thought the stereo was kinda wobbly.  Pretty sure strapping is not OEM.

Back of the door panel, will need some cutting to fit the new tweeters.

I will be mounting the crossovers in here - no headunit FTW!

Comments

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$\user.name\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):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

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/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
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 going...so here's a config and brain dump...

Why?
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)

How?
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
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…