When i login as root in the primary nameserver which is using centos and try to update it it gives the following error:

Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...86&repo=addons error was
[Errno 4] IOError: <urlopen error (110, 'Connection timed out')>
Error: Cannot find a valid baseurl for repo: addons

And updating it using the packet update is also not possible,it says maybe network connection problem and yes thats true but the network connection is active and it still has that problem..

When i login as non-root user i get the following message:

Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of disk space. Try logging in with one of the failsafe sessions to see if you can fix this problem.

But i have enough disk space..

And the exact content of ~/xsession -errors-file is:

/etc/gdm/PreSession/Default: Registering your sesion with utmp
/etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -u "/var/gdm/0.Xservers" -h "" -l ":0" "alisha"
localuser:alisha being added to access control list
No profile for user alisha found
Auto configuration failed
21859:error:0200100D:system library:fopen:Permission denied: bss_file .c :122 : fopen('/etc/pki/tls/openssl.cnf', 'rb')
21859:error:2006D002: BIO routines: BIO_new_file: system lib:bss_file.c: 127
21859: error: 0E078002: configuration file routines: DEF_LOAD: system lib: conf_def.c: 199

SO CAN ANYONE HELP ME RECTIFY THE PROBLEM PLEASE..
THANKS...

can anyone help me please..

anyone please??

hello everyone...help please...

We ran into this issue today on a server that we were doing testing with.
It turns out that we had broken the permissions and configuration of the /etc/pki folder and how the system was reading /etc/pki/
We pulled a copy of the folder from another machine with the same setup that was working correctly and copied it over the old one on the broken machine.
It didn't really hit me what had broken our version until we replace the old pki folder with the new one. We were running an ldap test and one of the people who had set it up had changed the ownership to root:ldap for the whole /etc/pki directory. Hopefully, if you run into this issue again, this will help you.
Everything seems to work fine now for us. :-)

Jenelle

well thank you for your reply..

Actually the /etc/pki directory looks fine and ownership has not changed either..

Well what is that /pki directory....is it safe to simply replace it with new one?