Support #19349
closed
ERF12-8202 [ProxyAPI::ProxyException]: Unable to retrieve unused IP ([RestClient::BadRequest]: 400 Bad Request)
Description
Hi,
we are using foreman version 1.13.0
we rebooted host running foreman services last week, and then permissions got messed up
can't able to start services automatically,
We manually created /run/foreman and /run/foreman-proxy directories and changed permissions
Then both services are running now except proxy can't assign IP using dhcp
I am guessing some gem or module updated recently .
Error from API:
ERF12-8202 [ProxyAPI::ProxyException]: Unable to retrieve unused IP ([RestClient::BadRequest]: 400 Bad Request)
The error from smart-proxy logs:
E, [2017-04-19T12:17:57.175466 #25940] ERROR -- : Error: 401 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>401 Authorization Required</title>
</head><body>
<h1>Authorization Required</h1>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
</body></html>
Files
Updated by Dominic Cleal about 7 years ago
- Project changed from Foreman to Smart Proxy
- Category set to DHCP
- Status changed from New to Need more information
The logs you provided don't match. One states a 400 error and the other states a 401 error. It's likely that the smart proxy log is an unauthorised request, not related to when the Foreman action occurred.
Please provide the full smart proxy log from when the Foreman error occurs, preferably at DEBUG level in /etc/foreman-proxy/settings.yml.
Updated by Bhanu Prasad Ganguru about 7 years ago
Please find the attached proxy.log
Updated by Anonymous about 7 years ago
It appears you have an issue with smart-proxy authenticating against an infoblox server. Make sure the credentials supplied in infoblox dhcp provider configuration file are correct.
Updated by Dominic Cleal about 7 years ago
- Tracker changed from Bug to Support
- Project changed from Smart Proxy to Infoblox
- Category changed from DHCP to DHCP plugin
Updated by Bhanu Prasad Ganguru almost 7 years ago
Thanks Dmitri,
We are able to solve the authentication issues and everything is working as excepted
But logging in to foreman API taking a very long time , previously it used to be instantaneous
How can we resolve this issue
--Bhanu
Updated by Bhanu Prasad Ganguru almost 7 years ago
- Status changed from Need more information to Resolved