Hello,
I am trying to upgrade fr 4.2x to 4.4x.
This is not the first time. I have run into permission errors:
I run another instance fo SuiteCRM in a folder/website just next door to this one. It never has permissions problems.
Why is one having problems, and not the other?
AS well, you can see what the values are:
644
What is the correct value supposed to be?
Thanks for any leads:)
Joseph
John
9 December 2015 09:39
2
Hi,
The permissions values we usually recommend can be set with the commands:
sudo chmod -R 755 .
sudo chmod -R 775 cache custom modules themes data upload config_override.php
This will set the permissions for all files/folders to 755
If you feel that these aren’t secure enough, feel free to change them back to whatever you wish after the upgrade has finished.
Hello John,
Thanks for your helping ideas.
Can I presume that I do this from the command line inside the SuiteCRM folder, right?
This happens just about every time when I upgrade. Your help will save time running to my IT friend:)
But, can I use the same exact command, regardless what permission errors come up, or will I need to target the files/folders affected by the permission errors?
Thanks for your assistance!
John
9 December 2015 13:49
4
Yep, these are run from the Command line inside the SuiteCRM folder
As these commands are recursive, they should cover all files/folders in the SuiteCRM directory
Hello John,
YOu idea has definitely reduced my errored permisisons.
Here is the latest list:
As you see, 95% are gone.
They have the permission status as defined, and still does not pass.
As well, does on need the sugarcrm_log files? Each one of the old files is over 10MB large. Are they needed for anything, or can they be erased?
Let me know how to “correct” the permissions on the last difficult files:)
Thanks
Joseph
jyka
10 December 2015 08:03
6
Joe,
Seems to me that you are using ISPConfig in your host that’s why these errors seems familiar to me.
I think you should change the owner:
chown -R web5:client *
At least that helped me when upgrading.
Jysse
Hello, Jyse
Using this command will set permission of al items to web5, and it should work at that point?
Do I use it inside the CRM folder?
Thanks
Joseph
jyka
10 December 2015 16:12
8
At least this helped me earlier. I am not an expert with Suitecrm but slowly learning.
There is a typo in earlier post. I think that the exact command is:
chown -R web5:client2 *
In fact Ispconfiq will change automatically ownership afterwards for example for Stats directory. So you must do this again when upgrading next time.
I am making progress!! I made one of the updates (7.2x to 7.3x.). Worked fine.
But, when making a nother update - 7.3x to 7.4x, I get a new permission error.
Show Files with Bad Permissions
File Name Permissions Owner Group
Funny part is that this fine is actually the back up file of the install.
So, I figured that the easy way to solve the issue would be to get rid of the file.
I put a copy on my PC and then proceeded to erase the original on the server.
But, when SuiteCRM does the pre-check before upgrade, it keeps coming back with a permission error on this non-existant file.
Can some one help me to let me know how to get rid of this ghost permission error?
Thanks
Joseph
Hello Jysse
It has been awhile sinc eyou answered my question abou teros during upgrading my SuiteCRM. Hopefully you are still out there:)
You also use ISPConfig.
I am having an issue. I use the permissions changing collands for the folders. They helped a lot on my last install. But, my last install, Iam having an issue with one of you ideas that have helped me inth epast. You said also to use the followng command:
chown -R web5:client *
I get the error:
It has always worked before.
Now, I am having issues with getting kicked out of my new install with in 1-2 minutes o fusing it. I am thinking that it is related to not getting the chown command to work.
Thanks fo rgetting back to me, or someone else.
Thanks
Joseph
pgr
18 April 2017 09:04
11
If your suitecrm.log files are still showing ownership by root (like in that old listing above), then I would say your cron jobs are running as root (possibly your service provider’s fault), which is sure to break things in SuiteCRM. That would explain all the problems you’re having, and the need to keep reinstating permissions.
Just ask your service provider to run the Scheduler jobs as the correct user (your web server user, not root), fix permissions once more, and you should be ok (for good).
Detailed explanations here: https://pgorod.github.io/Scheduler-Jobs/
Hello,
I have an update.
I sat down with my IT guy, and he sat in front of his computer 1`5 minutes and nver got kicked out of suitecrm.
He was using Chrome.
I then tried it on my compuyter, ands I was still having issues.
I use FireFox.
So, I tried disabling all plug ins. No success on 1 the new install, but pon my older install, it starting working with no issues.
I tried another browser, and it works fine on all installs!
I will reinstall Firefox, and see if this has any affect.
Anyone else have an issue with Foe Fox?
Jospeh
pgr
29 April 2017 20:43
13
I always use Firefox exclusively, never had problems with SuiteCRM because of this…
I went back and confirmed, my ownership is as follows:
which reflects the owner of the directories.
Root is no longer the owner.
This removes the idea that you had put forth that it is because the files were owned by root.
But then, an even older install, (still on the same server), has been working fine for years and no issues.
I also tried firefox on my Mac. Same issues. It kicks me out.
Chrome on my Mac works fine.
NOt sure
Thanks
JOseph
pgr
30 April 2017 15:16
15
Well, permissions problems always involve 3 aspects: ownership, permission values, and which user your web server is using. You can only take conclusions after making sure all three match appropriately.
Anyway, if the problem is browser-specific I agree you could investigate in a different direction. Maybe try opening Web Developers tools on Firefox and see if any error catches your eye at the moment where you are “kicked out”.
Also check your suitecrm.log and php_errors.log at that same moment.
