Method server will not startup

rstav · ‎May 05, 2014

Windchillers,

I restarted our servers this weekend, as I do once a month, and now the method servers and the background method server will not start up.

They both keep timing out.

The servermanager log states unable to get server. I am not sure what I am missing.

Thanks
Rich

Mon 5/5/14 03:37:52: MethodServerMonitor: INFO : wt.server.manager.startup - Starting 3 additional MethodServer instances
Mon 5/5/14 03:37:52: MethodServerMonitor: INFO : wt.manager.ServerLauncher - Starting MethodServer
Mon 5/5/14 03:39:22: BackgroundMethodServerMonitor: ERROR : wt.manager.ServerManagerImpl - Start of BackgroundMethodServer timed out.
Mon 5/5/14 03:39:22: BackgroundMethodServerMonitor: ERROR : wt.server.manager.startup - Unable to start BackgroundMethodServer wt.util.WTRemoteException: Unable to get server; nested exception is:
Mon 5/5/14 03:39:22: BackgroundMethodServerMonitor: (wt.manager.managerResource/3) wt.util.WTException: Start of BackgroundMethodServer timed out.
Mon 5/5/14 03:39:52: BackgroundMethodServerMonitor: INFO : wt.server.manager.startup - Starting 1 additional BackgroundMethodServer instance
Mon 5/5/14 03:39:52: BackgroundMethodServerMonitor: INFO : wt.manager.ServerLauncher - Starting BackgroundMethodServer
Mon 5/5/14 03:40:52: MethodServerMonitor: ERROR : wt.manager.ServerManagerImpl - Start of MethodServer timed out.
Mon 5/5/14 03:40:52: MethodServerMonitor: ERROR : wt.server.manager.startup - Unable to start MethodServer wt.util.WTRemoteException: Unable to get server; nested exception is:
Mon 5/5/14 03:40:52: MethodServerMonitor: (wt.manager.managerResource/3) wt.util.WTException: Start of MethodServer timed out.
Mon 5/5/14 03:42:22: wt.jmx.core.SharedScheduledExecutor.worker: INFO : wt.summary.general - JVMName=8188@vikings, HeapMemoryUsage=162020832, NonHeapMemoryUsage=24308696, Uptime=1201203, ProcessCpuTime=6750000000, JITCTime=4011, GarbageCollectors=[MarkSweepCompact,ParNew], GCTime=[0,0], GCCount=[0,0], Classes=2518, Threads=14
Mon 5/5/14 03:42:52: BackgroundMethodServerMonitor: ERROR : wt.manager.ServerManagerImpl - Start of BackgroundMethodServer timed out.
Mon 5/5/14 03:42:52: BackgroundMethodServerMonitor: ERROR : wt.server.manager.startup - Unable to start BackgroundMethodServer wt.util.WTRemoteException: Unable to get server; nested exception is:
Mon 5/5/14 03:42:52: BackgroundMethodServerMonitor: (wt.manager.managerResource/3) wt.util.WTException: Start of BackgroundMethodServer timed out.
Mon 5/5/14 03:43:22: BackgroundMethodServerMonitor: INFO : wt.server.manager.startup - Starting 1 additional BackgroundMethodServer instance
Mon 5/5/14 03:43:22: BackgroundMethodServerMonitor: INFO : wt.manager.ServerLauncher - Starting BackgroundMethodServer

Richard Stavish
Pro/E System Administrator

[cid:image009.jpg@01CF6814.D76F3D60] [cid:image011.jpg@01CF6814.D76F3D60] <">http://www.linkedin.com/company/sargent-aerospace-&-defense> [cid:image012.jpg@01CF6814.D76F3D60] <">https://twitter.com/SargentAero>

E-Mail:
Office: Mobile:
Fax:

RStavish@sargentaerospace.com
520-744-1000 x4570
520-437-5811
520-744-7529

jessh · ‎May 05, 2014

This log only shows that your method servers (foreground and background)
aren't starting up (either at all or in a timely fashion).

You need to examine the method servers logs to actually delve into the
problem.

If there are no method server logs, then this points to the method
server not even getting far enough to produce logs (in which case there
are ways to launch a method server process directly from the
command-line to see what goes awry prior to logging being established).
I'd hope this is not occurring simply due to a server restart, though --
as this generally implies a serious misconfiguration (e.g. bad
command-line parameters, pointing the method server to a non-existant
Java executable or the like).