Something else to consider rolling into this one: it appears (from https://groups.google.com/forum/#!topic/dataverse-community/34FWJIlYXNo and elsewhere) that there are cases where the installer should be aborting (due to problems with database configuration, application deployment, etc), but doesn't actually abort.

ping @4tikhonov - you mentioned on the call that you were having some installer issues and I pointed you to this issue as a place to put some specifics.

We're having trouble to run on Google Cloud new SOLR Docker image created from this build https://github.com/IQSS/dataverse-docker/tree/master/solr7

We've found the solution for this problem with new SOLR.
For the deployment on Google Cloud both SOLR_HOST and SOLR_PORT should be set to those values:

• "SOLR_HOST=solr"
• "SOLR_PORT=8983"

Without SOLR_PORT we're getting error messages as somehow SOLR_PORT is coming from cloud configuration:
bin/solr: line 2068: /usr/local/solr/solr-7.3.0/bin/solr-tcp://10.31.251.78:8983.pid: No such file or directory
bin/solr: line 2065: /usr/local/solr/solr-7.3.0/server/logs/solr-tcp://10.31.251.78:8983-console.log: No such file or directory

@4tikhonov could you let us know which version (or which commit) you're using the installer from?

@pameyer it's latest one, 4.9.2

@4tikhonov thanks

@pdurbin where are you seeing that path?
short answer is no, we are not doing this on purpose.

@landreev this was as of c90f762 on my Mac. I'll attach the output from the run: installer-run-c90f762-pdurbin-mac.txt

with the smtp port - i can add that easily; to get it to work with smtp.google though, doesn't it need more configuration, other than the different port?
with the EZID, I'll implement what was discussed during the meeting - switch the default to datacite and add the 2 lines telling them to register for an account. I will test that it is actually possible to do that and use that setup to publish in the test doi namespace... if it does NOT work easily like that, I would prefer to keep the ezid setup and defer this until 4.10; the ezid config has the advantage of working, and I don't think ezid is going away abruptly any time soon.

@pdurbin Do you have a default.config file sitting around?

(but yeah, I'm willing to invest a bit of extra work into making it possible to have the installer work with google's smtp out of the box; it would be useful to a lot of people...)

@landreev whoops! I do. Sorry! Here it is:

$ cat default.config
HOST_DNS_ADDRESS	localhost
GLASSFISH_DIRECTORY	/home/glassfish/glassfish4
MAIL_SERVER	localhost

As you're changing installation folders please consider to move files folder to docroot containing logos. We've discovered limitation of Google Cloud to mount 2 persistent volumes in the same time (one to keep files and second to keep pictures from logos folder).

After I moved files and logos to docroot it's started to work with persistent volume to keep all stuff that users/admins creating.

@4tikhonov sorry, this was my mistake. We are not changing the default installation folder. I had a default.config file that was being read.

Hello !

I just ran into this problem (I am on Linux). I tried pulling the last version of develop, but had this problem, so @pdurbin asked me to use the 4966-installer-fixes branch and ... I still has the issue.

I attach my glassfish logs.
server.log.txt

And an extract of the script error:

Attempting to deploy the application.
Command line: /usr/local/glassfish4/bin/asadmin deploy ../../target/dataverse-4.9.2.war
remote failure: Error occurred during deployment: Exception while deploying the app [dataverse-4.9.2] : Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : org.postgresql.ds.PGPoolingDataSource
Error Code: 0. Please see server.log for more details.
Command deploy failed.
Failed to deploy the application! WAR file: ../../target/dataverse-4.9.2.war.
(exit code: 256)
Aborting.

@landreev I asked @rmo-cdsp to try the "installer fixes" branch because it worked for me. He's on Linux, if it matters. He (Romain) has code written for NESSTAR import (#4593) and is trying to merge the latest from develop before making a pull request. In IRC I've been trying and failing to help him get a working dev environment set up.

I made a couple tiny tweaks to docs and comments (no code changes) and I'm moving this to code review. I didn't execute any code but I did try this branch last week on my Mac (I don't think I wrote down the commit) and it worked fine. @rmo-cdsp and I with help from @pameyer and @donsizemore worked through his installation woes in IRC and he's all set now. Phew.