我刚刚在一个新磁盘上安装了CentOS。我是在一个稍微有点非常规的男子中这样做的--我在Debian的yum中运行了一个完整的chroot安装。因此,我遇到了一些问题,使grub和fstab正确。但现在我觉得我被堵住了。
cat /etc/redhat-release CentOS Linux7.1.1503版(核心)
系统启动(启动时屏幕上的所有绿色OK),但我无法登录到一个tty -当我键入用户名和密码时,屏幕刷新使用用户名提示。我可以通过chroot登录两个帐户,所以这不是问题所在。
下面是(我认为)与/var/log/messages相关的部分:
Sep 16 01:45:01 localhost systemd: Starting Multi-User System.
Sep 16 01:45:01 localhost systemd: Reached target Multi-User System.
Sep 16 01:45:01 localhost systemd: Starting Graphical Interface.
Sep 16 01:45:01 localhost systemd: Reached target Graphical Interface.
Sep 16 01:45:01 localhost systemd: Starting Update UTMP about System Runlevel Changes...
Sep 16 01:45:01 localhost systemd: Starting Stop Read-Ahead Data Collection 10s After Completed Startup.
Sep 16 01:45:01 localhost systemd: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
Sep 16 01:45:01 localhost systemd: Started Update UTMP about System Runlevel Changes.
Sep 16 01:45:01 localhost systemd: Startup finished in 829ms (kernel) + 4.879s (initrd) + 23.991s (userspace) = 29.700s.
Sep 16 01:45:01 localhost NetworkManager[713]: <info> startup complete
Sep 16 01:45:02 localhost systemd: SELinux policy denies access.
Sep 16 01:45:02 localhost systemd-logind: Failed to start unit user-42.slice: Access denied
Sep 16 01:45:02 localhost systemd-logind: Failed to start user slice: Access denied
Sep 16 01:45:02 localhost systemd-logind: Assertion 's->user->slice' failed at src/login/logind-session.c:515, function session_start_scope(). Aborting.
Sep 16 01:45:02 localhost abrt-hook-ccpp: Saved core dump of pid 609 (/usr/lib/systemd/systemd-logind) to /var/spool/abrt/ccpp-2015-09-16-01:45:02-609 (614400 bytes)核心转储中的backtrace与CentOS Bug: 8905完全相同。
接下来,我将把SELinux=0添加到grub脚本中,但我不想永久地这样做。编辑:我将selinux=1 enforcing=0添加到grub引导参数中,然后编辑/etc/sysconfig/selinux并将状态更改为SELINUX=permissive来修复它。
我可以登录,现在一切都正常,但是如果我将SElinux设置为强制,则根本无法登录。还在找答案..。
发布于 2015-10-15 04:50:55
我也遇到了同样的问题。非常规安装也是如此,我使用的是extlinux,而不是grub。我试着以root用户和普通用户的身份登录,但两者都不起作用。
cat /etc/redhat-release CentOS Linux7.1.1503版(核心)
我通过做一个完整的SELinux重命名来解决这个问题。
# inside the chroot from Debian
touch /.autorelabel有关更多详细信息,请参阅CentOS SELinux。
https://unix.stackexchange.com/questions/229989
复制相似问题