Hi Paul, Many thanks for these details. We had the problem when using /etc/init.d as well as after switching to /etc/init which allows a crashed wotaskd to auto restart. This startup problem isn't a crashing wotaskd, but I suspect a wotaskd that fails to get the network info it needs on the processes it started up and despite starting them, doesn't know it has, though I could be speculating too much.
Can I ask if you have a hostname configured on your server(s)? There is something on it here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-hostname.html As there is some talk in a forum on needing a DNS-locatable host to avoid the getnameinfo failed error. Thanks John On 8 Aug 2014, at 11:36, Paul Hoadley <pa...@logicsquad.net> wrote: > Hi John, > > On 8 Aug 2014, at 5:48 pm, John Pollard <j...@pollardweb.com> wrote: > >> Any thoughts on whether this getnameinfo failed might relate to the WO >> startup issues? The failure only happens occasionally it seems, but does >> seem to happen in clumps. > > We've been running WebObjects apps with wotaskd+JavaMonitor on Amazon Linux > for several years. I didn't jump on your thread from mid-July ("Auto restart > of wotaskd in Linux") only because we don't have a solution to that specific > problem—admittedly our deployment setup is fairly modest, but I've never seen > a crashed wotaskd (that I can recall). I tested it at the time, and > certainly killing wotaskd on a fresh appserver instance didn't re-spawn a new > one—it's just not a problem we've needed to solve, so I had nothing to add > for you. > > Our appservers certainly do survive reboots, though, so I'll described the > setup briefly here. (We only run "standalone" appservers where JavaMonitor > monitors wotaskd on the same host, nothing with app instances distributed > over more than one host.) We have a very simple initialisation script (with > '# chkconfig: - 90 20') that starts (and stops and restarts) wotaskd and > JavaMonitor (minimally modified from the script that was posted to the > mailing list years ago, and is probably still available via the wiki) > installed as /etc/init.d/webobjects, and at appserver creation time we run: > > chkconfig --add webobjects > chkconfig webobjects on > /etc/init.d/webobjects start > > And that's pretty much it. That should start wotaskd+JavaMonitor at > appserver creation time, and re-start it on reboot. Any app instances > running prior to reboot should also be re-started after reboot. > > > -- > Paul Hoadley > http://logicsquad.net/ > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-deploy/jpollard%40inrax.com > > This email sent to jpoll...@inrax.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
