duplicity-team team mailing list archive

[Kenneth Loafman <kenneth@xxxxxxxxxxx>]

I'll ping him on that.  Could be a problem, but max_user_processes is
showing 31429, so unless he's running a big web server, it should be enough.

...Ken

~$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 31429
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 65535
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 31429
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited



On Thu, Mar 15, 2018 at 7:12 AM, <edgar.soldin@xxxxxx> wrote:

> On 15.03.2018 12:49, Kenneth Loafman wrote:
> > Hi guys,
> >
> > I need your help on https://bugs.launchpad.net/bugs/1727653.  I thought
> it was a resource problem, and it may still be.  This appears to happen on
> the 17.x series of Ubuntu, with it's mix of inetd and systemd permissionsk
> and limits.  I've suggested changes to both sides and it's not working.
> I'm thinking there may be some sort of resource limit I'm missing, but I'm
> just not seeing it.  Or perhaps there's a threading change needed.  Just
> don't know.
> >
>
> Ken,
>
> i can't see that anyone checked/raised '/proc/sys/kernel/threads-max' in
> the autostart environment as suggested here
>   https://stackoverflow.com/questions/43560230/thread-
> error-cant-start-new-thread
> in the ticket.
>
> also a debug out of threading.active_count() just before spawing might
> shed some light on the issue.
>
> ..ede
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help   : https://help.launchpad.net/ListHelp
>