- Ошибка входа пользователя домена в astra se 1.6
- tagilchanin
- tagilchanin
- fonarshik
- azm9s
- fonarshik
- Как запустить систему
- Failed to boot after system update, Arch linux (Failed to start Hostname Services) and others
- 1 Answer 1
- Failed to start permit user sessions
- [SOLVED] Login error: «System is booting up»
- [SOLVED] Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: Login error: «System is booting up»
- Re: [SOLVED] Login error: «System is booting up»
Ошибка входа пользователя домена в astra se 1.6
Всем привет! Проблема следующего характера(
Есть контроллер домена на astra se 1.5. Есть ald-client на astra se 1.6!
Клиент на 1.6 великолепно подключился к домену на 1.5 но. пользователь которому делегировпны все права и т.д. для входа на этот клиент есть. при входе логин и пароль принимается и вылетает окошко для выбора режима. но потом черный экран на 3 секунда и вуаля опять экран входа в систему! Подскажите господа куда смотреть, что делать(
tagilchanin
New member
Sep 6 09:40:55 astra-client [3769]: pam_ald(fly-dm:session): Не удалось подключить домашний каталог ‘/run/ald.mounts/astra’ пользователя ‘astra’.
Sep 6 09:40:55 astra-client systemd-logind[452]: New session 46 of user astra.
Sep 6 09:40:55 astra-client aldd: GSSAPI client step 1
Sep 6 09:40:55 astra-client aldd: GSSAPI client step 1
Sep 6 09:40:55 astra-client systemd: pam_ald(systemd-user:account): Failed to obtain Kerberos credential cache name.
Sep 6 09:40:55 astra-client [3769]: pam_ald_mac(fly-dm:session): Ошибка создания символической ссылки «/ald_home/astra/mac»: Нет такого файла или каталога
tagilchanin
New member
Спасибо всем. Разобрался сам. Оказывается в настройке пользователя стоят тип файловой системы по умолчания (он был а cifs) , переключил на local и нормально аутентифицировался.
fonarshik
New member
Всем привет! Проблема следующего характера(
Есть контроллер домена на astra se 1.5. Есть ald-client на astra se 1.6!
Клиент на 1.6 великолепно подключился к домену на 1.5 но. пользователь которому делегировпны все права и т.д. для входа на этот клиент есть. при входе логин и пароль принимается и вылетает окошко для выбора режима. но потом черный экран на 3 секунда и вуаля опять экран входа в систему! Подскажите господа куда смотреть, что делать(
Добрый день! Столкнулся с такой же проблемой, подскажите решение есть? Смена файловой системы в настройках не помогает.
azm9s
New member
fonarshik
New member
Jun 11 09:58:09 sm16 fly-dm: :0[2016]: pam_unix(fly-dm:session): session opened for user qwqw by (uid=0)
Jun 11 09:58:09 sm16 fly-dm: :0[2016]: GSSAPI client step 1
Jun 11 09:58:09 sm16 fly-dm: :0[2016]: GSSAPI client step 1
Jun 11 09:58:10 sm16 fly-dm: :0[2016]: GSSAPI client step 1
Jun 11 09:58:10 sm16 fly-dm: :0[2016]: GSSAPI client step 2
Jun 11 09:58:10 sm16 fly-dm: :0[2016]: pam_ald(fly-dm:session): ДОСТУП ЗАПРЕЩЕН: Домашний каталог ‘/ald_home/qwqw’ не принадлежит польвателю ‘qwqw’ или его группе.
Jun 11 09:58:10 sm16 systemd-logind[412]: New session 14 of user qwqw.
Jun 11 09:58:10 sm16 systemd: pam_ald(systemd-user:account): Failed to obtain Kerberos credential cache name.
Jun 11 09:58:10 sm16 fly-dm: :0[2016]: pam_unix(fly-dm:session): session closed for user qwqw
Jun 11 09:58:10 sm16 systemd-logind[412]: Removed session 14.
Jun 11 09:58:10 sm16 fly-dm[2071]: pam_unix(fly-dm-greeter:session): session opened for user fly-dm by (uid=0)
Jun 11 09:58:10 sm16 systemd-logind[412]: Removed session c9.
Jun 11 09:58:10 sm16 systemd-logind[412]: New session c10 of user fly-dm.
Как запустить систему
Gave up waiting for suspend/resume device
/dev/sdc1: recovering journal
/dev/sdc1: clean, 172491/959104 files, 3835904/3840000 blocks
[[0;1;31mFAILED[0m] Failed to start kesl.
See ‘systemctl status kesl-supervisor.service’ for details.
[[0;32m OK [0m] Started Save/Restore Sound Card State.
[[0;32m OK [0m] Started PARSec events logging daemon.
[[0;32m OK [0m] Started Login Service.
[[0;32m OK [0m] Started LSB: Start some power management scripts.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;1;31mFAILED[0m] Failed to start Hostname Service.
See ‘systemctl status systemd-hostnamed.service’ for details.
[[0;32m OK [0m] Started VirtualBox Linux kernel module.
Starting vboxballoonctrl-service.service.
Starting vboxweb-service.service.
Starting vboxautostart-service.service.
[[0;32m OK [0m] Started vboxballoonctrl-service.service.
[[0;32m OK [0m] Started vboxweb-service.service.
[[0;32m OK [0m] Started vboxautostart-service.service.
[[0;32m OK [0m] Started Intitialize Parsec Subsystem.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting Permit User Sessions.
Starting OpenBSD Secure Shell server.
Starting Network Manager Wait Online.
[[0;32m OK [0m] Started Permit User Sessions.
Starting Network Manager Script Dispatcher Service.
Starting Hold until boot process finishes up.
Starting Terminate Plymouth Boot Screen.
[[0;32m OK [0m] Started The FLY get exec service.
[[0;32m OK [0m] Started The FLY login manager.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.
Failed to boot after system update, Arch linux (Failed to start Hostname Services) and others
After I updated the system through pacman , the system fails to boot. It seems that some services are not started during boot time. It shows like this: Error
Failed to start Hostname Services. Failed to Start WPA supplicant. Failed to start Network Manager Script Dispatcher Services. Failed to start dhcpd on various interfaces. Failed to start Permit User Sessions.
- By using bootable USB,
- I mounted the drive,
- arch-chroot to enter the system,
- Updated the packages, re-installed linux , mkinitpcio and systemd as suggested in troubleshooting in arch-wiki.
Next time after reboot, same problem arises. Every time, need to open the system in rescue mode.
Please suggest the solution. I exactly don’t know the cause. Thank you in advance.
1 Answer 1
Have same issue. @fra-san: Thank you for the hint, how to get easily more information from logs, so here’s what I got from that:
Apr 23 22:30:19 myhost systemd[1]: systemd-hostnamed.service: Failed to create cgroup /system.slice/systemd-hostnamed.service: No such file or directory Apr 23 22:30:19 myhost systemd[1]: Starting Hostname Service. Apr 23 22:30:19 myhost systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=219/CGROUP Apr 23 22:30:19 myhost systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. Apr 23 22:30:19 myhost systemd[1]: Failed to start Hostname Service.
On my system, after some warm reboots it was starting up again, so looks like timing or race condition issue.
This same issue has been posted on the Arch Linux Forums. It turned out to be a bug in dhcpcd 9.0.1 (for details: the report on Arch’s bug tracker and the one on dhcpcd’s mailing list).
A working temporary solution is to downgrade dhcpcd to a pre-9.0.1 version. The bug was fixed in version 9.0.2.Failed to start permit user sessions
When my RP boots, I get several errors about some services failing. Most notably ‘permit user sessions’. Which means I can not log in to the device, and I can not make changes to it. I can of course remove the SD card and change the contents that way. I would prefer solutions that do not involve ‘try writing the image to the SD card again.’ I have tried that several times (see other questions by me). So far I have not yet found a way to keep my raspberry pi running more than 1 day. Questions:
- What is happening?
- Why is this happening?
- How do I fix it?
- Is there a release of Raspbian that is at least more stable. This thing feels buggy. Like I mentioned, I have not yet gotten this to work more than 1 day in a row.
Buy a new quality SD Card and make sure to power it down properly. I have several Pi that run for months without issues, but once a SD Card becomes flaky nothing will help.
Why do you assume it’s the SD card? How did you pinpoint that as the root cause? Not making any accusations. Just trying to learn.
I make no assumptions — you have provided no information to draw any conclusions but the error messages indicate OS problems. My (few) similar experiences were flaky SD Cards.
There might be useful information in the system log as to what the errors are. If you haven’t looked at it, that would be a great place to start. If you can’t login, you’ll have to sort out how to look at the /var/log files from another system. Difficult from Windows, easier from Linux, and I assume Mac (altho I am Mac illiterate by choice, so can’t say for sure)
[SOLVED] Login error: «System is booting up»
[SOLVED] Login error: «System is booting up»
by tanrax » Sat Oct 27, 2012 7:54 pm
Since I updated, I have this problem when I try to identify with a non-root user.
She always says:
«System is booting up»Re: Login error: «System is booting up»
by pepedog » Sat Oct 27, 2012 8:26 pm
Re: Login error: «System is booting up»
by tanrax » Sat Oct 27, 2012 9:59 pm
Re: Login error: «System is booting up»
by pepedog » Sat Oct 27, 2012 11:28 pm
Re: Login error: «System is booting up»
by tanrax » Sat Oct 27, 2012 11:44 pm
Re: Login error: «System is booting up»
by pepedog » Sun Oct 28, 2012 12:27 am
Do you have a hdmi monitor or tv plugged in, what does it say on that screen?
Does it say login: and other stuff? Can you login there?Re: Login error: «System is booting up»
by tanrax » Sun Oct 28, 2012 10:21 am
$this->bbcode_second_pass_code(», ‘[FAILED] Failed to start Permit User Sessions.
See ‘systemctl status systemd-user-sessions.service’ for details.
Starrting Getty on tty1′)And execute ‘systemctl status systemd-user-sessions.service’.
$this->bbcode_second_pass_code(», ‘systemd-user-sessions.service — Permit User Sessions
Loaded: loaded (/usr/lib/systemd/system/systemd-user-sessions.service; static)
Active: failed (Result: exit-code) since Thu, 1970-01-01 01:00:16 BST; 42 years and 9 months ago
Docs: man:systemd-user-sessions.service(8)
Process: 106 ExecStart=/usr/lib/systemd/systemd-user-sessions start (co de=exited, status=203/EXEC)
CGroup: name=systemd:/system/systemd-user-sessions.service
‘)Re: Login error: «System is booting up»
by pezz » Sun Oct 28, 2012 12:25 pm
This is because of /usr/lib/tmpfiles.d/systemd.conf:
$this->bbcode_second_pass_code(», ‘F /run/nologin 0755 — — — «System is booting up.»‘)
While /run/nologin exists, the system will only allow root to login, so login as root and either rm the file, or just reboot.
pezz Posts: 74 Joined: Fri Sep 14, 2012 11:19 pm Location: Geelong, Australia
Re: [SOLVED] Login error: «System is booting up»
by tanrax » Sun Oct 28, 2012 1:59 pm