Hi!
About your laptop problem - I see two possible reasons: maybe your
network interface comes up too slow, so agent is unable to bind to
listening address (should't be the case, but just may be...)? Or agent
service starts prior to firewall service? You can try to add
"StartupDelay" parameter to agent's configuration to delay agent's
networking initialization. For example, to add 30 seconds delay, add
StartupDelay = 30
Another possible issue that just comes into my mind is that agent might
be unable to resolve the name of your management server at start time,
thus rejecting all incoming connections as unauthorized. You can try to
replace management server name with IP address in MasterServers
parameter.
Win98 - by default, agent writes output to system event log. Try to set
event logging to file. You will see debug output in the log file, as
well as on the screen.
Best regards,
Victor
-----Original Message-----
From: Sam Deforest [mailto:netxms.srv_at_walpolewood.net]
Sent: Tuesday, 20 June, 2006 17:32
To: NetXMS Users
Subject: Re: [netxms-users] Not connecting to agent
Victor Kirhenshtein wrote:
> Hello!
>
> 1. Sounds very strange. Can you please check that:
> A. Agent service is up after workstation start (not set to Manual
> startup for example)? B. If you do a status poll from the console,
> what exact messages you see?
> C. Is there any records in agent's log file (or Windows Event Log)
after
> agent start and before you manually restart service?
>
> Also, if possible, can you send me agent's configuration file?
>
> 2. To send an email when specific host is down, do the following:
>
> A. Create new action (View -> Control Panel -> Actions -> New). B. Set
> action type to "Send e-mail" C. Enter recipient e-mail address
> D. In subject and message text fields, enter desired email text. You
can
> also use macros described here:
> http://www.netxms.org/documentation/macros.shtml
> E. Close action editor
> F. Open event processing policy (View -> Control Panel -> Event
> Processing Policy)
> G. Add new rule and add desired host (or hosts) to source field, event
> SYS_NODE_DOWN to event field, and in action field, add your newly
> created action. Please note that you can also use subnets or
containers
> in the source field, which means that all hosts belonging to that
subnet
> (container) will be matched.
> H. New processing policy will apply as soon as you close policy editor
> or save your changes.
>
>
> 3. I have tested agent on Win98, but not it's last version. Maybe
> something is broken. Can you please try to run agent in debug mode
> (nxagentd.exe -D), try to poll node with the agent, and send me an
> output?
>
> Hope that helps!
>
> Best regards,
> Victor
>
>
> -----Original Message-----
> From: Sam Deforest [mailto:netxms.srv_at_walpolewood.net]
> Sent: Monday, 19 June, 2006 20:58
> To: NetXMS Users
> Subject: [netxms-users] Not connecting to agent
>
>
>
> Hi all...it's been awhile, and finally I am testing a full
> implementation of NetXMS. I am planning to monitor, workstations, and
> servers. All of the devices are on our own private network, with all
of
>
> our locations spread out on the East Coast US. So far things have
> gone
> very well, but with all things some issues are popping up. Any
insight
> in the following issues would be helpful.
>
> 1. If I restart a windows workstation (host) running XP-Pro, the
> NetXMS
> server cannot connect to the agent. I get the "Error Getting Agent's
> Configuration File:Communication Failure". The wakeup tool does not
> work either, as well as polling for status or configuration. I have
> found that if I restart the NetXMS Agent service on the workstation,
> THEN poll for status, it will come back up.......any ideas on this
one?
>
> 2. Is there a message (email event) variable that will fire to the
> recipient if a host is down?...using the internal network (default for
> new host) DCI does not pass any variables to the event. There are
some
> hosts I just want to know if they are up or down.
>
> 3. Im finding that the agent does not play well with Win98 SE. Or at
> least my win98 box. I cannot connect to that agent as well.
>
> Any tips would be appreciated.
> Regards,
> Sam
>
>
>
Victor,
Thanks for the response....I have attached the following screen shots
for your review. I started up this morning one of the workstations
(mine actually) and the server would not connect, the screen shots are
of when I try to "Poll Status", "Poll Configuration", and "Edit Agent
Configuration". The Windows Event viewer, shows only agent start and
stops...as well as the sub-agents. If I restart the agent service on
the workstation and then poll, things seem to pop up just fine. Here
are the lines from the config file.
>>start file
#
# NetXMS agent configuration file
# Created by agent installer at Fri Jun 16 15:47:55 2006
#
MasterServers = walp-admin1
LogFile = {syslog}
FileStore = C:\NetXMS\var
SubAgent = ping.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
<<end file
Of course i got this after I restarted the service. I am going to see
If i can make the Netxms agent service start last. The odd thing is,
It's only occuring on my laptop....my other workstations seem to be
starting fine and visible to the server as soon as they are booted.
This may be an isolated case.
As far as the win98 goes...where would the debug info get logged?
Thanks,
Sam
Received on Tue Jun 20 2006 - 21:40:47 EEST
This archive was generated by hypermail 2.2.0 : Tue Jun 20 2006 - 21:50:32 EEST