chmod errors after 5.5 installation

jwargo · #1 2010-01-08, 12:35 AM

I've been having a lot of trouble getting the upgrade wizard to work on my server so I've finally given up and whacked the whole installation and installed a clean copy of 5.5. After the installation completes, I get a page with a bunch of warnings indicating that the chmod function wasn't working as it tried to change the permissions on the includes folder. When opening the SugarCRM home page I get all of the text for the home page, but none of the layout and the top of the page has the following error:

Warning: chmod() [function.chmod]: Permission denied in /hermes/web09/b1333/moo.mcnell/sas/crm/include/utils/sugar_file_utils.php on line 196

Which is very similar to the multitude of errors I got at the end of the installation.

Can someone please help me understand why I'm getting this error and how to fix it?

salesagility · #2 2010-01-08, 05:53 AM

you're right - these are permissions issues. to prove that your installation works, chmod -R 777 yoursugarrootdirectory

if that works then apply the correct permissions

jwargo · #3 2010-01-16, 06:29 PM

OK, I whacked the database and file structure and did a completely clean installation. After I uploaded the files, I followed the instructions for setting file and directory permissions. At the conclusion of the upgrade, I get the following page of errors:

Creating Sugar configuration file (config.php)

Creating Sugar application tables, audit tables and relationship metadata

Warning: chmod() [function.chmod]: Permission denied in /hermes/web09/b1333/moo.mcnell/sas/crm/include/utils/sugar_file_utils.php on line 196

DELETED A BUNCH OF REPEATED ERRORS HERE

Warning: chmod() [function.chmod]: Permission denied in /hermes/web09/b1333/moo.mcnell/sas/crm/include/utils/sugar_file_utils.php on line 196
.

Creating default Sugar data

Creating default users... done
Creating default scheduler jobs... done

The setup of Sugar 5.5.0 is now complete!
Total time: 12.5536599159 seconds.
Approximate memory used: 20145820 bytes.

So I went back in and set all permissions (recursively - doing all subdirectories as well) to 777 using FileZilla version 3.3.1. When I try to access index.php, I get the following error:

"The server encountered an unexpected condition which prevented it from fulfilling the request.
The script had an error or it did not produce any output. If there was an error, you should be able to see it in the error log. "

It seems to be trying to set the time zone (http://www.singinasong.com/crm/index...on=SetTimezone) when it generates that error.

Just for grins, I went back in and set permissions to 775 for the specific folders listed in the documentation. I get the same error:

"The server encountered an unexpected condition which prevented it from fulfilling the request.
The script had an error or it did not produce any output. If there was an error, you should be able to see it in the error log. "

I don't know what I could be doing wrong here. When I look in the server logs, I don't see anything being generated when the internal error happens.

jwargo · #4 2010-01-25, 11:34 PM

I could really use some help here. Does anyone have any other suggestions?

Angel · #5 2010-01-25, 11:47 PM

Did you try the phpinfo() trick referenced here: http://cheleguanaco.blogspot.com/200...lified_19.html ?

mapm · #6 2010-01-26, 01:30 AM

Can you post some more information about software and versions used? (Linux Ubuntu?Windows?MySQL...)

rmaxwell · #7 2010-01-29, 09:21 PM

JWargo: I see from the path to the files in the error message that you're hosted on FatCow. I'm hosted on FatCow as well and have similar problems. There is something about file permissions and group ownership that cannot be changed and users don't have access to because they don't give us shell access (?!@#!#%>@$%#$%)

The only way I've found around these errors is to edit the sugar_file_utils.php in the following way:
Around line 196 of that file you'll find the following code:

if(isset($mode) && $mode > 0){
return chmod($filename, $mode);
}else{

Replace this with:

if(isset($mode) && $mode > 0){
// return chmod($filename, $mode);
return true;
}else{

That will get rid of the endless CHMOD PERMISSION DENIED error messages.

As to the error 500: chmod the directory where sugar lives to "755" but DO NOT APPLY RECURSIVELY

This will let you do almost everything you need to in Sugar.

Let me know if you figure out how to use the Upgrade Wizard, as that still dies in an error 500 for me.

Also: if anyone with more knowledge of Sugar can tell me how to get around the stupid need for the 755 permissions, or the error 500 when running the Upgrade Wizard, please let me know (upgradeWizard.log dies after "Starting file permission check..." with no other messages)

jwargo · #8 2010-02-08, 12:36 AM

Thanks for the help. I plugged away at this for a long time then gave up and called FatCow. They escalated me and the guy I worked with couldn't get InstallCentral (their internal package installer) to install 4.4 and when he tried the 5.5 install he couldn't get it to work as well. So, he opened a ticket and escalated it since no version was working.

After a few days, they sent me a message indicating that they were able to get 4.4 running, but REFUSE to tell me how they did it or provide any information about how to get 5.5 running. Frustrating - I love FatCow, but this is ridiculous.

OK, I followed your instructions and was able to 'hack' around the chmod problem in the sugar_file_utils.php. Thanks for that. It seems to be running now, but the screen doesn't look right. See attached screen shot.

nywebshop · #9 2010-02-09, 10:27 AM

Quote:

Originally Posted by jwargo

Thanks for the help. I plugged away at this for a long time then gave up and called FatCow. They escalated me and the guy I worked with couldn't get InstallCentral (their internal package installer) to install 4.4 and when he tried the 5.5 install he couldn't get it to work as well. So, he opened a ticket and escalated it since no version was working.

After a few days, they sent me a message indicating that they were able to get 4.4 running, but REFUSE to tell me how they did it or provide any information about how to get 5.5 running. Frustrating - I love FatCow, but this is ridiculous.

OK, I followed your instructions and was able to 'hack' around the chmod problem in the sugar_file_utils.php. Thanks for that. It seems to be running now, but the screen doesn't look right. See attached screen shot.

I got the similar problem like you Jargo.
The screen looks exactly the same, have tried almost everything, but can't figure out how to fix this error...

BR
Mogens

katzlbt · #10 2010-02-09, 10:53 AM

The problem is that cache/themes/<ThemeName> is created with permissions
drwxrws---
instead of
drwxr-xr-x
so ..
chmod g-s cache/themes
chmod go+rx cache/themes
should fix the problem until someone tries to use a new style.
Then you have to repeat this procedure.

+s permissions might be a security risk and write permissions (rws) to the group too!

BTW: cache/blowfish is created with identical permissions, but I have seen no effect by that.

One more thing: This occurs with a new 5.5 installation attaching to an old database as well as after an upgrade.