How to make render client write logs…

Viewing 5 posts - 1 through 5 (of 5 total)
  • Posted in: Linux
  • 18th May 2007 at 10:44 am #14184

    We recently moved our dispatcher and render clients into Linux environments(centos 5), but none of the render clients writes logs into specified folder, why? is it not available in linux?
    we’ve specified all the settings we can find as following:

    dispatcher.conf:
    rc_log_cmdline = 1
    rc_log_retcode = 1
    renderclient_log_format = %job_name%.%job_id%.%chunk_id%.%hostname%.%timestamp%.txt

    rc.conf:
    log_folder = /var/log/muster
    log_folder_share = \%*hostname*%muster_logs

    Any help will be appreciated!

    22nd May 2007 at 12:11 am #14662

    Check the renderclient.log file. At the beginning of each packet, there’s always a path dumped with the full file pathname of the log.

    23rd May 2007 at 9:08 am #14668

    Do you mean that I can find the full pathname of packets’ log files in the file “renderclient.log”?
    but I can’t find any logs’ path infomation from the my renderclient.log,
    I’m just confused what does the following settings do:
    ############################
    dispatcher.conf:
    rc_log_cmdline = 1
    rc_log_retcode = 1
    renderclient_log_format = %job_name%.%job_id%.%chunk_id%.%hostname%.%timestamp%.txt

    rc.conf:
    log_folder = /var/log/muster
    log_folder_share = \%*hostname*%muster_logs
    ############################

    the following is my renderclient.log:
    ########################################################
    23/05/2007 15:41:50 – [Renderclient] Virtual Vertex Muster Renderclient service
    23/05/2007 15:41:50 – [Renderclient] Version 5.12 build 1456 compiled Apr 12 2007 14:11:39 for X86 32BIT processors
    23/05/2007 15:41:50 – [Core] Bringing up 1 instances
    23/05/2007 15:41:50 – [Core] Spawning controlling threads
    23/05/2007 15:41:50 – [Core] Renderclient listening for management connections on port 7685
    23/05/2007 15:41:50 – [Core] Renderclient broadcasting presence on port 7685
    23/05/2007 15:41:54 – [1] Attempting connection to Dispatcher service on 172.168.20.52:7680
    23/05/2007 15:41:54 – [1] Connection on 172.168.20.52:7680 successfully
    23/05/2007 15:41:54 – [1] Template [UID:1] Maya Sw received
    23/05/2007 15:41:55 – [1] Template [UID:2] Maya Mr received
    23/05/2007 15:41:55 – [1] Template [UID:3] Maya Hw received
    23/05/2007 15:41:55 – [1] Template [UID:4] Maya Vr received
    23/05/2007 15:41:56 – [1] Template [UID:5] Maya Sw-Fs received
    23/05/2007 15:41:56 – [1] Template [UID:6] Maya Mr-Fs received
    23/05/2007 15:41:56 – [1] Template [UID:7] Maya Layer received
    23/05/2007 15:41:57 – [1] Template [UID:8] Maya Rman received
    23/05/2007 15:41:57 – [1] Template [UID:9] Maya Rman-Fs received
    23/05/2007 15:41:57 – [1] Template [UID:10] Maya Turtle received
    23/05/2007 15:41:57 – [1] Template [UID:11] Lightwave received
    23/05/2007 15:41:57 – [1] Template [UID:12] Lightwave-fs received
    23/05/2007 15:41:58 – [1] Template [UID:13] Xsi received
    23/05/2007 15:41:59 – [1] Template [UID:14] Xsi-Fs received
    23/05/2007 15:41:59 – [1] Template [UID:15] Mr-Multifile received
    23/05/2007 15:42:00 – [1] Template [UID:16] Mr-Singlefile received
    23/05/2007 15:42:00 – [1] Template [UID:17] After Effects received
    23/05/2007 15:42:00 – [1] Template [UID:18] 3DS Max received
    23/05/2007 15:42:01 – [1] Template [UID:19] Shake received
    23/05/2007 15:42:01 – [1] Template [UID:20] Combustion received
    23/05/2007 15:42:01 – [1] Template [UID:21] Digital Fusion received
    23/05/2007 15:42:01 – [1] Template [UID:22] Cinema 4D received
    23/05/2007 15:42:01 – [1] Template [UID:23] Alias Studio received
    23/05/2007 15:42:01 – [1] Template [UID:24] Maya Cloth received
    23/05/2007 15:42:01 – [1] Template [UID:25] Digital Fusion 5.1+ received
    23/05/2007 15:42:02 – [1] Template [UID:27] Maya Turtle 4+ received
    23/05/2007 15:42:02 – [1] Loading templates preferences
    23/05/2007 15:42:02 – [1] Instance available for selection
    23/05/2007 15:42:13 – [1] Starting job executable /opt/maya8.5/maya8.5/bin/Render with commands: -r mr -v 4 -proj /home/twang/kwMayaAppDir/projects/default -s 7.000 -e 7.000 -b 1.000 -rfs 7 -rfb 1 /home/twang/kwMayaAppDir/projects/default/scenes/mrRollingCube48f.mb
    23/05/2007 15:42:18 – [1] Real job process running as PID 7164
    23/05/2007 15:42:26 – [1] Job process terminated with exit code 0
    23/05/2007 15:42:27 – [1] Starting job executable /opt/maya8.5/maya8.5/bin/Render with commands: -r mr -v 4 -proj /home/twang/kwMayaAppDir/projects/default -s 8.000 -e 8.000 -b 1.000 -rfs 8 -rfb 1 /home/twang/kwMayaAppDir/projects/default/scenes/mrRollingCube48f.mb
    23/05/2007 15:42:30 – [1] Real job process running as PID 7229
    23/05/2007 15:42:38 – [1] Job process terminated with exit code 0
    23/05/2007 15:42:38 – [1] Starting job executable /opt/maya8.5/maya8.5/bin/Render with commands: -r mr -v 4 -proj /home/twang/kwMayaAppDir/projects/default -s 9.000 -e 9.000 -b 1.000 -rfs 9 -rfb 1 /home/twang/kwMayaAppDir/projects/default/scenes/mrRollingCube48f.mb
    23/05/2007 15:42:42 – [1] Real job process running as PID 7286
    23/05/2007 15:42:50 – [1] Sending heartbeat to Dispatcher service
    23/05/2007 15:42:50 – [1] Job process terminated with exit code 0



    ########################################################

    25th May 2007 at 6:43 pm #14675

    You’re writing inside /var/log/muster. Be sure that the account that’s starting the renderclient is able to write into that folder or redirect the logs in another folder.

    Regards.

    Leonardo.

    28th May 2007 at 5:12 am #14677

    I updated it to 5.2, and the problem disappeared automatically…
    Thanks a lot for your reply!

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.