HTTP Stats Code #400. Agent will not communicate with server.

[keeper05]

It's hard to solve a problem when important details are missing, that why we added this template, to help you and us.

General informations

Operating system : RHEL 8

Server informations

Perl version : v5.26.3 Mysql / Mariadb / Percona version : Ver 15.1 Distrib 10.3.35-MariaDB

OCS Inventory informations

Ocs server version : 2.12 installed via RPM

Problem's description

I am unable to get the Windows Agent (20.10.1.0) to connect to the server. I receive a HTTP 400 error. Below is the relevant part of the agent log and ini.

COM SERVER => Sending fileGet request to URL http://server_IP_Address/ocsinventory/deploy/label

COM SERVER => fileGet response received <HTTP Status Code #400>

COM SERVER => Cleaning cURL library

AGENT => Failed to retrieve Label <HTTP Status Code #400>

AGENT => Sending Prolog

DID_CHECK => Read DeviceID and MACs in file

COM SERVER => Initializing cURL library for sendRequest

COM SERVER => Using cURL without server authentication

COM SERVER => Disabling cURL proxy support

COM SERVER => Disabling cURL SSL server validation support

COM SERVER => Sending HTTP Post request to URL http://server_IP_Address/ocsinventory

COM SERVER => HTTP Post response received <HTTP Status Code #400>

COM SERVER => Cleaning cURL library

Most issues with HTTP Status Code #400 are due to the Agent version being higher than the server version. This is not the case here. Agent ini file looks like this:

[OCS Inventory Agent]

ComProvider=ComHTTP.dll

Debug=1

Local=

NoSoftware=0

HKCU=0

NoTAG=0

IpDisc=

WMI_FLAG_MODE=COMPLETE

DEFAULT_USER_DOMAIN=

[HTTP]

Server=http://server_IP_Address/ocsinventory

SSL=0

CaBundle=cacert.pem

AuthRequired=0

User=

Pwd=

ProxyType=0

Proxy=

ProxyPort=0

ProxyAuthRequired=0

ProxyUser=

ProxyPwd=

[OCS Inventory Service]

TTO_WAIT=1020

INVENTORY_ON_STARTUP=0

[Lea9250]

Hi @keeper05 ,

Do you have any logs referring to this on the server ? You'll want to look at the apache error log and the activity log populated by OCS (/var/log/ocsinventory-server/activity.log). If not already done, you'll need to enable LOGLEVEL under Configuration > Server from the GUI. For debugging purposes you can also set the OCS_OPT_DBI_PRINT_ERROR to 1 in /etc/apache2/conf-enabled/z-ocsinventory-server.conf, restart the apache service and then trigger an inventory of your computer before checking the logs.

Let me know how this goes.

Léa

[Lea9250]

Hi @keeper05,

Any update on this matter ?

Regards, Léa

[keeper05]

Yes Lea. I was unable to get it working via http. I ended up having to go to the SSL route due to this issue. As I had stated in the issue, the symptoms are indicative of using a new agent than the server version.

On Mon, Oct 30, 2023 at 11:04 AM Lea9250 @.***> wrote:

Hi @keeper05 https://github.com/keeper05,

Any update on this matter ?

Regards, Léa

— Reply to this email directly, view it on GitHub https://github.com/OCSInventory-NG/OCSInventory-Server/issues/440#issuecomment-1785539909, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABC4TYI3JJTC5VMQURCNWYTYB7FYJAVCNFSM6AAAAAA5P62SZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGUZTSOJQHE . You are receiving this because you were mentioned.Message ID: @.***>

[Lea9250]

Hi @keeper05,

I'll close this since the issue is no longer reproducible but feel free to reopen if you end up with the same problem at some point. As a side note, the fact that you were able to send inventory through https makes me think of an apache configuration issue, but that would depend on whether or not you had modified the "default" ocs configuration files and how. For agent vs server version conflicts though, the activity.log of the server (see previous message for enabling) usually gives a warning if there is any.

Best regards, Léa

[keeper05]

I had no issues accessing the dashboard via http. The agents just wouldn’t connect via http. On Dec 5, 2023, at 08:32, Lea9250 @.***> wrote: Hi @keeper05, I'll close this since the issue is no longer reproducible but feel free to reopen if you end up with the same problem at some point. As a side note, the fact that you were able to send inventory through https makes me think of an apache configuration issue, but that would depend on whether or not you had modified the "default" ocs configuration files and how. For agent vs server version conflicts though, the activity.log of the server (see previous message for enabling) usually gives a warning if there is any. Best regards, Léa

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>