Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Real work allocatio...
 
Notifications
Clear all

Real work allocation field can't be registered

11 Posts
2 Users
0 Reactions
10.9 K Views
(@vporcelli)
Posts: 25
Active Member
Topic starter
 
[#2334]

Hi !
I try to fill in value in real work allocation field for a resource and when i register, the server doesn't respond (the request is still in progress...)
I have to close my browser and open it on again to continue working with Projeqtor.
Data are not registered.

This worked well few days ago and no update has been done on profileof the resource.

Moreover, it works well for other resources.
There isn't any trace in the logs.

Have you an idea ?

Thanks for your feedback !


 
Posted : 28 May 2015 13H17
(@babynus)
Posts: 14952
Member Admin
 

It seems you are facing the max_input_vars issue.
Search for "max_input_vars" for hints : you'll have to increase this value in php.ini.


 
Posted : 31 May 2015 1H01
(@vporcelli)
Posts: 25
Active Member
Topic starter
 

Hi,

Thanks for your answer.

We 've already increased "max_input_vars" to 4000 when we started working with Projeqtor.
We increased value to 5000 and reload Apache but problem still happens 🙁

It's strange and annoying because it works well for others resources !


 
Posted : 01 Jun 2015 11H05
(@babynus)
Posts: 14952
Member Admin
 

Maybe your php also uses suhosin module, you you should also change values for it :

max_input_vars = 4000
suhosin.post.max_vars = 4000
suhosin.request.max_vars =4000

 
Posted : 01 Jun 2015 11H28
(@vporcelli)
Posts: 25
Active Member
Topic starter
 

We installed suhosin, updated parameters but problem still hapens...


 
Posted : 01 Jun 2015 11H47
(@babynus)
Posts: 14952
Member Admin
 

Hi,

Can you check for error in browser console ?

If not error appears, please try and reproduce and wait several minutes, to be sure you got response from server.
Then check again log file.

You should have either an error in the log or in the browser console.


 
Posted : 01 Jun 2015 13H14
(@vporcelli)
Posts: 25
Active Member
Topic starter
 

Console screenshot attached.

Thanks.


 
Posted : 01 Jun 2015 20H23
(@babynus)
Posts: 14952
Member Admin
 

Error 500 : it means you have some serious PHP error.
You should find error in the PHP or Apache Log file.


 
Posted : 01 Jun 2015 20H26
(@vporcelli)
Posts: 25
Active Member
Topic starter
 

Hi,

Bellow Apache log files

[Thu May 28 08:39:28 2015] [error] [client 10.10.11.21] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /pvo/projeqtor/model/persistence/SqlElement.php on line 2183, referer: http://projeqtor.selsia.fr/view/main.php
[Thu May 28 08:44:14 2015] [error] [client 10.10.11.21] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /pvo/projeqtor/model/Parameter.php on line 564, referer: http://projeqtor.selsia.fr/view/main.php
[Thu May 28 08:44:15 2015] [notice] child pid 18331 exit signal Segmentation fault (11)
[Thu May 28 08:49:59 2015] [error] [client 10.10.11.21] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /pvo/projeqtor/tool/projeqtor.php on line 309, referer: http://projeqtor.selsia.fr/view/main.php
[Thu May 28 08:52:34 2015] [error] [client 10.10.11.21] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /pvo/projeqtor/model/persistence/SqlElement.php on line 2047, referer: http://projeqtor.selsia.fr/view/main.php


 
Posted : 02 Jun 2015 16H38
(@babynus)
Posts: 14952
Member Admin
 

You're in Timeout !

Try and extend max_execution_time in php.ini.
Your value is 30, replace it with 300 (5 mn), just to see if it fixes the issue

But it is not normal it is so long.
Maybe you have issue with database connection.
For instance, if you are on Windows with local database, try and replace dbHost from "localhost" to "127.0.0.1" (this solves a DNS issue with MySql on Windows)


 
Posted : 02 Jun 2015 16H46
(@vporcelli)
Posts: 25
Active Member
Topic starter
 

After updated timeout, record was registered with correct time response.
We replace max_execution_time on again with 30 and all is ok !

Very odd but ok !

Thanks. 🙂


 
Posted : 02 Jun 2015 17H19
Share:

Scroll to Top