search

modxcms / revolution

MODX Revolution - Content Management Framework
https://modx.com/
GNU General Public License v2.0
1.36k stars 529 forks source link

MODX3: Error 503: Service temporarily unavailable after the installation #14844

Closed Ruslan-Aleev closed 4 years ago

Ruslan-Aleev commented 4 years ago

Bug report

Summary

Immediately after the NEW installation is completed, after redirecting to the login page, an error appears: Error 503: Service temporarily unavailable

503

This is solved by reloading the page, but the behavior is strange. I tried to install 3 times, and through the console, and the night build.

Environment

MODX 3, php7.1

Server information: Ubuntu Apache: 2.4.10 MySQL: 5.7.21-20-beget Nginx: 1.13.4 Perl: 5.26.1 PHP: 5.2 5.3 5.6 7.0 7.1 7.2 7.3 Python: 2.7

Ibochkarev commented 4 years ago

The problem does not reproduce in the next environment:

JoshuaLuckers commented 4 years ago

After you run setup, and before going to the manager login, does the config file exist (core/config/config.inc.php)?

Ruslan-Aleev commented 4 years ago

I will test later, and take a closer look.

Ruslan-Aleev commented 4 years ago

I did not manage to catch the moment, but sometimes the config.inc.php file is not created completely, as it seems to me. This does not always happen, but sometimes it happens, at 50% for me.

It’s not clear, but here is what it looks like during installation (after page reload the problem disappears):

503

JoshuaLuckers commented 4 years ago

@Ruslan-Aleev are you still able to reproduce this error? And if yes, does it also happen when you wait a bit before clicking next after installing?

Ruslan-Aleev commented 4 years ago

are you still able to reproduce this error?

I have not noticed this bug lately.

does it also happen when you wait a bit before clicking next after installing?

In my opinion, the wait time does not depend much, but I'm not sure.

This is not a bug, but maybe we should add some kind of check for config.inc.php if the error will happen again?

Ruslan-Aleev commented 4 years ago

I think it’s worth closing this issue now. In the future, if the error will happen again, we need to come up with something :)