-
Notifications
You must be signed in to change notification settings - Fork 638
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
unable to trigger pingbacknotification when Kolibri is running as a system service #5556
Comments
The system used to initialize the Kolibri server In order for this to work - please try:
In the file which opens, please add the lines:
Then save that file. Now, @indirectlylit - is there any practical non-testing reason why a user should ever need to apply environment variables? I tried adding:
In |
That's surprising, as all the testing VMs that I use extensively have the If those are not working correctly, @jamalex would have certainly noticed and complained a long time ago... |
If you have one of your VMs from the past that you know you've not had issues with - could you post the content of |
Environment variables are sometimes used instead of options.ini files in deployments, e.g. because it can be easier to set env vars in a docker instance than to modify a file on disk.
Is there any chance it's running as a |
I checked and I'm running it with the user that I see listed when I |
I forgot the |
FYI, this is the handling logic on the nutritionfacts side: |
closing in lieu of learningequality/kolibri-docs#98 |
Note that inside options.ini, you don't include the |
I tried both without any luck, unfortunately. My options.ini file on my VM is:
The port changes as expected, but I don't see the modal pop-up. However, when I
I see the modal pop-up Thanks for pointing that out, though - I've updated the issue I created regarding this here noting that I've tried this both with the |
Observed behavior
Trying to test the upgrade notification Gherkin scenario, but been unable to trigger the notification.
Had to set up
KOLIBRI_RUN_MODE
in the.bashrc
(testing VM has it setup to exclude the usage from the user stats). Variable seems set, but no notification when the admin signs in:Checking the DB reveals that
analytics_pingbacknotification
table is empty:@ralphiee22 recommended trying
KOLIBRI_RUN_MODE=msg-radina kolibri manage ping --once
, and that seems to create the ping correctly:Am I missing something, or there is a problem that needs fixing?
Expected behavior
Working ping notification.
User-facing consequences
No upgrade notification?
Errors and logs
…
Steps to reproduce
…
Context
The text was updated successfully, but these errors were encountered: