Ashwin Nair indianwhocodes

Problem Statement

Building the joyent/manta-monitor with JAVA 11, out of the box results in complie time errors something like:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project manta-monitor: Compilation failure
[ERROR] /Users/sachingupta/Documents/Joyent/java-manta-monitor/manta-monitor/src/main/java/com/joyent/manta/monitor/JettyServerBuilderModule.java:[18,8] cannot access java.lang.Object
[ERROR]   bad class file: /modules/java.base/java/lang/Object.class
[ERROR]     class file has wrong version 55.0, should be 53.0
[ERROR]     Please remove or make sure it appears in the correct subdirectory of the classpath.

Retrieving muskie logs

These instructions are adapted from the comprehensive Manta Debugging Guide, with added clarification. See the debugging guide for more information on everything related to log-based debugging.

Log locations

Each zone maintains a log file for the current hour (a real-time log) at /var/log/muskie.log. At the top of every hour, the past hour's log file (now a historical log) is uploaded to the datacenter's manta at /poseidon/stor/logs/COMPONENT/YYYY/MM/DD/HH/SHORTZONE.log, where:

COMPONENT varies based on the component you’re looking for
YYYY, MM, DD, and HH represent the year, month, day, and hour for the entries in the log file
SHORTZONE is the first 8 characters of the zone’s uuid.

	#!/usr/bin/env python

	"""
	This script scans the current working directory for changes to .go files and
	runs `go test` in each folder where *_test.go files are found. It does this
	indefinitely or until a KeyboardInterrupt is raised (<Ctrl+c>). This script
	passes the verbosity command line argument (-v) to `go test`.
	"""