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.

Deploy stops creating packages

We hadn't used the deploy functionality in OCS for some time and until then, it worked perfectly. I went to create a package for installing a new piece of software and, to my surprise, the functionality stopped working.

At the end of the build process, instead of the success screen, I get a blank screen with just the title Package Builder and the Reload build button.

In the /var/lib/ocsinventory-reports/download directory there are five empty directories (my five attempts to build  a package), i.e. the system starts the process by creating the directories in the download area, but it doesn't finish.

[root@lnxprd-ocs01 download]# ls -la
total 0
drwxr-xr-x. 7 apache root    96 mar  2 17:09 .
drwxr-xr-x. 9 apache root   104 out  3 09:33 ..
drwxr-xr-x. 2 apache apache   6 mar  2 16:32 1709407978
drwxr-xr-x. 2 apache apache   6 mar  2 16:34 1709408078
drwxr-xr-x. 2 apache apache   6 mar  2 16:36 1709408190
drwxr-xr-x. 2 apache apache   6 mar  2 17:02 1709409739
drwxr-xr-x. 2 apache apache   6 mar  2 17:09 1709410167

The only thing I remember from the last time we created deployment packages was that we upgraded the server from 2.11 to 2.12, but the person who upgraded didn't do the deployment tests. Everything else works perfectly.

Is there any configuration for debugging the application? We found nothing in the Apache and OCS logs.

  • AlmaLInux 9.3
  • ocs-server 2.12 (official RPM repository)
  • PHP 8
in OCS Inventory NG server for Unix by (160 points)
edited by

1 Answer

0 votes

After several tests, the only way to deploy that works is custom packages. Any other way of deploying (exe, msi, scripts, etc.) does not work.

Below are attempts to create a deploy using .exe and another using powershell. Result: blank screen for both.

What frustrates me the most is not being able to track the error. I can't find anything in the Apache logs or in the Chrome/Edge development tools console. 


by (160 points)
Powered by Question2Answer