vray4maya_log.txt

[isoparmesan]

Where do the vray logs show up now? In 2.4 I could see them at /tmp/vray4maya_log.txt. With 3.1/Maya 2016 that log file no longer appears.

[vlado]

There are two environment variables, VRAY_FOR_MAYA_LOG_FILE_PATH and VRAY_FOR_MAYA_LOG_FILE_NAME that can change the path/name of that file. Are you sure you are not using one of them?

Best regards,
Vlado

[isoparmesan]

I don't see those variables set in /etc/profile. Is there another place they would be?

EDIT: They are also not present in /etc/launchd.conf

[vlado]

Are you on OS X? Which version?

Best regards,
Vlado

[isoparmesan]

My main workstation is on 10.10.4. I have render nodes and a render manager on 10.9.x and the logs don't show there either.

[isoparmesan]

I was able to get the log to show up again by adding a .plist to /Library/LaunchDaemons that points to the log location (adding VRAY_FOR_MAYA_LOG_FILE_PATH to /etc/profile alone didn't do it). I got the idea from a support ticket I had to resolve an issue with back burner permissions/vray licensing.

I did have to manually set the permissions/owner/group for the .plist files and then restart.

contents of .plist file should be

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<!-- This file was generated by the CHAOS GROUP installer. Please do NOT edit the file by yourself. -->
<plist version="1.0">
        <dict>
                <key>Label</key>
                <string>setenv.chaos_group.VRAY_FOR_MAYA_LOG_FILE_PATH</string>
                <key>ProgramArguments</key>
                <array>
                        <string>/bin/launchctl</string>
                        <string>setenv</string>
                        <string>VRAY_FOR_MAYA_LOG_FILE_PATH</string>
                        <string>/tmp</string>
                </array>
                <key>RunAtLoad</key>
                <true/>
                <key>ServiceIPC</key>
                <false/>
        </dict>
</plist>

if you have to do this and you aren't sure how to edit file permissions, there are two commands you need.

sudo chown root:wheel /Library/LaunchDaemons/*plist file you created*
sudo chmod 644 /Library/LaunchDaemons/*plist file you created*

[vlado]

I'm guessing that /tmp was not writable... I was going to suggest redirecting it to a writable location.

Best regards,
Vlado