Comments (13)
I have the exact same problems. Also user/developer of the superior variety etc.
from cells.
Hello,
Have had little luck getting cells to run under the "pydio" user - I followed your guide to the letter, and I am a longtime web developer (superuser) so I know what I am doing... Have you tested your guide on Ubuntu Bionic? Or at all?
Yes, I installed Cells a bunch of times on Ubuntu 18.04 during documentation redaction process and it worked.
I encountered a whole host of problems. Tried starting over just running it as root and not bothering with SSL. I finally get cells to bind to port 80 - but when visiting the frontend I just get a "File not found" message, from Caddy I presume.
It would help if you could give a little more details.
The cells startup log reveals:
2018-08-16T20:07:09.341Z INFO Warning, could not find static directory for web resoures idm/auth/web - Only API and GRPC accesses will be available
This is only a warning and does not prevent the application to run smoothly.
Is this beta software?
Pydio Cells is a full rewrite of the Pydio Server (that has been used in production since more than 10 years) that has been released only 2 months ago. It is not a beta software but we acknowledge there are glitches to be fixed, both in the app itself and in the documentation. In this phase, we are trying to be as reactive as possible to fix issues.
Last thing, thanks for your feedback, but as quoted in the contributing documentation, you should rather give this kind of feedback / ask your question on our forum, issues on github are for qualified bugs only.
Kind regards.
from cells.
@bsinou Ah I see. Well I think you need to work on the setup procedure and documentation a bit more before it feels mature and something workable. As it is a binary with a guided install, you have lot's of edge cases and ways to eff things up as a user. Also, it might be a good idea for you to have a "uninstall" or "clear data" option in the CLI. I figured I could nuke the pydio dir in .configure and then I could start from scratch. Another idea: You should bake into the installer setting cells up as a service. Your documentation is fine, but it seems like a simple addition which would be nice.
In any case, I appreciate the work you have put into this, I am just not sure you've gone down the right path if you want Pydio to be easily accessible and usable by mainstream users. As mentioned, I think I have a fair idea of the inner workings on Linux after 10+ years as a devops. If I have so many issues with this, the problem is not with me ... It's really on your end.
With that ranting out of the way :O) What sort of details do you want? I figured that error message was the relevant message, as I get the File not found message from the Cells webserver, which indicates it's not finding any php to execute.
In case this is what you need/want, I have included the entire startup log here:
018-08-17T09:44:34.838Z INFO nats started
2018-08-17T09:45:03.498Z INFO pydio.grpc.jobs started
2018-08-17T09:45:03.508Z INFO pydio.grpc.update started
2018-08-17T09:45:03.519Z INFO pydio.grpc.data.sync started
2018-08-17T09:45:03.581Z INFO
2018-08-17T09:45:03.581Z INFO 0.0.0.0:80 {
2018-08-17T09:45:03.581Z INFO proxy /a localhost:33583 {
2018-08-17T09:45:03.581Z INFO without /a
2018-08-17T09:45:03.581Z INFO transparent
2018-08-17T09:45:03.581Z INFO }
2018-08-17T09:45:03.581Z INFO proxy /auth localhost:40113 {
2018-08-17T09:45:03.581Z INFO without /auth
2018-08-17T09:45:03.581Z INFO transparent
2018-08-17T09:45:03.581Z INFO }
2018-08-17T09:45:03.581Z INFO proxy /io localhost:34629 {
2018-08-17T09:45:03.581Z INFO transparent
2018-08-17T09:45:03.581Z INFO }
2018-08-17T09:45:03.581Z INFO proxy /ws localhost:42023 {
2018-08-17T09:45:03.582Z INFO websocket
2018-08-17T09:45:03.582Z INFO without /ws
2018-08-17T09:45:03.582Z INFO }
2018-08-17T09:45:03.582Z INFO proxy /plug/ localhost:35071 {
2018-08-17T09:45:03.582Z INFO transparent
2018-08-17T09:45:03.582Z INFO without /plug/
2018-08-17T09:45:03.582Z INFO }
2018-08-17T09:45:03.582Z INFO proxy /dav/ localhost:33137 {
2018-08-17T09:45:03.582Z INFO transparent
2018-08-17T09:45:03.583Z INFO without /dav/
2018-08-17T09:45:03.583Z INFO }
2018-08-17T09:45:03.583Z INFO
2018-08-17T09:45:03.583Z INFO
2018-08-17T09:45:03.583Z INFO
2018-08-17T09:45:03.583Z INFO fastcgi / localhost:9000 php {
2018-08-17T09:45:03.583Z INFO root "/root/.config/pydio/cells/static/pydio"
2018-08-17T09:45:03.583Z INFO index index.php
2018-08-17T09:45:03.583Z INFO }
2018-08-17T09:45:03.583Z INFO status 403 {
2018-08-17T09:45:03.583Z INFO /data
2018-08-17T09:45:03.584Z INFO /core
2018-08-17T09:45:03.584Z INFO /conf
2018-08-17T09:45:03.584Z INFO }
2018-08-17T09:45:03.584Z INFO rewrite {
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/a/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/auth/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/io"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/ws/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/plug/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/dav/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/wopi/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/loleaflet/"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/hosting/discovery"
2018-08-17T09:45:03.584Z INFO if {path} not_starts_with "/lool/"
2018-08-17T09:45:03.584Z INFO to {path} {path}/ /index.php
2018-08-17T09:45:03.584Z INFO }
2018-08-17T09:45:03.584Z INFO
2018-08-17T09:45:03.584Z INFO
2018-08-17T09:45:03.584Z INFO root "/root/.config/pydio/cells/static/pydio"
2018-08-17T09:45:03.584Z INFO errors "/root/.config/pydio/cells/logs/caddy_errors.log"
2018-08-17T09:45:03.584Z INFO }
2018-08-17T09:45:03.584Z INFO
2018-08-17T09:45:03.585Z INFO Activating privacy features... done.
2018-08-17T09:45:03.587Z INFO http://0.0.0.0
2018-08-17T09:45:03.587Z INFO http://0.0.0.0
2018-08-17T09:45:03.647Z INFO pydio.grpc.data.objects started
2018-08-17T09:45:03.667Z INFO pydio.grpc.chat started
2018-08-17T09:45:03.685Z INFO pydio.grpc.docstore started
2018-08-17T09:45:03.685Z INFO pydio.grpc.log started
**2018-08-17T09:45:03.784Z ERROR pydio.grpc.config Could not run {"error": "Invalid database url"}**
2018-08-17T09:45:03.842Z INFO pydio.grpc.meta started
2018-08-17T09:45:03.843Z INFO pydio.grpc.acl started
2018-08-17T09:45:03.851Z INFO pydio.grpc.user-key started
2018-08-17T09:45:03.871Z INFO pydio.grpc.policy started
2018-08-17T09:45:03.872Z INFO pydio.grpc.user-meta started
2018-08-17T09:45:04.528Z INFO pydio.api.front-plugins started
2018-08-17T09:45:04.589Z INFO pydio.grpc.gateway.proxy started
2018-08-17T09:45:04.647Z INFO micro.api started
2018-08-17T09:45:04.915Z INFO pydio.grpc.tasks started
2018-08-17T09:45:06.108Z INFO pydio.grpc.data.sync.pydiods1 started
2018-08-17T09:45:06.122Z INFO pydio.grpc.data.sync.cellsdata started
2018-08-17T09:45:06.159Z INFO pydio.grpc.data.sync.personal started
2018-08-17T09:45:06.212Z INFO pydio.grpc.data.objects.local1 started
2018-08-17T09:45:06.255Z INFO pydio.grpc.data.objects.local1 Starting objects service local1
2018-08-17T09:45:33.492Z INFO pydio.grpc.mailer Starting mailer with queue 'boltdb'
2018-08-17T09:45:33.492Z INFO pydio.grpc.mailer Starting mailer with sender 'smtp'
2018-08-17T09:45:33.493Z INFO pydio.grpc.mailer started
2018-08-17T09:45:33.506Z INFO pydio.grpc.tree started
2018-08-17T09:45:33.650Z INFO pydio.api.websocket started
2018-08-17T09:45:33.735Z INFO pydio.grpc.data.index started
2018-08-17T09:45:33.812Z INFO pydio.grpc.role started
2018-08-17T09:45:33.820Z INFO pydio.grpc.data-key started
2018-08-17T09:45:33.821Z INFO pydio.grpc.workspace started
2018-08-17T09:45:33.832Z INFO pydio.grpc.user started
2018-08-17T09:45:36.228Z INFO pydio.grpc.data.index.personal started
2018-08-17T09:45:36.237Z INFO pydio.grpc.data.index.cellsdata started
2018-08-17T09:45:36.251Z INFO pydio.grpc.data.index.pydiods1 started
2018-08-17T09:45:42.357Z INFO pydio.grpc.data.sync.cellsdata Sending event to start datasource resync
2018-08-17T09:45:42.359Z INFO pydio.grpc.tasks Run Job resync-ds-cellsdata on timer event <nil>
2018-08-17T09:45:42.366Z INFO pydio.grpc.data.sync.personal Sending event to start datasource resync
2018-08-17T09:45:42.378Z INFO pydio.grpc.tasks Run Job resync-ds-personal on timer event <nil>
2018-08-17T09:45:42.385Z INFO pydio.grpc.data.sync.pydiods1 Sending event to start datasource resync
2018-08-17T09:45:42.394Z INFO pydio.grpc.tasks Run Job resync-ds-pydiods1 on timer event <nil>
2018-08-17T09:45:42.600Z INFO pydio.grpc.data.sync.cellsdata Listing all S3 objects for path {"bucket": "cellsdata", "path": ""}
2018-08-17T09:45:42.624Z INFO pydio.grpc.data.index.cellsdata Opening Indexation Session 4e8bf52d-a202-11e8-93cf-00163e730ebd
2018-08-17T09:45:42.625Z INFO pydio.grpc.data.index.cellsdata Closing Indexation Session 4e8bf52d-a202-11e8-93cf-00163e730ebd
2018-08-17T09:45:42.626Z INFO pydio.grpc.data.index.cellsdata Sent all events event on topic
2018-08-17T09:45:42.675Z INFO pydio.grpc.data.sync.personal Listing all S3 objects for path {"bucket": "personal", "path": ""}
2018-08-17T09:45:42.678Z INFO pydio.grpc.data.index.personal Opening Indexation Session 4e9442fe-a202-11e8-ac1e-00163e730ebd
2018-08-17T09:45:42.679Z INFO pydio.grpc.data.index.personal Closing Indexation Session 4e9442fe-a202-11e8-ac1e-00163e730ebd
2018-08-17T09:45:42.679Z INFO pydio.grpc.data.index.personal Sent all events event on topic
2018-08-17T09:45:42.775Z INFO pydio.grpc.data.sync.pydiods1 Listing all S3 objects for path {"bucket": "pydiods1", "path": ""}
2018-08-17T09:45:42.777Z INFO pydio.grpc.data.index.pydiods1 Opening Indexation Session 4ea37a35-a202-11e8-a302-00163e730ebd
2018-08-17T09:45:42.779Z INFO pydio.grpc.data.index.pydiods1 Closing Indexation Session 4ea37a35-a202-11e8-a302-00163e730ebd
2018-08-17T09:45:42.779Z INFO pydio.grpc.data.index.pydiods1 Sent all events event on topic
2018-08-17T09:46:03.519Z INFO pydio.grpc.share started
2018-08-17T09:46:03.631Z INFO pydio.grpc.timer started
2018-08-17T09:46:03.633Z INFO pydio.grpc.activity started
2018-08-17T09:46:03.737Z INFO pydio.grpc.timer Registering Job {"job": "actions.auth.prune.tokens"}
2018-08-17T09:46:03.737Z INFO pydio.grpc.timer Registering Job {"job": "archive-changes-job"}
2018-08-17T09:46:03.737Z INFO pydio.grpc.timer Registering Job {"job": "flush-mailer-queue"}
2018-08-17T09:46:03.737Z INFO pydio.grpc.timer Registering Job {"job": "internal-prune-jobs"}
2018-08-17T09:46:03.738Z INFO pydio.grpc.timer Registering Job {"job": "prune-versions-job"}
2018-08-17T09:46:03.738Z INFO pydio.grpc.timer Registering Job {"job": "resync-changes-job"}
2018-08-17T09:46:03.738Z INFO pydio.grpc.timer Registering Job {"job": "users-activity-digest"}
2018-08-17T09:46:03.820Z INFO pydio.grpc.changes started
2018-08-17T09:46:33.737Z INFO pydio.rest.workspace started
2018-08-17T09:46:33.738Z INFO pydio.rest.frontend started
2018-08-17T09:46:33.769Z INFO pydio.grpc.versions started
2018-08-17T09:46:33.803Z INFO pydio.grpc.auth started
2018-08-17T09:46:33.818Z INFO pydio.grpc.auth config using log level: debug
2018-08-17T09:46:33.818Z INFO pydio.grpc.auth config issuer: http://127.0.0.1:40113/dex
2018-08-17T09:46:33.835Z INFO pydio.grpc.auth config storage:
2018-08-17T09:46:33.835Z INFO pydio.grpc.auth config static client: cells-front
2018-08-17T09:46:33.842Z INFO pydio.grpc.auth config connector: pydio
2018-08-17T09:46:33.848Z INFO pydio.grpc.auth config response types accepted: [code token id_token]
2018-08-17T09:46:33.848Z INFO pydio.grpc.auth config id tokens valid for: 10m0s
2018-08-17T09:46:33.854Z INFO Warning, could not find static directory for web resoures /root/.config/pydio/cells/static - Only API and GRPC accesses will be available
2018-08-17T09:46:33.892Z INFO pydio.grpc.auth keys expired, rotating
2018-08-17T09:46:34.124Z INFO pydio.grpc.auth keys rotated, next rotation: 2018-08-17 15:46:34.067993571 +0000 UTC
2018-08-17T09:46:34.124Z INFO pydio.grpc.auth listening (http) on 0.0.0.0:40113
2018-08-17T09:47:03.576Z INFO pydio.grpc.search started
2018-08-17T09:47:03.693Z INFO pydio.rest.role started
2018-08-17T09:47:03.706Z INFO pydio.rest.docstore started
2018-08-17T09:47:03.736Z INFO pydio.rest.log started
2018-08-17T09:47:03.737Z INFO pydio.rest.user-meta started
2018-08-17T09:47:03.739Z INFO pydio.rest.update started
2018-08-17T09:47:03.739Z INFO pydio.rest.config started
2018-08-17T09:47:03.784Z INFO pydio.rest.policy started
2018-08-17T09:47:03.784Z INFO pydio.rest.mailer started
2018-08-17T09:47:03.787Z INFO pydio.rest.activity started
2018-08-17T09:47:04.487Z INFO pydio.grpc.gateway.data started
2018-08-17T09:47:04.512Z INFO pydio.rest.gateway.wopi started
2018-08-17T09:47:04.707Z INFO pydio.rest.gateway.dav started
etc ...
The only other error I see is the one about database. The installer could connect fine to MariaDB to my socket, so I am assuming this is not the MySQL database but something else..?
from cells.
Hi,
2018-08-17T09:45:03.581Z INFO 0.0.0.0:80
Could you try using another URL, for instance localhost:80, there are some issues with some TP dependencies with this 0.0.0.0 IP.
Also, do you have any error in the caddy_errors.log file ?
.../.config/pydio/cells/logs
from cells.
just stepping in
Ah I see. Well I think you need to work on the setup procedure and documentation a bit more before it feels mature and something workable. As it is a binary with a guided install, you have lot's of edge cases and ways to eff things up as a user. Also, it might be a good idea for you to have a "uninstall" or "clear data" option in the CLI. I figured I could nuke the pydio dir in .configure and then I could start from scratch. Another idea: You should bake into the installer setting cells up as a service. Your documentation is fine, but it seems like a simple addition which would be nice.
In any case, I appreciate the work you have put into this, I am just not sure you've gone down the right path if you want Pydio to be easily accessible and usable by mainstream users. As mentioned, I think I have a fair idea of the inner workings on Linux after 10+ years as a devops. If I have so many issues with this, the problem is not with me ... It's really on your end.
@Kramerican, this is open source software and contributions are more than welcome : even our doc is open source, so feel free to PR! The goal is to make this as much devops-friendly as possible, so any hint is appreciated. Just, please, avoid the "did you ever test at all?"-mode, if you want the core team to stay motivated to work freely for you, thanks in advance ;-) If you can help with packaging recommandations (e.g. to distribute a ready-to-use service), we are all ears.
Finally, FYI we are working on removing php completely, which will greatly ease the installation steps in the next version. And also the Docker image may be a good option to test?
Have a nice day, i let @bsinou help on the concrete issues (I'm on vacations right now ;-) )
Charles
from cells.
@bsinou Yes the Caddy error log reveals:
20/Aug/2018:15:39:27 +0000 [ERROR 0 /] Primary script unknown
20/Aug/2018:15:39:27 +0000 [ERROR 0 /index.php] Primary script unknown
As I suspected, it can't find anything to execute in the primary web root as it's misconfigured, somehow.
EDIT Where can I find the Caddy config file Cells uses, so I can inspect it / correct it? I just tried using localhost:80 and that just gives me
404 Site xxxx.dk is not served on this interface
I'm running this in an LXD container on a bridged / NAt'ed IP - so seems to me Caddy doesn't know to resolve localhost -> external IP, which makes sense
from cells.
from cells.
Hi i’m out of office right now, can help more next week. Did you check https://github.com/mholt/caddy/wiki/Troubleshooting-PHP-FPM-and-FastCGI ? You must have a permission issue somewhere
from cells.
Hi,
On my side, I took a little bit of time to re-do a full install from scratch on following system:
- Fresh Ubuntu 18.4.1 Server VM (KVM on centOS7)
- Cells 1.0.3 Home edition
- Using :8080 on both bind and external address (e.g: 192.168.1.22:8080)
- No ssl (testing on a local host...)
I have strictly followed to the letter the admin guide that you can find here: https://github.com/pydio/pydio-doc-admin-guide/blob/cells-v1/1_installation_guides/03_home_and_enterprise_edition/ubuntu_install.md <= I have updated a few point to take your feedback into account, so please rather follow this to be sure, we will publish this on the pydio.com website ASAP.
There are still some errors that show up in the log, typically:
2018-08-22T14:48:17.843Z ERROR pydio.grpc.tasks {"id":"","code":0,"detail":"sql: Scan error on column index 0: converting driver.Value type \u003cnil\u003e (\"\u003cnil\u003e\") to a uint64: invalid syntax","status":""}
and
2018-08-22T14:25:35.507Z ERROR pydio.grpc.policy Error while inserting relation {"error": "Error 1062: Duplicate entry 'rest-apis-default-accesses-shares-default-policy' for key 'idm_policy_u1'"}
These errors are not blocking, but we will publish a patch for this soon. Yet, the application is running fine and all expected features are there.
@parkush the info message that gave the title to this thread ("Warning, could not find static directory etc...") is not blocking and always there. So you might not have the same problem as @Kramerican .
Do you have exactly the same setup and symptoms? (otherwise, you might want to open a thread on the forum
@Kramerican I must admit I have not yet tested Cells in an LXD container, we tend to prefer docker images or LVM depending on our needs.
Thus said, can you precise the bind and external URLs you use, I will try to have a look?
Where can I find the Caddy config file Cells uses, so I can inspect it / correct it?
The config CaddyFile is generated on the fly before being loaded.
from cells.
from cells.
For the record:
when it works outside of specific test environments.
It does already (I for instance use it for on a CentOS VPS with FQDN and SSL). Here, I was rather trying to reproduce @Kramerican issue to see if the problem could be on our side.
from cells.
Fwiw, i faced the same warning/error in the log, but after ditching ~pydio/.config
and redoing the install from scratch, i have a working cells 1.0.3 instance following https://pydio.com/en/docs/cells/v1/debian-systems on a debian stretch lxc container, accessing localhost:8080 over ssh forwarding from my machine.
Will be able to compare it with pydio 8.2.1, as i understand the latter will be in "maintenance mode only" in the future... but at least its community version supports LDAP ootb :)
from cells.
Hi,
For the record and as already noted in this thread, the warning message that gave the title of this issue is not blocking and rather a legacy warning that comes from the integration with the coreos/dex library that provides auth nechanisms via JWT.
We have removed the message from the log. Thus, the next commit will close this issue.
The fix will be included in the v1.0.4 that will be published in the next few days.
If you still have some problems to install and/or run cells, please refer to the forum and feel free to open a new thread there.
Regards.
from cells.
Related Issues (20)
- Password change fails when forcing MFA at the same time HOT 1
- Enhancement: language support for collabaro (editor libreoffice) HOT 1
- docker image: variable for database location and database passord
- cannot install (cells.exe configure) HOT 2
- Docs for k8s installs HOT 12
- writing files to webdav share / mountpoint of public links creates empty files (locking enabled)
- Remember me feature is not available
- WebDAV directory listing is too slow HOT 5
- docker image does not recognise timezone appropriately HOT 2
- Policy applied on shared cell is also affecting own cell HOT 1
- Web Interface Menu point of return to main page from cells console are missed if turn off home section HOT 2
- The circle that allows the user to navigate through an audio file during preview disappear HOT 4
- Impossible to make Pydio work with collabora online HOT 2
- Typo? HOT 1
- Cells not working behind cloudflare tunnel HOT 5
- File and folder rename won't allow to change case HOT 2
- Increase timeout for response when indexing files.
- Last-Modified time format is invalid when synchronizing image files/photos using reverse proxy. HOT 4
- [UX Improvement] Context Menu: File Deletion Menu Item Should be Red (Danger) HOT 1
- Collabora is used in pydio cells, and the Collabora interface cannot display Chinese. HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cells.