Skip to main content

SonarQube & TeamCity & RDS

Our environment

  • All-AWS
  • Mysql RDS for DB
  • Running the sonar java app off our Linux Teamcity server on port 9000 (as a service)
  • Teamcity agents are Windows boxes w. (cinst -y JDK8)
  • Active Directory on 2012R2
  • Sonar 6.2 (probably a bad idea)

Some key points to getting things actually running...
RDS

  • Create a new parameter group in RDS that matches your RDS instance type (e.g. mysql 5.6)
  • Set these params (because trial and error is fun with a 1GB repo scan)
    • max_allowed_packet: 32768000
    • innodb_log_file_size: 1024217728
  • I also set some stuff via MySQL Workbench as per their documentation (collation stuff)
    • USE sonar;
    • ALTER DATABASE sonar CHARACTER SET utf8 COLLATE utf8_bin;
LDAP
Was so pleased that after hours of googling, found something that 'just worked'...I wish I'd saved the link with this.  It was a StackOverflow result, of course.  Tried 2-3 that did not work...

This config is obviously wide-open, but only accessible via our VPN, so acceptable for now.

###################################
###################################
# LDAP configuration
# General Configuration
ldap.realm=domain.production
sonar.security.realm=LDAP
sonar.security.savePassword=true
ldap.url=ldap://DC.IP.AD.RS:389
ldap.bindDn=CN=Your LDAP Service Account,CN=Users,DC=domain,DC=production
ldap.bindPassword=passwordHere
# User Configuration
ldap.user.baseDn=CN=Users,DC=domain,DC=production
ldap.user.request=(&(objectClass=user)(sAMAccountName={login}))
ldap.user.realNameAttribute=cn
ldap.user.emailAttribute=mail
# Group Configuration
#ldap.group.baseDn=CN=Domain Users,CN=Users,DC=domain,DC=production
#ldap.group.request=(objectClass=group)

TeamCity config
SonarQube Server connection

  • URL: http//sonar.domain.com:9000
  • Login: sonar (service account in AD - using the admin account I made this account also an admin - not sure if required)
  • Password: the service account's password
  • JDBC URL:  the RDS DB connection string
  • Username/pass: the RDS DB connection creds
Sonar Scanner build step
This is where I fell down...
  • Sources location:  Set a list of dirs, but couldn't get this working...it still scanned every dir
  • Additional parameters:  -e  (error reporting verbosity)

Will update this with correct params once we figure it out...at this point it's scanning, but scanning even 3rd party stuff that we are ok with excluding.

I also want to figure out the dotCover integration bit, but not sure if that's a thing yet.






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…