These are a little different. I don't have my full config to hand at
the moment, but from the
http://edocs.bea.com/wls/docs81/admi...onitoring.html

>>Node Manager Output—If you start a Managed Server with Node Manager,
>>you can access Node Manager output using Domain—>Server—>Remote Start
>>Output—>View Node Manager output

You need to look at the SavedLogsDirectory parameter in the
nodemanager.properties file. And you'll then find a folder created for
each of the managed servers underneath a NodeManagerLogs folder.

Http://edocs.bea.com/wls/docs81/admi...r.html#1146748

Once the managed server starts, they keep using the same log file, and
don't rotate them based on size or date like with the normal domain
logs - unless I'm missing something.

Pete

Will,

You're going to actually see three different types of logs when you use the
NM:

1. The Node Manager log files which contain NM specific entries.
2. The Managed Server log files which contain the managed server specific
info such as you're used to seeing from stdout, stderr when you start the
server from the command line. Also you'll find additional info such as the
server's PID, and copy of the server's configuration called
nodemanager.config
3. Node Manger client logs which reside on the admin server and contain
subdirectories for each managed server issued a NM command.

You won't see these last two log file types or their subdirectories until
you actually use the NM to start the managed servers. All of these logs
however, are stored in a parent subdirectory called NodeManagerLogs. By
default this directory is created in the directory where you called
startNodeManager[.cmd .sh] from. So if I ran . startNodeManager.sh from
mydomain then I would see

$BEA_HOME/user_projects/domains/mydomain/NodeManagerLogs

The easiest way I have found to deal with this is to ensure that
$WL_HOME/server/bin is in your PATH and simply call . startNodeManager.sh
from the directory you want the logs to be created in --of course with the
appropriate arguments or values in nodemanger.properties--

but remember the NM defaults to $WL_HOME/common/nodemanager so you may see
the logs under their initially.

//provide a follow up if any of that didn't make sense

~RU


"Will Hartung" wrote in message
news:3fff427c$1@newsgroups.bea.com...
> When you fire up the NodeManager, and start up managed servers from the
web
> console, where do the logs of the respective servers go? I couldn't seem
to
> find anything telling in my domain directory when I looked.
>
> Thanx!
>
> Regards,
>
> Will Hartung
> (willh@msoft.com)
>
>

Am I right in thinking though that when you use node manager, you don't
get the normal domain log rotation facilities - the server log just
gets bigger and bigger, When you stop the server a new log file will be
created and the previous log file will be kept?

Pete

Yeah Pete you're absolutely right the server logs aren't subject to normal
rotation. You will get kind of a funky rotation when you restart the NM it
creates new logs for each restart of the server storing the old ones under
the name .output.log_prev and creating a new
.output.log

"Pete" wrote in message
news:VA.00000029.029cc254@yahoo.co.uk...
> Am I right in thinking though that when you use node manager, you don't
> get the normal domain log rotation facilities - the server log just
> gets bigger and bigger, When you stop the server a new log file will be
> created and the previous log file will be kept?
>
> Pete
>