Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 01-19-2007, 05:18 PM
Loyal Member
 
Posts: 76
Question Postfix fatal: fstat flow pipe write descriptor: Value too large for defined data typ

Hello again,

after successfully installing 4.5 (SLES9) I run into the next problem. It is not possible to recieve or sent any messages. Se the enclosed Messages from zimbra.log.

Any help is apreciated,

Friedmar


Jan 20 01:58:42 vs2053015 postfix/smtpd[3142]: TLS connection established from acm26-4.acm.org[63.118.7.109]: SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)
Jan 20 01:58:43 vs2053015 postfix/cleanup[3157]: fatal: fstat flow pipe write descriptor: Value too large for defined data type
Jan 20 01:58:44 vs2053015 postfix/smtpd[3142]: warning: premature end-of-input on public/cleanup socket while reading input attribute name
Jan 20 01:58:44 vs2053015 postfix/smtpd[3142]: fatal: unable to connect to the public cleanup service
Jan 20 01:58:44 vs2053015 postfix/master[25748]: warning: process /opt/zimbra/postfix-2.2.9/libexec/cleanup pid 3157 exit status 1
Jan 20 01:58:44 vs2053015 postfix/master[25748]: warning: /opt/zimbra/postfix-2.2.9/libexec/cleanup: bad command startup -- throttling
Jan 20 01:58:45 vs2053015 postfix/master[25748]: warning: process /opt/zimbra/postfix-2.2.9/libexec/smtpd pid 3142 exit status 1
Jan 20 01:58:45 vs2053015 postfix/master[25748]: warning: /opt/zimbra/postfix-2.2.9/libexec/smtpd: bad command startup -- throttling
Jan 20 01:59:45 vs2053015 postfix/smtpd[3281]: initializing the server-side TLS engine
Jan 20 01:59:45 vs2053015 postfix/smtpd[3281]: connect from host13-74-dynamic.1-87-r.retail.telecomitalia.it[87.1.74.13]
Jan 20 01:59:45 vs2053015 postfix/smtpd[3281]: lost connection after CONNECT from host13-74-dynamic.1-87-r.retail.telecomitalia.it[87.1.74.13]
Jan 20 01:59:45 vs2053015 postfix/smtpd[3281]: disconnect from host13-74-dynamic.1-87-r.retail.telecomitalia.it[87.1.74.13]
Reply With Quote
  #2 (permalink)  
Old 01-19-2007, 06:11 PM
Zimbra Employee
 
Posts: 274
Default

What is the output of

/opt/zimbra/postfix/sbin/postconf -n
__________________
Bugzilla - Wiki - Downloads - Before posting... Search!
Reply With Quote
  #3 (permalink)  
Old 01-20-2007, 12:10 AM
Loyal Member
 
Posts: 76
Default

# /opt/zimbra/postfix/sbin/postconf -n
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /opt/zimbra/postfix-2.2.9/sbin
config_directory = /opt/zimbra/postfix-2.2.9/conf
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /opt/zimbra/postfix-2.2.9/libexec
disable_dns_lookups = no
header_checks = pcre:/opt/zimbra/conf/postfix_header_checks
html_directory = no
mail_owner = postfix
mailbox_size_limit = 0
mailq_path = /opt/zimbra/postfix-2.2.9/sbin/mailq
manpage_directory = /opt/zimbra/postfix-2.2.9/man
message_size_limit = 10240000
myhostname = myserver.vserver.de
newaliases_path = /opt/zimbra/postfix-2.2.9/sbin/newaliases
queue_directory = /opt/zimbra/postfix-2.2.9/spool
readme_directory = no
recipient_delimiter =
relayhost =
sample_directory = /opt/zimbra/postfix-2.2.9/conf
sender_canonical_maps = ldap:/opt/zimbra/conf/ldap-scm.cf
sendmail_path = /opt/zimbra/postfix-2.2.9/sbin/sendmail
setgid_group = postdrop
smtpd_client_restrictions = reject_unauth_pipelining
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_helo_required = yes
smtpd_recipient_restrictions = reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unlisted_recipient, reject_invalid_hostname, reject_non_fqdn_sender, reject_unauth_destination, permit
smtpd_reject_unlisted_recipient = no
smtpd_sasl_auth_enable = yes
smtpd_tls_auth_only = no
smtpd_tls_cert_file = /opt/zimbra/conf/smtpd.crt
smtpd_tls_key_file = /opt/zimbra/conf/smtpd.key
smtpd_tls_loglevel = 3
smtpd_use_tls = yes
transport_maps = ldap:/opt/zimbra/conf/ldap-transport.cf
virtual_alias_domains = ldap://opt/zimbra/conf/ldap-vad.cf
virtual_alias_maps = ldap:/opt/zimbra/conf/ldap-vam.cf
virtual_mailbox_domains = ldap:/opt/zimbra/conf/ldap-vmd.cf
virtual_mailbox_maps = ldap:/opt/zimbra/conf/ldap-vmm.cf
virtual_transport = error
Reply With Quote
  #4 (permalink)  
Old 01-22-2007, 10:43 PM
Loyal Member
 
Posts: 76
Angry

Hello,

I still had no success solving this problem. Could it be something external?

After I restored my 4.05 Zimbra the error was still there!. Then I restored the complete system (system backup) to a state that worked. Guess what? The error stayed.

So I installed Zimbra from scratch. It seems to work. Then I added the data to it. Here it is again. Semms there is a part for the postfix configuration somewhere in the databases or in LDAP.

Any idea?

Friedmar
Reply With Quote
  #5 (permalink)  
Old 01-23-2007, 12:21 AM
Zimbra Employee
 
Posts: 274
Default

googling that error, looks like you might have a broken fstat() implementation - perhaps because of your vserver?

http://groups.google.com/group/maili...bae9ad3f2d59b7
__________________
Bugzilla - Wiki - Downloads - Before posting... Search!
Reply With Quote
  #6 (permalink)  
Old 01-23-2007, 12:54 PM
Loyal Member
 
Posts: 76
Default

I guess not. If I use a new installad version it works. When I put in my data the error occurs.

I found this hint in google as well and it I checked it. Also this error is in debian 3.1 and suse 9.3.

The only reason that could be is that the hostserver has a problem. That is possible because they changed something last week. But the provider says we are not gilty. Of cause!

Any idea for a workarround?

Friedmar
Reply With Quote
  #7 (permalink)  
Old 01-28-2007, 11:46 AM
Loyal Member
 
Posts: 76
Talking

Hallo,

thank everybody that tried to help.

Yesterday the host-server of my vps stopped working. The provider informed me that due to hardwarefailers the hardware has to be changed.

Two hours ago the system was available again. And Zimbra worked!

So the reason for the error seames to be the hardware failure. But the provider denied last week that they were responsible. They offerd only charged support. When I asked for compensation if the reason is caused by the provider they told me that they will not support me. To fix the problem I should reinstall my vps. I did so without eleminating the error.



Regards,

Friedmar
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.