sure! this one?

Wow i appreciate that 😆

i fount the solution!! i added configuration to helm’s values.yaml below.

additionalConfigs:
# services.conf: |
# tasks {
# non_responsive_tasks_watchdog {
# # In-progress tasks that haven’t been updated for at least ‘value’ seconds will be stopped by the watchdog
# threshold_sec: 21000
# # Watchdog will sleep for this number of seconds after each cycle
# watch_interval_sec: 900
# }
# }
apiserver.co...

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

Are there other people experiencing the same issue as me?

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

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?

yes!

alright. thanks 🙂 i hope that too.

@<1523701087100473344:profile|SuccessfulKoala55> yes. It only occurs when running on the cloud. It’s fine when running on-premises.

I want to get task id, properties right after submitting clearml-session task

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

The clearml server I installed is a self-hosted server, and developers log in using a fixed ID and password for authentication. That’s it!

Futhermore, to access ssh/vscode/jupyterlab directly without ssh tunneling, I modified the clearml-session script, and once I upload this script to the DevOps project in draft status, developers clone it to their own project. Then, they enqueue and wait for the command and URL to access ssh/vscode/jupyterlab, which will be displayed.

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

It also shows on project detail page.

nope. just running “clearml-agent daemon --queue shelley”

thank you CostlyOstrich36

@<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...

It seems that there is no way to add environments, so i customized charts and using it on my own.

pls also refer to None :)

it is working on on-premise machine(i can see gpu usage on WORKERS & QUEUES Dashboard). but it is not working on cloud pod

because clearml-agnet is not installed in my gke cluster

I’m also curious if it’s available to bind the same GPU to multiple queues.

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

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

clearml==1.9.2
clearml-session==0.4.0

@<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> Okay..but how can i specify agent’s verison in helm chart?