LFS207 - LAB 29.3 (using LDAP) - oddjob to install

luigicucciolillo

hi all,
maybe i'm getting it wrong, or maybe the problem is somewhere else,
but,

in LAB 29.3, step 5, when it comes to restart the modified service,
i cannot find it,
it was necessary to install with apt.

from terminal

missing

~$ systemctl restart sssd oddjob
Failed to restart sssd.service: Access denied
See system logs and 'systemctl status sssd.service' for details.
Failed to restart oddjob.service: Access denied
See system logs and 'systemctl status oddjob.service' for details.

installing

~$ sudo apt install oddjob oddjob-mkhomedir
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
oddjob is already the newest version (0.34.7-2).
oddjob set to manually installed.
oddjob-mkhomedir is already the newest version (0.34.7-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

restart

~$ systemctl restart sssd oddjobd
~$ systemctl enable sssd oddjobd
Synchronizing state of sssd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable sssd

Running on

~$ hostnamectl
...
Operating System: Ubuntu 24.04.4 LTS
Kernel: Linux 7.0.0-28-generic
Architecture: x86-64
...

btw, something wrong with the triple-backtick code fence to add terminal here!

fazlur.khan

Dear @luigicucciolillo

Good catch on posting the full command and the error output, as that makes this easy to diagnose. The Access denied message tells us this is a privileges issue rather than anything wrong with the services themselves. systemctl restart needs root, and your prompt ending in $ suggests you're currently running as a regular user, whereas the lab manual asks you to work as root, where the prompt ends in** #**. You can fix this in one of two ways. Either switch to a root shell with sudo -i, after which your prompt will change to # and you can run the command exactly as written in the manual, or simply prefix the single command with sudo, i.e. sudo systemctl restart sssd oddjob. Both work equally well. One thing worth noting as you continue through the lab: read-only commands like systemctl status sssd will run fine as a regular user, so it's specifically the state-changing operations (start, stop, restart, enable, disable) that require root. Give it another go and let us know how you get on.

luigicucciolillo

hi there.
sorry for late reply.

well, it happened that i rebooted the laptop, really bad decision:

the modified PAM in local machine created a misunderstanding with the GRUB.
when the GRUB was starting gdm3, it got stacked and was returning a black screen.

after ours of troubleshooting,
addressing the GRUB for a while,
and after swearing against gdm3,
i just entered in text mode via an older version (systemd.unit=multi-user.target), reistalled several packages and changed graphic server (now running on LightDM)

Helped by AI, seems that when init (after GRUB) was giving control to GDM3, it got stacked because PAM rules changed.

So, black screen due to GDM3 failing at startup because PAM changed.

it was a long trip into the bowels of Linux