On server start on Ubuntu Server 15.10: MultipleCompilationErrorsException

[Zsar]

Starting the server like this (ReadMe line obsolete!): groovy AberOWLServer.groovy 10000

Error output attached: log.txt

Network conflict?

There are two network devices on that (virtual) machine:

• enp0s3 : DHCP-enabled VirtualBox NAT (internet access)
• enp0s8 : static IP VirtualBox host-only network (for browsing the service) Might it pick the wrong one? Should it then not more informatively complain about lack of internet access?

Note that the previous steps were all successful (in their internet accesses), so this is probably not the case.

Unlisted dependency?

Will try again with Ubuntu Desktop 15.10 and report back whether the issue persists. (I had previously used Ubuntu Desktop and advanced further than this step.)

[reality]

Hi,

This seems to be an issue with downloading the dependencies. I have experienced this before, and it seems to be an intermittent problem with http://mvnrepository.com/ (I think that perhaps they have load issues?)

Give it another try a little later and let me know if it persists!

[Zsar]

I see. Tried thursday (2016-02-11) and today (2016-02-16). Will try again in a few days.

May I suggest adding information to this and similar messages ("reason: could not connect to repository" or something along such lines; to point out it is not the local program that failed)?

[Zsar]

Note that within the last fifteen minutes I successfully started the server on a Ubuntu Desktop machine, then shutdown -P now that machine, started the Ubuntu Server machine and repeated the attempt.

This produced the original error on the Server machine. I do not think an online repository is to blame.

[Zsar]

The issue persists. It really does seem to be something about Ubuntu Server.

Is there a way to execute the command in some kind of "verbose" mode? Changing the line Logger.getRootLogger().setLevel(Level.ERROR) to Logger.getRootLogger().setLevel(Level.DEBUG) did not provide additional insight.

[reality]

Could you please post the version of Groovy you're using? You can get this by running "groovy --version"

[Zsar]

On both virtual machines (the one where it's working and the one where it's not): Groovy Version: 2.4.5 JVM:1.8.0_66-internal Vendor: Oracle Corporation OS: Linux Unsurprising, considering that both were installed in the same way on the same day.

I googled a bit for "groovy error grabbing grapes unresolved dependencies" and found that this and similar issues are pretty common, usually without solutions that work for everyone. ... Several people theorise that Groovy/grapes itself is to blame. It is apparently known as "notoriously unreliable". Well, in this particular case it is very reliably not working.

[reality]

Hi,

This is a bit of a difficult issue I've not been able to reproduce, but I have a couple of things it might be worth trying:

1. rm -rf ~/.groovy/grapes and try running the software again
2. Try placing the following in your ~/.groovy/grapeConfig.xml and re-run:

<ivysettings>
 <settings defaultResolver="downloadGrapes"/>
 <resolvers>
   <chain name="downloadGrapes">
     <filesystem name="cachedGrapes">
               <ivy
                   pattern="${user.home}/.groovy/grapes/[organisation]/[module]/ivy-[revision].xml"/>
                       <artifact
                           pattern="${user.home}/.groovy/grapes/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/>
     </filesystem>
           <!-- todo add 'endorsed groovy extensions' resolver here
           -->
                 <ibiblio name="codehaus"
                          root="http://repository.codehaus.org/"
                          m2compatible="true"/>
                 <ibiblio name="ibiblio" m2compatible="true"/>
                       <ibiblio name="java.net2"
                                root="http://download.java.net/maven/2/"
                                m2compatible="true"/>
   </chain>
 </resolvers>
</ivysettings>

[Zsar]

Tried only 1): no change. Tried only 2): no change. Tried 1) & 2): no change.

Note that no file ~/.groovy/grapeConfig.xml existed. I had to create it. I checked the Ubuntu Desktop system, and there neither does such a file exist: On both systems, the folder ~/.groovy only contained the folder grapes and nothing more.

[reality]

Yes, this file has to be created

[Zsar]

Interestingly, the not-working machine had files in its ~/.groovy/grapes directory, which the working one lacks - and which I deleted via 1).

Two of these were recreated: resolved-caller-all-caller-working10.[properties|xml]. The former seems to be a log file. The latter might or might not be interesting, containing the tokens named in the "Error grabbing Grapes" message. I attached it for convenience. resolved-caller-all-caller-working10.zip

I assume that in case of a successful execution, these would be temporary files deleted on completion.