Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1513 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Broken Pipe With Mail

susana
Hello.
We have a Astaro v. 7.101 and when we send e-mails with the WebMail client, sometimes we see a error (screenshot attachment). 
In the log we can see "broken pipe" errors:
2008:02:26-07:38:43 (none) httpproxy[16684]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x853ee48" function="tunnel_response" file="tunnel.c" line="225" message="write: Broken pipe"

2008:02:26-07:38:43 (none) httpproxy[16684]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="block" method="GET" srcip="172.16.60.57" user="" statuscode="502" cached="0" profile="profile_0" filteraction="action_REF_MmaEnLngct" size="5307" time="5 ms" request="0x853ee48" url="www.correoaytopalencia.es/.../main.css

What is the cause of this error?


This thread was automatically locked due to age.
  • 0
    Hi,

    Hello.
    We have a Astaro v. 7.101 and when we send e-mails with the WebMail client, sometimes we see a error (screenshot attachment). 
    In the log we can see "broken pipe" errors:
    2008:02:26-07:38:43 (none) httpproxy[16684]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x853ee48" function="tunnel_response" file="tunnel.c" line="225" message="write: Broken pipe"

    2008:02:26-07:38:43 (none) httpproxy[16684]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="block" method="GET" srcip="172.16.60.57" user="" statuscode="502" cached="0" profile="profile_0" filteraction="action_REF_MmaEnLngct" size="5307" time="5 ms" request="0x853ee48" url="http://www.correoaytopalencia.es/default/main.css?v=235949a08a4a763156d6cbc2fd22541c" error="Broken pipe"

    What is the cause of this error?


    Can you update to 7.103 and check if that fixes this error? This is a known issue in version prior to ASG 7.102 which should be fixed in the latest version.

    Cheers,

    Sven.