Re: Config problem - monitor trying to launch monitor....

Hello Mike

> Things still aren't going smoothly here. I've followed your instructions 
> to the letter (well, apart from adding the s onto WOServices in 
> places...), and afaics wotaskd isn't starting automagically. Performing 
> a manual start of wotaskd makes one of the two apps I'm wanting start 
> fine, the other has problems - it basically never ends the launch 
> process, and dies repeatedly. I guess there's something wrong with that 
> app.

...and so do I.

Have a look at the logfile, or try starting the app by copying all 
parameters from the apps instance detail view to the commandline (except 
-nsprojectsearchpath() ).

> A few things I'm thinking I possibly didn't do correctly:
> - When copying, I used the cp command. It seems to have left at @ symbol 
> after WOServices in /etc/init.d - does this matter?

I guess this is because of your command (or your shells environment 
settings): ls -F classifies the files by appending symbols and the @ 
stands for a symbolic link (see 'man ls' for more details). Maybe you 
have defined a alias for ls?

Though /etc/init.d/WOServices could even be a symbolic to the script in 
$NEXT_ROOT, I'd suggest to copy it.

> - I didn't initially know how to make it executable, so left that until 
> the end. I then ran chmod a-x WOServices - correct?

No, chmod a+x WOServices, or better chmod 0744 /etc/init.d/WOServices. 
This file should belong to root.

> Other than that, I don't know why things aren't running smoothly. I'm 
> still having the problems occasionally in Monitor, but on the whole 
> that's running smoothly. I'm not sure why the second app isn't working 
> smoothly, but am guessing it's not configured right somewhere (it works 
> fine on my local system when the database connection's been changed, but 
> as I said above simply refuses to launch properly on the actual server...).

have a look at your logfiles for exceptions

> Can you / anyone help at all with this?

regards

Thomas