Displaying 14 results from an estimated 14 matches for "7680kb".
2015 Aug 14
4
persistent change of max_stack_depth
...tem services.) becomes apparent.
Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >LOG:
invalid value for parameter "max_stack_depth": 10240
Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >DETAIL:
"max_stack_depth" must not exceed 7680kB.
Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >HINT:
Increase the platform's stack depth limit via "ulimit -s" or local
equivalent.
So, I then run 'ulimit -s 12288' and still can't restart my service.
How can I increase stack depth for system p...
2015 Aug 17
2
persistent change of max_stack_depth
...gt;> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >LOG:
>> invalid value for parameter "max_stack_depth": 10240
>> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >DETAIL:
>> "max_stack_depth" must not exceed 7680kB.
>> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >HINT:
>> Increase the platform's stack depth limit via "ulimit -s" or local
>> equivalent.
>>
>> So, I then run 'ulimit -s 12288' and still can't restart my service.
&g...
2016 Feb 17
2
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...atabase offline.
>
>
> Feb 17 13:46:11 db1 systemd: Starting PostgreSQL database server...
> Feb 17 13:46:11 db1 pg_ctl: LOG: invalid value for parameter
> "max_stack_depth": 16384
> Feb 17 13:46:11 db1 pg_ctl: DETAIL: "max_stack_depth" must not exceed
> 7680kB.
> Feb 17 13:46:11 db1 pg_ctl: HINT: Increase the platform's stack depth
> limit via "ulimit -s" or local equivalent.
> Feb 17 13:46:11 db1 pg_ctl: FATAL: configuration file
> "/var/lib/pgsql/data/postgresql.conf" contains errors
> Feb 17 13:46:16 db1 pg_ctl...
2015 Aug 17
0
persistent change of max_stack_depth
...14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >LOG:
>>> invalid value for parameter "max_stack_depth": 10240
>>> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >DETAIL:
>>> "max_stack_depth" must not exceed 7680kB.
>>> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >HINT:
>>> Increase the platform's stack depth limit via "ulimit -s" or local
>>> equivalent.
>>>
>>> So, I then run 'ulimit -s 12288' and still can't re...
2016 Feb 17
4
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
On 02/17/2016 07:08 AM, Michael H wrote:
> On 17/02/16 13:01, Johnny Hughes wrote:
>> I normally just let the daily announce post to this list show what
>> is available for updates, but there is a CVE (CVE-2015-7547) that
>> needs a bit more attention which will be on today's announce list
>> of updates.
>>
>> We released a new glibc yesterday for
2016 Feb 17
2
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...; Feb 17 13:46:11 db1 systemd: Starting PostgreSQL database server...
>>> Feb 17 13:46:11 db1 pg_ctl: LOG: invalid value for parameter
>>> "max_stack_depth": 16384
>>> Feb 17 13:46:11 db1 pg_ctl: DETAIL: "max_stack_depth" must not exceed
>>> 7680kB.
>>> Feb 17 13:46:11 db1 pg_ctl: HINT: Increase the platform's stack depth
>>> limit via "ulimit -s" or local equivalent.
>>> Feb 17 13:46:11 db1 pg_ctl: FATAL: configuration file
>>> "/var/lib/pgsql/data/postgresql.conf" contains errors...
2016 Feb 17
1
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...d it
knocked my master postgresql database offline.
Feb 17 13:46:11 db1 systemd: Starting PostgreSQL database server...
Feb 17 13:46:11 db1 pg_ctl: LOG: invalid value for parameter
"max_stack_depth": 16384
Feb 17 13:46:11 db1 pg_ctl: DETAIL: "max_stack_depth" must not exceed
7680kB.
Feb 17 13:46:11 db1 pg_ctl: HINT: Increase the platform's stack depth
limit via "ulimit -s" or local equivalent.
Feb 17 13:46:11 db1 pg_ctl: FATAL: configuration file
"/var/lib/pgsql/data/postgresql.conf" contains errors
Feb 17 13:46:16 db1 pg_ctl: pg_ctl: could not start...
2015 Aug 17
2
persistent change of max_stack_depth
...< 2015-08-14 16:22:17.839 BST >LOG:
>>>> invalid value for parameter "max_stack_depth": 10240
>>>> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST
>>>> >DETAIL:
>>>> "max_stack_depth" must not exceed 7680kB.
>>>> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >HINT:
>>>> Increase the platform's stack depth limit via "ulimit -s" or local
>>>> equivalent.
>>>>
>>>> So, I then run 'ulimit -s 12288' an...
2015 Aug 14
0
persistent change of max_stack_depth
...parent.
>
> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >LOG:
> invalid value for parameter "max_stack_depth": 10240
> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >DETAIL:
> "max_stack_depth" must not exceed 7680kB.
> Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >HINT:
> Increase the platform's stack depth limit via "ulimit -s" or local
> equivalent.
>
> So, I then run 'ulimit -s 12288' and still can't restart my service.
>
> How can...
2015 Aug 14
2
persistent change of max_stack_depth
...t; Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >LOG:
> > invalid value for parameter "max_stack_depth": 10240
> > Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >DETAIL:
> >?? "max_stack_depth" must not exceed 7680kB.
> > Aug 14 16:22:17 db1 pg_ctl[3177]: < 2015-08-14 16:22:17.839 BST >HINT:
> > Increase the platform's stack depth limit via "ulimit -s" or local
> > equivalent.
> >
> > So, I then run 'ulimit -s 12288' and still can't restart my s...
2016 Feb 17
0
Kernel parameters ignored -
...d it
knocked my master postgresql database offline.
Feb 17 13:46:11 db1 systemd: Starting PostgreSQL database server...
Feb 17 13:46:11 db1 pg_ctl: LOG: invalid value for parameter
"max_stack_depth": 16384
Feb 17 13:46:11 db1 pg_ctl: DETAIL: "max_stack_depth" must not exceed
7680kB.
Feb 17 13:46:11 db1 pg_ctl: HINT: Increase the platform's stack depth
limit via "ulimit -s" or local equivalent.
Feb 17 13:46:11 db1 pg_ctl: FATAL: configuration file
"/var/lib/pgsql/data/postgresql.conf" contains errors
Feb 17 13:46:16 db1 pg_ctl: pg_ctl: could not start...
2015 Aug 14
4
persistent change of max_stack_depth
Hi All,
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.
I've Googled plenty and can't find any solution,
thanks
Michael
2016 Feb 17
0
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...>>
>> Feb 17 13:46:11 db1 systemd: Starting PostgreSQL database server...
>> Feb 17 13:46:11 db1 pg_ctl: LOG: invalid value for parameter
>> "max_stack_depth": 16384
>> Feb 17 13:46:11 db1 pg_ctl: DETAIL: "max_stack_depth" must not exceed
>> 7680kB.
>> Feb 17 13:46:11 db1 pg_ctl: HINT: Increase the platform's stack depth
>> limit via "ulimit -s" or local equivalent.
>> Feb 17 13:46:11 db1 pg_ctl: FATAL: configuration file
>> "/var/lib/pgsql/data/postgresql.conf" contains errors
>> Feb 17...
2016 Feb 17
2
Kernel parameters ignored -
...atabase offline.
>
>
> Feb 17 13:46:11 db1 systemd: Starting PostgreSQL database server...
> Feb 17 13:46:11 db1 pg_ctl: LOG: invalid value for parameter
> "max_stack_depth": 16384
> Feb 17 13:46:11 db1 pg_ctl: DETAIL: "max_stack_depth" must not exceed
> 7680kB.
> Feb 17 13:46:11 db1 pg_ctl: HINT: Increase the platform's stack depth
> limit via "ulimit -s" or local equivalent.
> Feb 17 13:46:11 db1 pg_ctl: FATAL: configuration file
> "/var/lib/pgsql/data/postgresql.conf" contains errors
> Feb 17 13:46:16 db1 pg_ctl...