On 2020-05-09, Lucas <lu...@sexy.is> wrote: > Hello misc@, > > Starting today, reposync is running out of memory for me. Happened 3 > times in a row already, in different stages. It looks like this when it > happens: > >>f.st...... ports/net/megatools/pkg/PLIST,v > ERROR: out of memory in flist_expand [receiver] > rsync error: error allocating core memory buffers (code 22) at util2.c(105) > [receiver=3.1.3] > rsync: [generator] write error: Broken pipe (32) > rsync error: error in socket IO (code 10) at io.c(820) [generator=3.1.3] > rsync: [receiver] write error: Broken pipe (32) > reposync: rsync failed > > I'm issuing the following command: > > oolong$ doas -u cvs /usr/local/bin/reposync > rsync://obsdacvs.cs.toronto.edu/obsdcvs/ /home/cvs > > I set up cvs user as described in the pkg-readme: > > oolong$ getent passwd cvs; id -c cvs > cvs:*:1001:1001::/nonexistent:/sbin/nologin > default > > default class is unaltered in the system: > > default:\ > :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin > /usr/local/sbin:\ > :umask=022:\ > :datasize-max=768M:\ > :datasize-cur=768M:\ > :maxproc-max=256:\ > :maxproc-cur=128:\ > :openfiles-max=1024:\ > :openfiles-cur=512:\ > :stacksize-cur=4M:\ > :localcipher=blowfish,a:\ > :tc=auth-defaults:\ > :tc=auth-ftp-defaults: > > FTR, I'm using reposync since it came out and this is the first time it > happens. I update once a week, if that matters. > > Is anyone experiencing this too? I guess I can work it around bumping > datasize for cvs user, but if this is happening to other ones, maybe > it's worht to add something to the pkg-readme.
I can add something to the readme after the ports tree has unlocked. I think you're seeing this now due to the churn because every file in the repositories was touched when the tree was tagged with OPENBSD_6_7. I haven't seen it on the 2 machines I have running reposync, but they update more frequently so probably didn't have to deal with updating all of ports+src+xenocara together, which is probably what tipped it over the edge. > Just in case, dmesg can be found after the email. Thanks in advance. Thank you for the nice clear report.
