• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Postfix still sending hundreds 'queue file write error'

I still get that bloody error in a fresh install of Plesk 9.5.1

Apr 23 22:49:55 server1 before-remote[30085]: System error: Broken pipe
Apr 23 22:49:55 server1 before-remote[30085]: Unable to write data to stream
Apr 23 22:49:55 server1 before-remote[30085]: Some error occured
Apr 23 22:49:55 server1 postfix/spawn[30084]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255

Centos OS 5
 
I think it would be a good thing to release an update for plesk 9.3 to get this fix over the plesk update.
 
Just as a note; problems seem to have gone away after upgrade to 9.5.2, most workarounds mentioned in the start of this thread are still in place, though.

Having to upgrade (meaning: having to maintain the SUS on the license) for this is of course still atrocious...
 
Just as a note; problems seem to have gone away after upgrade to 9.5.2, most workarounds mentioned in the start of this thread are still in place, though.

Having to upgrade (meaning: having to maintain the SUS on the license) for this is of course still atrocious...

Are you sure?
what about this thread:
http://forum.parallels.com/showthread.php?t=100914

I am worried to upgrade to 9.5.x version before make sure this error is gone

Sc
 
I am hesitant to say the problem has completely gone; the upgrade was done on friday, and no 'lost connection with localhost' errors have been reported over the weekend, but of course not much mail was sent over the weekend.

Also, i have very long timeouts and have disabled the spam filtering on the Plesk host. This may not be a viable solution for anyone else..
 
Are you sure?
what about this thread:
http://forum.parallels.com/showthread.php?t=100914

I am worried to upgrade to 9.5.x version before make sure this error is gone

Sc
Writing in to confirm the problem has gone for me, but then again I disabled all forms of spam filtering (as evidenced in my post somewhere in the first pages of this topic). AFAIK the only part of Postfix built/extended by parallels still in use on my system is plesk_virtual (to actually deliver the mail to Maildir).
 
SMTP Timeouts with 9.5.2

Hello,

_since upgrading_ to 9.5.2 I get these SMTP timeouts.
The log shows:

Jul 26 10:42:08 k1 postfix/spawn[15324]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 10:42:08 k1 postfix/spawn[29048]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 10:49:08 k1 postfix/spawn[17682]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 10:54:15 k1 postfix/spawn[4596]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 10:54:47 k1 postfix/spawn[28504]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 16056: command time limit exceeded
Jul 26 10:54:47 k1 postfix/spawn[28506]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 16057: command time limit exceeded
Jul 26 10:57:58 k1 postfix/spawn[20384]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:13:23 k1 postfix/spawn[8474]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:13:23 k1 postfix/spawn[8476]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:25:21 k1 postfix/spawn[27521]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:26:01 k1 postfix/spawn[22470]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 23615: command time limit exceeded
Jul 26 11:26:01 k1 postfix/spawn[22004]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 23614: command time limit exceeded
Jul 26 11:30:39 k1 postfix/spawn[26701]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:30:53 k1 postfix/spawn[24373]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 24796: command time limit exceeded
Jul 26 11:30:53 k1 postfix/spawn[22006]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 24797: command time limit exceeded
Jul 26 11:32:39 k1 postfix/spawn[27521]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:36:46 k1 postfix/spawn[8476]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 26470: command time limit exceeded
Jul 26 11:36:46 k1 postfix/spawn[8474]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 26469: command time limit exceeded
Jul 26 11:39:26 k1 postfix/spawn[28504]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:39:26 k1 postfix/spawn[28506]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Jul 26 11:40:42 k1 postfix/spawn[21412]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 27473: command time limit exceeded
Jul 26 11:40:42 k1 postfix/spawn[26703]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 27474: command time limit exceeded
Jul 26 11:47:22 k1 postfix/spawn[27890]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 30123: command time limit exceeded
Jul 26 11:47:22 k1 postfix/spawn[27921]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 30124: command time limit exceeded
Jul 26 11:47:32 k1 postfix/spawn[26616]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 30230: command time limit exceeded
Jul 26 11:47:32 k1 postfix/spawn[25821]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 30231: command time limit exceeded
Jul 26 11:50:30 k1 postfix/spawn[26701]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 31439: command time limit exceeded
Jul 26 11:50:30 k1 postfix/spawn[27523]: warning: /usr/lib/plesk-9.0/postfix-queue: process id 31440: command time limit exceeded

I bought a support ticket but I want to have this refunden if it is a bug within Plesk.
My receipt shows that I will get additional information in about 1 business day - I hope this will take not that long - my clients go mad...

Is there ANYTHING I can do??

BR

Daniel Khan
 
Plesk 9.5.2

Hi, I read in the release notes that the bug is fixed on 9.3.0 ::

- Timeout in postfix-queue prohibiting to send messages with big attachments from Parallels Plesk Panel server bug is fixed.

But I still get the email about "Out: 451 4.3.0 Error: queue file write error" and "Out: 451 4.3.0 Error: queue file write error" in my mail log.

Is it only fixed for 9.3.x but not 9.5.x ?

Thanks.
 
All bugfixes from 9.3.x are included to 9.5.x version of Plesk.
 
Thanks for your reply IgorG.. So i'll open another thread with that issue but for 9.5.2 then.
 
Back
Top