2.2 upgrage to 2.2.1 issue

[rigu12]

1. in magento2.2
2. php7,1

1. I don't know why i in admin > setup upgradd >Update application is running ->will be show error upgrade. Did't suggest anything wrong?
2. i re-installed new 2.2.0 (no date) try to test, upgrade to 2.2.1. still have this problem in upgrade system

1. How to solve this issue?

1.

Update application is not running
Error in Update!
Please refer to documentation Doc link to perform manual rollback.
To attempt automatic rollback, please click the "Rollback" button.
[Module 'Magento_******':
Running schema recurring...Source class "\SignifydAvsDefault" for "SignifydAvsDefaultMapper" generation does not exist.
[2017-11-10 11:19:32 UTC] Job "setup:upgrade {"command":"setup:upgrade"}" has been successfully completed
[2017-11-10 11:19:32 UTC] Job "setup:static:regenerate []" has started
[2017-11-10 11:19:32 UTC] Cleaning generated files...
[2017-11-10 11:19:32 UTC] Clearing cache...
[2017-11-10 11:20:12 UTC] Cleaning static view files
[2017-11-10 11:20:12 UTC] Job "setup:static:regenerate []" has been successfully completed
[2017-11-10 11:20:12 UTC] Job "setup:maintenance:disable []" has started
Disabled maintenance mode
[2017-11-10 11:20:12 UTC] Job "setup:maintenance:disable []" has been successfully completed

[Tom Robertshaw]

I see that you've already posted to github too (https://github.com/magento/magento2/issues/12174). I think that's the most appropriate place for this issue and there's someone else that appears to have experienced it too so hopefully someone from the Magento engineering team will be in touch soon. 

[rigu12]

@Tom Robertshaw

Hello, They said ask this issue in there and then closed my topic......

and

Steps to reproduce

1. magento web wizard -> system upgrade FAIL on last step: maintenance disable
   it's made a rollback loop

The Update to 2.2.1 is completed but now it hangs on the error with the rollback message. How to solve this issue?

[fabianus]

I do have the exact same problem. 

The update finished, but this roll back message remains

[fabianus]

Solution: just had to delete/rename this file: 

/var/.update_error.flag

[rigu12]

i upgraded, but becoming very slowly, do you know why? or need run some command? thank you

[thomas911]

I had the same problem, it came from CRON that was executed in ROOT rather than user !