On Wed, Feb 15, 2023 at 03:10:08PM +0100, Why 42? The lists account. wrote:
> However, I also tried testing the same two filesystems using the
> "Flexible IO Tester" or fio (it's available as a package). When I used it
> to do random 4K reads and writes, I appear to have the opposite result:
...
On Mon, Feb 13, 2023 at 01:50:13PM -, Stuart Henderson wrote:
> ...
> It maybe worth checking whether mfs is actually helping -
> it's easy to assume that because it's in RAM it must be fast,
> but I've had machines where mfs was slower than SSD
> (https://marc.info/?l=openbsd-misc&m=16494211
On 2023-02-12, Why 42? The lists account. wrote:
>
> You're exactly right. With this entry in fstab:
>> swap /tmp mfs rw,nodev,nosuid,-s=4194304 0 0
>
> I now have this /tmp space:
>> mjoelnir:~ 12.02 13:15:07 % df -h
>> Filesystem SizeUsed Avail Capacity Mounted on
>> /dev/sd1a 10
On Sun, Feb 12, 2023 at 01:28:04PM +0100, Why 42? The lists account. wrote:
>
> On Sun, Feb 05, 2023 at 02:50:44PM -0300, Crystal Kolipe wrote:
> > On Sun, Feb 05, 2023 at 06:05:22PM +0100, Why 42? The lists account. wrote:
> > ...
> > > The fstab file contains this mount entry for tmp:
> > > swap
On Sun, Feb 05, 2023 at 02:50:44PM -0300, Crystal Kolipe wrote:
> On Sun, Feb 05, 2023 at 06:05:22PM +0100, Why 42? The lists account. wrote:
> ...
> > The fstab file contains this mount entry for tmp:
> > swap /tmp mfs rw,nodev,nosuid,-s=16777216 0 0
>
> This is 8 Gb, which exceeds the default
On Sun, Feb 05, 2023 at 06:05:22PM +0100, Why 42? The lists account. wrote:
> mount_mfs: mmap: Cannot allocate memory
...
> The fstab file contains this mount entry for tmp:
> swap /tmp mfs rw,nodev,nosuid,-s=16777216 0 0
This is 8 Gb, which exceeds the default value for datasize for t
is clean; not checking
/dev/sd1l (281ef747da03afe7.l): file system is clean; not checking
/dev/sd2c (67c92dad63883338.c): file system is clean; not checking
mount_mfs: mmap: Cannot allocate memory
kbd: keyboard mapping set to de.nodead
keyboard.encoding -> de.nodead
pf enabled
kern.maxproc: 1
Le 04/04/2022 à 15:43, Claudio Jeker a écrit :
You should really use as-set for this:
as-set ru-set { 2148 2585 2587 ... }
And also not match any (at least I think you don't really want that to
match on ibgp sessions):
match from ebgp AS as-set ru-set set { localpref 250 nexthop blackhole }
Le 04/04/2022 à 15:43, Claudio Jeker a écrit :
On Tue, Mar 29, 2022 at 09:53:56AM +0200, Laurent CARON wrote:
Hi,
I'm happily running several OpenBGPd routers (Openbsd 7.0).
After having applied the folloxing filters (to blackhole traffic from
certain countries):
include "/etc/bgpd/deny-asn
On Tue, Mar 29, 2022 at 09:53:56AM +0200, Laurent CARON wrote:
> Hi,
>
> I'm happily running several OpenBGPd routers (Openbsd 7.0).
>
> After having applied the folloxing filters (to blackhole traffic from
> certain countries):
>
> include "/etc/bgpd/deny-asn.ru.bgpd"
> include "/etc/bgpd/deny-
On Mon, Apr 04, 2022 at 03:14:35PM +0200, Laurent CARON wrote:
>
> Le 01/04/2022 à 14:38, Claudio Jeker a écrit :
> >
> > The numbers look reasonable with maybe the exception of prefix and BGP
> > path attrs. Unless this system is pushing or pulling lots of full feeds to
> > peers I would not exp
Le 01/04/2022 à 14:38, Claudio Jeker a écrit :
The numbers look reasonable with maybe the exception of prefix and BGP
path attrs. Unless this system is pushing or pulling lots of full feeds to
peers I would not expect such a high number of prefixes. Also the number
of path attributes is high b
Le 29/03/2022 à 14:50, Stuart Henderson a écrit :
Also: check the values for bgpd's login class (as root, "su -c bgpd -"
then "ulimit -a"), and are you starting bgpd from the rc-script or by hand?
Hi Stuart,
# ulimit -a
time(cpu-seconds) unlimited
file(blocks) unlimited
coredum
On Thu, Mar 31, 2022 at 09:06:05PM +0200, Laurent CARON wrote:
> Le 29/03/2022 à 12:10, Claudio Jeker a écrit :
> > I doubt it is the filters. You run into some sort of memory leak. Please
> > monitor 'bgpctl show rib mem' output. Also check ps aux | grep bgpd output
> > to see why and when the mem
Le 29/03/2022 à 12:10, Claudio Jeker a écrit :
I doubt it is the filters. You run into some sort of memory leak. Please
monitor 'bgpctl show rib mem' output. Also check ps aux | grep bgpd output
to see why and when the memory starts to go up.
With that information it may be possible to figure out
Le 29/03/2022 à 12:10, Claudio Jeker a écrit :
I doubt it is the filters. You run into some sort of memory leak. Please
monitor 'bgpctl show rib mem' output. Also check ps aux | grep bgpd output
to see why and when the memory starts to go up.
With that information it may be possible to figure out
hop blackhole }
>> match from any AS 2895 set { localpref 250 nexthop blackhole }
>>
>> The bgpd daemon crashes every few days with the following:
>>
>> Mar 21 11:36:54 bgpgw-004 bgpd[76476]: 338 roa-set entries expired
>> Mar 21 12:06:54 bgpgw-004 bgpd[76476]: 36 r
with the following:
>
> Mar 21 11:36:54 bgpgw-004 bgpd[76476]: 338 roa-set entries expired
> Mar 21 12:06:54 bgpgw-004 bgpd[76476]: 36 roa-set entries expired
> Mar 21 12:11:54 bgpgw-004 bgpd[76476]: 82 roa-set entries expired
> Mar 21 12:22:36 bgpgw-004 bgpd[99215]: fatal in RDE:
[76476]: 82 roa-set entries expired
Mar 21 12:22:36 bgpgw-004 bgpd[99215]: fatal in RDE: prefix_alloc:
Cannot allocate memory
Mar 21 12:22:36 bgpgw-004 bgpd[65049]: peer closed imsg connection
Mar 21 12:22:36 bgpgw-004 bgpd[65049]: main: Lost connection to RDE
Mar 21 12:22:36 bgpgw-004 bgpd[76476]:
Le 30/06/2020 à 11:56, Claudio Jeker a écrit :
Can you check and monitor with ps aux | grep bgpd and or top the VSZ and
RSS of the RDE process. What is the maximum you notice. Also how do you
start bgpd? Make sure the limits from login.conf are actually applied
(using rcctl start should do that w
29055 entries
> min 0 max 8 avg/std-dev = 1.773/0.925
> attr hash: size 16384, 18541 entries
> min 0 max 8 avg/std-dev = 1.132/0.848
>
>
> More often than not the BGPd daemon is crashing (although having plenty of
> RAM (80G) on the server) wit
y
of RAM (80G) on the server) with: /var/log/messages
fatal in RDE: rde_dispatch_imsg_session: imsg_get error: Cannot allocate
memory
fatal in RDE: prefix_alloc: Cannot allocate memory
fatal in RDE: communities_copy: Cannot allocate memory
peer closed imsg connection
main: Lost connection t
On 2018-07-09, Nan Xiao wrote:
> Hi Stuart,
>
> This is my kernel information:
>
> $ sysctl -n kern.version | head -1
> OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST 2018
>
> I remember I used to build -current code before. So is it possible
> that will mess up my system?
Anything that yo
Hi Stuart,
This is my kernel information:
$ sysctl -n kern.version | head -1
OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST 2018
I remember I used to build -current code before. So is it possible
that will mess up my system?
Thanks!
Best Regards
Nan Xiao
On Sun, Jul 8, 2018 at 10:17 PM
On 2018/07/08 21:56, Nan Xiao wrote:
> Hi Stuart,
>
> Thanks for your reply!
>
> $ cat /etc/installurl
> https://ftp.openbsd.org/pub/OpenBSD
>
> Does my /etc/installurl will always fetch -current?
>
> Thanks in advance!
> Best Regards
> Nan Xiao
>
>
> On Sun, Jul 8, 2018 at 7:33 AM, Stuart He
Hi Stuart,
Thanks for your reply!
$ cat /etc/installurl
https://ftp.openbsd.org/pub/OpenBSD
Does my /etc/installurl will always fetch -current?
Thanks in advance!
Best Regards
Nan Xiao
On Sun, Jul 8, 2018 at 7:33 AM, Stuart Henderson wrote:
> On 2018-07-07, Tom Smyth wrote:
>> Hi otto
>>
>>
On 2018-07-07, Tom Smyth wrote:
> Hi otto
>
> I must check that last time i read man page it was related it was for
> syspatch
/etc/installurl is used if present, pkg_add selects /snapshots/ or /6.3/
etc depending on the kernel version string.
If set, PKG_PATH overrides /etc/installurl, and thi
Hello
yeah the installurl functionality appears to have been added to
after 6.1
thanks Otto
On 7 July 2018 at 17:10, Tom Smyth wrote:
> Hi otto
>
> I must check that last time i read man page it was related it was for
> syspatch
>
>
> Thanks
>
>
>
> On Sat 7 Jul 2018, 17:07 Otto Moerbeek, wrot
Hi otto
I must check that last time i read man page it was related it was for
syspatch
Thanks
On Sat 7 Jul 2018, 17:07 Otto Moerbeek, wrote:
> On Sat, Jul 07, 2018 at 03:52:44PM +0100, Tom Smyth wrote:
>
> > Hello Nan,
> > you need to set the PKG_path as Stuart suggested to install package
On Sat, Jul 07, 2018 at 03:52:44PM +0100, Tom Smyth wrote:
> Hello Nan,
> you need to set the PKG_path as Stuart suggested to install packages using
>
> pkg_add command
>
> for example to use fastly cdn mirror you would set your pkg_path variable as
> shown below
>
> export PKG_PATH=https://fa
Hello Nan,
you need to set the PKG_path as Stuart suggested to install packages using
pkg_add command
for example to use fastly cdn mirror you would set your pkg_path variable as
shown below
export PKG_PATH=https://fastly.cdn.openbsd.org/pub/OpenBSD/$(uname
-r)/packages/$(uname -p)/
/etc/insta
HI Stuart,
Thanks for your reply!
I don't set PKG_PATH environment.
Yes, it seems I installed the current package:
$ ls -l /usr/local/bin/egdb
-rwxr-xr-x 1 root bin 10040410 Jun 28 19:03 /usr/local/bin/egdb
But I can't remember what I have done. I can only remember I modified
/etc/installurl
On 2018-07-07, Nan Xiao wrote:
> Hi Philip,
>
> Thanks very much for your time and effort!
>
> The following is the command output:
>
> $ readelf -Wl /usr/local/bin/egdb | awk '/RANDOM/{print ($5+0)/1024}'
> 88.4844
>
> The same as yours.
That is from -current.
> Honestly, I am not sure whether
Hi Philip,
Thanks very much for your time and effort!
The following is the command output:
$ readelf -Wl /usr/local/bin/egdb | awk '/RANDOM/{print ($5+0)/1024}'
88.4844
The same as yours.
Honestly, I am not sure whether the package is for -stable or -current.
After installation, I just add fo
On Wed, Jul 4, 2018 at 6:31 PM Nan Xiao wrote:
> Thanks very much for your time and patience. I run "syspatch" command
> regularly, so it should be 6.3-stable.
>
> My full dmesg output is here:
>
...
Okay, nothing weird in there.
And full ouput of "vmstat -m":
>
Nothing stands out in that out
Hi Philip,
Thanks very much for your time and patience. I run "syspatch" command
regularly, so it should be 6.3-stable.
My full dmesg output is here:
OpenBSD 6.3 (RAMDISK_CD) #98: Sat Mar 24 14:26:39 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 422
On Wed, Jul 4, 2018 at 12:57 AM Nan Xiao wrote:
> My OS is 6.3. I already use "pkg_add -u" to upgrade all installed
> packages. cmake and egdb are are installed by "pkg_add", not compiled
> by me.
>
You don't mention -release, or -stable, or -current, which is utterly
critical: 6.3-release and 6
HI Philip,
Thanks very much for your detailed explanation!
My OS is 6.3. I already use "pkg_add -u" to upgrade all installed
packages. cmake and egdb are are installed by "pkg_add", not compiled
by me.
"vmstat -m" gives some information:
$ vmstat -m
Memory statistics by bucket size
Size
On Tue, 3 Jul 2018, Philip Guenther wrote:
Flakey button on my mouse; time to clean it again and throw it out if it
keeps glitching. Sorry about that.
> On Tue, Jul 3, 2018 at 4:53 PM Nan Xiao wrote:
> > Thanks for your reply! The "ulimit -a" outputs following:
> >
> > $ ulimit -a
> > time(c
9:37 PM, Marc Espie wrote:
> > On Tue, Jul 03, 2018 at 05:31:22PM +0800, Nan Xiao wrote:
> >> Hi all,
> >>
> >> Greeting from me!
> >>
> >> I am running OpenBSD 6.3, and don't know from when, loading some
> >> binary will prompt &
me!
>>
>> I am running OpenBSD 6.3, and don't know from when, loading some
>> binary will prompt "Cannot allocate memory":
>>
>> $ egdb
>> ksh: egdb: Cannot allocate memory
>>
>> $ cmake
>> ksh: cmake: Cannot allocate memory
>&
On Tue, Jul 03, 2018 at 05:31:22PM +0800, Nan Xiao wrote:
> Hi all,
>
> Greeting from me!
>
> I am running OpenBSD 6.3, and don't know from when, loading some
> binary will prompt "Cannot allocate memory":
>
> $ egdb
> ksh: egdb: Cannot allocate memory
Hi all,
Greeting from me!
I am running OpenBSD 6.3, and don't know from when, loading some
binary will prompt "Cannot allocate memory":
$ egdb
ksh: egdb: Cannot allocate memory
$ cmake
ksh: cmake: Cannot allocate memory
But the memory seems enough:
$top
..
Memory: Real: 57
7eb5d0,0x7f7ebb60,0x7f7ebb78)
> 7097 ktrace NAMI "/usr/X11R6/bin/node"
> 7097 ktrace RET execve -1 errno 2 No such file or directory
> 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78)
> 7097 ktrace NAMI "/usr/local/bin/
CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78)
7097 ktrace NAMI "/usr/local/bin/node"
7097 ktrace RET execve -1 errno 12 Cannot allocate memory
7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3)
7097 ktrace RET mprotect 0
7097 ktrace CAL
I can't reproduce this on -current amd64, neither with a snapshot from last
week, nor after updating today.
thfr@e5570:~$ node -v
v8.11.1
thfr@e5570:~$ node
> console.log('test log');
test log
undefined
> .exit
thfr@e5570:~$
> node -v
> bash: /usr/local/bin/node: Ca
The subject is the problem:
node -v
bash: /usr/local/bin/node: Cannot allocate memory
I am on current, last grabbed the snapshot last Friday I think.
Plenty of swap and memory available
vmstat
procsmemory pagedisk traps cpu
r s avm fre flt re
MB. Then programs being run as another user stopped working with
> `cannot allocate memory' error, while there's clearly plenty of
> memory. E.g. useradd -m a7sl4 ; doas -u a7sl4 mpv "$x". Then reboot,
> cannot login as usual user to xdm. Login(1)s on ttys didn't
Solved, thank you. I was imprudent.
I have strange issues. I installed go port and figured out that go
compiler and executables produced by it require 770 MB of datasize.
I bumped datasize-max and datasize-cur of login class `default' to
771 MB. Then programs being run as another user stopped working with
`cannot allocate m
On 2016-01-30, Lampshade wrote:
> xz: Adjusted the number of threads from 2 to 1 to not exceed the memory
> usage limit of 1600 MiB
>
> 1600 is clearly larger than 674*2=1348
A closer reading of the man page reveals that memory consumption
is even higher in multi-threaded mode.
In multi-thr
d: "Christian Weisgerber"
Do: "Lampshade" ;
Wysłane: 16:25 Sobota 2016-01-30
Temat: Re: xz: (stdin): Cannot allocate memory
> Lampshade:
>
> > I have following error:
> > cat archive.tar | xz -zf --format=xz -9e --threads=2 - >
archive.tar.xz
> > xz: (stdin
This xz command worked in past so I think something must
have been changed in past. Indeed, this command worked
when I had 4G of DDR3@1333Mhz RAM. Now I have 6GB DDR3
on the same laptop so I have even more.
I will look at ulimit -d this evening. I didn't changed them manually, so they
must have bee
Lampshade:
> I have following error:
> cat archive.tar | xz -zf --format=xz -9e --threads=2 - > archive.tar.xz
> xz: (stdin): Cannot allocate memory
You are using the most extreme compression setting, which requires
about 674 MB per thread according to the xz(1) man page. This
c
-beta (GENERIC.MP) #1846: Sun Jan 17 02:34:54 MST
> 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> I have following error:
> cat archive.tar | xz -zf --format=xz -9e --threads=2 - > archive.tar.xz
> xz: (stdin): Cannot allocate memory
(GENERIC.MP) #1846: Sun Jan 17 02:34:54 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
I have following error:
cat archive.tar | xz -zf --format=xz -9e --threads=2 - > archive.tar.xz
xz: (stdin): Cannot allocate memory
Hi, had same Problem.the only (poor) workaround i found is running qemu as
root .
max or both but
:(
>
> From: Alexis de BRUYN
> Sent: Thu Jul 17 14:56:11 CEST 2014
> To:
> Subject: Re: [Cannot allocate memory][Qemu][x86 & i386] limits ? login.conf ?
>
>
> On 16.07.2014 10:48, Francois Pussault wrote:
> > Hi all.
>
On 16.07.2014 10:48, Francois Pussault wrote:
> Hi all.
Hi François,
> I experiment qemu problems while playing with emulators/virtual machines ...
>
> When I try to create any virtual machines with x86_64 or i 386 hardware and
> more than 256Mo ram that fail.
> Qemu return
Hi all.
I experiment qemu problems while playing with emulators/virtual machines ...
When I try to create any virtual machines with x86_64 or i 386 hardware and
more than 256Mo ram that fail.
Qemu returns "Cannot allocate memory".
I tryied to modify login.conf & ulimits values,
Running 4.9, downloading large files (>250MB) from a website behind a
firewall clustered with relayd fails with the following error in our logs:
Dec 6 12:14:15 fw01 relayd[5615]: relay httpproxy, session 768464 (23
active), 0, * -> 192.168.15.101:80, Cannot allocate memory
He
Kevin Chadwick wrote:
>On Wed, 18 May 2011 17:41:32 +
>annathemerm...@hush.com wrote:
>
>> I'm just trying to make it take advantage of the swap
>> encryption (random keys unlike a single key I have to remember
the
>> password for);
>
>bioctl or vnconfig and /dev/urandom maybe useful here
So
On 2011-05-18, annathemerm...@hush.com wrote:
>> In -current it has been bumped to 2GB so you'll be able to use
>> more there.
>
> A bit below, but now it works. I'm quite happy with stable. Unless
> current fixes my X11 keyboard issues, I'd rather not deal with
> current unless I have a second ha
On Wed, 18 May 2011 17:41:32 +
annathemerm...@hush.com wrote:
> I'm just trying to make it take advantage of the swap
> encryption (random keys unlike a single key I have to remember the
> password for);
bioctl or vnconfig and /dev/urandom maybe useful here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 May 2011 21:25, Stuart Henderson wrote:
> On 2011-05-03, annathemerm...@hush.com
wrote:
>>
>> So, I'm trying to create put my /tmp partition on my swap.
>>
>> So I have a line like this in my fstab:
>> swap /tmp mfs rw,nodev,nosuid,-s=2097152
>>
On 2011-05-03, annathemerm...@hush.com wrote:
>
> So, I'm trying to create put my /tmp partition on my swap.
>
> So I have a line like this in my fstab:
> swap /tmp mfs rw,nodev,nosuid,-s=2097152
> I also tried changing swap to /dev/wd0b, and changing the n in -s=n
> to smaller numbers.
[assuming
/tmp returns:
mount_mfs: mmap: Cannot allocate memory.
swapctl says neither of my swap partitions are being used.
Computer is a PowerPC, G3 iBook.
Also, is there any way to switch consoles? On i386 it was
Ctrl+Alt+F2, Ctrl+Alt+F3, and so on (in fact I think the Ctrl was
optional unless leaving X11)
Hi Claudio,
Le 30 nov. 2010 ` 19:38, Claudio Jeker a icrit :
>> This patch, opens another problem, seems that FIB is not updated at all
when applied.
>>
>> I reverted to openbgp 4.8 release.
>>
>
> You sure you have
> http://ftp.openbsd.org/pub/OpenBSD/patches/4.8/common/001_bgpd.patch
> installed
On Tue, Nov 30, 2010 at 06:24:32PM +0100, Xavier Beaudouin wrote:
> Hi Claudio,
>
> Le 30 nov. 2010 ` 17:45, Xavier Beaudouin a icrit :
>
> > Hi Claudio,
> >
> >> Maybe it is time to change the default datalimit in the RDE. So maybe
> >> something like this may help.
> >> bgpd needs quite a bit
Hi Claudio,
Le 30 nov. 2010 ` 17:45, Xavier Beaudouin a icrit :
> Hi Claudio,
>
>> Maybe it is time to change the default datalimit in the RDE. So maybe
>> something like this may help.
>> bgpd needs quite a bit more (temporary) memory when running with
>> softreconfig. A lot of additional memory
Hi Claudio,
> Maybe it is time to change the default datalimit in the RDE. So maybe
> something like this may help.
> bgpd needs quite a bit more (temporary) memory when running with
> softreconfig. A lot of additional memory is needed on reloads and when
> large sessions flap that cause a lot of
> > >
> > > > Hello,
> > > >
> > > > I have updated a openbgpd router from OpenBSD 4.7 i386 to 4.8 amd64.
> > > >
> > > > Now I have new instability like this :
> > > >
> > > > Nov 29 21:25:22 core-3 bgpd[
29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot
allocate
>> memory
>> Nov 30 02:01:47 core-3 bgpd[5522]: fatal in RDE: up_generate: Cannot
allocate
>> memory
>
> Is this box acting as a route-reflector?
>
No route reflector at all.
It is a peering b
router from OpenBSD 4.7 i386 to 4.8 amd64.
> > >
> > > Now I have new instability like this :
> > >
> > > Nov 29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot
> > > allocate
> > > memory
> > > Nov 30 02:01:47 core-3 b
like this :
> >
> > Nov 29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot
> > allocate
> > memory
> > Nov 30 02:01:47 core-3 bgpd[5522]: fatal in RDE: up_generate: Cannot
> > allocate
> > memory
> >
> > I have 2Gb on this machi
On 2010-11-30, Xavier Beaudouin wrote:
> Hello,
>
> I have updated a openbgpd router from OpenBSD 4.7 i386 to 4.8 amd64.
>
> Now I have new instability like this :
>
> Nov 29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot allocate
> memory
> Nov 30 02:01:
On Tue, Nov 30, 2010 at 08:35:46AM +0100, Xavier Beaudouin wrote:
> Hello,
>
> I have updated a openbgpd router from OpenBSD 4.7 i386 to 4.8 amd64.
>
> Now I have new instability like this :
>
> Nov 29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot allocate
Hello,
I have updated a openbgpd router from OpenBSD 4.7 i386 to 4.8 amd64.
Now I have new instability like this :
Nov 29 21:25:22 core-3 bgpd[28895]: fatal in RDE: path_alloc: Cannot allocate
memory
Nov 30 02:01:47 core-3 bgpd[5522]: fatal in RDE: up_generate: Cannot allocate
memory
I have
On 21-06-2010 22:44, Ruy Bento wrote:
...
My question is: In this small env. (100 MB - RAM) I need to change the
Kernel memory or other sysctl value, which one?
Thank you for all your replys and comments.
In 4.6 everything work perfect, so what happen 4.6 -> 4.7, it need more mem?
And if
On 2010-06-21, Ruy Bento wrote:
> spamd_black=YES # set to YES to run spamd without greylisting
you don't want blacklist-only mode if you have limited RAM.
Theo de Raadt wrote:
OpenBSD 4.7 (GENERIC) #558: Wed Mar 17 20:46:15 MDT 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 234MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX
real mem =
> > OpenBSD 4.7 (GENERIC) #558: Wed Mar 17 20:46:15 MDT 2010
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 234MHz
> > cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX
> > real mem = 10
amlogd_flags="-i rl0" # use eg. "-i interface" and see spamlogd(8)
/etc/mail/spamd.conf:
with:china:korea: it's ok
with :uatraps:china:korea: -> pfctl: Cannot allocate memory.
or
:nixspam::china:korea: -> pfctl: Cannot
> avail mem = 87961600 (83MB)
> with:uatraps:china:korea: -> pfctl: Cannot allocate memory.
Not enough kernel memory.
i rl0" # use eg. "-i interface" and see spamlogd(8)
/etc/mail/spamd.conf:
with:china:korea: it's ok
with :uatraps:china:korea: -> pfctl: Cannot allocate memory.
or
:nixspam::china:korea: -> pfctl: Cannot allocate mem
> Thanks for your advice but it did not work. So, we bought another hard
> disks.
What for? If you didn't need the data that was on the broken /home,
you could have just newfs'ed the partition ...
Jan
g (/home)
>
> I must run fsck_ffs manually.
>
> However, when I run it :
>
> fsck_ffs /dev/rwd0g
>
> 1824 DUP I=2678
> 1825 DUP I=2678
>
> cannot allocate memory for inode cache.
>
> I tried to reboot, same problem. I didn't find informations about
me partition (125 Go, ffs type).
> >
> > The following file system had unexpected inconsistency
> > ffs: /dev/rwd0g (/home)
> >
> > I must run fsck_ffs manually.
> >
> > However, when I run it :
> >
> > fsck_ffs /dev/rwd0g
> >
> > 1824 DUP
stency
> ffs: /dev/rwd0g (/home)
>
> I must run fsck_ffs manually.
>
> However, when I run it :
>
> fsck_ffs /dev/rwd0g
>
> 1824 DUP I=2678
> 1825 DUP I=2678
>
> cannot allocate memory for inode cache.
Run fsck by using the fsck(8) command. It sets up the max
/rwd0g
1824 DUP I=2678
1825 DUP I=2678
cannot allocate memory for inode cache.
I tried to reboot, same problem. I didn't find informations about it in
fsck_ffs manpage.
Do you have some advices to repair this disk, and for booting my
OpenBSD?
Regards,
--
Nicolas
SizeUsed Avail Capacity Mounted on
/dev/wd0a 72.4G6.8G 62.0G10%/
/dev/sd0a 186G159G 17.7G90%/mnt
/dev/sd1a 229G166G 51.7G76%/mnt2
# umount /mnt2
umount: /mnt2: Cannot allocate memory
# sync
# w
10:14AM up 15 days, 20:58, 1 user,
On 2008-12-30, Thilo Pfennig wrote:
>
> I have a FAT32 disk on wd1i as a disk for interchange with other
> computers. On every bootup I get the message "No space for FAT (Cannot
> allocate memory)" and then get into a shell where I should check
> manually.
This is comin
2008/12/30 Thilo Pfennig :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have a FAT32 disk on wd1i as a disk for interchange with other
> computers. On every bootup I get the message "No space for FAT (Cannot
> allocate memory)" and then get into a shell whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a FAT32 disk on wd1i as a disk for interchange with other
computers. On every bootup I get the message "No space for FAT (Cannot
allocate memory)" and then get into a shell where I should check
manually. But I can mount the disk w
On 2008-10-07, Henning Brauer <[EMAIL PROTECTED]> wrote:
> * Christophe Rioux <[EMAIL PROTECTED]> [2008-10-07 13:15]:
>> > # pfctl -f pf.conf
>> > pfctl: failed to create table __automatic_e11ee055_282 in :
>> > Cannot allocate memory
>
> so
isc@openbsd.org
> > Objet : Re: OpenBSD 3.9 -> 4.3: pfctl Cannot allocate memory
> >
> > On 2008-10-07, Christophe Rioux <[EMAIL PROTECTED]> wrote:
> > >> # pfctl -f pf.conf
> > >> pfctl: failed to create table __automatic_e11ee055_282 in :
> >
MAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > De la part de Stuart Henderson
> > Envoyi : mardi 7 octobre 2008 15:10
> > @ : misc@openbsd.org
> > Objet : Re: OpenBSD 3.9 -> 4.3: pfctl Cannot allocate memory
> >
> > On 2008-10-07, Christophe Rioux <[EMAIL PRO
The workaround work fine ... thanks
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Stuart Henderson
> Envoyi : mardi 7 octobre 2008 15:10
> @ : misc@openbsd.org
> Objet : Re: OpenBSD 3.9 -> 4.3: pfctl Cannot allocat
* Stuart Henderson <[EMAIL PROTECTED]> [2008-10-07 15:16]:
> On 2008-10-07, Christophe Rioux <[EMAIL PROTECTED]> wrote:
> >> # pfctl -f pf.conf
> >> pfctl: failed to create table __automatic_e11ee055_282 in :
> >> Cannot allocate
> >> memory
> # pfctl -f pf.conf
> > pfctl: failed to create table __automatic_e11ee055_282 in :
> > Cannot allocate memory
so the ruleset optiomizer optimized a large list of addresses into a
table for you. then allocating memory for that table failed.
> > pfctl in free(): error: chunk is already free
tha
1 - 100 of 131 matches
Mail list logo
