• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: javamonitor and wotaskd won't start after os x updates
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: javamonitor and wotaskd won't start after os x updates

  • Subject: Re: javamonitor and wotaskd won't start after os x updates
  • From: Elizabeth Lynch <email@hidden>
  • Date: Mon, 01 Jul 2013 23:41:41 +0100
Hi

I have followed email@hidden 's suggestion of installing the Wonder wotaskd and JavaMonitor, and this has solved the problem on our client's server.

You can download these from the jenkins site at:

http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild

After copying them to the correct location (I made sure to take a backup copy of the original Apple ones first), remove the quarantine bit for both apps:

xattr -d com.apple.quarantine wotaskd.woa

and set the permissions:

chown -R appserver wotaskd.woa

Then restart via launchctl or reboot the server.

This worked for me: I hope it does for you too.

Liz


On 1 Jul 2013, at 22:40, Bogdan Zlatanov <email@hidden> wrote:

Hi Greg,

On 1 Jul 2013, at 23:36, Greg Lappen wrote:

Thanks for the info Liz.  I did what you said, but when the monitor page opens in the browser and I try to start my app, it never starts.  Nothing relevant appears in the log files :(


Check the application permissions, especially the executable.


On Mon, Jul 1, 2013 at 5:20 PM, Elizabeth Lynch <email@hidden> wrote:
Hi

We have exactly the same problem: some Apple updates were applied yesterday on a client's Snow Leopard server (I don't know exactly what), and now wotaskd and JavaMonitor won't start automatically. We got the kCGErrorFailure message at one point: now I just see 'Exited with exit code (1)'.

Both start fine when started from Terminal, so for the moment I have got the site back running by starting the 2 apps from Terminal with:

        sudo -u appserver  /System/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd
and
        sudo -u appserver  /System/Library/WebObjects/JavaApplications/wotaskd.woa/JavaMonitor

But of course this is just a temporary 'fix' to keep the client's website up while we find the real solution.

I have tried setting permissions for /Library/LaunchDaemons/JavaMonitor.woa and wotaskd.woa to be owned by appserver:wheel and by appserver:appserverusr. This made no difference.

Liz

On 1 Jul 2013, at 21:03, Christoph Wick <email@hidden> wrote:

> Hi Greg,
>
> can you start WOMonitor manually? Try to execute
>
>       /System/Library/WebObjects/JavaApplications/JavaMonitor.woa/JavaMonitor
>
> (if you are using the original Apple WOMonitor, or the one from Wonder wherever you've installed it)
>
> Does the log (defined in your LaunchDaemon's com.apple.webobjects.womonitor.plist) tells you anything?
>
> C.U.CW
> --
> What are the three enemies of a programmer? Sunlight, oxygen, and the appalling roar of the birds.
>
> On 01.07.2013, at 21:09, Greg Lappen <email@hidden> wrote:
>
>> Hello,
>>
>> We have a WebObjects app running on a Snow Leopard Server.  Some OS X updates were applied recently, and now WebObjects javamontor, wotaskd, and hence our app are not starting up.
>>
>> I saw this error in /var/log/system.log:
>>
>> Suspicious setup: User "appserver" maps to user: _appserver
>>
>> I modified the LaunchAgent plist files so that the user and group name now have dashes in front of them and reloaded the files into launchd with launchctl.  The error I see now is this:
>>
>> kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
>>
>> This seems like some issue with java not being able to connect to the window server, but I was not able to find any solutions.  Does this look familiar to anyone?
>>
>> Much thanks,
>>
>> Greg
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >javamonitor and wotaskd won't start after os x updates (From: Greg Lappen <email@hidden>)
 >Re: javamonitor and wotaskd won't start after os x updates (From: Christoph Wick <email@hidden>)
 >Re: javamonitor and wotaskd won't start after os x updates (From: Elizabeth Lynch <email@hidden>)
 >Re: javamonitor and wotaskd won't start after os x updates (From: Greg Lappen <email@hidden>)
 >Re: javamonitor and wotaskd won't start after os x updates (From: Bogdan Zlatanov <email@hidden>)

  • Prev by Date: Re: javamonitor and wotaskd won't start after os x updates
  • Next by Date: Tomcat deployment and CSS images
  • Previous by thread: Re: javamonitor and wotaskd won't start after os x updates
  • Next by thread: Re: javamonitor and wotaskd won't start after os x updates
  • Index(es):
    • Date
    • Thread