Description of problem: mga7 beta2 dovecot.service: Failed at step NAMESPACE spawning /usr/bin/doveadm: No such file or directory Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Clean network install 2. journalctl | grep doveadm # journalctl --no-hostname| grep dovecot <snippet> systemd[24787]: dovecot.service: Failed to set up mount namespacing: No such file or directory systemd[24787]: dovecot.service: Failed at step NAMESPACE spawning /usr/bin/doveadm: No such file or directory systemd[1]: dovecot.service: Control process exited, code=exited status=226
I have no idea why my old cauldron 2019-01-21 19:09 clean plus updates, did not fail, but today's clean install has the problem. Temporary workaround: As root mkdir /etc/systemd/system/dovecot.service.d/ cat > /etc/systemd/system/dovecot.service.d/xz__dovecot.service [Service] PrivateTmp=false Ctrl d systemctl start dovecot systemctl status dovecot
Weird, my other clean install on a different node does not have the same problem nor requires the workaround.
(In reply to Bit Twister from comment #2) > Weird, my other clean install on a different node does not have > the same problem nor requires the workaround. Assigning to the registered maintainer, who might have an idea what causes this.
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMEDAssignee: bugsquad => shlomifCC: (none) => marja11
Closing as resolved. I have no idea why original install caused problem. All install are done with custom install scripts and everything goes into log files using the script command. Nothing in any logs about dovecot install problems Did a urpme dovecot and answered y to delete other package files. Then did urpmi dovecot, and ran my dovecot_changes script just like it was done via my "new_install" script. start/status dovecot show no errors.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED