Please reopen this issue.
Mantis - rest api - authorization header problem
Hi @RAB68, I'm glad to hear that you managed to solve the issue and thank you for sharing all this information. I proceed to close this ticket as solved. If you have any other questions, please do not hesitate to open a new thread. Best Regards, Jota
Somehow the issue is back. Whilst after the reboot the it was resolved for a while, polling the the environment "HOME" now shows "/root" again which breaks the source integration.
Any idea/suggestion what changes the environment variable for the apache service?
The only thing I can imagine is that I have a backup cron job which runs as root (sudo crontab -e).
This script stops and starts the services by running:
Would it be better to backup in a cron job of/by bitnami user?
(testing as we speak)
OK - it survived the night including the backup cronjob which is now run as user bitnami rather than root ...
I've just opened this ticket again to continue helping you with the environment variable issue. Did you modify any of the configuration files or scripts that Bitnami includes in the stack? Are you running any script that is modifying that environment variable?
In order to check the current home directory of the daemon user, you can run the following command to get that information.
sudo su daemon -s /bin/bash -c 'echo $HOME'
I also want to let you know that we released the latest version of Mantis in bitnami.com and it includes the changes to disable PHP-FPM by default in the cloud images and virtual machines.