solution is to add the two lines below to your .htaccess file preferably at top

Options +FollowSymLinks

AllowOverride All

make sure these lines are not already added to your apache config file or you may get internal server errors.

if it doesn’t works in .htaccess file which can happen occassionally then you need to add these lines to apache conf. which should work for sure.

Related Articles

• August 27, 2008 — Welcome to haris Raheem’s Site (0)

here is a very simple solution, use yum remove libcurl and then use yum install libcurl.

it worked for me as it was just a libcurl version issue. i tried everything i found on forums but nothing worked.

yolu can try it out if nothing works for you too.

No related articles but you may like it

• October 13, 2008 — Will the New MacBook Pros be Decent Gaming PCs? - PC World (0)
• October 16, 2008 — US loses to Trinidad and Tobago, 2-1 - Los Angeles Times (0)
• October 16, 2008 — Tampa Bay Rays swap starters despite lead on Red Sox - Boston Herald (0)

Test postgresql
Check whether postgresql is running:
    # service postgresql status
If service replies that postgresql is stopped, then:
    # service postgresql start
service should reply OK

Login and Exit postgresql Shell

To login, type following on command line 

psql -U username. it would ask for password on next line. type in the password. 

to exit type \q on command line.

postgresql helpful hints
This section is just a few helpful pointers and links about how to handle you postgres installation. Actual instruction begins again in the next section (Enable proper logging for postgresql).
PostgreSQL configuration is in /var/lib/pgsql/data/postgresql.conf
Host Based Access configuration file is in /var/lib/pgsql/data/pg_hba.conf
To make a database (which will be owned by the operating system user who issues the command):
   bash-2.05b$ createdb <dbname>
All user and db management can be done through the PostgreSQL interactive terminal (which accepts both SQL statements and Postgres metacommands) called psql (man psql for reference):
bash-2.05b$ psql <dbname>
which takes you to a prompt which looks like:
<dbname>=#
To add/manage users:
PGSQL User Management
To create users:
<dbname>=# CREATE USER <username>
Every db must be VACUUMed at least once every billion transactions with the vacuum command in psql (or risk catastrophic data loss). See Routine Vacuuming.
A few useful tools.
To list all postgresql users:
<dbname>=> SELECT * FROM pg_user;
To list all postgresql databases:
<dbname>=> SELECT * FROM pg_database;
To find out the currently selected database, look at the name in the prompt:
<dbname>=>

Enable proper logging for postgresql
Edit the file /etc/init.d/postgresql
Find the line that reads:
   su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D #PGDATA -p /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null
Edit the line to read (changes marked in bold, note double greater than after ’start’):
   su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D #PGDATA -p /usr/bin/postmaster -o ‘-i’ start >> /var/log/pgsql 2>&1″ < /dev/null
Save the file
Restart postgresql:
    # service postgresql restart
service should reply OK

Configure pgsql users and databases
First, the user called ‘postgres’, who is the superuser for the postgresql service, must have a new, secure password assigned both in the operating system and in the postgresql service. Next, a file called ‘admins’ must be created to indicate that the postgres user can connect to any database with a password challenge. Then, other users must be added to pgsql. One user should be defined for each timeLines installation on the machine. Finally, the new database(s) for the timeLines installation(s) must be created.

Create the postgresql admin user and set permissions for postgresql users:

1. As root, change the password for user postgres in the operating system by using the command passwd:
      # passwd postgres
   This command will now challenge you for the new secure database admin password which should be carefully kept track of, with the usual precautions of length, and a mix of letters, numbers, and symbols. This password will be needed again in step 4.
2. Run a shell as the postgres user:
      # su postgres
   which takes you to a prompt which looks something like:
      bash-2.05b$
3. Connect to template1 (postgresl’s template database) as user postgres by using the command psql, which opens the PostgreSQL interactive terminal. (Whenever in the terminal, be sure to expect confirmations of any action; a null response is a sure sign of no action performed.)
      bash-2.05b$ psql template1
4. Change the password for user ‘postgres’ in the postgresql service by using the ‘ALTER USER’ command. Be sure to surround the password with single quotes/apostrophes as shown. The terminal should confirm by replying ‘ALTER USER’. When using the following example, <newpassword> should be replaced with the new, secure password assigned in step 1. above. (Note that unlike the passwd command above, ‘ALTER USER’ will not automatically conceal the password as it is being typed. Be sure to enter it only in a secure environment.)
      template1=# ALTER USER postgres WITH PASSWORD '<newpassword>';
5. Exit psql.
      template1=# \q
6. Exit postgres user session.
      bash-2.05b$ exit
7. Initially, PostgreSQL allows anyone from the local machine to connect to the databases without a password challenge, so as to allow the administrator to set the password for the postgres user. Once that has been done, access to the databases must be securely restricted. This is controlled from the file /var/lib/pgsql/data/pg_hba.conf. Open this file and make the following edits:
   • Make two copies of line 221 at the bottom of the file. Uncomment the lines by deleting the pound sign ‘#’ from the front of both lines (the ‘#’ is a comment character, which tells the configuration engine to ignore that instruction). In the second copy, edit the word ’sameuser’ to say ‘template1′. The first copy will allow any user to connect to a databse with the same name as their username. The second, edited copy will allow all users to be able to connect to the template database in order to create their own.
   • Copy line 222 to the bottom of the file, uncommenting it by deleting the ‘#’. This will allow the postgres user to connect to any database.
   • Copy line 190 to the bottom of the file and uncomment it. Edit the word ‘template1′ to say ‘all’, and edit the ip address in this line to match the machine’s ip address. This will allow remote connections.
   • Comment out line 250 by putting a ‘#’ at the front of it.

   In the same directory /var/lib/pgsql/data/, create a file called ‘admins’. Write into this file one word, the name of the database admin user, ‘postgres’ (excluding the single quotes/apostrophes in this case). These configuration changes will only be applied the next time the service is restarted.

8. Restart the postgresql service.
      # service postgresql restart

Create new users and databases:

1. Run a shell as the user postgres to do some user management.
      # su postgres
   Create a new database user. The name of this new user should correspond to the fully qualified domain name of the site that the database will be supporting, subtituting underscores for the dots. For example, if your domain name is “www.example.tld”, the corresponding user name should be “www_example_tld”. This should also be the name of the database. Permissioning restricts users other than the admin user “postgres” to connect only to “template1″ and the database with the same name as the user.
   To make users (outside psql) as user postgres:
      bash-2.05a$ createuser <options> <username>
   The options that should be used are:
   -d = allowed to create databases
   -P = prompt for a password
   -A = not allowed to create users
   Using our example:
      bash-2.05a$ createuser -d -P -A www_example_tld
   The password for the new user will now be prompted for. This should be another equally secure password, preferably different from the postgres user password, especially if there will be multiple timeLines installations on this machine. This password will be required by the timeLines installation script later in order to initialize the database and enable the application.
   The password will be challenged for a second time for confirmation.
   Finally the postgres admin password will be asked for, to authorize the new user.
   createuser should reply CREATE USER
   The new user has now been created!
   (man createuser for details, dropuser to delete users, and ALTER USER from inside psql to change settings for a user)