Re: owncloudclient GUI issues - core dumps when non-root
On Wed, May 04, 2016 at 08:24:09AM -0400, Nick wrote: > Thanks for responding to me, appreciate your tips/advice.. I checked > the details though and my login class is 'staff', and as far as I can > see the limits are plenty (I've been changing them) > Here is the output of those commands/files: (Can you see an issue I am > maybe blind too, thanks) > > I checked my login class: > > login nick > passwd * > uid 1000 > groups nick wheel operator staff > change NEVER > class staff > gecos nick > dir /home/nick > shell /bin/ksh > expire NEVER > > And my ulimit -a: > > time(cpu-seconds) unlimited > file(blocks) unlimited > coredump(blocks) unlimited > data(kbytes) 1572864 > stack(kbytes) 4096 > lockedmem(kbytes) 2675596 > memory(kbytes) 8006984 > nofiles(descriptors) 2048 > processes 1310 > > And my login.conf: > > staff:\ > :datasize-cur=1536M:\ > :datasize-max=infinity:\ > :maxproc-max=4096:\ > :maxproc-cur=2048:\ > :ignorenologin:\ > :requirehome@:\ > :openfiles-cur=2048:\ > :openfiles-max=infinity:\ > :tc=default: Check how many files you have on your shared folder and set your limits accordingly. In my case I have $ find ~/ownCloud | wc -l 2744 My soft limit is 2048, and the hard limit is 4096: $ ulimit -n 2048 $ ulimit -Hn 4096 so I bump the soft limit when starting ownCloud: $ ulimit -n 3072 && owncloud How many file descriptors does is actually open? $ fstat -fp `pgrep owncloud` | wc -l 2853 --
Re: owncloudclient GUI issues - core dumps when non-root
Thanks for responding to me, appreciate your tips/advice.. I checked the details though and my login class is 'staff', and as far as I can see the limits are plenty (I've been changing them) Here is the output of those commands/files: (Can you see an issue I am maybe blind too, thanks) I checked my login class: login nick passwd * uid 1000 groups nick wheel operator staff change NEVER class staff gecos nick dir /home/nick shell /bin/ksh expire NEVER And my ulimit -a: time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 1572864 stack(kbytes) 4096 lockedmem(kbytes) 2675596 memory(kbytes) 8006984 nofiles(descriptors) 2048 processes 1310 And my login.conf: staff:\ :datasize-cur=1536M:\ :datasize-max=infinity:\ :maxproc-max=4096:\ :maxproc-cur=2048:\ :ignorenologin:\ :requirehome@:\ :openfiles-cur=2048:\ :openfiles-max=infinity:\ :tc=default: Original Message Subject: Re: owncloudclient GUI issues - core dumps when non-root Local Time: May 4, 2016 5:58 AM UTC Time: May 4, 2016 4:58 AM From: o...@drijf.net To: s...@protonmail.com CC: misc@openbsd.org On Tue, May 03, 2016 at 09:05:36PM -0400, Nick wrote: > Thanks for your advice, however it makes no difference changing login.conf in > the way you mentioned.. Still errors out and core dumps. > Root can't get access to it now either. Here's my login.conf, I changed the: > > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > > on my staff group as well, for which I'm a member of. login class != group The question is, which login group are you in. Also, the synatx of login.conf is a bit tricky. Check which login class you are in with useinfo and check you actual limits with ulimit -a, -Otto > > *-*-*-*-*-*-*-*-*-*-*-*-*-* MY LOGIN.CONF: -*-*-*-*-*-*-*-*-*-*-*-*- > # /etc/login.conf > > default:\ > :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/$ > :umask=022:\ > :datasize-max=2048M:\ > :datasize-cur=2048M:\ > :maxproc-max=1024:\ > :maxproc-cur=512:\ > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > :stacksize-cur=4M:\ > :localcipher=blowfish,8:\ > :tc=auth-defaults:\ > :tc=auth-ftp-defaults: > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AS REGULAR USER: -*-*-*-*-*-*-*-*-*-*-*-*- > $ owncloud > > (owncloud:29572): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > > Trace/BPT trap (core dumped) > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AND AS ROOT: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > $ su > $ owncloud > > (process:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > > Trace/BPT trap > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > > I can't think what could be causing this issue, not entirely sure how to > debug this.
Re: owncloudclient GUI issues - core dumps when non-root
On Wed, May 04, 2016 at 06:58:32AM +0200, Otto Moerbeek wrote: > On Tue, May 03, 2016 at 09:05:36PM -0400, Nick wrote: > > > Thanks for your advice, however it makes no difference changing login.conf > > in the way you mentioned.. Still errors out and core dumps. > > Root can't get access to it now either. Here's my login.conf, I changed the: > > > > :openfiles-cur=2048:\ > > :openfiles-max=4096:\ > > > > on my staff group as well, for which I'm a member of. > > login class != group > > The question is, which login group are you in. Also, the synatx of err, login class above > login.conf is a bit tricky. Check which login class you are in with > useinfo and check you actual limits with ulimit -a, userinfo sorry, for the typos, it's early here > > -Otto > > > > > *-*-*-*-*-*-*-*-*-*-*-*-*-* MY LOGIN.CONF: -*-*-*-*-*-*-*-*-*-*-*-*- > > # /etc/login.conf > > > > default:\ > > :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/$ > > :umask=022:\ > > :datasize-max=2048M:\ > > :datasize-cur=2048M:\ > > :maxproc-max=1024:\ > > :maxproc-cur=512:\ > > :openfiles-cur=2048:\ > > :openfiles-max=4096:\ > > :stacksize-cur=4M:\ > > :localcipher=blowfish,8:\ > > :tc=auth-defaults:\ > > :tc=auth-ftp-defaults: > > > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AS REGULAR USER: -*-*-*-*-*-*-*-*-*-*-*-*- > > $ owncloud > > > > (owncloud:29572): GLib-ERROR **: Creating pipes for GWakeup: Too many open > > files > > > > Trace/BPT trap (core dumped) > > > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AND AS ROOT: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > > $ su > > $ owncloud > > > > (process:3224): GConf-WARNING **: Client failed to connect to the D-BUS > > daemon: > > Did not receive a reply. Possible causes include: the remote application > > did not send a reply, the message bus security policy blocked the reply, > > the reply timeout expired, or the network connection was broken. > > > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > > daemon: > > Did not receive a reply. Possible causes include: the remote application > > did not send a reply, the message bus security policy blocked the reply, > > the reply timeout expired, or the network connection was broken. > > > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > > daemon: > > Did not receive a reply. Possible causes include: the remote application > > did not send a reply, the message bus security policy blocked the reply, > > the reply timeout expired, or the network connection was broken. > > > > (owncloud:3224): GLib-ERROR **: Creating pipes for GWakeup: Too many open > > files > > > > Trace/BPT trap > > > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > > > > I can't think what could be causing this issue, not entirely sure how to > > debug this. > > > > > > > > Original Message > > Subject: Re: owncloudclient GUI issues - core dumps when non-root > > Local Time: May 3, 2016 9:58 PM > > UTC Time: May 3, 2016 8:58 PM > > From: zel...@zeloff.org > > To: > > CC: misc@openbsd.org > > > > On Tue, May 03, 2016 at 04:20:37PM -0400, Nick wrote: > > > The owncloudclient refuses to work and core dumps on non-root user > > > Works but throws out warnings on root.. although I feel a little edgy > > > running this client as root. > > > > > > Application: owncloudclient > > > System: 5.9 Stable > > > > > > ### > > > $ owncloud > > > (owncloud:30815): GLib-ERROR **: Creating pipes for GWakeup: Too many > > > open files > > > Trace/BPT trap (core dumped) > > > > You need to bump openfiles on login.conf, e.g. > > > > :openfiles-cur=2048:\ > > :openfiles-max=4096:\ > > > > see login.conf(5), and don't forget to run cap_mkdb when you're done. > > You'll also need to log out and back in for it to take effect. When in > > doubt check things with ulimit -a and ulimit -Ha > > > > > > > $ gdb owncloud owncloud.core > > > #0 0x066932b634c5 in _g_log_abort () > > > from /usr/local/lib/libglib-2.0.so.4200.2 > > > > > > # > > > > > > $ su root > > > $ owncloud > > > > > > (process:12834): GConf-WARNING **: Client failed to connect to the D-BUS
Re: owncloudclient GUI issues - core dumps when non-root
On Tue, May 03, 2016 at 09:05:36PM -0400, Nick wrote: > Thanks for your advice, however it makes no difference changing login.conf in > the way you mentioned.. Still errors out and core dumps. > Root can't get access to it now either. Here's my login.conf, I changed the: > > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > > on my staff group as well, for which I'm a member of. login class != group The question is, which login group are you in. Also, the synatx of login.conf is a bit tricky. Check which login class you are in with useinfo and check you actual limits with ulimit -a, -Otto > > *-*-*-*-*-*-*-*-*-*-*-*-*-* MY LOGIN.CONF: -*-*-*-*-*-*-*-*-*-*-*-*- > # /etc/login.conf > > default:\ > :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/$ > :umask=022:\ > :datasize-max=2048M:\ > :datasize-cur=2048M:\ > :maxproc-max=1024:\ > :maxproc-cur=512:\ > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > :stacksize-cur=4M:\ > :localcipher=blowfish,8:\ > :tc=auth-defaults:\ > :tc=auth-ftp-defaults: > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AS REGULAR USER: -*-*-*-*-*-*-*-*-*-*-*-*- > $ owncloud > > (owncloud:29572): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > > Trace/BPT trap (core dumped) > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AND AS ROOT: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > $ su > $ owncloud > > (process:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > > Trace/BPT trap > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > > I can't think what could be causing this issue, not entirely sure how to > debug this. > > > > Original Message > Subject: Re: owncloudclient GUI issues - core dumps when non-root > Local Time: May 3, 2016 9:58 PM > UTC Time: May 3, 2016 8:58 PM > From: zel...@zeloff.org > To: > CC: misc@openbsd.org > > On Tue, May 03, 2016 at 04:20:37PM -0400, Nick wrote: > > The owncloudclient refuses to work and core dumps on non-root user > > Works but throws out warnings on root.. although I feel a little edgy > > running this client as root. > > > > Application: owncloudclient > > System: 5.9 Stable > > > > ### > > $ owncloud > > (owncloud:30815): GLib-ERROR **: Creating pipes for GWakeup: Too many open > > files > > Trace/BPT trap (core dumped) > > You need to bump openfiles on login.conf, e.g. > > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > > see login.conf(5), and don't forget to run cap_mkdb when you're done. > You'll also need to log out and back in for it to take effect. When in > doubt check things with ulimit -a and ulimit -Ha > > > > $ gdb owncloud owncloud.core > > #0 0x066932b634c5 in _g_log_abort () > > from /usr/local/lib/libglib-2.0.so.4200.2 > > > > # > > > > $ su root > > $ owncloud > > > > (process:12834): GConf-WARNING **: Client failed to connect to the D-BUS > > daemon: > > Did not receive a reply. Possible causes include: the remote application > > did not send a reply, the message bus security policy blocked the reply, > > the reply timeout expired, or the network connection was broken. > > > > (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS > > daemon: > > Did not receive a reply. Possible causes include: the remote application > > did not send a reply, the message bus security policy blocked the reply, > > the reply timeout expired, or the network connection was broken. > > Qt: Session management error: Authentication Rejected, reason : None of the > > authentication protocols specified are sup
Re: owncloudclient GUI issues - core dumps when non-root
Thanks for your advice, however it makes no difference changing login.conf in the way you mentioned.. Still errors out and core dumps. Root can't get access to it now either. Here's my login.conf, I changed the: :openfiles-cur=2048:\ :openfiles-max=4096:\ on my staff group as well, for which I'm a member of. *-*-*-*-*-*-*-*-*-*-*-*-*-* MY LOGIN.CONF: -*-*-*-*-*-*-*-*-*-*-*-*- # /etc/login.conf default:\ :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/$ :umask=022:\ :datasize-max=2048M:\ :datasize-cur=2048M:\ :maxproc-max=1024:\ :maxproc-cur=512:\ :openfiles-cur=2048:\ :openfiles-max=4096:\ :stacksize-cur=4M:\ :localcipher=blowfish,8:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults: *-*-*-*-*-*-*-*-*-*-*-*-*-* AS REGULAR USER: -*-*-*-*-*-*-*-*-*-*-*-*- $ owncloud (owncloud:29572): GLib-ERROR **: Creating pipes for GWakeup: Too many open files Trace/BPT trap (core dumped) *-*-*-*-*-*-*-*-*-*-*-*-*-* AND AS ROOT: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- $ su $ owncloud (process:3224): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (owncloud:3224): GLib-ERROR **: Creating pipes for GWakeup: Too many open files Trace/BPT trap *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- I can't think what could be causing this issue, not entirely sure how to debug this. Original Message Subject: Re: owncloudclient GUI issues - core dumps when non-root Local Time: May 3, 2016 9:58 PM UTC Time: May 3, 2016 8:58 PM From: zel...@zeloff.org To: CC: misc@openbsd.org On Tue, May 03, 2016 at 04:20:37PM -0400, Nick wrote: > The owncloudclient refuses to work and core dumps on non-root user > Works but throws out warnings on root.. although I feel a little edgy running > this client as root. > > Application: owncloudclient > System: 5.9 Stable > > ### > $ owncloud > (owncloud:30815): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > Trace/BPT trap (core dumped) You need to bump openfiles on login.conf, e.g. :openfiles-cur=2048:\ :openfiles-max=4096:\ see login.conf(5), and don't forget to run cap_mkdb when you're done. You'll also need to log out and back in for it to take effect. When in doubt check things with ulimit -a and ulimit -Ha > $ gdb owncloud owncloud.core > #0 0x066932b634c5 in _g_log_abort () > from /usr/local/lib/libglib-2.0.so.4200.2 > > # > > $ su root > $ owncloud > > (process:12834): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > Qt: Session management error: Authentication Rejected, reason : None of the > authentication protocols specified are supported and host-based > authentication failed > > (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. This doesn't crash /probably/ because owncloud using root's owncloud configuration (whatever that is), i.e., it's not monitoring the same folder as when it is run by you. > > -*-*-* > > Thanks > --
Re: owncloudclient GUI issues - core dumps when non-root
On Tue, May 03, 2016 at 04:20:37PM -0400, Nick wrote: > The owncloudclient refuses to work and core dumps on non-root user > Works but throws out warnings on root.. although I feel a little edgy running > this client as root. > > Application: owncloudclient > System: 5.9 Stable > > ### > $ owncloud > (owncloud:30815): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > Trace/BPT trap (core dumped) You need to bump openfiles on login.conf, e.g. :openfiles-cur=2048:\ :openfiles-max=4096:\ see login.conf(5), and don't forget to run cap_mkdb when you're done. You'll also need to log out and back in for it to take effect. When in doubt check things with ulimit -a and ulimit -Ha > $ gdb owncloud owncloud.core > #0 0x066932b634c5 in _g_log_abort () > from /usr/local/lib/libglib-2.0.so.4200.2 > > # > > $ su root > $ owncloud > > (process:12834): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > Qt: Session management error: Authentication Rejected, reason : None of the > authentication protocols specified are supported and host-based > authentication failed > > (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. This doesn't crash /probably/ because owncloud using root's owncloud configuration (whatever that is), i.e., it's not monitoring the same folder as when it is run by you. > > -*-*-* > > Thanks > --
owncloudclient GUI issues - core dumps when non-root
The owncloudclient refuses to work and core dumps on non-root user Works but throws out warnings on root.. although I feel a little edgy running this client as root. Application: owncloudclient System: 5.9 Stable ### $ owncloud (owncloud:30815): GLib-ERROR **: Creating pipes for GWakeup: Too many open files Trace/BPT trap (core dumped) $ gdb owncloud owncloud.core #0 0x066932b634c5 in _g_log_abort () from /usr/local/lib/libglib-2.0.so.4200.2 # $ su root $ owncloud (process:12834): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. -*-*-* Thanks
