Hi Thanks for your answer.
I don't think that's the answer....because i haven't replaced anything really (well, apart from replacing the binaries with a copy of the ones that were already running). I also have those binaries running on two more servers and I don't have this problem there. This suddenly showed up after trying a few new parameters in main.cf and is still there after they have been removed and why postfix seems to add new parameters to main.cf after startup is also a mystery. Is there any way to see what "large file" that might case this ? I will try 2.8.7 compiled the same way as the present 2.8.5 to see if that changes anything. Br Johan -----Ursprungligt meddelande----- Från: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] För Wietse Venema Skickat: den 20 januari 2012 14:59 Till: Postfix users Ämne: Re: Strange Postfix error Johan Andersson: > Jan 19 23:56:21 servername postfix/cleanup[29089]: [ID 947731 > mail.crit] fatal: fstat flow pipe write descriptor: Value too large > for defined data type The logging comes from this code fragment: ssize_t mail_flow_get(ssize_t len) { const char *myname = "mail_flow_get"; char buf[BUFFER_SIZE]; struct stat st; ... if (fstat(MASTER_FLOW_WRITE, &st) < 0) msg_fatal("fstat flow pipe write descriptor: %m"); This is on a pipe between master daemon and child processes. On some UNIX(-like) systems such as 32-bit Solaris and Linux, programs have to be compiled specifically for large (>2GB) files. File handles created in a "large file" process will produce fstat and other errors when inherited by programs that aren't built for "large file" support. Likely cause: you replaced Postfix with a "small file" build, but the "large file" master daemon is still running. Its file handles are inherited by smpd, cleanup, etc., and are causing errors in the "small file" programs. Likely solution: #postfix stop #postfix start Wietse
