Author Topic: 1.6 DR  (Read 34175 times)

2017-03-28, 18:17:27
Reply #90

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging
So this is a problem on DR slaves? Is Master working properly?

Is complicated to answer...

I am in a very tight deadline and the Master workstation is not participating in these DR jobs. I have 2 DR slaves for this and I sent the Backburner Job to one of them which via DR is connected to the second one. Simple setup, nothing strange... But I don't know if my Master PC could give the same errors as I use it right now with IR, modelling, texturing,ecc and everything is fine.

The images have a VR format 8192x8192.
But all the 3507px are rendered fine without errors!

2017-03-29, 14:26:01
Reply #91

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging
So this is a problem on DR slaves? Is Master working properly?

Is complicated to answer...

I am in a very tight deadline and the Master workstation is not participating in these DR jobs. I have 2 DR slaves for this and I sent the Backburner Job to one of them which via DR is connected to the second one. Simple setup, nothing strange... But I don't know if my Master PC could give the same errors as I use it right now with IR, modelling, texturing,ecc and everything is fine.

The images have a VR format 8192x8192.
But all the 3507px are rendered fine without errors!

For now DR continuously gives me the same error via Backburner, adapter error etc,etc, etc... only in very high resolutions!
3507px works perfectly while 8192px not.

Thanks,

Dionysios -

2017-03-29, 19:55:27
Reply #92

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile
For now DR continuously gives me the same error via Backburner, adapter error etc,etc, etc... only in very high resolutions!
3507px works perfectly while 8192px not.

Thanks,

Dionysios -

Good thing it's reproducible. Could you please check if a minidump file was created on the machine where backburner failed?
If not, it would be very helpful if you could try the render without backburner, by directly connecting to DR slave(s).
Also, could you send me logs from the crashing machine? Corona logs in particular (CoronaMax201* files). Thank you.

2017-03-29, 19:57:28
Reply #93

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile
I sent  a job to backburner but render doesnt start in 27.03.2017 version.Having the same problem with this daily build.


It's time to go back to 13 th Dec. version :)

Is the DR working if you don't use Backburner? Are there some warnings/errors in Backburner logs?

2017-03-29, 21:00:02
Reply #94

ihabkal

  • Active Users
  • **
  • Posts: 253
    • View Profile
So this is a problem on DR slaves? Is Master working properly?

Is complicated to answer...

I am in a very tight deadline and the Master workstation is not participating in these DR jobs. I have 2 DR slaves for this and I sent the Backburner Job to one of them which via DR is connected to the second one. Simple setup, nothing strange... But I don't know if my Master PC could give the same errors as I use it right now with IR, modelling, texturing,ecc and everything is fine.

The images have a VR format 8192x8192.
But all the 3507px are rendered fine without errors!

For now DR continuously gives me the same error via Backburner, adapter error etc,etc, etc... only in very high resolutions!
3507px works perfectly while 8192px not.

Thanks,

Dionysios -


Hope you're quick on the thank you button because this will blow your mind: this has been happening to me since the beginning. what you do is move your vray plugins from ther plugin folder (2 plugins and the vray folder) and render on the backburner, it will render but you will get an error notification when you open max, then when done move them back.
the vray plugins crash corona maybe, I don't use it of course you can't use it unless it is activated, but you need it there to switch all vray materials into corona ones via the script.

2017-03-29, 21:29:50
Reply #95

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging



Hope you're quick on the thank you button because this will blow your mind: this has been happening to me since the beginning. what you do is move your vray plugins from ther plugin folder (2 plugins and the vray folder) and render on the backburner, it will render but you will get an error notification when you open max, then when done move them back.
the vray plugins crash corona maybe, I don't use it of course you can't use it unless it is activated, but you need it there to switch all vray materials into corona ones via the script.
[/quote]

Thanks in advance for now! :)
What I can't understand is why this happens with the very high res images and not with the lower ones + only with the latest daily builds...
Probably I should give a try but not this week. I am very tight with a deadline and I'll install the build which was every stable here.

Thanks for your support and in any case I'll let you know!!!! ;-)

2017-03-29, 21:58:06
Reply #96

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile

Thanks in advance for now! :)
What I can't understand is why this happens with the very high res images and not with the lower ones + only with the latest daily builds...
Probably I should give a try but not this week. I am very tight with a deadline and I'll install the build which was every stable here.

Thanks for your support and in any case I'll let you know!!!! ;-)

Was there a build with new DR where the large images (8192x8192) rendered without problem?

2017-03-29, 22:11:16
Reply #97

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging

Thanks in advance for now! :)
What I can't understand is why this happens with the very high res images and not with the lower ones + only with the latest daily builds...
Probably I should give a try but not this week. I am very tight with a deadline and I'll install the build which was every stable here.

Thanks for your support and in any case I'll let you know!!!! ;-)

Was there a build with new DR where the large images (8192x8192) rendered without problem?

No unfortunately, was the 09/01 if I am not wrong.

2017-03-29, 23:00:53
Reply #98

ihabkal

  • Active Users
  • **
  • Posts: 253
    • View Profile
how much ram do you have on the machines? I rendered 8000 pixels wide and almost maxed 64GB,
Thanks

