IP Address

Written by Sam McGeown on 16/5/2016
Published under VMware

I ran into this problem at a customer site where all the Log Insight nodes were changed due to some IP address conflicts. I think the problem occurred because the IP addresses were all changed and the VMs shut down, without time for the application to update the node IPs.

The symptoms:

  • The web interface was down, a netstat -ano | grep -i “443” showed the service was listening
  • _service loginsight status|restart|stop|start _hung and then timed out on the Master node
  • The loginsight service was not running on the Worker nodes
  • /var/log/loginsight/runtime.log contains warning messages about “Cassandra cluster not ready yet”
  • Running /usr/lib/loginsight/application/lib/apache-cassandra-*/bin/nodetool status showed the two data nodes down (DN) and used the old IP address

All of the nodes were up with their new IP addresses, however Cassandra on the Master node was still looking for the old IP addresses for the Worker nodes. The Worker nodes were in a similar state, knowing their own new IP addresses but not being able to update the Master node because they didn’t have the Master node’s new IP address.

Written by Sam McGeown on 24/11/2010
Published under Microsoft

Today I was configuring a new FTP server based on IIS7 (well, 7.5 technically as it’s a Server 2008 R2 host), and I wanted an easy way to add and remove allowed IP addresses based on either an XML config file or a CSV import. Customers’ IP addresses are added or removed regularly, but I didn’t want to have to update their details twice, once on the server and once in the documents.