Skip to main content

First steps for the new lab

First task is to install a Wiki server to hold my documentation.  It will probably end up here as a 2nd page or something.

I will need to start making choices soon about when to blow away the old domain as I need the name.

The wiki is up, and the first two pieces of documentation are done - MediaWiki 1.17 install and config and CentOS 6 install/config.

Ew...formatting...definitely have to do something soon.

1.       Create new VM,

a.       Do not set an installer (it auto-installs the GUI)

b.      Give disk as 20GB, single file.

                                                               i.      Note that logging will eventually all flow to the syslog server, so no need for a huge amount of space.

c.       Assign an IP and document in the spreadsheet.

d.      Choose the ‘basic server’ spec.

2.       Set up VMware tools

a.       Mount /dev/ /mnt

b.      Copy the vmware-tools file into /tmp

c.       Un-tar it

d.      Run the .pl file - default install stuff.

3.       Configure the networking

a.       Change the DNS if necessary.

b.      Set onboot to yes.

c.       ifup etho

4.       Set up the RPMforge repo.

5.       Set up the user

a.       Adduser chris

b.      Passwd chris

c.       Vi /etc/group

                                                               i.      Add chris to sshd and wheel

d.      Visudo
                                                               i.      Uncomment wheel – all

 MediaWiki installation/configuration

2.       Yum –y install php mysql-server httpd php-mysql

3.       Change the httpd.conf file (/etc/httpd/conf/httpd.conf)

a.       Point the root dir to /srv/mediawiki/mediawiki-1.17.0

4.       setenforce = 0

5.       stop iptables

6.       Connect to the server/index.php and run through the media

7.       Save the LocalSettings.php file into the root dir.


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…