Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - zillo

Pages: [1]
1
General Support / Re: Management Console in FreeBSD
« on: July 17, 2015, 11:37:00 pm »
Thanks for your answer.

That is the way I thought about also.
Unfortunately the linux emulation layer in FreeBSD at this moment is 32 bits only. From what I have read this will change in FreeBSD 11, now known as CURRENT.

On my desktop machine I'm not willing to run CURRENT for vary reasons.

So I will have this problem:
On my machine I have Java 7 and Java 8 both 64 bits working.
If I try the netxms console 64bits linux version the problem is with the executable wrapper which must start the java application. The wrapper is 64 bits also and it won't run under linux compatibility layer (32 bits).

If I use the netxms console 32 bits variant for linux, the wrapper work and start the application which crash with error 13 (that is the error return by JVM 64 bits running an 32 bits java app).

That is the reason I want to try to build it myself.

Thanks,
VV

2
General Support / Management Console in FreeBSD
« on: July 17, 2015, 06:22:00 am »
Hello,

Is there a way to run the Java Management Console in FreeBSD?

More exactly, I use PC-BSD 10.1.2. I can run Eclipse without problem and I know the Console is based on Eclipse.
If there is no binary for FreeBSD, is possible to download the source and build for FreeBSD?

I use NetXMS 2.0-M2 for the moment and I prepare to move to 2.0-M5. Also I want to leave windows behind and use PC-BSD as my main desktop OS. So I need the Management Console to run under FreeBSD.

Thanks,
VV

3
General Support / Agent on FreeBSD
« on: May 20, 2014, 10:52:49 am »
Hi,

I try to run the NetXMS Agent on FreeBSD under a normal user (non-root).
First, for this to be possible, this user must be member in kmem group in order for kvm_openfiles and kvm_read operations to properly work.
With this settings, now the Net.Interface.BytesIn and related probes properly return the value requested by DCIs.

I still have some problem and questions.
When I start the Agent as root (with DebugLevel 9) the log looks clean. This is not the case when I start the Agent as normal user (non-root).
In the latest case I see log like this:
Quote
[20-May-2014 09:26:08.827] [DEBUG] External parameters providers poller thread will not start
[20-May-2014 09:26:08.828] [DEBUG] Core Agent Trying to bind on 0.0.0.0:4700
[20-May-2014 09:26:08.828] [INFO ] Listening on socket 0.0.0.0:4700
[20-May-2014 09:26:08.828] [DEBUG] StorageDiscoveryConnector: bind failed (Address already in use)
[20-May-2014 09:26:08.828] [DEBUG] StorageDiscoveryConnector: listener thread stopped
[20-May-2014 09:26:08.828] [DEBUG] PushConnector: bind failed (Address already in use)
[20-May-2014 09:26:08.828] [DEBUG] PushConnector: listener thread stopped
[20-May-2014 09:26:09.829] [INFO ] NetXMS Agent started

I was trying to see why StorageDiscoveryConnector and PushConnector failed. I need to understand exactly what this are need for.
I have surfing the code and in the src/agent/core/nxagentd.cpp file beginning from line no 917 (Agent start time), I have found an if/else test which run in one case "MasterAgentListener" and in the other "ListenerThread" and "SessionWatchdog". In this second case there is call to StartPushConnector and StartStorageDiscoveryConnector which I have found to log the "bind failed" error seen in the log.

I try to debug and hope to fix this, but I need some explanation from the developers as why this test is there and what are the differences between those different executions path. I will love to learn more about the code and I try to do this reading the sources, but a little help here will be mode than welcomed.

My real problem is that I still can not use the FreeBSD NetXMS Agent as proxy for other agents. At this moment I try to find the problem by myself and right now it is not clear for me if the proxy problem can be related to the above error ("bind failed") and different execution path.

Info:
NetXMS Agent & Server 1.2.14 on (uname -a):
FreeBSD amstel.DOMAIN.TLD 9.2-STABLE FreeBSD 9.2-STABLE #0 r264299: Thu Apr 10 01:10:40 EEST 2014
NetXMS Agent 1.2.7 - 1.2.14 on different platform including (uname -a):
FreeBSD neo.DOMAIN.TLD 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013

Thanks,
V.V.

4
Polls / Re: Binary packages: which distribution is most demanded
« on: May 12, 2014, 06:25:36 pm »
Hi,

There is a port for 1.2.13 in preparation.
Check http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/188406

I have used it.
I have had to delete "NO_PACKAGE=     yes" line from the Makefile in order to build and install.
It build and install ok, the server is stable.

I have problem with the agent (1.2.13). For different parameters the agent return INTERNAL_ERROR.
An agent log (debug level 9) look like this:

[11-May-2014 11:51:52.658] [DEBUG] [session:0] Received message CMD_GET_PARAMETER
[11-May-2014 11:51:52.659] [DEBUG] [session:0] Requesting parameter "Net.Interface.BytesIn(1)"
[11-May-2014 11:51:52.659] [DEBUG] [session:0] GetParameterValue(): result is 500 (INTERNAL_ERROR)
[11-May-2014 11:51:52.659] [DEBUG] [session:0] Sending message CMD_REQUEST_COMPLETED (size 32)
[11-May-2014 11:51:52.661] [DEBUG] [session:0] Message dump:
  ** 004100000000005800002E8000000001
  ** 00000055010000000000003600530079
  ** 007300740065006D002E004D0065006D
  ** 006F00720079002E0050006800790073
  ** 006900630061006C002E005500730065
  ** 0064000000650072
  ** code=0x0041 (CMD_GET_PARAMETER) flags=0x0000 id=11904 size=88 numFields=1
  ** [    85] STRING "System.Memory.Physical.Used"

[11-May-2014 11:51:52.661] [DEBUG] [session:0] Received message CMD_GET_PARAMETER
[11-May-2014 11:51:52.661] [DEBUG] [session:0] Requesting parameter "System.Memory.Physical.Used"
[11-May-2014 11:51:52.662] [DEBUG] [session:0] GetParameterValue(): result is 0 (SUCCESS)
[11-May-2014 11:51:52.662] [DEBUG] [session:0] Sending message CMD_REQUEST_COMPLETED (size 64)
[11-May-2014 11:51:52.663] [DEBUG] [session:0] Message dump:
  ** 004100000000004800002E8100000001
  ** 00000055010000000000002600530079
  ** 007300740065006D002E004300500055
  ** 002E004C006F00610064004100760067
  ** 0035320033003900
  ** code=0x0041 (CMD_GET_PARAMETER) flags=0x0000 id=11905 size=72 numFields=1

Maybe somebody have a suggestion.

Thanks,
V.V.

Pages: [1]