Libreoffice online - "Unknown resource:"

With the integration of Libreoffice online, the following error is displayed

Error occurs when opening an existing document or create a new document

Here is the Docker log:

loolforkit version details: 2.0.1 - 2.0.1
kit-00046-0046 0:00:11.685798 [ loolkit ] ERR symlink("…/lo","/opt/lool/child-roots/46/opt/collaboraoffice5.1") failed (errno: File exists)| kit/Kit.cpp:257
kit-00047-0047 0:00:11.703482 [ loolkit ] ERR symlink("…/lo","/opt/lool/child-roots/47/opt/collaboraoffice5.1") failed (errno: File exists)| kit/Kit.cpp:257
kit-00046-0046 0:00:11.721471 [ loolkit ] ERR Poco Exception: Exception: symlink() failed| kit/Kit.cpp:1721
1mkit-00047-0047 0:00:11.721472 [ loolkit ] ERR Poco Exception: Exception: symlink() failed| kit/Kit.cpp:1721
wsd-00025-0028 0:00:21.466073 [ client_req_hdl ] WRN WOPI host did not pass optional access_token_ttl| wsd/FileServer.cpp:255
wsd-00025-0029 0:00:22.018448 [ client_ws_0002 ] ERR Unknown resource: /lool/https://office.acckey.org/index.php/apps/richdocuments/wopi/files/28%3Faccess_token=EavPx7R1jSnTLNibhpqaACO8O7nDFbP9&access_token_ttl=0&permission=edit/ws| wsd/LOOLWSD.cpp:1204
wsd-00025-0029 0:00:34.138454 [ client_ws_0003 ] ERR Unknown resource: /lool/https://office.acckey.org/index.php/apps/richdocuments/wopi/files/28%3Faccess_token=EavPx7R1jSnTLNibhpqaACO8O7nDFbP9&access_token_ttl=0&permission=edit/ws| wsd/LOOLWSD.cpp:1204
wsd-00025-0029 0:00:34.251622 [ client_ws_0004 ] ERR Unknown resource: /lool/https://office.acckey.org/index.php/apps/richdocuments/wopi/files/28%3Faccess_token=EavPx7R1jSnTLNibhpqaACO8O7nDFbP9&access_token_ttl=0&permission=edit/ws| wsd/LOOLWSD.cpp:1204
wsd-00025-0028 0:00:50.524310 [ client_ws_0005 ] ERR Unknown resource: /lool/https://office.acckey.org/index.php/apps/richdocuments/wopi/files/28%3Faccess_token=EavPx7R1jSnTLNibhpqaACO8O7nDFbP9&access_token_ttl=0&permission=edit/ws| wsd/LOOLWSD.cpp:1204

Please help solve the problem

Does the WOPI discovery URL work?
https://office.nextclo.ud/hosting/discovery

Can you translate the error message to english?

“Cannot connect to the document. Try again” - how could this be? I couldn’t find this error

Did you setup the Collabora online server in the admin panel?

Yes.

Well, this is embarrassing, we cannot connect to your document. Please try again.

I have now also this error after runing: docker pull collabora/code

I did also stop and removed container and run new one but it now show that error:

wsd-00024-0027 0:21:52.352890 [ client_ws_000a ] ERR Unknown resource: /lool/https://xxx.xxx.com/index.php/apps/richdocuments/wopi/files/336_ocgrfxxgs6tc%3Faccess_token=QSqq3X6pBFchW28xj4FROIwXtZQXVYoT&access_token_ttl=0&permission=edit/ws| wsd/LOOLWSD.cpp:1204

What do you get when your run docker info

I had that error, could see the empty openoffice container but no document.

It was Debian 8 without Aufs support.

I am on Ubuntu 16 with DigitalOcean, it show me this:

Containers: 40
 Running: 1
 Paused: 0
 Stopped: 39
Images: 3
Server Version: 1.12.3
Storage Driver: devicemapper
 Pool Name: docker-253:1-398488-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 7.125 GB
 Data Space Total: 107.4 GB
 Data Space Available: 21.83 GB
 Metadata Space Used: 14.3 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.133 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.110 (2015-10-30)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-45-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 992.5 MiB
Name: cloud
ID: DMJS:X674:PHBB:AX43:5QF2:7BCP:DTO7:763P:OC4G:YKHH:BZJO:MIUC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 127.0.0.0/8

Think its sudo apt-get install linux-image-extra-‘uname -r’ to get aufs enabled.

Damn how do you escape the forum codes! :slight_smile:
do a uname -r and paste that on the end of sudo apt-get install linux-image-extra- :slight_smile:

prob need to delete that container after a reboot and recreate to be sure

docker ps (list containers)
docker rm

but after linux-extras do a docker info first and see if you have aufs

https://docs.docker.com/engine/installation/linux/ubuntulinux/

As forgot linux-image-extra-virtual

sudo apt-get install linux-image-extra-$(uname -r) linux-image-extra-virtual

OK, just to confirm I execute this:

sudo apt-get install linux-image-extra-4.4.0-45-generic linux-image-extra-virtual

uname -r give me this: 4.4.0-45-generic

Tnx for help :slight_smile: For escape forum codes are your reffering to this: https://s3.amazonaws.com/upload.screenshot.co/5084260bc0

А какая у тебя ОС/версия? Ошибка в создании симлинка при создании джейла. Это может быть на убунте 14.04 что описано здесь
Known problems:
This docker image does not work on Ubuntu 14.04 LTS, because Ubuntu 14.04 LTS has missing kernel compile option CONFIG_AUFS_XATTR=y, which is leading to setcap not working on docker’s aufs storage.

Yeah the code quotes and the forum quotes where twisting my head.
Doesn’t take a lot though… :confused:

Yeah that is the one.

Or sudo apt-get install linux-image-extra-$(uname -r) linux-image-extra-virtual
As that will end up the same.

Then a docker info on here to see if you have aufs and you can recreate that container working.

I guess the collabora container is overlaying the nextcould file with its own file system and when aufs doesn’t exist you can not access, open or create new.

Stealing @Ark74 thunder as he fixed mine and I presume the same is true.

Executed, stoped, removed container started new, but same error.

here docker info:

Containers: 40
 Running: 1
 Paused: 0
 Stopped: 39
Images: 3
Server Version: 1.12.3
Storage Driver: devicemapper
 Pool Name: docker-253:1-398488-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 7.125 GB
 Data Space Total: 107.4 GB
 Data Space Available: 21.09 GB
 Metadata Space Used: 14.3 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.133 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.110 (2015-10-30)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-45-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 992.5 MiB
Name: cloud
ID: DMJS:X674:PHBB:AX43:5QF2:7BCP:DTO7:763P:OC4G:YKHH:BZJO:MIUC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 127.0.0.0/8

Docker isn’t using aufs, but devicemapper.
That could be your issue.

Please confirm aufs support with,
grep aufs /proc/filesystems

It is not showing me nothing when execute grep aufs /proc/filesystems

Here https://docs.docker.com/engine/userguide/storagedriver/selectadriver/ it say it can be changed do you recommend ?