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.

Error 404 Agent [closed]

Hello ,

Actually i can't receive inventory from the agent , my error :

ERROR *** AGENT => Failed to send Prolog <HTTP Status Code #404>

I've install ocs server 2.4 on debian 9 and agent 2.3.1 on win 10 machine ; I can access to http://myserv/ocsreports with no error and apache log receive :

 "POST /ocsinventory HTTP/1.1" 404 450 "-" "OCS-NG_WINDOWS_AGENT_v2.3.1.1"

when i start the agent . Can you help me . Thank you .
closed with the note: Problème résolu
in OCS Inventory NG server for Unix by (240 points)
closed by

5 Answers

0 votes

Hi,

  1. Which url  have you set in ocsinventory.ini file? 
  2. is mod_perl installed and activated in apache ?
  3. Please post ocsinventory.ini and error_log file contents
Regards
Frank
by (88.5k points)
0 votes

1°my ocsinventory.ini file :

[OCS Inventory Agent]
ComProvider=ComHTTP.dll
Debug=2
Local=
NoSoftware=0
HKCU=0
NoTAG=0
IpDisc=
[HTTP]
Server=http://192.168.10.41/ocsinventory
SSL=0

2° I think mod_perl is activated for apache ( do you have a solution to check for ensure it was ?)

3°the error log :

Starting OCS Inventory NG Agent on Wednesday, May 30, 2018 13:15:26.
AGENT => Running OCS Inventory NG Agent Version 2.3.1.1
AGENT => Using OCS Inventory NG FrameWork Version 2.3.1.1
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.3.1.1>
    AGENT => Sending getLabel request
    COM SERVER => Initializing cURL library for getFile
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Disabling cURL SSL server validation support
    COM SERVER => Sending fileGet request to URL <http://192.168.10.41/ocsinventory/deploy/label>
    COM SERVER => fileGet response received <HTTP Status Code #404>
    COM SERVER => Cleaning cURL library
    AGENT => Failed to retrieve Label <HTTP Status Code #404>
AGENT => Sending Prolog
    DID_CHECK => Read DeviceID <GCS-PC-046-2018-05-29-11-39-12> and MACs <00:FF:A9:2B:5A:F000:FF:AE:26:2B:AA00:FF:6D:66:D1:8500:FF:A9:2B:5A:F000:FF:AE:26:2B:AA00:FF:6D:66:D1:8500:FF:A9:2B:5A:F000:FF:AE:26:2B:AA00:FF:6D:66:D1:8500:FF:A9:2B:5A:F000:FF:A9:2B:5A:F000:FF:AE:26:2B:AA00:FF:A9:2B:5A:F000:FF:6D:66:D1:8500:FF:6D:66:D1:8500:FF:6D:66:D1:8500:FF:AE:26:2B:AA00:FF:AE:26:2B:AA60:F6:77:F6:1A:F200:FF:6D:66:D1:85A4:4C:C8:94:A6:F600:FF:AE:26:2B:AA00:FF:A9:2B:5A:F060:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE60:F6:77:F6:1A:EE00:00:00:00:00:00> 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 => Disabling cURL SSL server validation support
    COM SERVER => Sending HTTP Post request to URL <http://192.168.10.41/ocsinventory>
    COM SERVER => HTTP Post response received <HTTP Status Code #404>
    COM SERVER => Cleaning cURL library
================= TRACE START ===============

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

side server :

192.168.10.131 - - [30/May/2018:13:26:14 +0200] "GET /ocsinventory/deploy/label HTTP/1.1" 404 463 "-" "OCS-NG_WINDOWS_AGENT_v2.3.1.1"
192.168.10.131 - - [30/May/2018:13:26:14 +0200] "POST /ocsinventory HTTP/1.1" 404 450 "-" "OCS-NG_WINDOWS_AGENT_v2.3.1.1"


 

by (240 points)
0 votes
Testes la connexion sur http://192.168.10.41/ocsinventory depuis un navigateur. Si tu as l'erreur 400 alors le module mod_perl est bien activé et les inventaires vont remonter et s'inscrire correctement en base, sinon c'est que le module n'est pas actif.
Cordialement

Frank
by (88.5k points)
0 votes
Ok , merci , j'ai toujour l'erreur 404 depuis le lien , je regarde coté du module ce qui ne va pas ..
by (240 points)
0 votes
Ok , ca marche bien avec la bonne version de mod_perl . Merci
by (240 points)
 
Powered by Question2Answer
...