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

Get Failed to log params warning without using MLFlowLogger #401

Closed
lingsond opened this issue Jun 4, 2020 · 3 comments
Closed

Get Failed to log params warning without using MLFlowLogger #401

lingsond opened this issue Jun 4, 2020 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@lingsond
Copy link
Contributor

lingsond commented Jun 4, 2020

I'm testing the lm_finetuning script on Kubernetes. The docker image is based on Dockerfile-GPU.

The script has been modified a little where I remove the import MLFlowLogger and also the use of it in the lm_finetuning method (so I'm not using the MLFlowLogger at all). I still use the logging.basicConfig(..) though so I still can see the infos during runtime.

However, when I run the script, I see this showed up almost after every INFO:
WARNING - farm.utils - Failed to log params: 'getpwuid(): uid not found: 1174'

I looked into farm.utils and the only part that will throw this message is inside the log_params method of MLFlowLogger.

I didn't use the MLFlowLogger at all, why do I get this warning? How to solve this problem?
Thanks in advance.

@lingsond lingsond added the question Further information is requested label Jun 4, 2020
@lingsond
Copy link
Contributor Author

lingsond commented Jun 5, 2020

Additional information:

I added some line to my Dockerfile:

## config
ARG USER=myusernamewashere
ARG UID=1174

RUN adduser ${USER} --uid ${UID} --home /home/${USER}/ --disabled-password --gecos "" --no-create-home
RUN mkdir -p /home/${USER}
RUN chown -R ${USER} /home/${USER}

So the warning has disappeared now. The reason the warning showed up was because my user information wasn't included in the Docker image.

However, it doesn't answer my original question:
I didn't use the MLFlowLogger at all, why do I get this warning?

Thanks in advance! :)

@tanaysoni
Copy link
Contributor

Hi @lingsond, thank you for raising the issue. In the current version, an MLFlowLogger instance is instantiated by default. With work in progress #305, there's a new StdoutLogger being added that'd allow logging params/metrics on the stdout.

@lingsond lingsond closed this as completed Jun 5, 2020
@lingsond
Copy link
Contributor Author

lingsond commented Jun 5, 2020

Thanks for the info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants