[1.4] zbx_malloc: out of memory. requested '3084308801' bytes.

[zabbix_es]

zabbix_server dies after start.
I have attached log file with debug enabled.

[alexandro]

I have the same trouble with zabbix 1.4 from www, 1.4.1 from svn, trunk from svn.
This bug doesn't occur when zabbix compiled with '--without-libcurl' flag.
OS is Debian GNU/etch

PS: svn 1.4.1 and trunk versions doesn't have "include/dbsync.h" file...



Log file without debug:
25102:20070601:121022 Starting zabbix_server. ZABBIX 1.4.
25102:20070601:121022 **** Enabled features ****
25102:20070601:121022 SNMP monitoring: YES
25102:20070601:121022 WEB monitoring: YES
25102:20070601:121022 Jabber notifications: NO
25102:20070601:121022 **************************
25105:20070601:121022 server #3 started [Trapper]
25106:20070601:121022 server #4 started [Trapper]
25107:20070601:121022 server #5 started [ICMP pinger]
25103:20070601:121022 server #1 started [Poller. SNMP:ON]
25104:20070601:121022 server #2 started [Poller. SNMP:ON]
25109:20070601:121022 server #6 started [Alerter]
25111:20070601:121022 server #7 started [Housekeeper]
25111:20070601:121022 Executing housekeeper
25111:20070601:121022 Deleted 0 records from history and trends
25112:20070601:121022 server #8 started [Timer]
25114:20070601:121022 server #10 started [Node watcher. Node ID:0]
25113:20070601:121023 server #9 started [Poller for unreachable hosts. SNMP:ON]
25115:20070601:121023 server #11 started [HTTP Poller]
25102:20070601:121023 server #0 started [Watchdog]
25117:20070601:121023 server #12 started [Discoverer. SNMP:ON]
25115:20070601:121023 zbx_malloc: out of memory. requested '3083355761' bytes.
25102:20070601:121023 One child process died. Exiting ...
25102:20070601:121025 ZABBIX Server stopped

[knarfS]

Same problem here

Hi.

I think it has something to do with web monitoring and curl:

18489:20070601:043225 Error doing curl_easy_perform [server returned nothing (no headers, no data)]
18489:20070601:043225 zbx_malloc: out of memory. requested '3083440494' bytes.
18450:20070601:043225 One child process died. Exiting ...
18450:20070601:043227 ZABBIX Server stopped

This happens with zabbix 1.4, openSUSE 10.2 and kernel 2.6.18.2-34-default

HTH, Frank

[ghislain]

i have the same error when i enable discovery mode. When not enabled it runs ok but if i enable it then..memory alloction troubles

Ghislain.

[Alexei]

Are you using MySQL?

[alexandro]

Yes, i am using mysql.
5.0.32-7etch1

[knarfS]

Yes, I'm using mysql (version 5.0.26) shipped with openSUSE.

[Eugene]

Please try this patch to solve your problems.

[alexandro]

This patch don't solve my problem.

[zabbix_es]

Me too

Yes I am also using MySQL:

>mysql -V
mysql Ver 14.12 Distrib 5.0.18, for suse-linux (i686) using readline 5.1

>cat /proc/version
Linux version 2.6.16.13-4-smp (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Wed May 3 04:53:23 UTC 2006

SUSE Linux 10.1

Are you using MySQL?

[zabbix_es]

Me neither.

I have applied the patch but error remains ...

(See attachment)

[schulzor2004]

patch didn't work

We also applied the patch and it didn't work, here the log:

18730:20070604:113620 Starting zabbix_server. ZABBIX 1.4.
18730:20070604:113620 **** Enabled features ****
18730:20070604:113620 SNMP monitoring: YES
18730:20070604:113620 WEB monitoring: YES
18730:20070604:113620 Jabber notifications: NO
18730:20070604:113620 **************************
18739:20070604:113621 server #7 started [Trapper]
18740:20070604:113621 server #8 started [Trapper]
18743:20070604:113621 server #9 started [Trapper]
18746:20070604:113621 server #11 started [Trapper]
18733:20070604:113621 server #1 started [Poller. SNMP:ON]
18734:20070604:113621 server #2 started [Poller. SNMP:ON]
18744:20070604:113621 server #10 started [Trapper]
18751:20070604:113621 server #12 started [ICMP pinger]
18752:20070604:113621 server #13 started [Alerter]
18754:20070604:113621 server #14 started [Housekeeper]
18754:20070604:113621 Executing housekeeper
18756:20070604:113621 server #15 started [Timer]
18760:20070604:113621 server #17 started [Node watcher. Node ID:0]
18761:20070604:113621 server #18 started [HTTP Poller]
18763:20070604:113621 server #19 started [HTTP Poller]
18735:20070604:113621 server #3 started [Poller. SNMP:ON]
18768:20070604:113621 server #21 started [HTTP Poller]
18770:20070604:113621 server #22 started [HTTP Poller]
18730:20070604:113621 server #0 started [Watchdog]
18765:20070604:113621 server #20 started [HTTP Poller]
18737:20070604:113621 server #5 started [Poller. SNMP:ON]
18736:20070604:113621 server #4 started [Poller. SNMP:ON]
18759:20070604:113621 server #16 started [Poller for unreachable hosts. SNMP:ON]
18738:20070604:113621 server #6 started [Poller. SNMP:ON]
18772:20070604:113621 server #23 started [Discoverer. SNMP:ON]
18765:20070604:113621 zbx_malloc: out of memory. requested '3083190611' bytes.
18730:20070604:113621 One child process died. Exiting ...
18730:20070604:113623 ZABBIX Server stopped

-----

We just have a Web-Page monitored, that produces an 404-error (because it is not present, just for testing). The out-of-mem-error occurs short after starting the zabbix_server. When the monitored website was present (no error 404), there was no out-of-mem.

[Alexei]

We just have a Web-Page monitored, that produces an 404-error (because it is not present, just for testing). The out-of-mem-error occurs short after starting the zabbix_server. When the monitored website was present (no error 404), there was no out-of-mem.

Thanks for the note. This may help us a lot, really!

[zabbix_es]

Me too!

Yes, It's the same in my case, I have also a web page monitorized with zabbix but I did not related with this issue. Sorry!

Now, I see that it could be a reason of the issue.

[zabbix_es]

But

But my monitorized web page works properly.
I don't have any errors when I surf my monitorized web page ...