Seafile really broken ?/ Seafile est vraiment cassé?

My YunoHost server :

Virutal server on Celeron J4125 4g of ram dedicated and 500go of Hard disk self-hosted - Internet operator : Free (optical fiber) - With two domain names at OVH

YunoHost 11.2.3 (stable) - no special settings

I have access to my server : Through SSH AND through the webadmin

Description of my issue : no issue, just a question


Mon serveur YunoHost :

Serveur virtualisé sur un Celeron J4125 4g de ram dédié et 500go de disque dur auto-hébergé - FAI : Free (fibre optique) – Avec deux noms de domaine chez OVH

YunoHost 11.2.3 (stable) – pas de paramétrage spécifique

J’ai accès à mon serveur par : SSH et via l’interface webadmin

-EN:
Being tired of Nextcloud synchronization bugs, I wanted to install Seafile (first keeping both and in the future, hopefully, migrating totally).

Nevertheless and while nothing indicates it on the dedicated page of the Yunhost site, I note that the application is “broken” in the installation page of my server.

Is this an error or unfortunately we can no longer install Seafile? THANKS

-FR: Etant lassé des bugs de synchronisation de Nextcloud, j’ai voulu installer Seafile (d’abord en conservant les deux et dans le futur, si tout va bien, migrer totalement).

Néanmoins et alors que rien ne l’indique sur la page dédiée du site de Yunhost, je constate que l’application est “cassée” dans la page d’installation de mon serveur.

Il s’agit d’une erreur ou hélas on ne peut plus installer Seafile ? Merci

Hello,

You can fond the answer here: Question: will Seafile be discontinued on YunoHost? · Issue #105 · YunoHost-Apps/seafile_ynh · GitHub

  • EN: Thanks for the reply and the work.

I’m crossing my fingers that you have time to resume maintenance of this application.

So I confirm that we cannot install the application (several errors during installation), but that this does not “break” the server ^^

Is it useful for me to publish the log or is it of no interest?

  • FR: Merci pour la réponse et le travail.

Je croise les doigts pour que vous ayez le temps de reprendre la maintenance de cette application.

Donc je confirme que l’on ne peut pas installer l’application (plusieurs erreurs à l’installation), mais que cela ne “casse” pas le serveur ^^

Est-il utile que je publie le log ou cela n’a pas d’intérêt ?

  • extract log :
