-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One agent getting HTTP 500 errors when trying to POST inventory #423
Comments
Hi @nroach44 , Can you set the Windows agent debug to 1 ? To do that :
Are all your agents in 2.10.1 ? Best regards, |
Hi @charleneauger ! The rest of the agents are on either the latest Windows or Linux agents. As far as I can tell, there are other Windows 10 machines, just like this one, working fine.
|
Hi @nroach44 , Can you send me back the server logs for this machine located in Regards, |
@charleneauger I've just checked again, getting the same results as in my original post:
|
Hi @nroach44 , This is not the correct log file you sent me :-) Regards, |
@charleneauger no luck, there's no activity in that log when the agent attempts a report. |
@nroach44 , have you enabled the |
Hi @nroach44 , Any update on this issue ? Regards, |
@Lea9250 @charleneauger My apologies for the delay. This is the
Here is the corresponding |
Hi @nroach44 , To set
Do you have any new logs showing up in Can you provide me with the Regards, |
Hi, I have the same error on my side. After some search, I have do this: set OCS_OPT_DBI_PRINT_ERROR 1 in z-ocsinventory-server.conf file and restart apache. Launch an inventory and look in apache error log file for errors. And in our log, now we have: DBD::mysql::st execute failed: Out of range value for column 'ID' at row 1 at /usr/local/share/perl5/Apache/Ocsinventory/Server/Inventory/Update.pm line 173. @charleneauger any idea? Thank you |
Hi @thenamelessthing , Can you provide me with the Best regards, |
Is it really relevant, I mean. I have added myself to this thread as I am experiencing exactly the same problem and the computer name will not be in the logs provided earlier in this thread. We have many computers with this problem. Our computer name nomenclature looks like this: T-SSO-99-001234 I also can provide our log file too if necessary. |
In my instance the computer name is "AAAAA" (where A is any capital latter between A-Z), no numbers, symbols, Unicode etc.
I'll try to check the logs to see if I'm getting the same error.
…On 28 October 2023 4:19:56 am AWST, thenamelessthing ***@***.***> wrote:
> Hi @thenamelessthing ,
>
> Can you provide me with the `HOSTNAME` of your machine in error ?
>
> Best regards, Charlene
Is it really relevant, I mean. I have added myself to this thread as I am experiencing exactly the same problem and the computer name will not be in the logs provided earlier in this thread. We have many computers with this problem. Our computer name nomenclature looks like this: T-SSO-99-001234
--
Reply to this email directly or view it on GitHub:
#423 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Hi @charleneauger , I provided our log too if this can help you. ocs_httpd_error.log One of the computer with the error is: L-SSO-21-008645 |
Hi, it is possible to obtain help on this? |
@charleneauger if you can give us a hint on how to solve this problem. That would be great! Thanks again for your help. In the apache error log with debug enable we see: DBD::mysql::db do failed: The table 'prolog_conntrack' is full at /usr/local/share/perl5/Apache/Ocsinventory/Server/Communication/Session.pm line 46. |
COncerning the following error : I answered you in the other issue you opened. The table prolog_conntrack is a memory temporary table that should purge from time to time. Regards, |
Hi @nroach44 , Any update on this issue ? Regards, |
General information
Operating system :
Server: Container using podman-compose on Debian 11
Client: Windows 10 x64
Server information
Perl version :
Mysql / Mariadb / Percona version :
OCS Inventory information
Ocs server version :
Problem description
One particular agent is unable to push the report:
I've tried to add
OCS_OPT_DBI_PRINT_ERROR
in various ways:docker-compose.yml
Dockerfile
and re-building the container, and updating thedocker-compose.yml
to use that containerdocker-compose.yml
:At no point do I seem to get any logs other than the single "500" error above.
All of the other clients seem to work fine.
This server did start out at 2.9.2 (because I didn't realise that it wasn't the newest version, oops!) but it has since been upgraded to 2.11.
The text was updated successfully, but these errors were encountered: