[Bf-viewport] 2.77 OGL requirement seems to break renderfarm job submission (possible?)

[Brecht Van Lommel]

Hi Adam,

It's unlikely this is related to the viewport, if you run blender with
-b it doesn't create a window or OpenGL context. This error indicates
an issue with Python, which was upgraded to version 3.5 in Blender
2.77:

Fatal Python error: Py_Initialize: can't initialize sys standard streams

It could be that you have another Python installation that is somehow
conflicting with Blender. The PYTHONPATH environment variable might
also have something to do with it, if it's set in one context but not
another.

Regards,
Brecht.



On Fri, May 13, 2016 at 8:34 PM, Mike Erwin <significant.bit at gmail.com> wrote:
> Hi Adam,
> Your interesting not about manual runs working *is* interesting. I'm not
> very familiar with Windows servers so bear with me...
>
> Do your render nodes have GPUs? The command string seems to suggest that. If
> so are they just used for CUDA/OpenCL and not OpenGL?
>
> In normal operation are the render nodes GUI-less and have no need for
> OpenGL or other display?
>
> During the successful manual run, something changes. Is simply "being there"
> enough to get it working? Meaning there is a display to draw to, a console
> to read from and write to, etc.
>
> Mike Erwin
> musician, naturalist, pixel pusher, hacker extraordinaire
>
> On Fri, May 13, 2016 at 1:35 PM, Adam Glick <adam at renderstorm.com> wrote:
>>
>> Greetings from www.renderstorm.com !
>>
>> This is *not* directly related to the viewport, but more related (*we
>> think*) to the new requirement in 2.77a for hardware-accelerated OGL and any
>> potential effect on spawning network rendering jobs in Windows.
>>
>> Our render farm queue manager executes blender.exe -b at the command line
>> using Windows "createProcess()" function.
>>
>> Here's what we're passing to the rendernodes :
>>
>> CreateProcessAsUser( token, NULL, commandToExecute, lpSA, NULL,
>> inheritHandles, CREATE_NEW_CONSOLE, NULL, NULL, &si, pi)
>>
>> commandToExecute typically looks something like this:
>>
>> ["C:\Program Files\Blender Foundation\Blender\blender.exe" -b
>> "\\DISKSTATION1\farm\SquidNetRenderFolder\sync\521450\87E82C8694\project\BMW1M
>> Mike Pangpu.blend" -x 1 -s 4 -e 4 -j 1 -F EXR --python-text
>> renderstorm_blender_0107.py -E CYCLES  -P "C:\Program Files
>> (x86)\SquidNetSoftware\SquidNet\plugins\\blender\squidnet_blender_gpu_render.py"
>> -o
>> \\Diskstation1\FusionIO_DS1\ProjectData\jobs\521450\6974A4\1AE094A25B\slices\slice-4\broken_277_agtest
>> -a -y]
>>
>>
>> This works great for 2.76b and previous builds.  But we get the following
>> errors back from all Blender 2.77 network jobs now  :
>>
>> "...
>> Fatal Python error: Py_Initialize: can't initialize sys standard streams
>>
>> OSError: [WinError 6] The handle is invalid
>> ...
>> "
>>
>> **Interesting note**  We can paste our full blender command string into
>> the Windows CMD shell on one of the rendernodes and manually run the job in
>> 2.77a with no errors at all!
>>
>>
>> Maybe there's something else in 2.77 that's breaking our process, but our
>> best guess is the new OGL implementation...
>>
>> Does anybody have any suggestions on how we might troubleshoot/remedy this
>> issue?
>>
>> Thanks in Advance!!
>>
>> Adam
>>
>>
>> --
>> Adam Glick,
>> VP, Pipeline Technology
>> 760--818-3668 (cell)
>> www.RenderStorm.com
>>
>> _______________________________________________
>> Bf-viewport mailing list
>> Bf-viewport at blender.org
>> https://lists.blender.org/mailman/listinfo/bf-viewport
>>
>
>
> _______________________________________________
> Bf-viewport mailing list
> Bf-viewport at blender.org
> https://lists.blender.org/mailman/listinfo/bf-viewport
>