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

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

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?

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

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

Wow i appreciate that 😆

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

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

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

then, is there any way to get embed code from scalars?

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

@<1523701070390366208:profile|CostlyOstrich36> Hello. Oh, sorry for the lack of explanation.when i execute the command “clearml-session ~“, jupyter url format is ‘ None :{local_jupyter_port}/?token={jupyter_token}’ and vs code url format is just ‘ None :{local_vscode_port}’ like the pic i attached here. I wonder why vs code url doesn’t have token.

thank you CostlyOstrich36

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

pls also refer to None :)

Thanks! also logs too?

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

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

because clearml-agnet is not installed in my gke cluster

any updates?..

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

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

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

alright. thanks 🙂 i hope that too.

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

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.

i am having same issue: 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