2017-03-29, 23:06:45
Reply #99

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging
how much ram do you have on the machines? I rendered 8000 pixels wide and almost maxed 64GB,
Thanks

It's not at all a ram problem. I rendered the same image with the 09/01 build without any issues. I thought about the ram too but when I checked during the rendering the SW was using 24GB on 64GB. I also rendered the same images at 3507px resolution without issues as well... The 8K ones don't want to be saved. Everything goes well and fast but at the end the DR system seems blocked from something, arrived at 100% and doesn't do anything. After several minutes I get the error... I hope to find the time to send the minidump file.

2017-03-29, 23:10:28
Reply #100

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging
I took a look at theDrLog.txt file and I found this:

2017-03-28 22:41:00   DR is finished
2017-03-28 22:41:00   Ready for new connection
2017-03-28 22:41:59   Received invalid message from master: Q£áh . Make sure you have the same version on Master and Slave.
2017-03-28 22:42:24   Accepted remote connection from 10.0.10.119

this is very stange as the installed version is exactly the same!!!! O.o

2017-03-30, 01:26:26
Reply #101

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile
I took a look at theDrLog.txt file and I found this:

2017-03-28 22:41:00   DR is finished
2017-03-28 22:41:00   Ready for new connection
2017-03-28 22:41:59   Received invalid message from master: Q£áh . Make sure you have the same version on Master and Slave.
2017-03-28 22:42:24   Accepted remote connection from 10.0.10.119

this is very stange as the installed version is exactly the same!!!! O.o

Sorry about that, this is only a bad error, it doesn't affect DR server in any way.
Could you look into Corona logs on the machine running backburner?

2017-03-30, 02:06:00
Reply #102

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging
I took a look at theDrLog.txt file and I found this:

2017-03-28 22:41:00   DR is finished
2017-03-28 22:41:00   Ready for new connection
2017-03-28 22:41:59   Received invalid message from master: Q£áh . Make sure you have the same version on Master and Slave.
2017-03-28 22:42:24   Accepted remote connection from 10.0.10.119

this is very stange as the installed version is exactly the same!!!! O.o

Sorry about that, this is only a bad error, it doesn't affect DR server in any way.
Could you look into Corona logs on the machine running backburner?

You mean the DRlog right?

The master machine have this

2017-03-28 10:35:32   DR server started
2017-03-28 10:35:32   Binded to localhost
2017-03-28 10:35:32   Running Corona DrServer build Mar 27 2017 on TCP/UDP ports 19668, loopback TCP/UDP19667
2017-03-28 10:35:32   Available 3dsmax versions:
2017-03-28 10:35:32   2017: C:/Program Files/Autodesk/3ds Max 2017/
2017-03-28 10:35:32   Running command:
"C:\Program Files\Autodesk\3ds Max 2017\3dsmaxcmd.exe" "C:\Users\dtsagkaropoulos\AppData\Local\CoronaRenderer\DrData\corona_dr.max"  -continueOnError -gammaCorrection:1 -rfw:1 -sf -v:5  -postRenderScript:"C:\Users\dtsagkaropoulos\AppData\Local\CoronaRenderer\DrData\post.ms"
2017-03-28 10:35:38   Received invalid message from master: Q£áh. Make sure you have the same version on Master and Slave.
2017-03-28 10:35:40   Started loopback connection with 3ds max
2017-03-28 10:35:41   Cannot contact 3ds Max, trying again ...
2017-03-28 10:35:41   3dsMax started successfully
2017-03-28 11:47:43   Received invalid message from master: Q£áhúKÌûKàûKÅX0w|¨ˆþÿÿÿ4,w14,ww. Make sure you have the same version on Master and Slave.
2017-03-28 15:00:03   Received invalid message from master: Q£áh¸Í4,wàûKÅX0w|¨ˆþÿÿÿ4,w8>ÍPÊ. Make sure you have the same version on Master and Slave.
2017-03-28 15:04:13   Closed loopback socket

As for the DRServer I attached the file here as it contains a lot of data.

Thanks!

2017-03-30, 02:22:58
Reply #103

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile
I meant the log from your master, the machine that starts the DR. If I understand your setup, you have PC1 from which you connect to PC2 via backburner. PC2 then starts the DR on slaves PC3, ... And then when the render ends, 3ds Max on PC2 crashes and reports the error in backburner log, is that right? I'd like to see the Corona logs from PC2. They should be stored in the config directory (C:\Users\Username\AppData\Local\Autodesk\3dsMax\2017 - 64bit\ENU\en-US\plugcfg\corona)

2017-03-30, 02:30:31
Reply #104

Dionysios.TS

  • Active Users
  • **
  • Posts: 766
    • View Profile
    • Evolvia Imaging
I meant the log from your master, the machine that starts the DR. If I understand your setup, you have PC1 from which you connect to PC2 via backburner. PC2 then starts the DR on slaves PC3, ... And then when the render ends, 3ds Max on PC2 crashes and reports the error in backburner log, is that right? I'd like to see the Corona logs from PC2. They should be stored in the config directory (C:\Users\Username\AppData\Local\Autodesk\3dsMax\2017 - 64bit\ENU\en-US\plugcfg\corona)

Yes it's right and I am sorry for the wrong file.
Here are the 3 log files found in the folder of "PC2".

Thanks again,

Dionysios -