NS8-GLPI App - First Pre Release

The error is caused by the owner set for the log file:


At first install it is set to the module instance ID (glpi4, in this example), after saving changes again, owner changes to some UID (427712, in this example).
Confirmed by manually changing file ownership to the same UID as the other files on the instance without requiring re-saving settings or a reboot.

2 Likes

does anyone experience the same issue as @dnutan or is this an isolated case?

Add :Z your volume is not selinux labelled

:z i if you need to share the volume among other containers

--volume glpi_html:/var/www/html/glpi:Z \

1 Like

would this resolve the issue @dnutan is facing?

why do we not have the same issue with the sharing

@dnutan could you test with

api-cli run update-module --data '{"module_url":"ghcr.io/geniusdynamics/glpi:dev","instances":["glpi1"],"force":true}'

You could go to all your modules and add it :slight_smile:

whoosh, those are 16 of them, but i think 2 have them, though for some reason there is one that i think already has.

Ill merge the dev branch to main, then you can add the module to nethforge, i remove it from genforge.

didn’t test to update an instance as the issue happens the first time settings are saved.
I added the module from dev branch ( add-module ghcr.io/geniusdynamics/glpi:dev) and had the same issue.

I have installed it using add-module, but https://ip/glpi just doesn’t work.

Hello @jjmmbb Glpi should not be availbale from the software center.
Kindly use this method on the link to always get the lates Updates

GenForge modules index for NS8 | ns8-genforge (genius.ke)

Equally, how do you mean after installing you visit ip/glpi?

the App is meant to be accessible through a FQDN configured in the App settings page.

Letter D says: main domain /glpi, but I use IP address as main domain.

MAin domain with NO trailing /

Sorry. It was my fault.

I did it. Configure it to use glpi.maindomain.

I got a problem about timezone in the logs
 Then I try to run:

root@glpi:/var/www/html/glpi# php8.2 bin/console database:enable_timezones Timezones usage cannot be activated due to following errors:

  • Access to timezone database (mysql) is not allowed.

When I try to access glpi.maindomain I got this:

Error: An error has occurred, but the trace of this error could not recorded because of a problem accessing the log file.

Anyone knows how to solve this issue to get it running correctly?

This error occcurs in the dev or main branch

If its the dev branch you can update
i have fixed the error in the latest commit
kindly confirm and let me know

We have a new Dev release available for testing.
Release 2.0.0-dev.1 · geniusdynamics/ns8-glpi (github.com)

You could Manually Update to this version for testing, from current release via
api-cli run update-module --data '{"module_url":"ghcr.io/geniusdynamics/glpi:2.0.0-dev.1","instances":["glpi1"],"force":true}'

it should sort most of the previous issues you mentioned.

Finally I can get it working. Thank you all for helping me.

1 Like

Hello. I am trying to update from 10.0.14 to 10.0.16, so I run:

api-cli run update-module --data ‘{“module_url”:“ghcr.io/geniusdynamics/glpi:latest",“instances”:[“glpi1”],"force”:true}’

But GLPI still showing 10.0.14 instead of 10.0.16. Do you know why? Is it necessary to run another command after update-module?

this seems to be a cache issue.

Did you save again the data on the settings page? We have implemented a script to update the db value to the latest for the corresponding version, once configure is run, however, it seems to still persist in some OS versions.(ROCKY) i have no idea why yet.

Yes, I saved on settings.
I also run db:check and db:update on console.

root@glpi:/var/www/html/glpi# php bin/console db:update
Some of the optional system requirements are missing. Run the command "php bin/console system:check_requirements" for more information.

| GLPI                   | 10.0.14        | 10.0.14 |
| Database GLPI | 10.0.14        | 10.0.14 |

No migration required.

i think we just need to Update it manually. on he database this only affects those who have updated from v 10.14 to 10.16