I often get questions around Log Insight agent configuration. While the options are clearly documented, it can be time-consuming and error prone to construct lengthy agent configuration files. In this post, I will introduce a CLI utility I wrote to make this process easier and less error prone.
If you remember reason 9 from my 12 reasons why you should use the Log Insight agent post then you may be wondering how you can support time deltas greater than 10 minutes between the client and the server. In this post, I will cover how to do it.
By default, Log Insight is configured listen on the following ports:
The question becomes, how do you change these default ports?
I have been noticing more and more frequently then when I switch between WiFi connections or switch between wired and WiFi connections that sometimes my WiFi connection would show that it was online, but I was unable to access anything on the LAN or WAN. I have experienced similar issues when DNS is not working properly, so my first test is to validate DNS is working. With this recent issue my test always returned:
$ > nslookup cnn.com /SourceCache/bind9/bind9-45.101/bind9/lib/isc/unix/socket.c:1890: internal_send: 192.168.1.1#53: Cannot allocate memory
So what is going on and how can you fix the issue?
I have heard of a few people who have restarted the Log Insight 2.5 virtual appliance and found that the Log Insight service failed to start with a Cassandra error stating it cannot connect. In this post, I would like to discuss how you can address the issue.
If you have deployed the VCSA a couple of dozen times like me then you quickly realize that it is necessary to script the initial configuration of the device. I would highly recommend taking a look at William Lam’s blog for some great setup scripts including:
Something that I noticed was missing from William’s scripts was the ability to configure application layer services such as NTP and Syslog. As such, I put together a couple quick scripts shared below.