Re: Compile Problems on SuSE SLES 9.0

Let me see if I can answer your questions below.

1. Yes it is running on a mulitiprocessor server. It is a Compaq ML370
server running SuSE SLES 9.0. I believe it has dual 2.4 P4's with 4gb
of ram.

2. I have only added 2 routers and 1 switch.

3. No I have not used any remote hosts. I only installed the server
(with agent) and loaded NetXMS on a windows workstation. Then I ran
NETXMS console and connected to the server. Just basic stuff to see
what it can do.

4. It always seems to stop half way through discovering the interfaces.
 The devices I added that it freezes on have probably about 40
interfaces. It seems to lock up when discovering those interfaces
(through poll....configuration).

Also, one other thing. Is there any default configuration that I can
change to have it use our read SNMP string by default rather than
public? I keep having to change it on every device. Also, I haven't
found any device discovery. Does it do that? Seems like a great tool
if I can get it stable.

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

>>> victor_at_opticom.lv 2/6/2006 9:23 AM >>>

Hello!

Tip: to unlock database after daemon crash, run "nxdbmgr check"
command.

Your problem is not common - I know 0.2.9 installations which runs
without any problems. However, they mostly run on Windows and FreeBSD,
so maybe it's a Linux-related problem. Can you please provide me with
more information (question follows)?

1. Do you run NetXMS on multiprocessor server?
2. What kind of devices you have added?
3. Do you use NetXMS agents on remote hosts?
4. Can you remember exact place in configuration poll when it stops?

Thank you in advance!

Best regards,
Victor

> -----Original Message-----
> From: TIM MOORE [mailto:MOORET10_at_odjfs.state.oh.us]
> Sent: Monday, February 06, 2006 4:10 PM
> To: NetXMS Users
> Cc: alk_at_ctco.lv
> Subject: Re: [netxms-users] Compile Problems on SuSE SLES 9.0
>
>
> I got everything working. However, this latest build doesn't
> seem stable. If I leave the server up and running (and
> agent) even with no console left open and running, the server
> locks up when I try to open another console connection to it
> later. For example, I got everything working well on Friday
> afternoon. I had to blow away the mysql database and
> re-create to do this. Then I opened a NetXMS console from a
> windows workstation and configured a few devices and saved
> the map(desktop). I then closed all external console
> connections. I left it up and running on the server over the
> weekend. Then on Monday morning, I opened a console
> connection to it again. Everything seems fine. I tried to
> add a device and it did. Then I try to poll (configuration)
> the device and it locks up half way through the polling.
> After that I can't do any more polling.
>
> When I get on the server I see that netxmsd is no longer
> running. It just crashes I guess. If I try to start it
> again, I get this error.
>
> [06-Feb-2006 08:42:59] Database is already locked by another
> NetXMS server instance (IP address: 10.3.8.41, machine info:
> noc-mon2 Linux Release 2.6.5-7.97-bigsmp)
>
> That IP address is the IP of the server that NetXMS is
> running on. For some reason, the daemon crashes and leaves
> the database locked. Last time it did this, I even rebooted
> the box and tried to start the daemon and it still shows locked.
>
> Anyone else experience this? Is this a configuration
> problem? I'll attach my configuration documents.
>
>
> --------------------------------------
> Tim Moore
> 614.387.8197
> Network Operations Center
> ODJFS
>
> >>> alk_at_ctco.lv 2/2/2006 2:23 PM >>>
>
> You should grab windows-binary package, install it windows box (or
any
>
> *NIX using wine) and then run nxcon.exe.
>
> wbr, alex.
>
> TIM MOORE wrote:
> > Sorry, but I got it working. It was a problem with my conf file.
> > However, I would still like to know how to run/configure with a
gui.
>
> > Agent and server are both running.
> >
>
>
>
> 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 Mon Feb 06 2006 - 17:50:28 EET