Authentication

[Jyotishmaan]

Some parts of this message have been removed. Learn more about Nabble's security policy.

 Hi all,

I had been trying repeatedly to log in from the console in my ldap server machine, but i could not log on to the ldap server machine successfully. Everytime i tried to log on, it popped-up with three dialog boxes one after another showing the messages as shown below inlcuded in double quotes:


The first pop-up dialog box displayed the following messages in it:-

"Your home directory is listed as :'home/jmaan' but it does not appear to exist. Do you  want to log in with the / (root) directory...... " with YES and NO buttons.

After clicking on the YES button, the second pop-up window displayed  the following messages:-"User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions...."

After clicking on the OK button, the third box has shown the following lines :-
"Your session only lasted less than  10 seconds. If you have not logged  out yourself, this could mean some installtion 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." It had also a check box associated with a combo box with a many messages as listed below:

The chk box was ticked and had a label displaying "View Details (~/.session-errors file).

When i clicked on the pull down combo box to vew the inside messages, i saw the following as i have noted down, while trying to log as "jmaan" through the console:-

localuser:jmaan being added to access control list
cann't create dir /home/jmaan/Desktop
cann't create dir /home/jmaan/Download
cann't create dir /home/jmaan/Public
cann't create dir /home/jmaan/Documents
cann't create dir /home/jmaan/Music
cann't create dir /home/jmaan/Pictures
cann't create dir /home/jmaan/Videos

-bin/bash:    /home/jmaan/.bash_profile: Permission denied.
(gnome-session:23626): libgnomevfs-WARNING**: Unable to create ~/.gnome2 directory:Permission denied Could not create per user. gnome configuration directory '/home/jmaan/.gnome2/':Permission denied

However, i could successfully log in to my server machine using ssh as shown below with an error message.

[root@authdns ~]# ssh localhost -l jmaan
jmaan@localhost's password:
Last login: Sun Dec 23 21:36:41 2007 from localhost.localdomain
Could not chdir to home directory /home/jmaan: Permission denied
-bash: /home/jmaan/.bash_profile: Permission denied
-bash-3.2$

Now why did i get this permission denied message.

Once again the /var/log/messages logged, while i had been trying to log in as "jmaan" are shown as below for your reference.

Dec 23 22:04:01 authdns gconfd (jmaan-25209): starting (version 2.18.0.1), pid 25209 user 'jmaan'
Dec 23 22:04:01 authdns gconfd (jmaan-25209): Failed to load source "xml:readwrite:/home/jmaan/.gconf": Failed: Could not make directory `/home/jmaan/.gconf': Permission denied
Dec 23 22:04:01 authdns gconfd (jmaan-25209): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Dec 23 22:04:01 authdns gconfd (jmaan-25209): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 1
Dec 23 22:04:01 authdns gconfd (jmaan-25209): None of the resolved addresses are writable; saving configuration settings will not be possible
Dec 23 22:04:01 authdns gconfd (jmaan-25209): No writable config sources successfully resolved, may not be able to save some configuration changes
Dec 23 22:04:01 authdns gconfd (jmaan-25209): Unable to open saved state file '/home/jmaan/.gconfd/saved_state': Permission denied
Dec 23 22:04:01 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
Dec 23 22:04:02 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
Dec 23 22:04:02 authdns gconfd (jmaan-25209): Failed to log addition of listener gnome-session (Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied));will not be able to restore this listener on gconfd restart, resulting in unreliable notification of configuration changes.
Dec 23 22:04:31 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
Dec 23 22:04:31 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
Dec 23 22:04:31 authdns gconfd (jmaan-25209): GConf server is not in use, shutting down.
Dec 23 22:04:31 authdns gconfd (jmaan-25209): Could not open saved state file '/home/jmaan/.gconfd/saved_state.tmp' for writing: Permission denied
Dec 23 22:04:31 authdns gconfd (jmaan-25209): Exiting


Can any body let me know, how tom resolve these issues of permission denied ?

Once this has been solved, i am sure i will be able to log in thorigh the console and authentication too would be successful.

One more thing, can any one let me know if the authroization in lunux oz is done locally ? (not so clear)

Excuse, me plz for asking a few questions altogether!! as i am a new bie in linux and opendlap!!

Regards,
Jyotishmaan

---

Looking for last minute shopping deals? Find them fast with Yahoo! Search.

[Alex Samad]

On Sun, Dec 23, 2007 at 08:50:45AM -0800, Jyotishmaan Ray wrote:
>
>  Hi all,
>
> I had been trying repeatedly to log in from the console in my ldap server machine, but i could not log on to the ldap server machine successfully. Everytime i tried to log on, it popped-up with three dialog boxes one after another showing the messages as shown below inlcuded in double quotes:
looks like you have your authentication working better than before

>
>
> The first pop-up dialog box displayed the following messages in it:-
>
> "Your home directory is listed as :'home/jmaan' but it does not
>  appear to exist. Do you  want to log in with the / (root) directory...... " with YES and NO buttons.
>
> After clicking on the YES button, the second pop-up window displayed  the following messages:-"User's
> $HOME/.dmrc file is being ignored. This prevents the default session
> and language from being saved. File should be owned by user and have
> 644 permissions...."
>
> After clicking on the OK button, the third box has shown the following lines :-
> "Your
> session only lasted less than  10 seconds. If you have not logged  out
> yourself, this could mean some installtion 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." It had also a check box associated with a combo box with a many messages as listed below:
>
> The chk box was ticked and had a label displaying "View Details (~/.session-errors file).
>
> When i clicked on the pull down combo box to vew the inside messages, i saw the following as i have noted down, while trying to log as "jmaan" through the console:-
>
> localuser:jmaan being added to access control list
> cann't create dir /home/jmaan/Desktop
> cann't create dir /home/jmaan/Download
> cann't create dir /home/jmaan/Public
> cann't create dir /home/jmaan/Documents
> cann't create dir /home/jmaan/Music
> cann't create dir /home/jmaan/Pictures
> cann't create dir /home/jmaan/Videos
>
> -bin/bash:    /home/jmaan/.bash_profile: Permission denied.
> (gnome-session:23626): libgnomevfs-WARNING**: Unable to create ~/.gnome2 directory:Permission denied Could not create per user. gnome configuration directory '/home/jmaan/.gnome2/':Permission
>  denied

try logging via the text console not gdm.

look at ls -l /home

see if jmaan has permission (rwx) to /home/jmaan

>
> However, i could successfully log in to my server machine using ssh as shown below with an error message.
>
> [root@authdns ~]# ssh localhost -l jmaan
> jmaan@localhost's password:
> Last login: Sun Dec 23 21:36:41 2007 from localhost.localdomain
> Could not chdir to home directory /home/jmaan: Permission denied
> -bash: /home/jmaan/.bash_profile: Permission denied
> -bash-3.2$
>
> Now why did i get this permission denied message.

you, jmaan, does have permission to /home/jmaan

>
> Once again the /var/log/messages logged, while i had been trying to log in as "jmaan" are shown as below for your reference.
>
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): starting (version 2.18.0.1), pid 25209 user 'jmaan'
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): Failed to load source "xml:readwrite:/home/jmaan/.gconf": Failed: Could not make directory `/home/jmaan/.gconf': Permission denied
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 1
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): None of the resolved addresses are writable; saving configuration settings will not be possible
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): No writable config sources successfully resolved, may not be able to save some configuration changes
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): Unable to open saved state file '/home/jmaan/.gconfd/saved_state': Permission denied
> Dec 23 22:04:01 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
> Dec 23 22:04:02 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
> Dec 23 22:04:02 authdns gconfd (jmaan-25209): Failed to log addition of listener gnome-session (Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied));will not be able to restore this listener on gconfd restart, resulting in unreliable notification of configuration changes.
> Dec 23 22:04:31 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
> Dec 23 22:04:31 authdns gconfd (jmaan-25209): Failed to open saved state file: Failed: Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (Permission denied)
> Dec 23 22:04:31 authdns gconfd (jmaan-25209): GConf server is not in use, shutting down.
> Dec 23 22:04:31 authdns gconfd (jmaan-25209): Could not open saved state file '/home/jmaan/.gconfd/saved_state.tmp' for writing: Permission denied
> Dec 23 22:04:31 authdns gconfd (jmaan-25209): Exiting
>
>
> Can any body let me know, how tom resolve these issues of permission denied ?

