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

Remove Start.log Requirement From Passport Startup #49

afroDC opened this Issue Oct 18, 2018 · 3 comments


None yet
3 participants

afroDC commented Oct 18, 2018

This seems to be a required element for Passport, but has no functional use from what I can tell. the /etc/init.d/passport script inside the Gluu chroot needs to be adjusted to point to passport.log once this issue is closed #48.

@afroDC afroDC added the enhancement label Oct 18, 2018

@afroDC afroDC added this to the 3.1.5 milestone Oct 18, 2018


This comment has been minimized.


jgomer2001 commented Nov 11, 2018

This contrast with issue #51 :

root@localhost:/etc/gluu/conf# rm -f -r /opt/gluu/node/passport/server/logs/*
root@localhost:/etc/gluu/conf# ls /opt/gluu/node/passport/server/logs/
root@localhost:/etc/gluu/conf# service passport start
Starting passport:
Checking logs for possible errors:
PID: [18321]
OK Sun Oct 21 19:15:53 UTC 2018

In this case start.log isn't present and there's no problem, but actually passport didn't start after default installation...

We have to make more demanding tests on the startup script accross serveral OSes


This comment has been minimized.

ganesh-at-wiw commented Dec 5, 2018

Okay @afroDC and @jgomer2001 , let's start by removing passport dependability on checking for logs.
If that works good, then we can go ahead with this setting in forthcoming versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment