Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.11.1 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

win agent 2.4.0 can't send info to server [closed]

win agent 2.4.0 can't send info to server

Logfile:

==============================================================================
Starting OCS Inventory NG Agent on Friday, October 05, 2018 11:24:01.
AGENT => Running OCS Inventory NG Agent Version 2.4.0.0
AGENT => Using OCS Inventory NG FrameWork Version 2.4.0.0
AGENT => Loading plug-in(s)
    DLL PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
    DLL PLUGIN => 0 DLL Plug-in(s) successfully loaded on 0 DLL(s) found
AGENT => Using network connection with Communication Server
    COM PROVIDER => Loading Communication Provider <C:\Program Files (x86)\OCS Inventory Agent\ComHTTP.dll>
AGENT => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.4.0.0>
AGENT => Sending Prolog
    DID_CHECK => Read DeviceID <MYPC-2018-10-05-11-21-36> and MACs <D4:BE:D9:67:AC:2774:E5:43:50:E3:0300:FF:B0:FB:87:6E> in file <ocsinventory.dat>
    COM SERVER => Initializing cURL library for sendRequest
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Enabling cURL SSL server validation support using CA Bundle <C:\ProgramData\OCS Inventory NG\Agent\cacert.pem>
    COM SERVER => Sending HTTP Post request to URL <https://ocs.xxxserverxxx.nl/ocsinventory>
    COM SERVER => HTTP Post response received <HTTP Status Code #400>
    COM SERVER => Cleaning cURL library
================= TRACE START ===============

================= TRACE STOP ===============
ERROR *** AGENT => Failed to send Prolog <HTTP Status Code #400>
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:00.

Config file

[OCS Inventory Agent]
ComProvider=ComHTTP.dll
Debug=2
Local=
NoSoftware=0
HKCU=0
NoTAG=0
IpDisc=
[HTTP]
Server=https://ocs.xxxserverxxx.nl/ocsinventory
SSL=1
CaBundle=C:\ProgramData\OCS Inventory NG\Agent\cacert.pem
AuthRequired=0
User=
Pwd=
ProxyType=0
Proxy=
ProxyPort=0
ProxyAuthRequired=0
ProxyUser=
ProxyPwd=
[OCS Inventory Service]
TTO_WAIT=0
INVENTORY_ON_STARTUP=0

Al computers with Agent version 2.3.0.0 are working fine
Testcomputers running Agent version 2.4.0.0 are not connecting to the server
Config file for both versions is identical

Tested with server version 2.4.0, 2.4.1 and 2.5.0
Al with the same result. Agent 2.3.0.0 is working fine and 2.4.0.0 is not.

As pointed out by others with the same error....
after installing agent 2.4.0.0 all software components are on version 2.4.0.0 except OcsService.exe witch is on version 2.3.1.1. Could this be the cause? Is a OcsService.exe available in version 2.4.0?

Where should I start with troubleshooting
- client side? how?
- server side? how? (Server = CentOS 7)

Other server info
Linux x86_64 - 3.10.0-862.6.3.el7.x86_64
Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16
PHP 5.4.16
mod_perl/2.0.10 Perl/v5.16.3
MariaDB Server version 10.1.34-MariaDB

Also tried via HTTP / SSL=0 but also no connection possible

Update 2018-10-05 / 13.27
Tried to install Agent version 2.3.1.1
Everything works fine
Issue is only with Agent version 2.4.0.0

closed with the note: workaround with new install
in OCS Inventory NG agent for Windows by (450 points)
closed by

8 Answers

0 votes
Hi,

Error 400 means that agent version is greater than server version. Agent version must be lower or equal to server version.

So if you want to use 2.4.0.0 agent then you must have server 2.4.x or 2.5.x.

Regards

Frank
by (88.5k points)
0 votes
Hi Frank,

Thanx for helping,

Our server is running 2.5, also tried with 2.4.0 and 2.4.1
So server release isn't the issue.
And as stated before, Al other agent versions, up to 2.3.1.1 are working fine.
by (450 points)
0 votes

Hi,

I've tested. My configuration is the following:

OS Name: Linux x86_64 

Version: 3.10.0-862.14.4.el7.x86_64

Php version: 5.4.45

Web server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_fcgid/2.3.9/PHP/5.4.45 mod_perl/2.0.10 Perl/v5.16.3

Database server: MariaDB Server version 5.5.60-MariaDB 

Version OCSReports: 2.5

  1. with agent 2.1.1.3 inventory sent without errors
  2. I've upgraded agent from 2.1.1.3 to 2.4 => inventory sent to the server without errors.
  3. I installed agent 2.4.0.0 directly (reset my windows vm) => inventory sent to the server without errors.

by (88.5k points)
0 votes
Hmm, strange....

Some questions about your test environment....

Do you have OcsService.exe v2.3.1.1 or v2.4? => Seems so strange to me that OcsService version doesn'n match other components

Do you run inventory via OcsService or start inventory manual?
by (450 points)
0 votes
I have ocsservice.exe 2.3.1.1. The windows developper has omit to update version number.
by (88.5k points)
0 votes
Only real difference is PHP version.

I'll update PHP first and test again.

Will have to wait for a couple of days though.... Busy times :)
by (450 points)
0 votes

I got the same problem, i will only get that HTTP Status Code #400 when i use 2.4.0.0 agent,
and my server already upgraded to 2.5

by (180 points)
0 votes

Couldn't find what wend wrong.

In the end decided to setup a new server.

- Centos 7
- PHP 7 via repository (# wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm and # wget http://rpms.remirepo.net/enterprise/remi-release-7.rpm

- MariaDB 10.3

New install is working fine.

by (450 points)
 
Powered by Question2Answer
...