failed to run ["adb" "-s" "XXXX" "shell" "find /data/syzkaller* -type l -exec unlink {} \\; && rm -Rf /data/syzkaller*"]

[tr4v3ler]

This error frequently occurs, making it impossible for the test to continue. Is there any way to solve or temporarily avoid it?

2023/08/28 16:19:10 failed to create instance: failed to run ["adb" "-s" "XXXX" "shell" "find /data/syzkaller* -type l -exec unlink {} \\; && rm -Rf /data/syzkaller*"]: exit status 1
find: /data/syzkaller-testdir7295512/syzkaller.BLS1Uo/1253/cgroup: No such file or directory

[a-nogikh]

Could you please check if https://github.com/google/syzkaller/pull/4171 changes anything? Though the chances that it's indeed the fix are near zero..

I unfortunately don't have any devices nearby to try to reproduce the problem locally.

[tr4v3ler]

Could you please check if #4171 changes anything? Though the chances that it's indeed the fix are near zero..

I unfortunately don't have any devices nearby to try to reproduce the problem locally.

Sorry for replying so late, I will verify as soon as possible.

[a-nogikh]

It would also really help if you could manually connect to a broken device (once you start seeing the error above) and execute something like find -D all /data/syzkaller* -type l -exec unlink {} \;, so that we could understand how exactly that command fails.

[tr4v3ler]

It would also really help if you could manually connect to a broken device (once you start seeing the error above) and execute something like find -D all /data/syzkaller* -type l -exec unlink {} \;, so that we could understand how exactly that command fails.

Regarding this issue, I am using the command you provided, but there are still issues:

$ "adb" "-s" "23R0123621000486" "shell" "find /data/syzkaller* -type l -depth -exec unlink {} \\; && rm -Rf /data/syzkaller*"
rm: file1: Operation not permitted
rm: file1: Operation not permitted
rm: file1: Operation not permitted
rm: file1: Operation not permitted
rm: file1: Operation not permitted
rm: file1: Operation not permitted

For the current issue, I am currently unable to reproduce it as there has been another ongoing issue.

[tr4v3ler]

It would also really help if you could manually connect to a broken device (once you start seeing the error above) and execute something like find -D all /data/syzkaller* -type l -exec unlink {} \;, so that we could understand how exactly that command fails.

The next time this issue is triggered, I will verify it, but it may take some time because the device is experiencing some abnormalities and I need to reset the device and retest it.

[ramosian-glider]

My syzkaller instance got stuck with the same error today:

2023/11/13 10:15:59 failed to create instance: failed to run ["adb" "-s" "0bf60e913788" "shell" "find /data/syzkaller* -type l -exec unlink {} \\; && rm -Rf /data/syzkaller*"]: exit status 1
find: /data/syzkaller-testdir3708258146/syzkaller.5B6Uv0/3486/cgroup.cpu: No such file or directory

The following command fixed the problem:

$ adb wait-for-device && adb root && adb wait-for-device && adb shell unlink /data/syzkaller-testdir3708258146/syzkaller.5B6Uv0/3486/cgroup.cpu

[dvyukov]

I think this is dup of #2831

[tr4v3ler]

My syzkaller instance got stuck with the same error today:

2023/11/13 10:15:59 failed to create instance: failed to run ["adb" "-s" "0bf60e913788" "shell" "find /data/syzkaller* -type l -exec unlink {} \\; && rm -Rf /data/syzkaller*"]: exit status 1
find: /data/syzkaller-testdir3708258146/syzkaller.5B6Uv0/3486/cgroup.cpu: No such file or directory

The following command fixed the problem:

$ adb wait-for-device && adb root && adb wait-for-device && adb shell unlink /data/syzkaller-testdir3708258146/syzkaller.5B6Uv0/3486/cgroup.cpu

Thanks for your reply. I will try it later.