Results 1 to 5 of 5

Thread: installation 4.51 getting Writable Session Save Path() Not A Valid Directory

  1. #1
    joeberg is offline Sugar Community Member
    Join Date
    Mar 2008
    Posts
    11

    Default installation 4.51 getting Writable Session Save Path() Not A Valid Directory

    i keep hitting the recheck, nothing happens,

    here is my configuration, i'm running on a server, where i can edit my php.ini file but cannot restart my apachi,
    i set all the permmision levels, like i saw in the wiki, still nothing, so i'm a bit confused and cannot get it to work.
    i created a temp folder in the root, and a temp folder in the crm root, still nothing, oh and yes on a unix box.
    can anyone help.

  2. #2
    julian's Avatar
    julian is offline Sugar Team Member
    Join Date
    Sep 2004
    Posts
    1,639

    Default Re: installation 4.51 getting Writable Session Save Path() Not A Valid Directory

    Hello joeberg,

    Just to check things out, where is your session directory? If you want to really check the directory that Sugar is using, you can create a test PHP file like this:

    PHP Code:
    <?php echo 'My session directory is: ' session_save_path(); ?>
    Check the permissions on that directory (by running something like ls -l), then paste those permissions here so we can take a look. It's also important to know the user/group which has permissions to the directory. Can you find out which user apache is running as?

    Also, if you can make changes to php.ini but cannot restart apache, can you get somebody else to restart apache for you? It should only take one restart to get this working.
    Julian Ostrow
    Systems and Applications Engineer
    SugarCRM Inc.

  3. #3
    joeberg is offline Sugar Community Member
    Join Date
    Mar 2008
    Posts
    11

    Default Re: installation 4.51 getting Writable Session Save Path() Not A Valid Directory

    Quote Originally Posted by julian
    Hello joeberg,

    Just to check things out, where is your session directory? If you want to really check the directory that Sugar is using, you can create a test PHP file like this:

    PHP Code:
    <?php echo 'My session directory is: ' session_save_path(); ?>
    Check the permissions on that directory (by running something like ls -l), then paste those permissions here so we can take a look. It's also important to know the user/group which has permissions to the directory. Can you find out which user apache is running as?

    Also, if you can make changes to php.ini but cannot restart apache, can you get somebody else to restart apache for you? It should only take one restart to get this working.
    i'm using bluehost.com really cool, cheap, quick, but shared, and they claim that any change i make in my php.ini file takes effect in the enviroment, but i guess not, i make that test php file you wrote, and it echoed what you asked but blank on the actual ( ) info. originally in my php.ini file it was set N;/tmp and i got rid of the N; set it on both to places to /tmp and i made a /tmp folder in the root, and in the crm folder, and gave them both 777 perm. and still nothing, so i am so confused,

  4. #4
    andopes's Avatar
    andopes is offline A Sugar Hero | Help Forum Moderator
    Join Date
    Jul 2006
    Location
    São Paulo - Brazil
    Posts
    8,335

    Default Re: installation 4.51 getting Writable Session Save Path() Not A Valid Directory

    Hi, joeberg

    I believe the session_save_path into your php.ini is empty, so the SugarCRM can't get it.
    You could easy figure out it by creating the script:

    PHP Code:
    <?php
    phpinfo
    ();
    ?>
    If you run this into your browser certainly the session_save_path will be empty.
    If it really is empty then you can't process the install without hardcoding the session_save_path into the index.php of SugarCRM or asking the support team of your hosted server to update it for you.
    If you really must hardcode the session_save_path, then look for it into php.ini site.

    Cheers

    --
    André Lopes
    Lâmpada Global Services
    Rua Bela Cintra, 299 conjunto. 51
    São Paulo, SP 01415-000
    tel1. 55 11 3237-3110
    cel. 55 11 7636-5859
    e-mail: info@lampadacrm.com.br

  5. #5
    b4syth is offline Junior Member
    Join Date
    May 2009
    Posts
    1

    Default Re: installation 4.51 getting Writable Session Save Path() Not A Valid Directory

    Bluehost 5/09:

    To install sugar community edition:

    - Goto Bluehost cpanel / PHP Configuration

    - Select Option:

    PHP5
    All files with the extension .php will be handled by the PHP5 engine.
    Current, most reliable and best performing version of PHP

    "Install php.ini master file" if you haven't already

    - In your web root find php.ini.default and rename/mv to php.ini
    - In your web root create a 'tmp' directory (if it doesn't already exist)
    - Open php.ini and find the line ';session.save_path =' and remove the semi-colon/uncomment
    - Change to session.save_path = /tmp
    - Run sugar install

    If the installation dies/screen goes blank
    - delete the .htaccess file in the sugar-root

    DB:
    Use: Hosting services prefixes in username and password
    Use: Localhost

    Default login isfor system is 'admin' with your install-specified password (odd they wouldn't tell you this)

    Essentially,no matter what your phpinfo script tells you, sugar will not accept any directory but 'tmp' to be the correct session.save.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 97
    Last Post: 2010-12-24, 12:18 PM
  2. Replies: 13
    Last Post: 2008-09-25, 05:49 PM
  3. Replies: 7
    Last Post: 2007-11-08, 10:44 PM
  4. Replies: 0
    Last Post: 2005-12-23, 04:48 AM
  5. Writable Session Save Path () Not A Valid Directory
    By smith_908 in forum General Discussion
    Replies: 1
    Last Post: 2005-10-11, 02:52 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •