@<1523701087100473344:profile|SuccessfulKoala55> what is task log? you mean the pod log provisioned by clearml-agent? do you want me to show them?

any updates?..

root@shelley-gpu-pod:/# clearml-agent daemon --queue shelley2 --foreground
/usr/local/lib/python3.8/dist-packages/requests/init.py:109: RequestsDependencyWarning: urllib3 (2.0.2) or chardet (None)/charset_normalizer (3.1.0) doesn’t match a supported version!
warnings.warn(
Using environment access key CLEARML_API_ACCESS_KEY=“”
Using environment secret key CLEARML_API_SECRET_KEY=********
Current configuration (clearml_agent v1.5.2, location: None):

agent.worker_id ...

here is the agent, task log file~!

pod log is too long. would it be ok if i upload pod log file here??

heres is the log when executing with --foreground. but is there any difference?

I set CLEARML_AGENT_UPDATE_VERSION=1.5.3rc2 ` in agentk8sglue.basePodTemplate.env as i mentioned

Hi again 😊 @<1523701087100473344:profile|SuccessfulKoala55> sure!

clearml==1.9.2
clearml-session==0.4.0

@<1523701205467926528:profile|AgitatedDove14> Good! I will try it

I run clearml-agent manually in gpu available pod using command clearml-agent daemon --queue shelley
and this doesn’t show gpu usage same with when i run task remotely

and here is the log

agent.worker_id =
agent.worker_name = shelley-gpu-pod
agent.force_git_ssh_protocol = false
agent.python_binary =
agent.package_manager.type = pip
agent.package_manager.pip_version.0 = <20.2 ; python_version < ‘3.10’
agent.package_manager.pip_version.1 = <22.3 ; python_ver...

I tried using K8S_GLUE_POD_AGENT_INSTALL_ARGS=1.5.3rc2 instead of CLEARML_AGENT_UPDATE_VERSION=1.5.3rc2 , but it’s same. doesn’t read gpu usage.. 🥲

Oh, It’s not the issue with eks.. We had the same issue on an on-premise cluster too(clearml-agent is installed). Could it be because of clearml-agent installed?

it’s been working well until i removed virtualenv and recreated, then i reinstall only clearml and clearml-session

hello CostlyOstrich36 unfortunately, i also did it to api server just in case. but didn’t work

thank you CostlyOstrich36

Oh, it didn’t generate conf file properly. I will try again

because clearml-agnet is not installed in my gke cluster

wow ! thank you for quick answer! it worked like a charm. have a nice day:)

I tried the suggestion you mentioned, but it’s the same. And it doesn’t seem to be an AMI issue. The same problem is occurring even in an on-premise environment.

Hope clearml-session will be more developed as clearml-agent. cause it is so useful! 👍
My issue: None

@<1523701087100473344:profile|SuccessfulKoala55> I realized that this is not an issue with the cloud or on-premise environment. it’s working well on gke but not working on eks. here is the log when i run “clearml-agent daemon --queue ~” command on eks

root@shelley-gpu-pod:/# clearml-agent daemon --queue shelley3
/usr/local/lib/python3.8/dist-packages/requests/init.py:109: RequestsDependencyWarning: urllib3 (2.0.1) or chardet (None)/charset_normalizer (3.1.0) doesn’t match a supported ve...

This is clearml-agent helm chart values.yaml file i used to install

can i hide some of them without fixing and rebuilding docker image?

@<1523701087100473344:profile|SuccessfulKoala55> Okay..but how can i specify agent’s verison in helm chart?

Thanks! also logs too?

Are there other people experiencing the same issue as me?

i am having same issue: None