When starting the search ranking check tool Serposcope, you can specify a conf file, but I’ll introduce the points to check when the configuration is not loaded.

Conclusion: Wrong order of -Dserposcope.conf=

[NG Case] -Dserposcope.conf after -jar

$ java -jar /path/to/serposcope-2.6.0.jar -Dserposcope.conf=/path/to/serposcope.conf
starting serposcope service
[2017-04-06 19:02:08,089] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.version          : 2.6.0
[2017-04-06 19:02:08,090] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.datadir          : /Users/username/serposcope
[2017-04-06 19:02:08,091] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.logdir           : /Users/username/serposcope/logs
[2017-04-06 19:02:08,091] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.db.url           : jdbc:h2:/Users/username/serposcope/db;MODE=MySQL
[2017-04-06 19:02:08,091] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.db.debug         : false
[2017-04-06 19:02:08,091] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.listenAddress    : 0.0.0.0
[2017-04-06 19:02:08,091] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.listenPort       : 7134
[2017-04-06 19:02:08,140] [NinjaJetty] WARN  o.e.j.s.h.ContextHandler - Empty contextPath
[2017-04-06 19:02:08,149] [NinjaJetty] INFO  s.l.MyNinjaJetty - Trying to start jetty vnull on 0.0.0.0:7134
[2017-04-06 19:02:08,301] [NinjaJetty] INFO  c.Module - now logging to /Users/me/serposcope/logs/2017-04-06.log

[OK Case] -Dserposcope.conf before -jar

$ java -Dserposcope.conf=/path/to/serposcope.conf -jar /path/to/serposcope-2.6.0.jar
starting serposcope service
[2017-04-06 19:03:44,007] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.version          : 2.6.0
[2017-04-06 19:03:44,009] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.datadir          : /Users/username/serposcope
[2017-04-06 19:03:44,009] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.logdir           : /Users/username/serposcope/logs
[2017-04-06 19:03:44,009] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.db.url           : jdbc:mysql://localhost/serposcope_db?user=serposcope_user&password=serposcope_pass&allowMultiQueries=true
[2017-04-06 19:03:44,009] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.db.debug         : false
[2017-04-06 19:03:44,009] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.listenAddress    : 0.0.0.0
[2017-04-06 19:03:44,009] [NinjaJetty] INFO  c.SerposcopeConf - serposcope.listenPort       : 7134
[2017-04-06 19:03:44,059] [NinjaJetty] WARN  o.e.j.s.h.ContextHandler - Empty contextPath
[2017-04-06 19:03:44,073] [NinjaJetty] INFO  s.l.MyNinjaJetty - Trying to start jetty vnull on 0.0.0.0:7134
[2017-04-06 19:03:44,261] [NinjaJetty] INFO  c.Module - now logging to /Users/me/serposcope/logs/2017-04-06.log

It seems the problem was not understanding the order of java command options well.

The Serposcope official documentation Install instructions | serposcope specifies the -Dserposcope.conf option in the correct order, so if you follow the official documentation, there shouldn’t be any particular problems.

That’s all from the Gemba.