Univention Bugzilla – Bug 51256
univention-self-service-passwordreset-umc.service fails with systemd-memcached-wrapper error
Last modified: 2020-05-12 14:35:35 CEST
After installing the self service frontend univention-self-service-passwordreset-umc.service can't start due to the following error reported in the journal: Mai 09 22:23:41 slave systemd[1]: Started memcached daemon (univention-self-service instance). Mai 09 22:23:41 slave systemd-memcached-wrapper[30462]: can't find the user self-service-umc to switch to Mai 09 22:23:41 slave systemd[1]: univention-self-service-passwordreset-umc.service: Main process exited, code=exited, status=67/n/a Mai 09 22:23:41 slave systemd[1]: univention-self-service-passwordreset-umc.service: Unit entered failed state. Mai 09 22:23:41 slave systemd[1]: univention-self-service-passwordreset-umc.service: Failed with result 'exit-code'. On the backend the service is able to start.
Needmoreinfo * Is the frontend app installed on a different server that the backend app? * What is the impact that the service cannot be started?
(In reply to Erik Damrose from comment #1) > Needmoreinfo > * Is the frontend app installed on a different server that the backend app? Yes, backend on DC Master, frontend on a DC Slave > * What is the impact that the service cannot be started? At least some UCR vars don't seem to work/take effect. For example I activated the self registration via and still it never showed up in the self service. There surely are some other effects but we had to fix it manually with the customer before I could test everything.
Please be specific in a bug report with that high user pain. We need as much information as possible to reproduce the issue. * What did the setup look like (we know a DC Master and DC Slave are used), erratalevel etc. * Which configuration steps were taken after the app installation * What did you/the customer want so accomplish, what did not work
(In reply to Erik Damrose from comment #3) > Please be specific in a bug report with that high user pain. We need as much > information as possible to reproduce the issue. > * What did the setup look like (we know a DC Master and DC Slave are used), > erratalevel etc. Actually there is a DC Master, 2 DC Backup and a couple of Slaves. (4.4-4 errata579). > * Which configuration steps were taken after the app installation I don't remember the exact details, but the error message from comment#0 is what we got on all slaves. Apparently something tried start the "univention-self-service-passwordreset-umc.service" there while the users "self-service-umc" does not exist. Looking at the univention-self-service-passwordreset-umc.postinst that seems to be correct. The user is only created on the master and backup server roles. Though we're unsure why that service is installed at all on the slave and what tried to enable/start it. > * What did you/the customer want so accomplish, what did not work