You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/05/24 03:50:19 UTC

[jira] [Resolved] (CLOUDSTACK-2639) Occasional error by restart network or virtual router

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang resolved CLOUDSTACK-2639.
------------------------------------

    Resolution: Fixed
    
> Occasional error by restart network or virtual router
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-2639
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2639
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.0.0
>            Reporter: Sheng Yang
>            Assignee: Sheng Yang
>             Fix For: 4.2.0
>
>
> Occasional error by restart network or virtual router
> Sometime we faces occasional error by restart network or virtual router.
> In case of restart network by API 200 times, we found 3 errors then, 
> in case of restart virtual router 200 times, we found 5 errors then.
> The errors are found in management server log, job-130187 for instance.
> ------------------------------------
> failed due to LoadBalancerConfigCommand on domain router 10.129.51.128 failed.
> message: [WARNING] 348/024433 (3249) : config : 'option forwardfor' ignored for
> proxy '210_129_192_105-8080' as it requires HTTP mode.
> ------------------------------------
> VR log's error is below:
> ------------------------------------
> Dec 14 02:44:41 r-17544-VM cloud: Loadbalancer public interfaces = eth2 eth3
> eth4
> Dec 14 02:44:43 r-17544-VM cloud: New instance failed to start, resuming
> previous one.
> Dec 14 02:44:43 r-17544-VM cloud: Reconfiguring loadbalancer failed
> ------------------------------------

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira