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

Forge installed as one user then errors out for another #171

Closed
pkim-auro opened this Issue Apr 4, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@pkim-auro

pkim-auro commented Apr 4, 2018

I installed forge as the ubuntu which went in fine and works fine.

However, realizing that I should be using my own user, I installed my own profile and switched to my user. then to test I tried just "forge" and received this:

Traceback (most recent call last):
File ".bootstrap/_pex/pex.py", line 367, in execute
File ".bootstrap/_pex/pex.py", line 293, in _wrap_coverage
File ".bootstrap/_pex/pex.py", line 325, in _wrap_profiling
File ".bootstrap/_pex/pex.py", line 410, in _execute
File ".bootstrap/_pex/pex.py", line 468, in execute_entry
File ".bootstrap/_pex/pex.py", line 482, in execute_pkg_resources
File ".bootstrap/pkg_resources/init.py", line 2235, in resolve
File "/home/pkim/.pex/install/Forge-0.4.7-py2-none-any.whl.d3ef9c6c3e933bb5f7e07959f7f5e6a6322239a0/Forge-0.4.7-py2-none-any.whl/forge/cli.py", line 25, in
setup()
File "/home/pkim/.pex/install/Forge-0.4.7-py2-none-any.whl.d3ef9c6c3e933bb5f7e07959f7f5e6a6322239a0/Forge-0.4.7-py2-none-any.whl/forge/tasks.py", line 37, in setup
format='%(levelname)s %(task_id)s: %(message)s')
File "/usr/lib/python2.7/logging/init.py", line 1547, in basicConfig
hdlr = FileHandler(filename, mode)
File "/usr/lib/python2.7/logging/init.py", line 913, in init
StreamHandler.init(self, self._open())
File "/usr/lib/python2.7/logging/init.py", line 943, in _open
stream = open(self.baseFilename, self.mode)
IOError: [Errno 13] Permission denied: '/tmp/forge.log'

I'm guessing I can get around it by chown the /tmp/forge.log file but it implies that only one user would be able to execute. I only see this as a possible problem in our control center where we manage troubleshooting.

let me know if any suggestions.

@rhs

This comment has been minimized.

Contributor

rhs commented Apr 4, 2018

The log is there really mostly for debugging purposes. I can just change it to live somewhere under the user's home directory. If you work around it as you suggested for now, I can put out a fix soon.

@pkim-auro

This comment has been minimized.

pkim-auro commented Apr 4, 2018

yep chown worked fine. file was empty anyway.

@rhs

This comment has been minimized.

Contributor

rhs commented Apr 4, 2018

I just released 0.4.8 with a fix for this. I ended up going with /tmp/forge-<USER>-<DATE>.log. I figure that will avoid polluting the user's home directory and older log files will be garbage collected from /tmp on typical systems.

@rhs rhs closed this Apr 4, 2018

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