I'm having an issue with a new cronjob - the machine is running leap155. I have a userid "dns24" which originally had a homedir of "/srv/dns24". We decided not to use that after all, but didn't change and then noticed these in the log: 2023-05-14T18:41:01+02:00 dns24 systemd[1]: Started User Manager for UID 111. 2023-05-14T18:41:01+02:00 dns24 systemd[1]: Started Session c17 of User dns24. 2023-05-14T18:41:01+02:00 dns24 cron[26821]: pam_unix(crond:session): session opened for user dns24 by (uid=0) 2023-05-14T18:41:01+02:00 dns24 CRON[26831]: (dns24) CMD (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:41:01+02:00 dns24 CRON[26831]: (CRON) ERROR chdir failed (/srv/dns24): No such file or directory ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2023-05-14T18:41:01+02:00 dns24 CRON[26821]: (dns24) CMDEND (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:41:01+02:00 dns24 CRON[26821]: pam_unix(crond:session): session closed for user dns24 2023-05-14T18:41:01+02:00 dns24 systemd[1]: session-c17.scope: Deactivated successfully. Ah, forgot to change the homedir. Changed the homedir using yast. 2023-05-14T18:46:01+02:00 dns24 systemd[1]: Started User Manager for UID 111. 2023-05-14T18:46:01+02:00 dns24 systemd[1]: Started Session c22 of User dns24. 2023-05-14T18:46:01+02:00 dns24 cron[30866]: pam_unix(crond:session): session opened for user dns24 by (uid=0) 2023-05-14T18:46:01+02:00 dns24 CRON[30876]: (dns24) CMD (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:46:01+02:00 dns24 CRON[30876]: (CRON) ERROR chdir failed (/srv/dns24): No such file or directory 2023-05-14T18:46:01+02:00 dns24 CRON[30866]: (dns24) CMDEND (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:46:01+02:00 dns24 CRON[30866]: pam_unix(crond:session): session closed for user dns24 2023-05-14T18:46:01+02:00 dns24 systemd[1]: session-c22.scope: Deactivated successfully. 2023-05-14T18:46:12+02:00 dns24 systemd[1]: Stopping User Manager for UID 111... nscd picked up the change: 2023-05-14T18:45:17+02:00 dns24 nscd[605]: 605 monitored file `/etc/passwd` was written to 2023-05-14T18:45:17+02:00 dns24 nscd[605]: 605 monitored file `/etc/passwd` was moved into place, adding watch yes, /etc/passwd has the new homedir and the new homedir exists. I'm sure I can reboot and all will be well, but .... -- Per Jessen, Zürich (12.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
nscd picked up the change:
I have just now tried 'nscd -i passwd', no change. -- Per Jessen, Zürich (12.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Carlos E. R. wrote:
Sure, but I would prefer not to :-) cron should not be caching this stuff. I'll probably need a reboot soon anyway.
If not, it would be the "user manager", dunno what exactly is that.
Nor me. -- Per Jessen, Zürich (11.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
* Per Jessen <per@opensuse.org> [05-14-23 14:29]:
Carlos E. R. wrote:
...
yast users -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Patrick Shanahan wrote:
The update to /etc/passwd was fine, I checked, but it looks like cron is caching the contents. I've just rebooted, now it's all fine. afaik, nscd is supposed to cache this sort of thing, so either it wasn't queried or cron does its own caching. Anyway, not a big deal. -- Per Jessen, Zürich (11.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Andrei Borzenkov wrote:
Hehe, yeah I did, but it hasn't been changed since 2015 :-) Also, most of it is skipped due to dependencies (intentional). Anyway, I expect the problem could probably be recreated, but it doesn't matter. -- Per Jessen, Zürich (12.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
nscd picked up the change:
I have just now tried 'nscd -i passwd', no change. -- Per Jessen, Zürich (12.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Carlos E. R. wrote:
Sure, but I would prefer not to :-) cron should not be caching this stuff. I'll probably need a reboot soon anyway.
If not, it would be the "user manager", dunno what exactly is that.
Nor me. -- Per Jessen, Zürich (11.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
* Per Jessen <per@opensuse.org> [05-14-23 14:29]:
Carlos E. R. wrote:
...
yast users -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Patrick Shanahan wrote:
The update to /etc/passwd was fine, I checked, but it looks like cron is caching the contents. I've just rebooted, now it's all fine. afaik, nscd is supposed to cache this sort of thing, so either it wasn't queried or cron does its own caching. Anyway, not a big deal. -- Per Jessen, Zürich (11.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
Patrick Shanahan -
Per Jessen