Issue implementing a certain number of custom modules

đź’¬ General Discussion
1

Hi everyone.
I’m having a problem in the local environment using vagrant with SuiteCRM 8.6.1 and PHP 7.3. After creating a certain amount of custom modules, it throws the following error in the console and everything stops working:

err
err1332Ă—85 45.4 KB

This seems to happen after deploying a fixed amount of custom modules, I don’t have the exact number (approximately between 20 and 30).
I have deleted some modules and redeployed them without problem, and when deploying a new module the problem occurs again.
It’s not a problem with any module configuration, as I’ve tried with different modules and the problem still occurs.
I suspect the problem is due to some limit configuration that prevents more than a certain amount of custom modules from being deployed.
Has anyone experienced something like this?
Thanks and regards!

2

Hi, welcome to the Community! :tada:

I would look for server-side logs, not browser errors.

In v8, the logs mentioned in that old blog post are found under directory public/legacy

3

Hi, thanks for your reply.

The only message I see in the log is:

PHP Fatal error: Uncaught Symfony\Component\Filesystem\Exception\IOException: Failed to remove directory “/var/www/html/public/…Q8R”: rmdir(/var/www/html/public/…Q8R): Text file busy in /var/www/html/vendor/symfony/filesystem/Filesystem.php:200\nStack trace:\n#0 /var/www/html/vendor/symfony/filesystem/Filesystem.php(159): Symfony\Component\Filesystem\Filesystem::doRemove()\n#1 /var/www/html/core/backend/Engine/Service/Extensions/ExtensionAssetCopy.php(98): Symfony\Component\Filesystem\Filesystem->remove()\n#2 /var/www/html/core/backend/Engine/Service/Extensions/ExtensionAssetCopy.php(64): App\Engine\Service\Extensions\ExtensionAssetCopy->cleanPublicExtensions()\n#3 /var/www/html/core/backend/Engine/Service/Extensions/ExtensionAssetCacheWarmupDecorator.php(88): App\Engine\Service\Extensions\ExtensionAssetCopy->copyAssets()\n#4 /var/www/html/vendor/symfony/http-kernel/Kernel.php(580): App\Engine\Service\Extensions\ExtensionAssetCacheWarmupDecorator->warmUp()\n#5 /var/www/html/core/backend/Kernel.php(124): Symfony\Component\HttpKernel\Kernel->initializeContainer()\n#6 /var/www/html/public/index.php(37): App\Kernel->init()\n#7 {main}\n thrown in /var/www/html/vendor/symfony/filesystem/Filesystem.php

And then it throws the following message indefinitely:

[core:notice] [pid 11008] AH00052: child pid 15649 exit signal Segmentation fault (11)

4

I don’t know, but check

  • if your ownerships and permissions are correct
  • if you have any software accessing SuiteCRM files, such as an anti-virus or a dropbox-style synchronization software
5

On Suite 8.6.x you can’t use PHP 7.3. You must upgrade to PHP 8.1 or 8.2.

6

Sorry for the mistake, the instance is running on PHP 8.2.11.
I’ll check the permissions but that doesn’t seem to be the problem. Everything works fine until about module number 20 is implemented.

7

It could be just php configuration limits. Check memory_limit, max_execution_time, upload_max_filesize and post_max_size. Also, you can allocate more CPU & memory for your vagrant. :white_check_mark:

8

I have checked and increased the values ​​of those parameters, I also assigned more resources to vagrant, and everything is still the same. I will continue trying and checking the server configuration parameters. If I find the solution I will let you know, and I will be on the lookout in case you think of something else to try.

9

update:
it seems the server is not picking up the changes in php.ini. I will fix that and try modifying the parameters again. I will report the results.

10

I have already managed to detect changes in php.ini, I have tried modifying the indicated values ​​and I have not yet been able to deploy a new module. The instance seems to be working correctly, but it is not possible to deploy a new module.
I will report if I have any news.
Thanks!