think it is fairly obvious, you don't have permission

>
> Once this has been solved, i am sure i will be able to log in thorigh the console and authentication too would be successful.
>
> One more thing, can any one let me know if the authroization in lunux oz is done locally ? (not so clear)
>
> Excuse, me plz for asking a few questions altogether!! as i am a new bie in linux and opendlap!!
>
> Regards,
> Jyotishmaan
>
>
>
>
>
>
>
>
>
>
>       ____________________________________________________________________________________
> Looking for last minute shopping deals?  
> Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

[Jyotishmaan]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hello (Alex),

plz see my reply in blue colour

try logging via the text console not gdm.

In my ldap server machine whenever i restart the system it ends up showing up the GUI, though at the startup, for a second it shows up the console log in prompt for a split of a second, it does nt hang on that and finally ends up with GUI based log in prompt

If I have to do anything with inittab ?

Any directions on how to start with console log in prompt in text mode, as i am a new bie in linux fedora OS.

Thanks,

Jyotishmaan

---

Looking for last minute shopping deals? Find them fast with Yahoo! Search.

[Alex Samad]

On Mon, Dec 24, 2007 at 02:01:09AM -0800, Jyotishmaan Ray wrote:

> Hello (Alex),
>
> plz see my reply in blue colour
>
> try logging via the text console not gdm.
>
> In my ldap server machine whenever i restart the system it ends up showing up the GUI, though at the startup, for a second it shows up the console log in prompt for a split of a second, it does nt hang on that and finally ends up with GUI based log in prompt
>
> If I have to do anything with inittab ?
>
> Any directions on how to start with console log in prompt in text mode, as i am a new bie in linux fedora OS.

try pressing ctrl+alt+F{1-6} for the vitrual consoles or ctrl+alt+F7 for
virtual console 7 where X usually displays

>
> Thanks,
>
> Jyotishmaan
>
>
>
>
>
>
>
>       ____________________________________________________________________________________
> Looking for last minute shopping deals?  
> Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

[Jyotishmaan]

Some parts of this message have been removed. Learn more about Nabble's security policy.

 

 

 Thank you so much, Alex.

try pressing ctrl+alt+F{1-6} for the vitrual consoles or ctrl+alt+F7 for
virtual console 7 where X usually displays

>
> Thanks,
>
> Jyotishmaan
>
>
>
>
>
>
>
>      ____________________________________________________________________________________
> Looking for last minute shopping deals? 
> Find them fast with Yahoo! Search.   http://tools.search.yahoo.com/newsearch/category.php?category=shopping

---

Never miss a thing. Make Yahoo your homepage.