Displaying 11 results from an estimated 11 matches for "limitstack".
2015 Aug 17
2
persistent change of max_stack_depth
...stgresql-9.4.service
>> /etc/systemd/system/multi-user.target.wants/postgresql-9.4.service
>> /usr/lib/systemd/system/postgresql-9.4.service
>>
>> I've edited
>> /etc/systemd/system/multi-user.target.wants/postgresql-9.4.service and
>> added
>>
>> LimitSTACK=12288
>>
>> to the [Unit] section of the service file.
>>
>> systemctl daemon-reload
>> systemctl restart postgresql-9.4
>>
>> I'm still getting the same errors when I try to start my service...
>>
>>
>> Aug 17 08:23:58 db1 pg_ctl[1683...
2015 Aug 17
2
persistent change of max_stack_depth
...for postgresql-9.4
[root at db1 multi-user.target.wants]# locate postgresql-9.4.service
/etc/systemd/system/multi-user.target.wants/postgresql-9.4.service
/usr/lib/systemd/system/postgresql-9.4.service
I've edited
/etc/systemd/system/multi-user.target.wants/postgresql-9.4.service and added
LimitSTACK=12288
to the [Unit] section of the service file.
systemctl daemon-reload
systemctl restart postgresql-9.4
I'm still getting the same errors when I try to start my service...
Aug 17 08:23:58 db1 pg_ctl[16839]: < 2015-08-17 08:23:58.533 BST >LOG:
invalid value for parameter "max_...
2015 Aug 17
0
persistent change of max_stack_depth
On 08/17/2015 03:34 AM, Michael H wrote:
> the [Service] section -
> [Service]
> LimitSTACK=12288
...
> By the errors I will assume that it should be in the [Service] section.
> I couldn't find confirmation of this online...
Yes, it belongs in the [Service] section.
$ man systemd.exec
...
"The execution specific configuration options are configured in the
[Service], [Soc...
2015 Aug 17
0
persistent change of max_stack_depth
...ti-user.target.wants]# locate postgresql-9.4.service
> /etc/systemd/system/multi-user.target.wants/postgresql-9.4.service
> /usr/lib/systemd/system/postgresql-9.4.service
>
> I've edited
> /etc/systemd/system/multi-user.target.wants/postgresql-9.4.service and
> added
>
> LimitSTACK=12288
>
> to the [Unit] section of the service file.
>
> systemctl daemon-reload
> systemctl restart postgresql-9.4
>
> I'm still getting the same errors when I try to start my service...
>
>
> Aug 17 08:23:58 db1 pg_ctl[16839]: < 2015-08-17 08:23:58.533 BST >...
2016 Feb 17
2
Systemd persistent change to service file
...ostgresql service that will not be
overwritten when updates are applied?
Am I correct in thinking it will be something like
vi /etc/systemd/system/postgresql.service.d/postgresql-limit-stack.conf
#with the contents:
.include /etc/systemd/system/multi-user.target.wants/postgresql.service
[Service]
LimitSTACK=17825792
thanks
Michael
2015 Aug 14
4
persistent change of max_stack_depth
Hi Thomas,
> Could anybody point me in the right direction for setting the kernel
> parameter, max_stack_depth, to 10240 for database tuning?
>
> I have currently set it by running 'ulimit -s 10240' but this does not
> survive a reboot.
>
>
Thanks for the response, I've been nosing around that file recently but
noted the first two lines;
#This file sets the
2016 Feb 17
2
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
On 17/02/16 14:44, Johnny Hughes wrote:
> On 02/17/2016 08:39 AM, Johnny Hughes wrote:
>> On 02/17/2016 08:10 AM, Michael H wrote:
>>>> The easy answer is yes .. glibc requires so many things to be restarted,
>>>> that is the best bet. Or certainly the easiest.
>>>>
>>>> Note: in CentOS 7, there is also a kernel update which is rated as
2015 Aug 14
2
persistent change of max_stack_depth
...crease the NOFILE limit for nfs-secure on a Fedora 20 machine so I set
>
> LimitNOFILE=16384
>
> In /etc/systemd/system/nfs-secure.service
>
>
Jason is probably on the right track here.
If it's centos 6 stick 'ulimit -s' in the init script
If it's centos 7 use LimitSTACK= in the service file
-Thomas
2014 Jul 17
2
ulimit warning when restarting
When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error:
Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 4096), because of default_client_limit
# doveconf default_internal_user
default_internal_user = dovecot
Should dovecot print this warning based on $default_internal_user, or
based on root?
As root:
# ulimit -n
1024
As user dovecot:
$ ulimit -n
2018 Apr 27
2
samba-tool ntacl sysvolcheck -> Too many open files
I just realize that i can't run a "samba-tool ntacl sysvolcheck" on my DC's (4.7.6):
ldb: unable to open modules directory '/usr/lib/x86_64-linux-gnu/ldb/modules/ldb' - Too many open files
ldb: unable to open modules directory '/usr/lib/x86_64-linux-gnu/samba/ldb' - Too many open files
.....
>From memory, it was just fine on samba 4.6
If I check system
2017 Feb 02
0
Dovecot performance and proxy loops with IPv6
...,
Daniel
And here system configs and dovecot configs:
sysctl:
fs.inotify.max_user_instances = 65535
fs.inotify.max_user_watches = 16384
systemd startup with ulimit settings:
[Unit]
Description=Dovecot Mailservice IMAP/POP
[Service]
Type=simple
LimitCORE=0
LimitNPROC=5000000
LimitNOFILE=65535
LimitSTACK=81920
LimitDATA=infinity
LimitMEMLOCK=infinity
LimitRSS=infinity
LimitAS=infinity
ExecStart=/usr/local/dovecot2/sbin/dovecot -F -c /usr/local/dovecot2/etc/dovecot/dovecot.conf
[Install]
WantedBy=multi-user.target
dovecot-ldap.conf:
uris = ldapi://%2Fvar%2Frun%2Fldapi
dn = cn=xxxxxxx,o=domain,...