Updating to latest release

[alexdobo]

Hey!
I've been running version 1.10, and I wanted to update to the latest release (1.93).
To do this, I followed the instructions on the Heroku Deployment guide.
Now I'm getting an Application Error (I wish I could tell you more, but that's all it says)

I have a feeling I may just need to delete the database and start from scratch, but for next time, how do I correctly update to the latest release?

[cbellone]

Hi @alexdobo,

oops, I think there's an error on the website. The latest release is 1.10.1, you can download it from here: https://github.com/exteso/alf.io/releases
just try to install this version as specified in the heroku how-to, and everything should run as expected.

I guess that the problem now is that you're trying to install a version (1.9.3) which is actually older than the current installed (1.10), and somehow the auto schema update doesn't like that.
Could you please extract all relevant logs (see https://devcenter.heroku.com/articles/logging#log-retrieval , please remove all sensitive data from there) and attach them to this issue?
Maybe we can fix this error in next release.

Anyway, we'll update the website asap. Sorry for that.
Celestino

[alexdobo]

I've gotten the latest release as per your instructions.
Here is the log with sensitive data removed:
2017-04-09T09:58:21.441779+00:00 heroku[web.1]: Starting process with command java $JAVA_OPTS -jar alfio-1.10.1-boot.war $JAR_OPTS
2017-04-09T09:58:23.547920+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2017-04-09T09:58:23.551447+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx350m -Xss512k -Dfile.encoding=UTF-8
2017-04-09T09:58:26.645749+00:00 app[web.1]: 09:58:26.641 [main] INFO alfio.config.SpringBootLauncher - requested profiles
2017-04-09T09:58:28.298379+00:00 app[web.1]: _ _ __ _
2017-04-09T09:58:28.298388+00:00 app[web.1]: / \ | |/ |() ___
2017-04-09T09:58:28.298389+00:00 app[web.1]: / _ \ | | |_ | |/ _
2017-04-09T09:58:28.298390+00:00 app[web.1]: / ___ | | || | () |
2017-04-09T09:58:28.298390+00:00 app[web.1]: // __||()|___/
2017-04-09T09:58:28.298391+00:00 app[web.1]:
2017-04-09T09:58:28.298392+00:00 app[web.1]: >> powered by Spring Boot
2017-04-09T09:58:28.298418+00:00 app[web.1]:
2017-04-09T09:58:29.304291+00:00 app[web.1]: 09:58:29.304 [main] INFO alfio.config.SpringBootLauncher - Starting SpringBootLauncher on e19f06a7-555c-4b5b-9f95-dc282584f710 with PID 4 (/app/alfio-1.10.1-boot.war started by u50954 in /app)
2017-04-09T09:58:29.321967+00:00 app[web.1]: 09:58:29.321 [main] INFO alfio.config.SpringBootLauncher - The following profiles are active: spring-boot
2017-04-09T09:58:33.955896+00:00 app[web.1]: 09:58:33.955 [main] INFO alfio.config.DataSourceConfiguration - Detected cloud provider: HEROKU, database: PGSQL
2017-04-09T09:58:43.238708+00:00 app[web.1]: 09:58:43.238 [main] INFO alfio.config.DataSourceConfiguration - Quartz scheduler configured to run!
2017-04-09T09:58:48.984797+00:00 app[web.1]: 09:58:48.984 [main] INFO alfio.config.ConfigurationStatusChecker - performing migration from previous version, if any
2017-04-09T09:58:49.190817+00:00 app[web.1]: 09:58:49.190 [main] INFO alfio.config.ConfigurationStatusChecker - done.
2017-04-09T09:58:49.191137+00:00 app[web.1]: 09:58:49.191 [main] INFO alfio.config.ConfigurationStatusChecker - initialized alf.io version 1.10.1
2017-04-09T09:58:49.647935+00:00 app[web.1]: 09:58:49.647 [main] INFO alfio.config.SpringBootLauncher - Started SpringBootLauncher in 22.466 seconds (JVM running for 26.096)
2017-04-09T09:58:49.648568+00:00 app[web.1]: 09:58:49.648 [main] INFO alfio.config.SpringBootLauncher - active profiles: spring-boot
2017-04-09T09:59:42.263396+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/admin" host=website.com request_id=a90c6fae-0303-4b93-bbbb-b641a36949dd fwd="1.2.3.4" dyno= connect= service= status=503 bytes= protocol=https
2017-04-09T09:59:51.476574+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 90 seconds of launch
2017-04-09T09:59:51.476696+00:00 heroku[web.1]: Stopping process with SIGKILL
2017-04-09T09:59:51.790646+00:00 heroku[web.1]: State changed from starting to crashed
2017-04-09T09:59:51.776343+00:00 heroku[web.1]: Process exited with status 137
2017-04-09T09:59:53.616030+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/admin" host=website.com request_id=e8586ebf-4ca1-4074-bbdc-83b3d426f29f fwd="1.2.3.4" dyno= connect= service= status=503 bytes= protocol=https

[cbellone]

that's weird.
In our test deployment, I see:
2017-04-09T10:24:50.056067+00:00 heroku[web.1]: Starting process with command java -Dserver.port=39550 $JAVA_OPTS -jar alfio-*-boot.war
while the corresponding line in your log states:
2017-04-09T09:58:21.441779+00:00 heroku[web.1]: Starting process with command java $JAVA_OPTS -jar alfio-1.10.1-boot.war $JAR_OPTS

Did you save the Procfile deployment descriptor in the same directory where you executed the command heroku deploy:jar? It looks like the deployment process is ignoring it...

[alexdobo]

That fixed it!
I was missing the Procfile
Cheers