FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 02-09-2012, 05:38 PM
don fisher
 
Default Cannot log in after boot:-(

When I boot to level 2 I receive the login prompt. But if I attempt to
login as a user or root the login prompt just returns. I booted into
single user mode and tried to fix the /etc/passwd, /etc/group and
/etc/gshadow. Executing pwconv and grpconv all appear to work. pwck and
grpck also are successful.


In single user mode I can su to my dfisher account, then su to another
user account that requires a passwd, and then su back to root that
requires a passwd. All are successful.


But when I type ^g and receive the login prompt, none of my accounts are
accessible.


That do I need to do to make the system login work?

Thanks,
Don

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 05:57 PM
Joe Zeff
 
Default Cannot log in after boot:-(

On 02/09/2012 10:38 AM, don fisher wrote:

When I boot to level 2 I receive the login prompt.


Why are you booting into level 2? In the old, pre-systemd days, a
complete CLI system without X was level 3; is that what you're referring to?

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 06:27 PM
don fisher
 
Default Cannot log in after boot:-(

On 02/09/12 11:57, Joe Zeff wrote:

On 02/09/2012 10:38 AM, don fisher wrote:

When I boot to level 2 I receive the login prompt.


Why are you booting into level 2? In the old, pre-systemd days, a
complete CLI system without X was level 3; is that what you're referring
to?


I guess I am not sure which level it is. I linked
/lib/systemd/system/multi-user.target to
/etc/systemd/system/default.target. It may be level 3. The system used
to work until a crash. I restored the system, but something is amiss in
the login verification.


Any other ideas on how to verify the passwd and shadow files?

Don

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 07:00 PM
James Wilkinson
 
Default Cannot log in after boot:-(

don fisher wrote:
> I guess I am not sure which level it is. I linked
> /lib/systemd/system/multi-user.target to
> /etc/systemd/system/default.target. It may be level 3. The system
> used to work until a crash. I restored the system, but something is
> amiss in the login verification.

Did you restore all the selinux contexts?

Try booting in permissive mode, or run
touch /.autorelabel
and reboot.

Hope this helps,

James.

--
E-mail: james@ | Time’s fun when you’re having flies.
aprilcottage.co.uk |
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 07:07 PM
don fisher
 
Default Cannot log in after boot:-(

On 02/09/12 13:00, James Wilkinson wrote:

don fisher wrote:

I guess I am not sure which level it is. I linked
/lib/systemd/system/multi-user.target to
/etc/systemd/system/default.target. It may be level 3. The system
used to work until a crash. I restored the system, but something is
amiss in the login verification.


Did you restore all the selinux contexts?

Try booting in permissive mode, or run
touch /.autorelabel
and reboot.

Hope this helps,

James.


James,

Please help with details. I just converted back from Ubuntu, so have
been away for awhile. What selinux contexts would need to be restored?
And how does one run in permissive mode? I have not been careful to
restore the rw permissions on the passwd/group etc. files. Does it check
for that?


Thanks
don
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 08:10 PM
"dwight at supercomputer.org"
 
Default Cannot log in after boot:-(

On Thursday 09 February 2012 10:57:21 am Joe Zeff wrote:
> On 02/09/2012 10:38 AM, don fisher wrote:
> > When I boot to level 2 I receive the login prompt.
>
> Why are you booting into level 2? In the old, pre-systemd days, a
> complete CLI system without X was level 3; is that what you're
> referring to?

That's incorrect. Init level 2 was the shell. Then networking came
along, and init level 3 was the shell + networking. X came along
later, and was put into init state 5.

Booting into init state 2 is perfectly valid, depending on what you
want to do.

-dwight-


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 08:36 PM
"dwight at supercomputer.org"
 
Default Cannot log in after boot:-(

On Thursday 09 February 2012 01:10:10 pm dwight at supercomputer.org
wrote:
> On Thursday 09 February 2012 10:57:21 am Joe Zeff wrote:
> > On 02/09/2012 10:38 AM, don fisher wrote:
> > > When I boot to level 2 I receive the login prompt.
> >
> > Why are you booting into level 2? In the old, pre-systemd days,
> > a complete CLI system without X was level 3; is that what you're
> > referring to?
>
> That's incorrect. Init level 2 was the shell. Then networking came
> along, and init level 3 was the shell + networking. X came along
> later, and was put into init state 5.
>
> Booting into init state 2 is perfectly valid, depending on what
> you want to do.
>
> -dwight-

Whoops. I misread that as the old pre-systemV days. RH/Fedora merged
the networking into init state 2. But the point remains that init
state 2 was a perfectly valid init state with the shell, without X.
And a very useful one as well, at times.

-dwight-
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 09:15 PM
"T.C. Hollingsworth"
 
Default Cannot log in after boot:-(

On Thu, Feb 9, 2012 at 12:27 PM, don fisher <hdf3@comcast.net> wrote:
> I guess I am not sure which level it is. I linked
> /lib/systemd/system/multi-user.target *to
> /etc/systemd/system/default.target. It may be level 3. The system used to
> work until a crash. I restored the system, but something is amiss in the
> login verification.

Yes, this is the systemd equivalent of runlevel 3.

-T.C.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 09:19 PM
"T.C. Hollingsworth"
 
Default Cannot log in after boot:-(

On Thu, Feb 9, 2012 at 1:07 PM, don fisher <hdf3@comcast.net> wrote:
> On 02/09/12 13:00, James Wilkinson wrote:
>>
>> don fisher wrote:
>>>
>>> I guess I am not sure which level it is. I linked
>>> /lib/systemd/system/multi-user.target *to
>>> /etc/systemd/system/default.target. It may be level 3. The system
>>> used to work until a crash. I restored the system, but something is
>>> amiss in the login verification.
>>
>>
>> Did you restore all the selinux contexts?
>>
>> Try booting in permissive mode, or run
>> touch /.autorelabel
>> and reboot.
>>
>> Hope this helps,
>>
>> James.
>>
> James,
>
> Please help with details. I just converted back from Ubuntu, so have been
> away for awhile. What selinux contexts would need to be restored? And how
> does one run in permissive mode? I have not been careful to restore the rw
> permissions on the passwd/group etc. files. Does it check for that?

You can boot into permissive mode by adding "selinux=permissive" to
the kernel command line. (You can also change to it on the fly by
running `setenforce 0` or change it permanently by editing
/etc/sysconfig/selinux.)

A script run during boot checks for the existence of /.autorelabel,
which will trigger a complete scan of your filesystem, relabeling any
strange SELinux contexts to their defaults, so `touch /.autorelabel`
should fix any SELinux issues you might have. You can also reset
individual files with the `restorecon` command.

It does not fix the standard Unix permissions on files though. If
you're concerned about that, just `chmod 644 /etc/passwd /etc/group`
and `chmod 000 /etc/shadow /etc/gshadow`.

-T.C.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 02-09-2012, 11:00 PM
don fisher
 
Default Cannot log in after boot:-(

On 02/09/12 15:19, T.C. Hollingsworth wrote:

You can boot into permissive mode by adding "selinux=permissive" to
the kernel command line. (You can also change to it on the fly by
running `setenforce 0` or change it permanently by editing
/etc/sysconfig/selinux.)

A script run during boot checks for the existence of /.autorelabel,
which will trigger a complete scan of your filesystem, relabeling any
strange SELinux contexts to their defaults, so `touch /.autorelabel`
should fix any SELinux issues you might have. You can also reset
individual files with the `restorecon` command.

Te setenforce 0 command appears to solve the problem. What did I break
to make this a requirement? How dd yo learn these ind of details? I am
quite jealous. Thanks again for help. I has been long one:-)

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 

Thread Tools




All times are GMT. The time now is 12:57 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org