> On 09/05/2012 20:05, Roberto De Ioris wrote: >>> Hi, >>> > >>> > Thanks for replying. ipcs says: >>> > >>> > Semaphores: >>> > T ID KEY MODE OWNER GROUP >>> > s 327680 5432001 --rw------- 70 70 >>> > s 327681 5432002 --rw------- 70 70 >>> > s 327682 5432003 --rw------- 70 70 >>> > _______________________________________________ >>> > >> The error you get is quite strange. >> >> I can only suppose you run out of ipc semaphores. >> >> Increase them (use an high value, like 1000) in /etc/loader.conf and >> reboot > > > Oh I see, the problem seems related to shared memory resources and > FreeBSD jails. > > From what I understand: In FreeBSD, SystemV IPC usage is disabled > within jails by default. This improves security because it prevents > non-root users from interfering with shared memory or semaphores in > different jails. This seems wise to me. > > To help figure this out, I enabled jail IPC support and restarted the > jail uWSGI runs in. When uWSGI tried to start this time, it said: > > lock engine: ipcsem > semget(): No space left on device [lock.c line 390] > semctl(): Invalid argument [lock.c line 469] > > As you suspected before, I guess this indicates that uWSGI is trying to > acquire more shared memory than is available by default on the system? >
Exactly. If you increase them it shoud work normally. Sadly i have not found other way to have interprocess locking til FreeBSD 9, where shared posix semaphores are available. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
