Forum

Ask, reply and learn. Join the community of Akaunting.

New Discussion

Update stopped from 2.0.27 to 2.1.0

Dirk Schiemenz   ( User )

Commented 3 years ago

Hello. I managed to run my update from 2.0.26 to 2.0.27 without any issues. Now I started the update from 2.0.27 to 2.1.0. The update runs and runs without any error message. My log below:

[2021-01-29 13:33:58] production.INFO: Running finish command for core update...
[2021-01-29 13:33:58] production.DEBUG: Console command:: '/usr/local/bin/php' artisan update:finish core 1 2.0.27 2.0.26
[2021-01-29 09:33:59] production.INFO: Firing update in event 2.1.0
[2021-01-29 13:34:06] production.DEBUG: Console command:: '/usr/local/bin/php' artisan help
[2021-01-29 13:37:32] production.DEBUG: Console command:: '/usr/local/bin/php' artisan update core 1 2.1.0
[2021-01-29 09:37:32] production.INFO: Downloading core update...
[2021-01-29 09:37:53] production.INFO: Unzipping core update...
[2021-01-29 16:49:11] production.DEBUG: Console command:: '/usr/local/bin/php' artisan help
[2021-01-29 20:46:24] production.INFO: Downloading core update...
[2021-01-29 20:46:45] production.INFO: Unzipping core update...

I tried to restart the update after 5 hours. Same result. It runs for ever without any result.
Log looks like this:
[2021-01-30 00:46:06] production.DEBUG: Console command:: '/usr/local/bin/php' artisan help
[2021-01-30 00:46:22] production.DEBUG: Console command:: '/usr/local/bin/php' artisan update core 1 2.1.0

What could be the issue?

Leonardo Gomes   ( User )

Commented 3 years ago

Hello.

Take a look into this thread: https://akaunting.com/forum/discussion/installation-update/missing-documents-table

Dirk Schiemenz   ( User )

Commented 3 years ago

Hello Leonardo,
I have seen this thread, but can't confirm that it is the same issue. I installed a new version 2.1.0 on my server and run the update to 2.1.1. Some issue it stops by 60% without any error. If I reload the page and start update again, it was running smoothly and now it is updated to 2.1.1.

But to update 2.0.27 to 2.1.0 wasn't successful.

Please login or register to leave a response.

Showing 1 to 3 of 3 discussions