Hi Alex,
What user is the mysql daemon running as? Are there any limits on
that user or user class (/etc/login.conf). Just because you have
raised the kernel limits does not mean they are raised for the user.
Can you login as that user and type "limit" and get something like -
%limit
cputime unlimited
filesize unlimited
datasize 1581056 kbytes
stacksize 524288 kbytes
coredumpsize unlimited
memoryuse unlimited
vmemoryuse unlimited
descriptors 19000
memorylocked unlimited
maxproc 5547
sbsize unlimited
%
Hope this helps,
Ken
----- Original Message -----
From: "Heikki Tuuri" <Heikki.Tuuri@stripped>
To: "Varshavchick Alexander" <alex@stripped>
Cc: <mysql@stripped>
Sent: Tuesday, October 21, 2003 9:54 AM
Subject: Re: InnoDB or OS restriction?
> Alex,
>
> because 512 MB is not an InnoDB or MySQL restriction, it must be an
OS
> restriction :).
>
> I assume you have not allocated 1.5 GB of MySQL key_buffer.
>
> Best regards,
>
> Heikki
> Innobase Oy
> http://www.innodb.com
> InnoDB - transactions, row level locking, and foreign keys for MySQL
> InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up
> MyISAM tables
>
>
> ----- Alkuperäinen viesti -----
> Lähettäjä: "Varshavchick Alexander" <alex@stripped>
> Vastaanottaja: "Heikki Tuuri" <Heikki.Tuuri@stripped>
> Kopio: <mysql@stripped>
> Lähetetty: Tuesday, October 21, 2003 2:55 PM
> Aihe: Re: InnoDB or OS restriction?
>
>
> > Hi Heikki,
> >
> > here is a snip from the original posting which you probably have
> > overlooked:
> >
> > > > > The first strange thing is that MAXDSIZ and DFLDSIZ in
kernel config
> are
> > > > > setted to 1536M
> >
> > Regards
> >
> > ----
> > Alexander Varshavchick, Metrocom Joint Stock Company
> > Phone: (812)118-3322, 118-3115(fax)
> >
> > On Mon, 20 Oct 2003, Heikki Tuuri wrote:
> >
> > > Date: Mon, 20 Oct 2003 22:05:07 +0300
> > > From: Heikki Tuuri <Heikki.Tuuri@stripped>
> > > To: mysql@stripped
> > > Subject: Re: InnoDB or OS restriction?
> > >
> > > Alex,
> > >
> > > in FreeBSD user process memory space is often restricted to 512
MB. You
> have
> > > to reconfigure or recompile the FreeBSD kernel to increase that
limit.
> > >
> > > Best regards,
> > >
> > > Heikki Tuuri
> > > Innobase Oy
> > > http://www.innodb.com
> > > Foreign keys, transactions, and row level locking for MySQL
> > > InnoDB Hot Backup - a hot backup tool for InnoDB: now
> > > also backs up your MyISAM tables
> > >
> > >
> > > ----- Original Message -----
> > > From: "alex" <alex@stripped>
> > > Newsgroups: mailing.database.myodbc
> > > Sent: Monday, October 20, 2003 1:30 PM
> > > Subject: Re: InnoDB or OS restriction?
> > >
> > >
> > > > Hi again,
> > > >
> > > > as there was not a single answer to my question I can imagine
that no
> one
> > > > encountered the same issue, but anyways, can there be any
hints? First
> of
> > > > all, are there any means of looking at mysql memory allocation
list
> > > > grouped by some major parts - for example,
> > > > innodb main pool - can be retrieved from innodb monitor
> > > > innodb additional pool - can be retrieved from innodb monitor
> > > > myisam main cache - ...?
> > > > myisam sort buffer - ...?
> > > > memory allocated from OS - ...?
> > > >
> > > > The questiion is why mysql is trying to allocate memory via
malloc
> from OS
> > > > while the innodb additional pool is occupied only by 50%? Or
is it
> myisam
> > > > buffer that mysql is trying to extend?
> > > >
> > > > Regards
> > > >
> > > > ---
> > > > Alex
> > > >
> > > > On Tue, 14 Oct 2003, alex wrote:
> > > >
> > > > > Hi people,
> > > > >
> > > > > I have mysql 4.0.7-gamma/linuxthreads running under FreeBSD
4.6.2
> > > (server
> > > > > has 4G phisical memory), and occasionally mysql traps with
the
> message:
> > > > >
> > > > > InnoDB: Fatal error: cannot allocate 1064960 bytes of
> > > > > InnoDB: memory with malloc! Total allocated memory
> > > > > InnoDB: by InnoDB 513951016 bytes. Operating system errno:
12
> > > > > InnoDB: Cannot continue operation!
> > > > >
> > > > > The first strange thing is that MAXDSIZ and DFLDSIZ in
kernel config
> are
> > > > > setted to 1536M, and the second one is that each time it
happens,
> while
> > > > > the number of bytes reported to cannot be allocated is
different,
> total
> > > > > memory allocated by InnoDB is exactly the same - 513951016
bytes.
> Which
> > > > > restrictions are the cause of this - InnoDB's or FreeBSD's?
> > > > >
> > > > > Thanks in advance
> > > > >
> > > > > ----
> > > > > Alex
> > > > >
> > > > > --
> > > > > MySQL General Mailing List
> > > > > For list archives: http://lists.mysql.com/mysql
> > > > > To unsubscribe:
> http://lists.mysql.com/mysql?unsub=1
> > > > >
> > > >
> > > > --
> > > > MySQL General Mailing List
> > > > For list archives: http://lists.mysql.com/mysql
> > > > To unsubscribe:
> > >
http://lists.mysql.com/mysql?unsub=1
> > > >
> > >
> > >
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:
http://lists.mysql.com/mysql?unsub=1
> > >
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
http://lists.mysql.com/mysql?unsub=1
>
>