2023-08-05 17:21:47,074: DEBUG - + chattr +C /swap_seafile
2023-08-05 17:21:47,139: WARNING - chattr: Opération non supportée lors de l'initialisation des drapeaux sur /swap_seafile
2023-08-05 17:21:47,144: DEBUG - + true
[...]
2023-08-05 17:22:00,346: DEBUG -   Getting requirements to build wheel: started
2023-08-05 17:22:00,623: WARNING -   ERROR: Command errored out with exit status 1:
2023-08-05 17:22:00,624: WARNING -    command: /usr/bin/python3 /tmp/tmpji0i5l8b_in_process.py get_requires_for_build_wheel /tmp/tmpxh57bz5g
2023-08-05 17:22:00,626: WARNING -        cwd: /tmp/pip-install-fd905wa_/mysqlclient_16e0d631a90941bf8d0060fb3a455910
2023-08-05 17:22:00,630: WARNING -   Complete output (24 lines):
2023-08-05 17:22:00,632: WARNING -   /bin/sh: 1: pkg-config: not found
2023-08-05 17:22:00,633: WARNING -   /bin/sh: 1: pkg-config: not found
2023-08-05 17:22:00,638: WARNING -   Trying pkg-config --exists mysqlclient
2023-08-05 17:22:00,639: WARNING -   Command 'pkg-config --exists mysqlclient' returned non-zero exit status 127.
2023-08-05 17:22:00,640: WARNING -   Trying pkg-config --exists mariadb
2023-08-05 17:22:00,641: WARNING -   Command 'pkg-config --exists mariadb' returned non-zero exit status 127.
2023-08-05 17:22:00,641: WARNING -   Traceback (most recent call last):
2023-08-05 17:22:00,646: WARNING -     File "/tmp/tmpji0i5l8b_in_process.py", line 280, in <module>
2023-08-05 17:22:00,646: WARNING -       main()
2023-08-05 17:22:00,647: WARNING -     File "/tmp/tmpji0i5l8b_in_process.py", line 263, in main
2023-08-05 17:22:00,647: WARNING -       json_out['return_val'] = hook(**hook_input['kwargs'])
2023-08-05 17:22:00,648: WARNING -     File "/tmp/tmpji0i5l8b_in_process.py", line 114, in get_requires_for_build_wheel
2023-08-05 17:22:00,648: WARNING -       return hook(config_settings)
2023-08-05 17:22:00,649: WARNING -     File "/tmp/pip-build-env-dms04um9/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 341, in get_requires_for_build_wheel
2023-08-05 17:22:00,649: WARNING -       return self._get_build_requires(config_settings, requirements=['wheel'])
2023-08-05 17:22:00,650: WARNING -     File "/tmp/pip-build-env-dms04um9/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 323, in _get_build_requires
2023-08-05 17:22:00,654: WARNING -       self.run_setup()
2023-08-05 17:22:00,654: WARNING -     File "/tmp/pip-build-env-dms04um9/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 338, in run_setup
2023-08-05 17:22:00,655: WARNING -       exec(code, locals())
2023-08-05 17:22:00,655: WARNING -     File "<string>", line 154, in <module>
2023-08-05 17:22:00,656: WARNING -     File "<string>", line 48, in get_config_posix
2023-08-05 17:22:00,656: WARNING -     File "<string>", line 27, in find_package_name
2023-08-05 17:22:00,656: WARNING -   Exception: Can not find valid pkg-config name.
2023-08-05 17:22:00,657: WARNING -   Specify MYSQLCLIENT_CFLAGS and MYSQLCLIENT_LDFLAGS env vars manually
2023-08-05 17:22:00,662: WARNING -   ----------------------------------------
2023-08-05 17:22:00,662: DEBUG -   Getting requirements to build wheel: finished with status 'error'
2023-08-05 17:22:00,662: WARNING - WARNING: Discarding https://files.pythonhosted.org/packages/de/9c/b176826e8994551ce826404dab97e305a4bb76c8b0a4e016fabda2901c71/mysqlclient-2.2.0.tar.gz#sha256=04368445f9c487d8abb7a878e3d23e923e6072c04a6c320f9e0dc8a82efba14e (from https://pypi.org/simple/mysqlclient/) (requires-python:>=3.8). Command errored out with exit status 1: /usr/bin/python3 /tmp/tmpji0i5l8b_in_process.py get_requires_for_build_wheel /tmp/tmpxh57bz5g Check the logs for full command output.
2023-08-05 17:22:00,707: DEBUG -   Downloading mysqlclient-2.1.1.tar.gz (88 kB)
[...]
2023-08-05 17:23:55,934: DEBUG - + systemctl start seahub
2023-08-05 17:24:04,726: WARNING - Job for seahub.service failed because the control process exited with error code.
2023-08-05 17:24:04,728: WARNING - See "systemctl status seahub.service" and "journalctl -xe" for details.
2023-08-05 17:24:04,728: DEBUG - + ynh_exec_err journalctl --quiet --no-hostname --no-pager --lines=20 --unit=seahub
[...]
2023-08-05 17:24:04,792: DEBUG - + ynh_secure_remove --file=/tmp/tmp.gVwzIfaE7z
2023-08-05 17:24:04,793: WARNING - [Error] août 05 17:23:55 systemd[1]: Starting Seafile hub...
2023-08-05 17:24:04,797: WARNING - août 05 17:23:56 seahub.sh[535139]: LC_ALL is not set in ENV, set to fr_FR.UTF-8
2023-08-05 17:24:04,798: WARNING - août 05 17:23:56 seahub.sh[535139]: Starting seahub at port 8000 ...
2023-08-05 17:24:04,800: WARNING - août 05 17:23:56 seahub.sh[535148]: ----------------------------------------
2023-08-05 17:24:04,801: WARNING - août 05 17:23:56 seahub.sh[535148]: Successfully created seafile admin
2023-08-05 17:24:04,802: WARNING - août 05 17:23:56 seahub.sh[535148]: ----------------------------------------
2023-08-05 17:24:04,804: WARNING - août 05 17:24:04 seahub.sh[535139]: Error:Seahub failed to start.
2023-08-05 17:24:04,807: WARNING - août 05 17:24:04 seahub.sh[535139]: Please try to run "./seahub.sh start" again
2023-08-05 17:24:04,809: WARNING - août 05 17:24:04 systemd[1]: seahub.service: Control process exited, code=exited, status=1/FAILURE
2023-08-05 17:24:04,812: WARNING - août 05 17:24:04 systemd[1]: seahub.service: Failed with result 'exit-code'.
2023-08-05 17:24:04,813: WARNING - août 05 17:24:04 systemd[1]: Failed to start Seafile hub.
2023-08-05 17:24:04,815: WARNING - août 05 17:24:04 systemd[1]: seahub.service: Consumed 3.007s CPU time.
2023-08-05 17:24:04,900: DEBUG - + return 1
[...]
2023-08-05 17:24:05,511: DEBUG - + pkill -f seahub
2023-08-05 17:24:06,539: ERROR - Impossible d'installer seafile : Une erreur est survenue dans le script d'installation de l'application

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.