Skip to content
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

Init script doesn't check if globaleaks is effectively started #99

Closed
fpietrosanti opened this issue Mar 28, 2013 · 2 comments
Closed

Comments

@fpietrosanti
Copy link
Contributor

The init script, implemented at #66, does not check properly if globaleaks is started or not, by reporting the error.

For example during a debugging session globaleaks was not starting due to this error:
Traceback (most recent call last):
File "bin/startglobaleaks", line 144, in
GLSetting.parser.add_option("-s", "--storm", type="int",
NameError: name 'GLSetting' is not defined

but the init script was reporting started:
www-data@vz203:~$ /etc/init.d/globaleaks_dev start
Starting Globaleaks...
started.

@ghost ghost assigned evilaliv3 Mar 28, 2013
@fpietrosanti
Copy link
Contributor Author

Evilaliv3 reported that this should be related to the way we startup globaleaks under "nohup"

@evilaliv3
Copy link
Member

fixed with commit eb27dee and some other commits on GLBackend

vecna added a commit that referenced this issue Jun 13, 2013
implemented corrections related to foreign keys, delete on cascade and R...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants