Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 30 replies
  • Subscribers 1 subscriber
  • Views 20035 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

I/O timeout on content could not be loaded

ranchodeluxe
I received the following message after upgrade to 5.018, while surfing:

Content could not be loaded  
     
     
   Please check the spelling of your URL.

Make sure that your proxy settings are in order.

The following lines may provide some additional information to the cause of the failure.



I/O timeout 

I did not change any settings. Any ideas?


This thread was automatically locked due to age.
Parents
  • 0
    ok here's a possible workaround: 
    WARNING SUPPORT VOID AFTER THIS!!!
    in the file /var/chroot-http/etc/hyperdyper.conf find the segment:
    Code:
      

            5
            30
            30
            150
            30
            30

     

    and replace it with 

    Code:
      

            5
            300
            300
            300
            300
            30

     

    finally, restart the hyperdyper with 
    Code:

    /var/mdw/scripts/hyperdyper.sh restart
  • 0 in reply to Vukasin
    did you try this:
    [ QUOTE ]
    ok here's a possible workaround: 
    WARNING SUPPORT VOID AFTER THIS!!!
    in the file /var/chroot-http/etc/hyperdyper.conf find the segment:
    Code:
      

            5
            30
            30
            150
            30
            30

     

    and replace it with 

    Code:
      

            5
            300
            300
            300
            300
            30

     

    finally, restart the hyperdyper with 
    Code:

    /var/mdw/scripts/hyperdyper.sh restart
     

    [/ QUOTE ]
  • 0 in reply to Vukasin
    V,

    Does Astaro intend to rlease this workaround as an official up2date?  30 seconds is usually enough for 99% of all sites.  This issue did not appear until 5.018/19.  Did those up2dates change those timeouts to 30 seconds?  If not then leaving the content filter always rujnning is a big problem as even higher end hardware is having this issue it seems.

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

Reply
  • 0 in reply to Vukasin
    V,

    Does Astaro intend to rlease this workaround as an official up2date?  30 seconds is usually enough for 99% of all sites.  This issue did not appear until 5.018/19.  Did those up2dates change those timeouts to 30 seconds?  If not then leaving the content filter always rujnning is a big problem as even higher end hardware is having this issue it seems.

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

Children