** Description changed: Hello there, - I have a little timing issue on a freshly installed ubuntu mailing server. I want to deal with Spam through amavis using amavisd-milter in socket-pipe-mode. And it fails because of Permissions denied. + I have a little timing issue on a freshly installed ubuntu mailing server. I want to deal with Spam through amavis using amavisd-milter in socket-pipe-mode. And it fails with Permission denied. my postfix User is in the amavis-group and i have set - #MILTERSOCKETOWNER=amavis:amavis - MILTERSOCKETMODE=0660 + #MILTERSOCKETOWNER=amavis:amavis + MILTERSOCKETMODE=0660 in /etc/default/amavisd-milter. But somehow the Socket isn't there when the init-script tries to chmod on it. In syslog (or journalctl -e) there is a line like this: May 18 10:40:23 mail amavisd-milter[14311]: chmod: Zugriff auf '/var/run/amavis/amavisd-milter.sock' nicht möglich: Datei oder Verzeichnis nicht gefunden (Sorry for German Output..., it basically says "File or Directory not found") If i enable the MILTERSOCKETOWNER line in the configuration, the error in syslog says May 18 10:51:54 mail amavisd-milter[14698]: chown: Zugriff auf '/var/run/amavis/amavisd-milter.sock' nicht möglich: Datei oder Verzeichnis nicht gefunden As you can see, now the owner can not be set, but the permissions are ready to go. $ ll /var/run/amavis/amavisd-milter.sock srw-rw---- 1 amavis amavis 0 Mai 18 10:52 /var/run/amavis/amavisd-milter.sock= If i try another thing and add a `ls -l /var/run/amavis` into the init-script right before the if-block for the chown/chmod thing, no error is in the syslog. (see: - log_end_msg 0 - ls -l /var/run/amavis - if [ "$MILTERSOCKETTYPE" = "pipe" ]; then - if [ "$MILTERSOCKETOWNER" ]; then - chown "$MILTERSOCKETOWNER" "$MILTERSOCKET" - fi - if [ "$MILTERSOCKETMODE" ]; then - chmod "$MILTERSOCKETMODE" "$MILTERSOCKET" - fi - fi + log_end_msg 0 + ls -l /var/run/amavis + if [ "$MILTERSOCKETTYPE" = "pipe" ]; then + if [ "$MILTERSOCKETOWNER" ]; then + chown "$MILTERSOCKETOWNER" "$MILTERSOCKET" + fi + if [ "$MILTERSOCKETMODE" ]; then + chmod "$MILTERSOCKETMODE" "$MILTERSOCKET" + fi + fi ) - Can we do something about this? or is my Machine just too fast. (it's as of today just an empty Virtualbox-vm with an fresh installed ubuntu 16.04 for testing the new installation method. (ansible) + Can we do something about this? or is my Machine just too fast. (it's as of today just an empty Virtualbox-vm with a fresh installed ubuntu 16.04 on my Working-Machine for testing the new installation method. (ansible)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691707 Title: amavisd-milter timing issue on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1691707/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
