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

Hello again,

>> 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.
OK, this now just has a * next to it, so I'm thinking all is good there.

>> - 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.
Sorry - typo there. I ran chmod a+x, not a-x, before. I've now run 
chmod 0744 on it...

... and things still don't seem to be booting. I'm guessing that when 
it starts, I should be able to access wotaskd through 
:1085/cgi-bin/WebObjects/wotaskd.woa - but that isn't accessible. And 
none of the apps I've got set up are starting. All is good when I run 
wotaskd from the command line though... (is there a command that can be 
appended to ./wotaskd to keep it running after I exit the shell, at 
all?)

I'm thinking that it won't be a big problem if, just for now, it has to 
be manually started in the command line ... just as long as it stays 
running after I exit the shell.

>> 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
> 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() ).
ok, a few questions here:
a) where's the log files?
b) the problem seems to be when I start up more than one application at 
a time on the server. I get Failed to start Admin-1: 
java.io.IOException: Cannot allocate memory (that's through monitor) or 
Error occurred during initialization of VM /n Could not reserve enough 
space for object heap (through command line). Which seems odd, as we 
have 256MB of dedicated memory, with a max of 8GB (we're on a shared 
VPS server.) Any ideas how to get around this?

Many thanks,
Mike Peel