[SOLVED] Site currently locked

Using Neos & Flow
1

Hey there,

our site is finally online and since today we have a problem in the backend. A red message appears at the top of the page when we select a new page. It says “An error occurred.”. There are no more information. We’re not able to edit anything. And the only thing I can find in the logs is this exception:

Exception #1355480641 in line 300 of /var/www/neos/Packages/Framework/Neos.Flow/Classes/Core/Booting/Scripts.php: Site is currently locked, exiting.
The current lock will expire after 90 seconds.

12 Neos\Flow\Core\Booting\Scripts::executeCommand(“neos.flow:core:compile”, array|16|)
11 Neos\Flow\Core\Booting\Scripts::initializeProxyClasses(Neos\Flow\Core\Bootstrap)
10 call_user_func(array|2|, Neos\Flow\Core\Bootstrap)
9 Neos\Flow\Core\Booting\Step::__invoke(Neos\Flow\Core\Bootstrap)
8 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
7 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
6 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
5 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
4 Neos\Flow\Core\Booting\Sequence::invoke(Neos\Flow\Core\Bootstrap)
3 Neos\Flow\Http\RequestHandler::boot()
2 Neos\Flow\Http\RequestHandler::handleRequest()
1 Neos\Flow\Core\Bootstrap::run()

Why is the page locked, what does it mean and where does it come from? Does anybody know? Sometimes I even can’t flush the Flow cache, I’ll get the same message on the command line.

We’re using Neos 3.2.0 on a Unix system with nginx and MySQL.

Kind regards,
Michael

2

The locking mechanism is there to avoid duplicate generation of the php-proxy classes. This should only occur once after each install/deployment and can be avoided during deployment ./flow flow:cache:warmup before switch.

Do you see multiple of those messages, or just one? What does the Data/Logs/System.log say?

3

Yes I see this message more than once. The only thing I can see in the logs is this…

Security.log

17-11-22 07:25:44 16370 172.30.200.9 INFO Flow Session Enra84jNeEmuiFKVgBcyT6NXurzsXm7J contains auth token Neos\Flow\Security\Authentication\Token\PasswordToken for provider Neos.Setup:Login. Status: no credentials given
17-11-22 07:25:44 16370 172.30.200.9 INFO Flow Session Enra84jNeEmuiFKVgBcyT6NXurzsXm7J contains auth token Neos\Flow\Security\Authentication\Token\UsernamePassword for provider Neos.Neos:Backend. Status: authentication successful
17-11-22 07:25:44 16370 172.30.200.9 INFO Flow Session Enra84jNeEmuiFKVgBcyT6NXurzsXm7J contains auth token Neos\Flow\Security\Authentication\Token\UsernamePassword for provider Flowpack.Neos.FrontendLogin:Frontend. Status: no credentials given

System.log

17-11-22 07:25:23 21916 INFO Flow Session: Changed session id from GiQcSKSo3GUxanVOqr1JfzBzncircach to Enra84jNeEmuiFKVgBcyT6NXurzsXm7J
17-11-22 07:26:19 7778 NOTICE Flow Router route(): No route matched the route path “autodiscover/autodiscover.xml”.
17-11-22 07:26:24 21916 NOTICE Flow Router route(): No route matched the route path “autodiscover/autodiscover.xml”.
17-11-22 07:27:37 16370 NOTICE Flow Router route(): No route matched the route path “autodiscover/autodiscover.xml”.
17-11-22 07:28:18 21916 NOTICE Flow Router route(): No route matched the route path “wp-login.php”.
17-11-22 07:29:17 16370 NOTICE Flow Router route(): No route matched the route path “EWS/Exchange.asmx”.

4

We’ve found the problem, it was a JS error. One of our developers made changes that lead to this error. Problem solved! :wink: