Infoblox’s global team of threat hunters uncovers a DNS operation with the ability to bypass traditional security measures and control the Great Firewall of China. Read about “Muddling Meerkat” and the many other threat actors discovered by Infoblox Threat Intel here.

API & Integration, DevOps,NetOps,SecOps

Reply

restart_status() incorrectly returns nothing

New Member
Posts: 3
1001     0

We have a perl script which restarts our Infoblox service, but only when configuration changes require a service restart to take effect.

 

However, we've noticed that even though the Infoblox UI tells us configuration changes require a service restart, $session->restart_status() says it doesn't.

 

Sometimes restart_status() indicates a restart is needed, other times it wont.

Has something changed, or is this a known issue?

 

my @restart_list = $session->restart_status();
if (scalar( @restart_list ) > 0)
{
   $session->restart( delay_between_members => 10, );
}

Version information:
Perl module: 8.00660021654873509
Server's Infoblox appliance version: 8.6.2-49947-c076923293a0

Re: restart_status() incorrectly returns nothing

[ Edited ]
Moderator
Moderator
Posts: 298
1001     0

Please make note, the Perl API is deprecated since NIOS 8.4.0, March 2019.  At some point in the future it will no long er be supported.  It's recommended to move all development to use WAPI / REST API instead.

Re: restart_status() incorrectly returns nothing

New Member
Posts: 3
1001     0

Thanks MRichard,

 

Would you pass along a link to the deprecation notice?  I've searched everything I can think of.  But, my google-fu is weak today.

 

Many thanks,

Marshall

Re: restart_status() incorrectly returns nothing

Moderator
Moderator
Posts: 298
1001     0

This is detailed in the release notes for each recent release.  They can be found at https://support.infoblox.com within the Download Center section.

Re: restart_status() incorrectly returns nothing

New Member
Posts: 3
1001     0

We've been working with Infoblox support.

 

Through much testing, I've confirmed that in order to get restart_status() to correctly report if configuration changes require a restart; the user's account must be set to have super user permission.

Showing results for 
Search instead for 
Did you mean: 

Recommended for You