Flamenco Manager crashes after one hour on Windows #58084

Closed
opened 2018-11-27 11:50:00 +01:00 by Pascal · 6 comments

System Information

  • Windows 10 Pro
  • Intel Xeon 1650 v4
  • Asus Strix GTX 1080 A8G
  • 32GB DDR4 2400MHz

Blender Version

  • Blender 2.79b

Short description of error
I have four computer used exclusively as a renderfarm and each of them running Flamenco Worker (2.1.0). I have one main workstation used to run Flamenco Manager (2.1.1) and Flamenco Worker (2.1.0). Five computers in total, all using Windows 10 Pro.

The rendering works perfectly when creating a job for Flamenco but after one hour (two sometimes) Flamenco Manager crashes on the main workstation. The terminal simply closes itself without any error message. The only way to keep the render going is to reopen the Flamenco Manager manually. On the other hand I've never experienced a crash of the Flamenco Worker.

Exact steps for others to reproduce the error

  • Launch Flamenco Manager and Worker on a Windows computer
  • Launch Flamenco Worker on separate Windows computers
  • Wait from one to two hours for the Flamenco Manager to crash
**System Information** - Windows 10 Pro - Intel Xeon 1650 v4 - Asus Strix GTX 1080 A8G - 32GB DDR4 2400MHz **Blender Version** - Blender 2.79b **Short description of error** I have four computer used exclusively as a renderfarm and each of them running Flamenco Worker (2.1.0). I have one main workstation used to run Flamenco Manager (2.1.1) and Flamenco Worker (2.1.0). Five computers in total, all using Windows 10 Pro. The rendering works perfectly when creating a job for Flamenco but after one hour (two sometimes) Flamenco Manager crashes on the main workstation. The terminal simply closes itself without any error message. The only way to keep the render going is to reopen the Flamenco Manager manually. On the other hand I've never experienced a crash of the Flamenco Worker. **Exact steps for others to reproduce the error** - Launch Flamenco Manager and Worker on a Windows computer - Launch Flamenco Worker on separate Windows computers - Wait from one to two hours for the Flamenco Manager to crash
Author

Added subscriber: @PascalFerrere

Added subscriber: @PascalFerrere
Sybren A. Stüvel was assigned by Pascal 2018-11-27 11:50:38 +01:00

Can you start Flamenco Manager from a cmd.exe terminal? That way it stays open and you can read any error message. Start it with flamenco-manager.exe -verbose to get more verbose logging. If it turns out that that still doesn't give enough information we can use flamenco-manager.exe -debug to enable debug logging, but this will produce a rather copious amount of log messages.

Can you start Flamenco Manager from a `cmd.exe` terminal? That way it stays open and you can read any error message. Start it with `flamenco-manager.exe -verbose` to get more verbose logging. If it turns out that that still doesn't give enough information we can use `flamenco-manager.exe -debug` to enable debug logging, but this will produce a rather copious amount of log messages.

I've tried running Flamenco Manager on Windows 10 for close to 7 hours, and it keeps running just fine. It has one Worker connected to it, so it does get frequent polls for more tasks.

I've tried running Flamenco Manager on Windows 10 for close to 7 hours, and it keeps running just fine. It has one Worker connected to it, so it does get frequent polls for more tasks.
Author

I tried last night with a render. I started Flamenco Manager using cmd.exe and with the - verbose command.
The manager didn't crash and worked perfectly all night long.

I guess launching Flamenco Manager with the terminal solves the problem as I have never tried this before, I would always launch Flamenco Manager by double clicking on it.

I tried last night with a render. I started Flamenco Manager using `cmd.exe` and with the `- verbose` command. The manager didn't crash and worked perfectly all night long. I guess launching Flamenco Manager with the terminal solves the problem as I have never tried this before, I would always launch Flamenco Manager by double clicking on it.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

I tried again with double-clicking Flamenco Manager, and here it really doesn't crash. I'm archiving this now, because I can't reproduce the issue and thus can't find the root cause. If you have more information that can help, please comment here.

I tried again with double-clicking Flamenco Manager, and here it really doesn't crash. I'm archiving this now, because I can't reproduce the issue and thus can't find the root cause. If you have more information that can help, please comment here.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#58084
No description provided.