Published Module Builder ZIP installation stuck at 80% with no logs

Hi Artis, 

Is there any error in the PHP error log on the server? It could be that the clone runs into the memory limit of PHP for example which should be indicated in those logs. 

Let me know if there was any FATAL error that could explain this. 

Thanks,

Dennis

Hi Dennis,

I have just doubled PHP memory and execution time limits to what you can see in this screenshot, restarted apache2 and it still does not work.

Nothing at all pops into any PHP error log or SugarCRM log when trying to install this module.

I no longer have this issue, I later rebuilt my combined packages (Studio customisation exported + Module Builder published + custom code all in one) and did not have this issue anymore. If anyone else comes across this issue, it may very well be that your manifest.php needs more cleaning up as Studio and Module Builder create an excessive amount of extra files that may not be necessary for your use case.

I am facing same issue how can i rebuilt combined package ?

I have checked error log and found below error.

Error :

Session lock for user id seed_sally_id was held for 2 seconds which is longer than the maximum of 1 seconds. Request details: SERVER_NAME

I don't think the session lock has anything to do with this Module Loader error.

By combined package I mean I manually merged the files that you get when you do the following:

• Create a custom module in Module Builder and publish it
• Deploy/install the custom module, customise it in Studio and then export the Studio customisations
• Create custom code in a package that you would install through Module Loader

They all have their own manifest.php files,  so I combined the $installdefs arrays of all of them into one, removed excess generated language files, etc. and packaged it up as one customisation with one manifest.php file.

I don't think the session lock has anything to do with this Module Loader error.

By combined package I mean I manually merged the files that you get when you do the following:

• Create a custom module in Module Builder and publish it
• Deploy/install the custom module, customise it in Studio and then export the Studio customisations
• Create custom code in a package that you would install through Module Loader

They all have their own manifest.php files,  so I combined the $installdefs arrays of all of them into one, removed excess generated language files, etc. and packaged it up as one customisation with one manifest.php file.

Hi Artis,

Thanks for reply I have investigated more and found that recently this issue occurred in Sugar 7 and Sugar 8 we can not install any package in Sugar it stops at 80%

Can you please try at your end i got below error now.

And all the packages are previously working and not working currently and stop at 80% no change in package.

Error :

Exception in Controller: Elastica\Exception\ResponseException: no such index [index: 08518a3f6bc3d760af495ad6a93718f8_shared] in /var/www/sugar/vendor/ruflin/elastica/lib/Elastica/Transport/Http.php:179 Stack trace:

I don't have trouble installing customisations anymore. That error looks as though you need to run a re-index of global search for some reason.