[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 632
  • Last Modified:

Websphere service not starting cleanly on reboot

Hey everyone,

We currently have a machine in our environment that's running Server 2003 with IBM websphere installed.  We recently found that when rebooting the server, the websphere services "spin" for about 30 mins and never actually start (they are set to automatic).  This ultimately requires someone to go in and cycle the service manually, at which point they come up fine.  We've looked at the WAS logs, ran procmon against Java, etc and can't come up with a cause.  

I know there A LOT of variables that can come into play here, but I was just wondering if you guys might know anything in general that might be causing this /where I can concentrate troubleshooting?

Thanks!
0
blinkme323
Asked:
blinkme323
  • 3
  • 3
2 Solutions
 
HonorGodCommented:
Does anything special have to be done to get the services started?

Might the log files be filling the allocated space or something?

Do you have a Deployment Manager environment?

What kind of servers are services?
- Deployment Manager?
- Node agent(s)?
- Application Server(s)?
0
 
blinkme323Author Commented:
This particular setup does not utilize DMGR, these are application services.  The services run as designed at all other times, it's just these issues at reboot that we are having problems with.
0
 
HonorGodCommented:
Is it a specific (predictable) server that doesn't start at reboot, or a random one?
Does the start hang, or fail?

What version of WebSphere is being used?

What's the output of versionInfo command script that is found in the AppServe\bin directory?
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
blinkme323Author Commented:
Thanks for the suggestions so far, but I finally found what the issue was.  In the websphere settings, "Support referrals to other LDAP servers " was set to "follow" instead of "ignore".  I made the change, recycled the services and rebooted without issue.
0
 
HonorGodCommented:
Excellent.  I'm glad to hear that you identified the issue.

More importantly, I appreciate your sharing the solution with us!

Thanks
0
 
blinkme323Author Commented:
Found solution through own investigation.  All help was appreciated though.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now