-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
task remains on Pending #101
Comments
@R7JANV1 Thanks for reporting, possibly duplicate of #100. Checkout wiki notice and try manual installation instead of pre-compiled binaries (seems like some issue with permission). If you have any new info about that bug, feel free to write here. |
Facing the same issue with following log Tried manual installation instead of pre-compiled binaries still same error |
I am seeing the same issue
Yet the log shows this:
|
@timonline does this log is from run with unchecked Use pre-compilbed Python binaries box in cloud_py_api? As I see you installing python dependencies, I assume that you try running from source, am I right? |
Yes I’m using the requirement file from the source and yes the pre compiled python binaries is set |
Use pre-compiled Python binaries option must be disabled (unchecked) for usage from sources with manually installed Python packages. |
that did the trick, thank you. Now i am finally seeing the tasks progress instead of being stuck in pending |
@timonline can you (or someone else with such problem) describe how we can reproduce this, what do specific your installations have which leads to situation where php cannot start binary file - looks like we miss something when rewriting code. |
@timonline Could you check one thing please:
change L116: from L121: from
|
@andrey18106 the naming format of the file changed but the error came back
|
@timonline You missed to change one first |
I mean i upgraded to nextcloud v25, install the cloud python api, installed mediadc, created a task, stayed pending. So i checked the log file and found the error. Not sure there was anything special i did that reproduces the problem EDIT: I even tried removing and reinstalling both multiple times |
@andrey18106 don't see how i missed one.
|
@timonline in both |
Can you describe what OS you are using, what type of Nextcloud installation you have, maybe some specific steps were followed to install php. |
to either @andrey18106 or @bigcat88 I am happy to jump on discord or some sort of chat to troubleshoot the problem live. Would be happy to find the exact circumstances that leads to a broken install as it took me a whole day of messing with pip and installing the prerequisites to get it to work. There were MULTIPLE linux packages missing that I had to install to get the pip install -r requirements.txt to work because it kept erroring |
|
Nextcloud is a docker container from https://github.com/linuxserver/docker-nextcloud running on UnRaid whose base is
Inside the docker when i run uname, i get this:
|
@timonline ok, for your case, colon in logs paths not the issue, but in other cases it can be the reason. So, yea, it needs more investigation, discord is a good option. |
I am at PhoenixCoder#4861 on discord |
is there any progress on this? |
With what guide I can install Nextcloud AIO to get the same configuration that you have? |
then activate cloud_py_api and madiadc |
For me tasks seem to remain pending until i restart them |
unfortunately not for me |
@R7JANV1 Can you verify any errors in logs. Tasks run logs can be found here: Have you tried usage from sources instead of pre-compiled binaries. |
I think the problem with linuxserver docker image is that the python and php binaries location is different than the default one in mediaDC settings: (I'm not sure !) |
Update cloud_py_api, uninstall |
any update for this? |
Describe the bug
The processes cannot be executed, the status of the task remains on Pending.
To Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
cloud_py_api
version [0.1.1]Nextcloud AIO latest Stable
Additional context
nextcloud/all-in-one#1701
The text was updated successfully, but these errors were encountered: