Skip to main content

Miata: New stereo plans

Ok, I love the headrest speakers, very nifty idea in a convertible, but dang the rest of the system stinks.  Probably because it's 19 years-old, but probably also because it stinks.  The bass is provided by some novel 'vibrator' thingies in the lumbar area.  Unique, but gimmicky.  The MSSS portion relies on those, and is ultimately useless.


Head unit.  Gone.  MSSS unit.  Gone.  Door speakers/tweeters.  Gone.   Headrest speakers.  Disconnected. (or maybe Gone.)

New system as follows:

  • Head unit provided by my phone w. line-out direct into amplifier
    • Going to hard-wire a charger
    • Ordered 3 different suction mounts, just in case (yay eBay)
    • Going to run a shielded 3.5mm -> RCA cable under the carpet and up to the suction mount
  • Amplifier is an older Alpine V12 MR something or other.
    • 30A fuse, so can't be all bad.
    • 2ch, 100wrms@4ohms @12v (so a little more at 14.4v)
    • Neglected to take a pic...sorry.
  • Speakers are some fun little say it all.  
    • 125wrms@4ohms max, how convenient
    • Not certain where I will hide the crossovers
    • Tweeters are rather heavy

Should sound pretty decent when I'm done with it.  Thankfully I never threw out all my old power cabling/fuses, so just need appropriate speaker wire (should be fine with 16-18 gauge)


Dat's a huge magnet.

Stock headunit, for those interested.


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…