Re: NetXMS Daemon Crashing

Victor,

Thanks for the quick reply. I am using mysql 4.1.20. Let me try to
run it adding --debug-all to the startup script. Hopefully, I'll find
something for you.

--------------------------------------
Tim Moore
614.387.8197
Network Operations Center
ODJFS

>>> victor_at_opticom.lv 2/6/2007 8:51:33 AM >>>

Hello!

There are other server crash reports, so most likely it's not related
to
your hardware. Unfortunatelly, I'm still unable to reproduce this in
my
test environment. My production server also running very well -
currently on HP BL460c, but under VMWare ESX/Windows 2003 and uses MS
SQL as database. First thing you can try is to run server in debug
mode
- by adding --debug-all command line option - and send me log file
after
crash.Btw, what database you are using? Also, Alex will later post a
wrapper script which will run netxmsd under debugger and collect
valuable debug information in case of crash. I will also try to setup
CentOS environment, in case there are some library issues. I hope that
we solve this issue soon.

Best regards,
Victor

-----Original Message-----
From: TIM MOORE [mailto:MOORET10_at_odjfs.state.oh.us]
Sent: Tuesday, 06 February, 2007 15:15
To: NetXMS Users
Subject: [netxms-users] NetXMS Daemon Crashing

Victor or other NetXMS users,

I think NetXMS is a great tool. Very configurable and flexible. My
ony
problem is that the daemon continually crashed on me and leaves no log
entry or reason why. I'm starting to wonder if this is related to
what
hardware or OS I'm running. I don't hear of other people having this
problem, unless they don't write about it on the user list. I've
noticed that it also might have something to do with keeping an
external
connection to the server from a NetXMS client running on a windows box.

I would connect to the server from my workstation and leave it open
for
a long period of time. But it will work for days like this, then it
crashes once and after that it is never the same again. (Seems odd I
know).

I always get on the server and run `nxdbmgr check` to unlock the
database and fix issues caused by the crash. Then I restart the
daemon.
Now even with the daemon running I cannot connect from my remote
client.
Any thoughts what could be causing this? Here are some of my specs.

Hardware:
Compaq ML370 (G3) Server with Dual Intel P4 Xeon 2.8 Gb processors 4Gb
of memory 2-72gb hard drives in Mirror Raid

Software:
CentOS 4.3 (fully patched)
Kernel: 2.6.9-42.0.3.ELsmp
gcc version 3.4.6 200604
EXT3 Filesystem with journaling

I can provide other information if anyone has any thoughts. I wonder
if
it has to do with the hardware. Is anyone else running on server
grade
hardware? Also, is there anyway to turn up more detailed logging so I
can get any idea why the daemon crashes?

Thanks for any help.

--------------------------------------
Tim Moore
614.387.8197
Network Operations Center
ODJFS

This e-mail message, including any attachments, is for the sole use of
the intended recipient(s) and may contain private, confidential,
and/or
privileged information. Any unauthorized review, use, disclosure, or
distribution is prohibited. If you are not the intended recipient,
employee, or agent responsible for delivering this message, please
contact the sender by reply e-mail and destroy all copies of the
original e-mail message.

This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain private, confidential, and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, employee, or agent responsible for delivering this message, please contact the sender by reply e-mail and destroy all copies of the original e-mail message.
Received on Tue Feb 06 2007 - 16:19:45 EET