Hi all,
Trying out version 4.0 build 570 last night. When trying to record a batch I get the message " no space left on device". Anybody know how I can solve that? I'm running the cloudmakers suite 4.0 on a macbook with OS catalina 10.15.7.
cheers
No space left on device
- Peter Polakovic
- Posts: 2276
- Joined: Thu Apr 21, 2016 9:38 am
Re: No space left on device
It sounds like the filesystem is full. Is it possible?
Re: No space left on device
I still have 300 GB available. I will try version 3 to see if the problem persists
Re: No space left on device
I tried to make some subs with version 3 and that worked fine. Immediately after I tried version 4 which again gave the " no space left on device".
-
- Posts: 83
- Joined: Tue Jul 09, 2019 4:59 pm
Re: No space left on device
I can't help but think that this is related to the message I sometimes get about the "bad file descriptor" when attempting to write a new image file.
For this error and mine...something is clearly wrong...but the error message makes no sense. (In my case, I re-type the file name default value "IMG", instead of "IMG" and it works just fine the second time.)
For this error and mine...something is clearly wrong...but the error message makes no sense. (In my case, I re-type the file name default value "IMG", instead of "IMG" and it works just fine the second time.)
- Peter Polakovic
- Posts: 2276
- Joined: Thu Apr 21, 2016 9:38 am
Re: No space left on device
It may be related to the sandboxing. Changing the folder (even to the same) in "Agent setup" may help.
Re: No space left on device
Unfortunately that did not help. I'll reinstall, see what happens
- Peter Polakovic
- Posts: 2276
- Joined: Thu Apr 21, 2016 9:38 am
Re: No space left on device
I reproduced the "Bad descriptor" issue and it is apparently somehow related to the sandbox 
In my case selecting download folder in Agent setup dialog fixed the issue.
I'll try to find what's wrong, but it may be related to mixing v3.x and v4.x applications. If folder is selected in v3.x it is used in 4.x but the access rights are not granted for that build

In my case selecting download folder in Agent setup dialog fixed the issue.
I'll try to find what's wrong, but it may be related to mixing v3.x and v4.x applications. If folder is selected in v3.x it is used in 4.x but the access rights are not granted for that build
