a rather basic question, but somehow I seem to be unable to solve it ...
After installing textproc/apache-solr and then starting it, it complains like this:
Instead of disabling the warning, I decided to increase the maxprocs to the mentioned 65000. And so I created a new login class in login.conf(5) like this:
I then assigned the newly created login class to the solr user, so that
Upon restarting solr, the warning about the "Max Processes Limit" didn't go away. And so I checked with
Apparently my increased maxprocesses is ignored by the solr service script.
Investigating the script, I saw that it invokes the daemon using
So my best guess is that
Obviously I am missing something very trivial here, but how then do I configure different ulimits for users lacking a login shell?
After installing textproc/apache-solr and then starting it, it complains like this:
Code:
root@gwendolin:~ # service solr start
*** [WARN] *** Your Max Processes Limit is currently 8499.
It should be set to 65000 to avoid operational disruption.
If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in your profile or solr.in.sh
Instead of disabling the warning, I decided to increase the maxprocs to the mentioned 65000. And so I created a new login class in login.conf(5) like this:
Code:
solr:\
:maxproc=65000:
I then assigned the newly created login class to the solr user, so that
pw showuser solr
shows me this:
Code:
solr:*:161:161:solr:0:0:Apache Solr System:/var/db/solr:/usr/sbin/nologin
Upon restarting solr, the warning about the "Max Processes Limit" didn't go away. And so I checked with
limits -U solr
:
Code:
root@gwendolin:~ # limits -U solr
Resource limits for class solr:
cputime infinity secs
filesize infinity kB
datasize 33554432 kB
stacksize 524288 kB
coredumpsize infinity kB
memoryuse infinity kB
memorylocked infinity kB
maxprocesses 65000
openfiles 116847
sbsize infinity bytes
vmemoryuse infinity kB
pseudo-terminals infinity
swapuse infinity kB
kqueues infinity
umtxp infinity
Apparently my increased maxprocesses is ignored by the solr service script.
Investigating the script, I saw that it invokes the daemon using
su -m solr /usr/local/solr/bin/solr start
.So my best guess is that
su -m ...
interferes with my updated maxprocs setting for the user. As far as I understand it, "su(1) -m" is supposed to "leave the environment unmodified". But I can hardly think this refers to the ulimit settings.Obviously I am missing something very trivial here, but how then do I configure different ulimits for users lacking a login shell?