Reputation
Badges 1
49 × Eureka!Iâm also curious if itâs available to bind the same GPU to multiple queues.
Thanks! also logs too?
pls also refer to None :)
Oh, it didnât generate conf file properly. I will try again
hello CostlyOstrich36 unfortunately, i also did it to api server just in case. but didnât work
I want to get task id, properties right after submitting clearml-session task
@<1523701205467926528:profile|AgitatedDove14> Good! I will try it
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.. đĽ˛
Hope clearml-session will be more developed as clearml-agent. cause it is so useful! đ
My issue: None
Wow i appreciate that đ
Hi @<1523701205467926528:profile|AgitatedDove14>
The server is already self hosted. I realized i canât create a report using clearml sdk. so i think i need to find other ways
then, is there any way to get embed code from scalars?
i understand the reason that clearml-session supports only cli is because of SSH. right? i thought it was easy to develop sdk. instead, i can use your recommendation
for more info, I set CLEARML_AGENT_UPDATE_VERSION=1.5.3rc2
` in agentk8sglue.basePodTemplate.env
because clearml-agnet is not installed in my gke cluster
It seems that there is no way to add environments, so i customized charts and using it on my own.
@<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...
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 ...
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.
here is the agent, task log file~!
Hi again đ @<1523701087100473344:profile|SuccessfulKoala55> sure!
@<1523701087100473344:profile|SuccessfulKoala55> what is task log? you mean the pod log provisioned by clearml-agent? do you want me to show them?
@<1523701087100473344:profile|SuccessfulKoala55> yes. It only occurs when running on the cloud. Itâs fine when running on-premises.
pod log is too long. would it be ok if i upload pod log file here??
I set CLEARML_AGENT_UPDATE_VERSION=1.5.3rc2
` in agentk8sglue.basePodTemplate.env as i mentioned
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 also shows on project detail page.