On CentOS Linux (3.10.0-123.20.1.e17.x86_64) 7 (Core).
After selecting the above, the following line appears in the upper left corner of the black screen and does not move.
[OK] Started LSB: Start the ipr dump daemon.
[OK] Started Dynamic System Tuning Daemon.
_
When I tried to log in from Ctrl+Alt+F2, I found the following:
(host name) login: (account name)
Password:
Last failed login...
There was 3...
Permission denied
The line from Last... to Permission denied disappears after about 3 seconds and
Login will be restarted.
with the correct administrator user or regular user account
I tried, but all of them were Permission denied.
When the operating system was booting normally, the sudo command was troublesome and always su.
Also, for programming reasons, ulimit-nunlimited
(Unlimited number of files opened in OS at once) failed.
Does anyone have any idea of these symptoms?
Thank you for your cooperation.
and so on.
Boot to the CD-ROM and check the contents of the disk in rescue mode.
To be honest, I don't think I know what's wrong with this alone.
CentOS 7 uses systemd, so the rescue method is not the same as before, so you can stop it on the boot screen and edit the command to add systemd.unit=resque.target to the previous single user mode.
So as soon as you look at the log file, check it with the journalctl command, or see which target is failing in systemctl to investigate the cause.
IBM's document described the nofile limit:
If you set this limit to unlimited in the /etc/security/limits.conf file, the limit is 0
resets to the .This setting prevents associated users or groups from creating new processes. User is root
If you are a user, you cannot create a new process and the system shuts down slowly.
If this condition occurs, you will need to reset the value using the recovery disk.
If you run ulimit-nunlimited in your Centos 7 environment, you will see "Cannot change bash:ulimit:open files:limit:unauthorized operation"
The same symptom was reproduced when I tried unlimit and rebooted in /etc/sercurity/limits.conf.
*soft nofile unlimited
* hard nofile unlimited
ulimit-nunlimited is a temporary change, so I think it will be disabled after rebooting.
Is there a possibility that you have changed the maximum number of files in the configuration file under limits.conf or limits.d?
Some of you have already commented on how to restore it, but please boot it from a CD-ROM, mount the current disk, and edit the file.
© 2024 OneMinuteCode. All rights reserved.