Closed paolodedios closed 5 years ago
This would be caused by a mismatch between a DuperModel reference in VESPA_HOME/conf/configserver-app/services.xml vs the location of the DuperModel.class in the VESPA_HOME/conf/configserver-app/components/service-monitor.jar bundle. My initial sanity-check on this looked fine, so the next step for me will be to reproduce your case by install RPM etc.
The RPM also looks good - how did you start the config server?
What's the output of grep DuperModel /opt/vespa/conf/configserver-app/services.xml
and md5sum /opt/vespa/conf/configserver-app/components/service-monitor.jar
?
The grep command did not return a result.
$grep DuperModel conf/configserver-app/services.xml
Here is the output of md5sum.
$ md5sum /opt/vespa/conf/configserver-app/components/service-monitor.jar
df5b50a006361e37cdd627e1f06b597d /opt/vespa/conf/configserver-app/components/service-monitor.jar
After installation of the 6.319.4 RPM the DuperModel is defined as:
# grep DuperModel /opt/vespa/conf/configserver-app/services.xml
<component id="com.yahoo.vespa.service.monitor.application.DuperModel" bundle="service-monitor" />
So somehow your services.xml is not the one from 6.319.4.
Thanks for the tip. Turns out my copy of /opt/vespa/conf/configserver-app/services.xml is a couple of versions behind 6.319.4. After updating the file with the DuperModel, the configserver starts normally now.
Vespa 6.319.4 open source RPM builds throw an IllegalStateException on startup. Version 6.318.15 and earlier do not exhibit this behavior.