Installation stuck on 45%
By Robert E Wallace on Monday, 24 July 2017
Posted in Installation Issues
Replies 3
Likes 0
Views 1K
Votes 0
Hi,

I face the problem with 45% installation freeze.
All the requirements form the starting point of the installation are met.
No errors in browser console or php error_log (I enabled development mod).
I also find that this is kind of known issue and when I follow the steps described in the 'Common Installation Issues' it works fine. But this is not an option for us in our production environment.
The version I am using is 5.1.8. Unfortunately I can't give you access to the machine because of a company policy.
What I observe is that this issue happens only in PHP < 5.6, so my PHP is 5.4 and I have the 45% freeze when I tested it with latest PHP 7.1.* there was not issue.
The strange is that the log is empty and there is no error.
Do you have fix for this issue or do you have more details for it?
It's a problem only on fresh install, on upgrade there is no issue.

Thanks,
Georgi Velinov
Hi there,

It would be best if you can provide us with your backend access in order for us to get the exact ideas why it stops on 45% or maybe you can ask your web hosting service provider to enabled the error reporting on your site as it might your web hosting service provider have disabled it.

Thanks for you understanding
Abdul Warith Norudin
·
Monday, 24 July 2017 19:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok, as I said my company policy doesn't allow me to give you access.
Also, we do not use hosting providers, I manage the server by my own and PHP error reporting, error log and display errors are all enabled. I am able to see all errors, warnings and notices.
There are no errors in error log file or in the browser console (form the ajax call).
I also increase the memory limit for PHP and MySQL.
The freeze is on "Initializing Post Clean Up".
Could you tell me what cause this behavior which is marked as 'Common Installation Issues' by you?
Do you have another solution for it (different form re-installing after TRUNCATE TABLE `#__easyblog_acl_group` - it's not an option for us)?

Thanks,
Georgi Velinov
Robert E Wallace
·
Friday, 28 July 2017 16:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

It is required for us to access your site in order to get the exact issues why you hit those errors

By the way, have you restarted your server and enabled 'Error Reporting' to maximum on your site? It should shown you those error if you open your console from the start.

Please advice.
Abdul Warith Norudin
·
Friday, 28 July 2017 17:21
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post