-
Notifications
You must be signed in to change notification settings - Fork 704
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
Problems with nextcloud office since update to aio 10 #5682
Comments
I get a different error message, but it seems correlated. I post it here in case it helps:
NC Office seems working fine, but I'm flooded by this error message. In my case I get DETAILS: DETAILED LOG:
|
This is now fixed with v10.1.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
@szaimen i testet it but the problem is still exist. Message in NC LOG: Details
Details
|
/
Steps to reproduce
Expected behavior
Hello, since the update to NC AIO 10 I have the problem that my log runs full as soon as I use Nc Office. There seems to be some kind of access problem. I can see this behaviour with a new instance and an old updated instance. The instances are running on different servers each behind a nginxproxymanager which is configured as recommended here.
Everything else works fine and existing NC Office files can also be edited and saved, but I still get many entries in the log.
This error was not present before the update.
Actual behavior
Other information
Host OS
I have installed everything under Proxmox as Ubuntu 24.04 LXC.
Everything is up-to-date.
Output of
sudo docker info
Details
root@Nextcloud-kastl:~# sudo docker info Client: Docker Engine - Community Version: 27.3.1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.17.1 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.29.7 Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 10
Running: 10
Paused: 0
Stopped: 0
Images: 15
Server Version: 27.3.1
Storage Driver: overlay2
Backing Filesystem: zfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: true
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc version: v1.1.14-0-g2c9f560
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.12-4-pve
Operating System: Ubuntu 24.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 8GiB
Name: Nextcloud_K
ID: 44dbc800-dd64-42c7-a707-9230515e063c
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Docker run command or docker-compose file that you used
Other valuable info
nextcloud-aio-collabora log:
NC log:
The text was updated successfully, but these errors were encountered: