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.

Sign up for GitHub

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

Jump to bottom

Kamaki outputs log messages on stderr if it fails to open the log file #25

Closed
Erethon opened this issue Jun 3, 2014 · 0 comments
Closed

Kamaki outputs log messages on stderr if it fails to open the log file #25

Erethon opened this issue Jun 3, 2014 · 0 comments

Comments

@Erethon
Copy link
Contributor

Erethon commented Jun 3, 2014

If kamaki fails to open the log file specified in .kamakirc, it will output all log messages on stderr. This is reproducible with both a file that is on a non-existing path and a filename with wrong permissions.

Output:

root@snf-538967:~# kamaki file list

Failed to open any logging locations, file-logging aborted

kamaki(INFO) 2014-06-03 11:15:41,306

    /usr/bin/kamaki file list

- - -

kamaki.clients.send(INFO) 2014-06-03 11:15:41,388

    - -  -   -     -        -             -

kamaki.clients.send(INFO) 2014-06-03 11:15:41,389
saxtouri added a commit to saxtouri/kamaki that referenced this issue Jun 17, 2014
@saxtouri
Manage logs when log file is not accessible
74f5d51 
Fixes grnet#25

If the default log file location is not accessile, inform user
about the error (e.g., no write permission, location does not
exist). Also, make non-debug log messages shorter and make sure
all instructions and warnings are printed to standard error.
saxtouri added a commit to saxtouri/kamaki that referenced this issue Jun 17, 2014
@saxtouri
Manage logs when log file is not accessible
4b8763c 
Fixes grnet#25

If the default log file location is not accessile, inform user
about the error (e.g., no write permission, location does not
exist). Also, make non-debug log messages shorter and make sure
all instructions and warnings are printed to standard error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Erethon