On Sun, 2 Jan 2022, Ken Wright wrote:
On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
Does it also fail when run as root? In that case,
# strace -e connect postqueue -p |&grep showq
Otherwise, some temporary hack is needed.
As root, disdable file permissions:
# chmod 777 /var/spool/postfix/public
# chmod g-s /usr/sbin/postqueue
As non-root,list the queue:
$ strace -e connect postqueue -p
Here's the output:
connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
-1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_UNIX, sun_path="public/showq"}, 110) = 0
What permissions and ownership should I set for the /var/run/nscd
directory?
Ken
Chances are you don't have ncsd installed and running. It's normal for
that "error message" to appear when this is so. You don't need to have
nscd installed for normal operation of postfix. That's not the problem.
best regards
Kenneth
