500 Server Error SugarEnterprise v12.3.0 - Cannot load DB manager

Clinton Canarias

This may be a simple directory permissions issue - that is what I would check first.

Although I use VirtualBox not Vagrant (and Enrico's excellent SugarDockerized [*] ) I often get a similar issue when I have forgotten to update the directory permissions. My experience with restoring clones from downloaded cloud instances is that they always unpack with directory permissions only set for the owner. I always get similar errors until I remember to allow at least Read and Execute permissions to the group and other users. Without Execute permissions the Apache user cannot enter directories to read the contents. In *nix the following at the Sugar root directory should set the permissions for the "other" users:

chmod -R o+rX *

For those not familiar with *nix or bash, using an upper case "X" for the execute bit sets that only for directories and the -R flag sets the permissions recursively. As far as I know up to now, in a default installation no files need execute permissions and for safety none should be set.

You may also need to use a:

sudo chown -R {username} *

to update the ownership of the file tree depending on the setup of your environment.

This is what I would try first when seeing the errors you are.

Thanks,

JH.

[*] Like you I find the 512Mb is not enough for a 12.3 instance. SugarDockerized uses images for the default PHP container that are set with 512Mb by default for the memory setting. I found I need to alter the Dockerfile in the stacks path to up the memory to 1Gb and use the "local-build" yaml file to pull a container with enough memory to allow the 12.3 instance to function.

Clinton Canarias

This may be a simple directory permissions issue - that is what I would check first.

Although I use VirtualBox not Vagrant (and Enrico's excellent SugarDockerized [*] ) I often get a similar issue when I have forgotten to update the directory permissions. My experience with restoring clones from downloaded cloud instances is that they always unpack with directory permissions only set for the owner. I always get similar errors until I remember to allow at least Read and Execute permissions to the group and other users. Without Execute permissions the Apache user cannot enter directories to read the contents. In *nix the following at the Sugar root directory should set the permissions for the "other" users:

chmod -R o+rX *

For those not familiar with *nix or bash, using an upper case "X" for the execute bit sets that only for directories and the -R flag sets the permissions recursively. As far as I know up to now, in a default installation no files need execute permissions and for safety none should be set.

You may also need to use a:

sudo chown -R {username} *

to update the ownership of the file tree depending on the setup of your environment.

This is what I would try first when seeing the errors you are.

Thanks,

JH.

[*] Like you I find the 512Mb is not enough for a 12.3 instance. SugarDockerized uses images for the default PHP container that are set with 512Mb by default for the memory setting. I found I need to alter the Dockerfile in the stacks path to up the memory to 1Gb and use the "local-build" yaml file to pull a container with enough memory to allow the 12.3 instance to function.

Hi John Hawkins,

Thank you for your response. I already changed the permissions and owner of the files still did not work. But I was able to fix this issue by removing the db configuration below in config.php.

I don`t know what is the use of this configuration, but when I check my on-premises sugar instance config.php, this configuration is not available. Right now, I am currently exploring what would be the effect by removing of this configuration.

Regards,

Clinton Canarias