Every now and then, I need to parse through some log files where there are multiple files (like in a core dump or a whole logs directory) — figuratively looking for needle in a haystack.
My work has a Splunk license but I didn’t want to add the logs in and have them be a possible red herring for another if I left them in. So, I used Docker to host a Splunk instance on my Mac. Here’s the instructions on setting it up:
Things you need:
Docker ID and installer.
- Install and setup Docker.
- Get and install the Splunk repository.
docker pull splunk/splunk:7.0.0
- Setup a place on your Mac to drop logs and a place to store configs. I’ll use a base folder of ~/Local in this example.
- Create the Docker container.
docker run --name splunk7 -d -v ~/Local/SplunkWatch:/splunkwatch -v ~/Local/DockerData/splunk:/opt/splunk/etc -e "SPLUNK_START_ARGS=--accept-license" -e "SPLUNK_USER=root" -p "8000:8000" splunk/splunk:7.0.0
Login to the frontend at http://localhost:8000. Any logs dropped into ~/Local/SplunkWatch are parsed. Server configs are stored to persist (and be editable) in ~/Local/DockerData/splunk.
For a more GUI interface you can use https://kitematic.com.
Some helpful docker commands:
###list running docker containers
### list all docker containers
docker ps -a
### enter docker container
docker exec -it splunk7 /bin/bash
### stop/start docker
docker start splunk
docker stop splunk
### Clean out DB
docker exec -it splunk7 /bin/bash
/opt/splunk/bin/splunk clean eventdata
As tech tradition dictates, here’s a post on the build for the new server of mine.
Continue reading “The unBuild”
For years I have had a Dell Inspiron 537 with Ubuntu hosting a ZFS RAID 1 file-share. I’ve used it to be a
BitTorrent Resilio Sync server, a Plex Media Server, Apache web server, ssh relay and more. But, it started to show its age with Plex. I was content to let it struggle for another year until I found unRAID from https://lime-technology.com.
After trying a demo, I decided to upgrade and shuffle the Inspiron over to my parents – retiring a hacked together computer lovingly called ‘Frankenpoot‘ – and build a new computer to be a NAS server for me.
The main reasons to use unRAID over something like FreeNAS or Ubuntu again was ZFS’s (and like filesystems’) need for equal-sized disks. That requirement is limiting on a budget. The old Dell, called in its early days Zod (bad guy from Superman) and then Zorg from the movie The 5th Element, had a ZFS RAID1 pool of 2x 2TB drives called “ZorgZFS”. It worked great, no issues or complaints about ZFS. But the chassis of the Inspiron 537 had only room for 2x 3.5″ drives and a SSD boot drive haphazardly attached with only one screw. As I was going to build my own, I could have as many drive bays as I can afford. unRAID can handle drives of any size — as long as the parity drive is the largest.
Over the next few weeks, I’ll be documenting configuration, setup and other knowledge relating to unRAID.
So I recently encountered a weird error in the Admin Dashboard of GitLab:
It wasn’t a gitlab-shell error, the
bin/check script ran fine. Git and Ruby at accepted versions from the
rake gitlab:check command but it did show an error:
GitLab Shell version >= 1.7.9 ? ... <span style="color: #ff0000;">FAIL. Please update gitlab-shell to 1.7.9 from Unknown</span>
The fix is simple, a wrong path in gitlab.yml:
187 ## GitLab Shell settings
189 path: /wrong/git/gitlab-shell/
(Some of the machine I administer use a different /home path.)
So, simply fix the path, restart gitlab and things will work.
Gitlab 6.5 was released earlier this week so naturally it was time to upgrade my dev box. But things broke. I could authenticate fine but got redirected back to the login page. Also, in the production.log it spit out:
Continue reading “GitLab 6.5 and Secure Cookies”