SugarClub will be undergoing scheduled maintenance and will be inaccessible beginning on Friday, 10 April 2026 (15:00 UTC | 11am EDT | 1am AEST on 11 April).
This maintenance period will end on Monday, 13 April 2026 (12:00 UTC | 8am EDT | 10pm AEST). 
Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 378 subscribers
  • Views 1593 views
  • Users 0 members are here
Forum Actions
Related

permission issue on sugar log file (644)

pavan agrawal

Hello Team,

We are getting permission denied error on the default SugarCRM logfile. Whenever it creates a new log file with rw-r--r-- (644) access.

Every time, we require to change 777 permission on the log file. Please let us know how to fix it so that by default it set to 777.

Thanks!

Regards,

Pavan

Parents
  • 0

    For what it's worth, 664 should be good enough for the log file, 777 is a bit extreme :)

    My permissions panacea is to run these from sugar root (and sometimes other directories), they respectively: set ownership and group on every file and directory, from where you are down, to apache; set all directories to 775, and set all files to 664.

    I run these after every upgrade or any time I suspect permission issues. 

    sudo chown -R  apache:apache *

sudo find . -type d -exec chmod 775 {} \;

sudo find . -type f -exec chmod 664 {} \;

Reply
  • 0

    For what it's worth, 664 should be good enough for the log file, 777 is a bit extreme :)

    My permissions panacea is to run these from sugar root (and sometimes other directories), they respectively: set ownership and group on every file and directory, from where you are down, to apache; set all directories to 775, and set all files to 664.

    I run these after every upgrade or any time I suspect permission issues. 

    sudo chown -R  apache:apache *

sudo find . -type d -exec chmod 775 {} \;

sudo find . -type f -exec chmod 664 {} \;

Children
No Data