[
https://issues.apache.org/jira/browse/VCL-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth updated VCL-943:
---------------------------
Affects Version/s: (was: 2.3.2)
Remaining Estimate: (was: 48h)
Original Estimate: (was: 48h)
Fix Version/s: 2.5
Component/s: (was: database)
vcld (backend)
> Deep recursion on subroutine VCL::utils::get_vmhost_info
> --------------------------------------------------------
>
> Key: VCL-943
> URL: https://issues.apache.org/jira/browse/VCL-943
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.4.2
> Reporter: Mohammed AlQhatani
> Assignee: Andy Kurth
> Labels: build
> Fix For: 2.5
>
>
> our VCL isn't see images which implemented on KVM with follow error
> Testing api call
> OK: verified user affiliation exists in the database: 'Local'
> OK: verified user exists in the database: 'vclsystem@local'
> OK: verfied xmlrpc_pass value is the correct password for vclsystem@local
> VCL API call successful
> Enter the VCL login name or ID of the user who will own the image: ('c' to
> cancel) [admin]:
> vclsystem
> User who will own the image: vclsystem (ID: 3)
> Enter the hostname or IP address of the computer to be captured: ('c' to
> cancel):
> 10.100.0.188
> Deep recursion on subroutine "VCL::utils::get_computer_info" at
> /usr/local/vcl-2.4.2/bin/../lib/VCL/utils.pm line 3989, <STDIN> line 4
> (#2)
> (W recursion) This subroutine has called itself (directly or indirectly)
> 100 times more than it has returned. This probably indicates an
> infinite recursion, unless you're writing strange benchmark programs, in
> which case it indicates something else.
>
> This threshold can be changed from 100, by recompiling the perl binary,
> setting the C pre-processor macro PERL_SUB_DEPTH_WARN to the desired
> value.
>
> Deep recursion on subroutine "VCL::utils::get_vmhost_info" at
> /usr/local/vcl-2.4.2/bin/../lib/VCL/utils.pm line 7181, <STDIN> line 4
> (#2)
> plus setting for Virtual host setting which require i did please find
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)