Hi All,
So I have one last hurdle. All servers are working fine but one. One server doesn't seem to have wotaskd working at all. When I did an initial install a while back, it did work but now I can't access it even if I am running everything on localhost. Monitor will start but even though wotaskd
If I do a ps ax |grep java, it used to show wotaskd running but now it does not even though launctl indicates that it is loaded. I can't communicate with it at all. No telnet. Monitor can't talk to it. I tried a reinstall to no avail. Thoughts?
Here is the properties file
# Properties file for wotaskd
# Overrides the JavaWebObjects.framework Properties
# Changes to this file will be overwritten when you update wotaskd.
# Consider storing customizations in: /etc/WebObjects/wotaskd/Properties (or in the launchd file)
WOHost=localhost
#WOHost=192.168.169.16
# Uncomment this to get some basic logging (like lifebeats from instances), probably to the file: /Library/WebObjects/Logs/wotaskd.log
#_DeploymentDebugging=true
WOAutoOpenInBrowser=false
WODebuggingEnabled=false
WODirectConnectEnabled=true
WOCachingEnabled=true
WOPort=1085
er.extensions.ERXMessageEncoding.Enabled=false
# deployment defaults
WOMonitorEnabled=false
WOLifebeatDestinationPort=1085
WOLifebeatEnabled=false
# Sets the IP address that the wotaskd process listens to for multicast requests from the HTTP adaptor.
WOMulticastAddress=239.128.14.2
# Determines whether the wotaskd process responds to multicast queries from the HTTP adaptor.
WORespondsToMulticastQuery=false
# Determines whether the wotaskd process generates an HTTP adaptor configuration file.
WOSavesAdaptorConfiguration=false
# Used to determine the number of seconds that the wotaskd process waits without receiving any status messages
# from an instance before considering it dead. It species a multiplier against WOLifebeatInterval.
# If WOLifebeatInterval is 30, a wotaskd process waits 120 seconds from the last status message before
# determining that an instance is dead.
WOAssumeApplicationIsDeadMultiplier=4
# Controls whether wotaskd should start instances using a system-specific launcher;
# this allows for starting applications in the background, as well as circumventing
# Windows-specific issues with launch output.
WOShouldUseSpawn=true
# If an app instance has been told to 1) "stop" or 2) "refuse new sessions" and it does not stop,
# then it can be forcefully terminated after some time period if WOTaskd.forceQuitTaskEnabled is true
#WOTaskd.forceQuitTaskEnabled=false
# If an app instance has been told to "refuse new sessions" and it does not stop,
# then it can be forcefully terminated after this number of retries.
#WOTaskd.refuseNumRetries=3
# If WOTaskd.forceQuitTaskEnabled is true, setup a task to check the instance.
# If it still doesn't die, then force a QUIT command when the timer elapses.
# If the app was told to "stop" and does not stop, then it will be forcefully stopped after the killTimeout elapses.
# If the app was told to "refuse new sessions" and does not stop, then it will be forcefully stopped after
# (killTimeout + (refuseNumRetries-1 * killTimeout)) elapses.
# The value is specified in milliseconds. The minimum is 60000 (60 seconds).
#WOTaskd.killTimeout=120000
# The number of milliseconds before a timeout occurs for requests sent from WOTaskD to WOApplication instances.
#WOTaskd.receiveTimeout=5000
# The TCP port on which the built-in SSH/SCP server will run on
er.wotaskd.sshd.port=6022
# Enable or disable the built-in SSH/SCP server
er.wotaskd.sshd.enabled=false
log4j.rootCategory=INFO, A1
# A1 is set to be a FileAppender which outputs to System.out.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
# A1 uses PatternLayout.
log4j.appender.A1.layout=er.extensions.logging.ERXPatternLayout
log4j.appender.A1.layout.ConversionPattern=%d %-5p %V{u/f} [%t] %C{2} (%F:%L) - %m%n
So I have one last hurdle. All servers are working fine but one. One server doesn't seem to have wotaskd working at all. When I did an initial install a while back, it did work but now I can't access it even if I am running everything on localhost. Monitor will start but even though wotaskd
If I do a ps ax |grep java, it used to show wotaskd running but now it does not even though launctl indicates that it is loaded. I can't communicate with it at all. No telnet. Monitor can't talk to it. I tried a reinstall to no avail. Thoughts?
Here is the properties file
# Properties file for wotaskd
# Overrides the JavaWebObjects.framework Properties
# Changes to this file will be overwritten when you update wotaskd.
# Consider storing customizations in: /etc/WebObjects/wotaskd/Properties (or in the launchd file)
WOHost=localhost
#WOHost=192.168.169.16
# Uncomment this to get some basic logging (like lifebeats from instances), probably to the file: /Library/WebObjects/Logs/wotaskd.log
#_DeploymentDebugging=true
WOAutoOpenInBrowser=false
WODebuggingEnabled=false
WODirectConnectEnabled=true
WOCachingEnabled=true
WOPort=1085
er.extensions.ERXMessageEncoding.Enabled=false
# deployment defaults
WOMonitorEnabled=false
WOLifebeatDestinationPort=1085
WOLifebeatEnabled=false
# Sets the IP address that the wotaskd process listens to for multicast requests from the HTTP adaptor.
WOMulticastAddress=239.128.14.2
# Determines whether the wotaskd process responds to multicast queries from the HTTP adaptor.
WORespondsToMulticastQuery=false
# Determines whether the wotaskd process generates an HTTP adaptor configuration file.
WOSavesAdaptorConfiguration=false
# Used to determine the number of seconds that the wotaskd process waits without receiving any status messages
# from an instance before considering it dead. It species a multiplier against WOLifebeatInterval.
# If WOLifebeatInterval is 30, a wotaskd process waits 120 seconds from the last status message before
# determining that an instance is dead.
WOAssumeApplicationIsDeadMultiplier=4
# Controls whether wotaskd should start instances using a system-specific launcher;
# this allows for starting applications in the background, as well as circumventing
# Windows-specific issues with launch output.
WOShouldUseSpawn=true
# If an app instance has been told to 1) "stop" or 2) "refuse new sessions" and it does not stop,
# then it can be forcefully terminated after some time period if WOTaskd.forceQuitTaskEnabled is true
#WOTaskd.forceQuitTaskEnabled=false
# If an app instance has been told to "refuse new sessions" and it does not stop,
# then it can be forcefully terminated after this number of retries.
#WOTaskd.refuseNumRetries=3
# If WOTaskd.forceQuitTaskEnabled is true, setup a task to check the instance.
# If it still doesn't die, then force a QUIT command when the timer elapses.
# If the app was told to "stop" and does not stop, then it will be forcefully stopped after the killTimeout elapses.
# If the app was told to "refuse new sessions" and does not stop, then it will be forcefully stopped after
# (killTimeout + (refuseNumRetries-1 * killTimeout)) elapses.
# The value is specified in milliseconds. The minimum is 60000 (60 seconds).
#WOTaskd.killTimeout=120000
# The number of milliseconds before a timeout occurs for requests sent from WOTaskD to WOApplication instances.
#WOTaskd.receiveTimeout=5000
# The TCP port on which the built-in SSH/SCP server will run on
er.wotaskd.sshd.port=6022
# Enable or disable the built-in SSH/SCP server
er.wotaskd.sshd.enabled=false
log4j.rootCategory=INFO, A1
# A1 is set to be a FileAppender which outputs to System.out.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
# A1 uses PatternLayout.
log4j.appender.A1.layout=er.extensions.logging.ERXPatternLayout
log4j.appender.A1.layout.ConversionPattern=%d %-5p %V{u/f} [%t] %C{2} (%F:%L) - %m%n
-----Original Message-----
From: ch...@global-village.net
Sent: Tue, 12 Aug 2014 18:39:33 +0000
To: dtisd...@inbox.com, webobjects-deploy@lists.apple.com
Subject: Re: wotaskd only accessible from localhostIt’s purpose is to avoid problems with mismatching and incorrect host names / addresses.
On 2014-08-12, 11:35 AM, "David Tisdell" wrote:
I had wondered about that but was reluctant to try as i wasn't 100% sure of the purpose of that parameter
-----Original Message-----
From: ch...@global-village.net
Sent: Tue, 12 Aug 2014 18:21:48 +0000
To: dtisd...@inbox.com, webobjects-deploy@lists.apple.com
Subject: Re: wotaskd only accessible from localhost
Add WOHost=xxxxTo the Properties file or the launchd plist args
On 2014-08-12, 11:17 AM, "David Tisdell" wrote:
Can I bind wotaskd to a specific IP address? That might solve the issue
-----Original Message-----
From: dtisd...@inbox.com
Sent: Tue, 12 Aug 2014 10:08:39 -0800
To: webobjects-deploy@lists.apple.com
Subject: Re: wotaskd only accessible from localhost
I am having trouble disabling IP V6. In Mavericks, you can't do it in the gui anymore.but when I run it, I get this error:
I found this direction in several places
networksetup -setv6off Ethernet
Ethernet is not a recognized network service.
** Error: The parameters were not valid.
I also tried specifying en0 and en1 with the same error
Dave
-----Original Message-----
From: webobje...@berkling.us
Sent: Tue, 12 Aug 2014 10:56:45 -0700
To: webobjects-deploy@lists.apple.com
Subject: Re: wotaskd only accessible from localhost
On Aug 12, 2014, at 10:27 AM, David Tisdell <penguin...@yahoo.com> wrote:
Looks like it is using IP V6 and not v4. That could be an issue. I will see if I can disable IP v6
Yup. You'll happier once there is only one address for each host. It you have to you can use the WOHost flag/property for JavaMonitor, wotaskd and all app instances. That makes sure all parts are bound to explicit sockets.
Personally I like to have a simple private network for my instance nodes and then have a public IP address for the web server/head node. Alternatively you can use NAT to the private network head node. But this requires a larger infrastructure.
kib
Free Online Photosharing - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!
Free 3D Earth Screensaver
Watch the Earth right on your desktop! Check it out at www.inbox.com/earth
Free 3D Earth Screensaver
Watch the Earth right on your desktop! Check it out at www.inbox.com/earth
_______________________________________________ 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
