Skip to content
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

Linux client crashes with GLib-ERROR **: Creating pipes for GWakeup: Too many open files #1769

Closed
lapinsami opened this issue Feb 2, 2020 · 19 comments

Comments

@lapinsami
Copy link

Expected behaviour

The client doesn't crash

Actual behaviour

The client crashes after a few hours or a few days

Steps to reproduce

  1. Run the client
  2. Wait for a day or so, maybe longer, who knows. Took ~16 hours last time it happened (today).

Client configuration

Client version:
2.6.2git. Built from Git revision 1d7455 on Dec 24 2019.

Operating system:
Manjaro Linux 64bit

OS language:
English (en_GB)

Qt version used by client package (Linux only, see also Settings dialog):
5.14.0-1

Client package (From Nextcloud or distro) (Linux only):
nextcloud-client 2.6.2-1 from the Arch community repo

Logs

Nothing related to the issue in the logfile. Error from terminal output.

(process:93519): GLib-ERROR **: 23:08:28.546: Creating pipes for GWakeup: Too many open files

@rain0r
Copy link

rain0r commented Feb 11, 2020

Can confirm this error. Happens every night on my desktop.

  • glib-2.60.7-r1
  • glibc-2.30-r3
  • nextcloud-client-2.6.2
(process:4358): GLib-ERROR **: 04:14:30.687: Creating pipes for GWakeup: Too many open files
Trace/breakpoint trap

@subdee
Copy link

subdee commented Mar 12, 2020

I also confirm, it happens often and the client dies. I am continuously out of sync.

nextcloud-client-2.6.3git from AUR

@danjpgriffin
Copy link

I also have this issue. I have a PR that provides a fix.

#1899

@sputnick-dev
Copy link

sputnick-dev commented Apr 1, 2020

Same issue, happens when my system backup script run.

(nextcloud_20200330:15992): GLib-ERROR **: 00:17:17.968: Creating pipes for GWakeup: Too many open files

Nextcloud version 2.5.1git
Using Qt 5.11.3, built against Qt 5.11.3
Using 'OpenSSL 1.1.1d 10 Sep 2019'

@claell
Copy link

claell commented Apr 4, 2020

@danjpgriffin Thanks for providing a fix, let's hope, it gets merged soon!

Also do you think this is related or even the same issue as #1035?

@danjpgriffin
Copy link

@claell Not sure if the same issue. I will try and figure out a test-case to see if I can reproduce this on my own machine when I get time.

@ibschreiber
Copy link

Same here.
Ubuntu 16.04 LTS
current client version from ppa

(nextcloud:1787): GLib-ERROR **: Creating pipes for GWakeup: Zu viele offene Dateien
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

@ibschreiber
Copy link

ibschreiber commented Apr 30, 2020

Workaround script:

Put this into an executable file and just execute in Autostart instead of nextcloud binary

#!/bin/bash

NCC="/usr/bin/nextcloud"

while [ true ];
do
  /usr/bin/pgrep -x "nextcloud" > /dev/null
  if [ 0 = $? ]
  then
    echo "Already Running"
  else
    echo "Stopped - restarting"
    $NCC &
  fi
  sleep 5;
done;

@fndmossmann
Copy link

I'm having the same issue.

nextcloud[2171]: Creating pipes for GWakeup: Too many open files

I was using version 2.6.4 from flathub on Fedora 32.
The native version, from Fedora's repo, which was the same version, also had the same problem.

Just grabbed the latest daily AppImage build (https://download.nextcloud.com/desktop/daily/Linux/Nextcloud-2.7.0.20200515-daily-x86_64.AppImage), which should have @danjpgriffin's PR included, and will test it for a couple of days.
Hope if works.

@fndmossmann
Copy link

Yup, 6 days running the 2.7.0 client without crashes.

@claell
Copy link

claell commented May 21, 2020

Thanks for testing @fndmossmann. I will leave this open until it lands in a stable release.

@RampantPanda
Copy link

RampantPanda commented Jun 7, 2020

I get the error "Too many open files" when syncing a bunch of jpgs. I am using the appimage version 2.7.0. Not sure if this is a separate issue? The client doesnt crash, just doesn't sync.

I had the same issue in the stable version as well and tried the daily to see if that would fix the issue.

EDIT: Nevermind, I started a new sync with 2.7.0 and now it seems to work just fine.

@RampantPanda
Copy link

...actually,

This still happens, just took a while with a new sync. I'm using the 2.7.0 daily appimages, and the sync never completes. I get a lot of "too many files open" errors and the client sometimes crashes. I'm using Fedora 32 with Gnome and wayland.

@simonszu
Copy link

Similar issue on Mac OS:

2020-10-21 19:23:05:142 [ critical  ]:  QNetworkInterface: could not create IPv6 socket (Too many open files)
QThreadPipe: Unable to create pipe: Too many open files
2020-10-21 19:25:56:268 [ fatal default ]:      QEventDispatcherUNIXPrivate(): Can not continue without a thread pipe

Client is simply crashing after hours or few days after starting.

@michield
Copy link

Yes, this is definitely an issue. Using Ubuntu 20.04.1 LTS

Creating pipes for GWakeup: Too many open files

I think it's been happening to me for quite some time, but I didn't notice. Very awkward when restarting it, causes document conflicts in the team.

lsof |wc -l
returns 2751132

but further investigation with

lsof | cut -d ' ' -f 1 | sort | uniq -c

finds that

2164468 zoom

so, even if it's nice if nextcloud can handle this exceptional situation, the culprit (in my case) is zoom

@github-actions
Copy link

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@achimrothe
Copy link

The big still exists even with client 3.2.01
GLib-ERROR **: 10:45:37.701: Creating pipes for GWakeup: Too many open files

@github-actions github-actions bot removed the stale label May 5, 2021
@github-actions
Copy link

github-actions bot commented Jun 2, 2021

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Jun 2, 2021
@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests