| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 06/02/2010 09:31:35
|
rneuschul
SysAider
Joined: 06/02/2010
Messages: 5
Offline
|
We're testing SysAid for a client who run a distributed business: several locations, several LANs and several 2003 servers.
On two of the lans [installed on a server] Remote Discovery works perfectly, Agents have been deployed and RDS is reporting assets back to the SysAid server correctly: reporting and monitoring of assets works entirely as expected and agents can be undeployed or deployed as required, and SNMP scans run as expected.
On a third lan [on a server] RDS is installed, but any attempt to start the service immediately reports that the service has stopped and - in normal unhelpful MS fashion - tells me that "some services do start and stop like this". There are no useful entries in Windows Event Logs.
In %SYSTEMROOT%\Program Files\SysAidRemoteDiscovery\root\WEB-INF\logs there is no log file.
In %SYSTEMROOT%\Program Files\SysAidRemoteDiscovery\wrapper the wrapper log shows
WrapperSimpleApp: Unable to locate the class com.ilient.snmp.SnmpAgentService: java.lang.UnsupportedClassVersionError: com/ilient/snmp/SnmpAgentService (Unsupported major.minor version 49.0)
followed by a line that says "wrapper stopped"
The URL to which the RDS is pointing is correct. The other config details for the service are correct and match those on the other remote lans.
I'm completely stumped by this: I can't see why several RDS services should work and one fail.
Research on the Java wrapper issue isn't especially helpful.
Any pointers that would help fix this?
|
|
|
06/02/2010 14:05:23
|
SBIT
Super SysAider
Joined: 03/06/2009
Messages: 62
Location: Calgary
Offline
|
Hi rneuschul,
This might be related to a known DNS service issue, you can get a quick over-view here:
http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx
I wouldn't recommend changing any ports via the registry as they suggest at this stage though. Try the simple fix first, stop the DNS service, start the service that won't start, then start the DNS service.
See if that helps.
|
|
|
06/02/2010 19:17:31
|
rneuschul
SysAider
Joined: 06/02/2010
Messages: 5
Offline
|
Thanks for the thoughts.
It's not one of the DNS/UDP issues your link describes and all the other services mentioned in those MS KBs such as IPSEC or IAS are running perfectly normally. Have tested in various ways, including stopping DNS and attempting to start SysAid RDS as you suggest Makes no difference.
Stopping the TCPIP/Netbios helper service allows RDS to take a little bit longer [10 secs instead of 1-2 secs] to decide it isn't going to run, but still not long enough to generate any kind of RDS or System Event log.
Had, as a last resort, also tried altering the port values as discussed in the article you mention, with no change in behaviour. Have now set these values back to default and restarted the machine.
I am, officially, stumped.
|
|
|
06/02/2010 20:20:55
|
rneuschul
SysAider
Joined: 06/02/2010
Messages: 5
Offline
|
Further information:
Having done an extensive search I discover there are two other JRE installations on this server - one for the Dell DRAC Lights-Out Console and one for the APC UPS management tools. Based solely on file dates/sizes, each of these appears to use a different version of JRE to each other, and each is also different to the version installed with SysAid RDS.
Stopping both of the associated APC services and the DRAC Console Management service allows Sysaid RDS to start and work fine. Restarting the APC and DRAC services and SysAid keeps running, and reports in correctly to the remote SysAid server.
However if either the Dell DRAC Console service or the APC UPS services are running BEFORE Sysaid RDS starts then Sysaid RDS will not start. Clearly, there's a conflict somewhere, but I'm not sure how to resolve this - I'm reluctant to mess with either the APC UPS or DRAC Console service configurations since these are mission-critical.
One could alter the dependency order to ensure the RDS service starts before the other services, but again, I'm reluctant to do this without some definitive feedback/information from the SysAid team.
|
|
|
07/02/2010 21:56:07
|
Obelix
SysAid Wiz
Joined: 12/06/2008
Messages: 887
Offline
|
@rneuschul...
You seemed to have nailed the problem.
There are two ways an overlaping service in a single server could disrupt each other :
They are fighting for processor thread (ports, specific address in memories... etc).
or
They are fighting for resources (processor time, traffic... etc).
From your description I would guess it's the second one that's happening. Fighting over processor threads almost certain would trigger a blue screen.
Now APC and DRAC are device to server kinda thing, no ? They got no direct communication to clients. So... an alternative solution would be to group them on their own network. Most of the servers now got two nics anyway.
|
That is not a bug, it's a feature...
When everything else fail try SysAid Wiki by Techguy |
|
|
08/02/2010 06:51:17
|
rneuschul
SysAider
Joined: 06/02/2010
Messages: 5
Offline
|
Hmn, no blue screens so far, just a simple failure of the service to start and keep on running, but my conclusion from watching what's going on using SysInternals ProcMon and other tools is that it is indeed a conflict of versions and paths rather than a conflict over resources. The RDS service can't find the correct java classes when it attempts to start if another JRE service class is already running.
Given that the reverse is not true: i.e. that the APC and DRAC services have no difficulty finding their classes and objects if another JRE service is already running at the time they startup this hints at a possible coding problem in the SysAid JRE implementation - either a JRE version dependency or something else. Not conclusive, but certainly an indicator.
We've determined that we can safely remove the Dell DRAC console since we have direct telnet capability to the lights out port, which removes one possible source of conflict, but the APC services are another matter - we cannot remove these; we've asked APC if they have a more up to date version of their console [this one is 4 years old], but I won't hold my breath.
If worse comes to worst I'll adjust the load-order dependencies for each service to ensure that Sysaid RDS starts first, but it's not the most elegant solution, and with a cpu/os platform independent coding base such as java it really shouldn't be necessary.
|
|
|
18/02/2010 02:08:34
|
Lior
SysAid R&D
Joined: 03/01/2008
Messages: 187
Offline
|
The problem is due to for version 49.0 Jdk 1.5 or higher is required
Please take a look at the following links:
http://forums.sun.com/thread.jspa?threadID=736596
http://www.artima.com/forums/flat.jsp?forum=1&thread=108274
This message was edited 1 time. Last update was at 18/02/2010 02:10:57
|
|
|
04/03/2010 11:15:04
|
rneuschul
SysAider
Joined: 06/02/2010
Messages: 5
Offline
|
Sorry, but no cigar.
System is fully up to date running Java 6 Update 18 - version info 6.0.180 - which is required in order to run latest firefox as well as other JRE/Tomcat applications - and update is enabled and notifies us whenever a new version is available.
|
|
|
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
![[ICQ]](/Sysforums/templates/default/images/icon_icq_add.gif){kind=icon}
