unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Louis DeLosSantos <louis.delos@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: Issues with `lei` as non-root
Date: Tue, 28 Mar 2023 01:32:26 +0000	[thread overview]
Message-ID: <20230328013226.M125137@dcvr> (raw)
In-Reply-To: <CAE6jdTpoNijeb8gMTX2D=CNWOKx7LuC9vpn24TwSaKAXqrpHOA@mail.gmail.com>

Louis DeLosSantos <louis.delos@gmail.com> wrote:
> Hello,
> 
> I'm experimenting with `lei` as a nice search tool for `lore.kernel.org`
> 
> Everything works fine with the caveat that it seems to break if I'm not root.
> 
> When using `lei` as non-root we get this error:

I've never used lei as root nor has any part of public-inbox
ever been intended to run as root.

> ```
> E: Linux::Inotify2->new: Too many open files at
> /usr/share/perl5/vendor_perl/PublicInbox/DirIdle.pm line 40.
> connect(/run/user/1000/lei/5.seq.sock): Connection refused (after
> attempted daemon start)
> ```
> 
> Any ideas why this may occur? Is `lei` designed to only be ran as root
> or is Fedora installing perl in an odd fashion which results in root
> needing to be used?

What's the output of `ulimit -n` and `lsof -p $(lei daemon-pid)`?

(you may need to use `ps -ef |grep lei-daemon` to get the PID
if lei is broken and using too many FDs, though)

`ulimit -n' is the open file limit, typically 1024 or higher.

If `lsof -p $PID` may reveal a bug in lei which leaves too many
files open.  lei (especially with inotify on Linux) should use
far less than 1024.

(FreeBSD may end up using far more open files, but that's a
different story)

  reply	other threads:[~2023-03-28  1:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  1:00 Issues with `lei` as non-root Louis DeLosSantos
2023-03-28  1:32 ` Eric Wong [this message]
2023-03-28  1:36   ` public-inbox.org downtime expected in the next 6-8 hours Eric Wong
2023-03-28  2:30   ` Issues with `lei` as non-root Louis DeLosSantos
2023-03-28  2:52     ` Eric Wong
2023-03-28  3:05       ` Louis DeLosSantos
2023-03-28  3:38         ` Eric Wong
2023-03-28  4:08           ` Louis DeLosSantos
2023-03-28 11:12             ` [PATCH] inotify: wrap with informative error message Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230328013226.M125137@dcvr \
    --to=e@80x24.org \
    --cc=louis.delos@gmail.com \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).