[lujo]

Hi

I still have this problem: the .mxi files are only partially written. The size of the .mxi on the server doesn't go over 49.152 KB (it should be way over)

"Start writing MXI file...
WARNING: - MXI "\\SERVER\server_SSD\vbm\DOMOBAR_JUNIOR_HX MANUALE_FRONT_DX.mxi_mxitmp" not saved.
DEBUG: - MXI successfully renamed.
End writing MXI file...
Start writing image file...
End writing image file..."

The saved incomplete .mxi is always 49.151 KB

I have a MacOS X server and I'm using Windows10 workstations

No problems with Network Render instead

[F. Tella]

Hi Lujo,

This caught my attention: "\server_SSD\". Could it be that the SSD run out of space by any chance?

SSDs are very fast, but usually are much smaller than normal hard drives because the price of the SSDs is much higher.

Best,

Fernando

[lujo]

Hi Fernando

the disk space is not a problem (130GB free). I moved the render folder from the main server HD to the SSD only to try to solve the problem.
Moreover the Maxwell Network save big .mxi files in the same disk without any problem.

Thanks

[F. Tella]

Hi Lujo,

Does it happen with all the files and all the renders or just with some?

Best,
Fernando

[lujo]

Happens with every .mxi over 49.152 KB, that is a very small size for an .mxi

MR has no problems saving the image file in the same place instead. Usually in .TIF format and very large in size

[F. Tella]

That's odd. I cannot reproduce it here either in Windows 10 or OSX (ElCapitan).

Does it happen to you in both Windows and OSX or only when saving to the mac?

Could you give me more details about your system?

Best,
Fernando

[lujo]

I can't tray with a mac now but before switching to windows (3 Months ago) I was using only mac pro workstations without any problem. This is my system configuration:

3 Workstation Windows 10
7 Render nodes Windows 10

1 Server OSX El Capitan 10.11.5, server version 5.1.5. Had the issue even with Yosemite but less frequently, now it's continuous. I tried even with a mirror server with identical configuration

Every windows 10 PC has the same problem. Now what I'm doing is saving manually the .mxi locally on desktop and then copying it to the server

[F. Tella]

Hi again,

Could you try this test? Please open Studio, create a box, add a camera and set it to 3500 x 2625 then point Maxwell to save the mxi file to a specific folder; launch the render. Does it still happen? That should create an mxi of around 130MB.

If it doesn't happen it must be dependent on the scene.

If it still happens with that scene I can only think of some backup program which tries to zip the new files, or some other program which tries to use the file for something. That figure, 49.152, is dividable by 8, which is funny.

Fernando

[lujo]

I tried... It still happens even with a single cube scene made in Studio

It definitely doesn't depend on the scene

I really don't know what it could be on the server. I don't have any particular program installed except of Carbon Copy Cloner that makes a backup during the night but without compression or anything, I even tried to save to a different server disk (not SSD).

[F. Tella]

Hmm,

Could you disable CCC just for testing? When Maxwell is updating the mxi file it creates a temporal mxi file with the same name of the mxi file but with extension .mxi_mxitmp; then it deletes the existing .mxi file and renames the new one to .mxi
It could happen that CCC gets confused by all this file creation and renaming. It's just a hunch.

Best,
Fernando

[lujo]

I was thinking that I already did this test: the mirror server has not CCC installed and MR can't write the .mxi on it too.

Now I'll try to do some test saving the file on a completely different mac with El Capitan installed. I let you know when I have the results!

[lujo]

Hi Fernando

I did a new test: I used a mac pro with El Capitan and no server application installed, only file sharing enabled. The problem remain the same, file only partially written (49.152 KB).
Tried saving the .mxi from more than one windows pc

At this point I think we have done all the possible cross-testing we could!