Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10

Known Bugs, Fixes, and Patches / Qube core installer places API file in the incorrect directories

« Last post by jburk on June 20, 2018, 07:38:28 PM »

Versions affected: 7.0-0, 7.0-0a
Platforms affected: all
Severity: Newly-installed Windows and linux workers are unable to run python-based jobs. Upgraded workers on Windows and linux, and all workers on OS X may exhibit more subtle behavior mimicking a version mismatch between API and jobtype versions

We've noted that the qube-core installer has been incorrectly packaged, and will place the files that should be in the QBDIR/api/python/qb/.. directory tree all into the api/python directory. When upgrading from a previous version of Qube, the compiled .pyc files that were generated from the original.py modules are left behind, so the issue may not be immediately obvious as the .pyc can be used in place of the .py files.

On Windows and linux, the files are only in the api/python directory, while on OS X the files are duplicated into api/python.

A subtle side effect of this bug is that if older .pyc files are loaded, it can appear that the API is an older version than the jobtypes despite all Qube components being of the same version, and some python-based jobtypes will fail with the following error:

AttributeError: 'CmdRangeBackEnd' object has no attribute 'outputPaths_required'

Known Bugs, Fixes, and Patches / Qube 7 supervisor can fail to connect to the PostgreSQL server

« Last post by jburk on June 14, 2018, 12:41:01 AM »

This can occur either during the upgrade procedure from Qube 6 to Qube 7 or if the supervisor configuration is modified with WranglerView 7.0-0 or 7.0-0a at any time after a successful installation or upgrade.

The root cause of both of these issues is due to a

database_port=3300 (or 3306)

line present in the supervisor's qb.conf file. If your supervisor's supelog file contains entries like:

[Jun 13, 2018 17:37:29] jburk-15-mbPro[74627]: ERROR: QbDatabasePostgreSQL::_connect() Unable To Init Database: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.3306"?

please open the qb.conf in a text editor, comment out the database_port line, and restart the supervisor service.

We will be patching the installation and upgrade procedures, as well as WranglerView, to address this in the next few days.

Announcements / Maintenance/Patch Release 7.0-0a of Qube! Now Available

« Last post by jburk on May 31, 2018, 07:56:04 PM »

This is a supervisor-only patch release of Qube! 7.0.0 that includes the following key fix:

@FIX: jobs submitted that reserve a global resource never run

This bug was introduced at 7.0-0, where jobs specifying any global resource reservation would be stuck indefinitely in "pending" state.

It was previously noted in our 'Known Issues' board as topic: Qube 7.0-0 supervisor - jobs reserving a global resource never start

Complete release notes are available on our documentation site.

Known Bugs, Fixes, and Patches / FIXED: Qube 7.0-0 supervisor - jobs reserving a global resource never start

« Last post by jburk on May 29, 2018, 08:46:12 PM »

UPDATE: this has been fixed in 7.0-0a, released 5/31/2018 at 12:00 PDT

The 7.0-0 supervisor has a known bug which prevents jobs reserving a global resource from running. These jobs stay in the "pending" state forever and are not dispatched. We are actively working on this, and will be releasing a 7.0-0a patch in the next few days.

Customers using Qube's global resource feature in production should wait until 7.0-0a is available before upgrading.

This topic will be updated once this issue is fixed, and we will also be posting in our Announcements forum. We'd recommend subscribing to either this topic or the Announcements in order to receive notifications when 7.0-0a is available.

Announcements / Qube! 7.0-0 with Postgres Released!

« Last post by pipelinescott on May 23, 2018, 11:36:44 PM »

Version 7.0-0 of Qube! has been released and is immediately available for download.

Major and groundbreaking changes come to this version of Qube!

- Qube! now runs off of Postgres
- Supervisors can be acquired free of charge
- Performance is noticeably better with Postgres
- A functional version of the NEW Qube UI is available for you to test upon request

Other benefits included in this release:

- New Metered Licensing email alerts about usage and spending
- Support in OS X 10.13 High Sierra
- Support for Maya and 3DS Max 2018
- Support for After Effects CC 2018
- Support for Nuke Frame Server and NukeStudio
- Support for Unreal Sequencer job submission
- Support for Keyshot job submission

Downloads available at:
https://www.pipelinefx.com/downloadversions/

Tech specs:
https://www.pipelinefx.com/technical-specifications/

Documentation:
http://docs.pipelinefx.com/display/QUBE/What%27s+New+in+Qube

Jobtypes and Applications / Re: Multiple Instances of aerender on the same worker

« Last post by Kevin MacPhail on December 12, 2017, 10:58:19 PM »

Hi,

While technically possible it is not recommended to run more than one instance of aerender per worker. The issue is that each instance of aerender will attempt to use all available cores on the worker, and in our experience this creates a higher rate of hung processes and failed frames.

Cheers,

-Kevin

Jobtypes and Applications / Multiple Instances of aerender on the same worker

« Last post by johndavidwright on December 12, 2017, 09:19:51 PM »

Is it possible for a worker to run multiple instances of aerender? Say my worker has 44 slots. If I give my job the reservation host.processors=4 and set it to have 11 instances, would that worker be able to pickup all 11 instances and run 11 instances of aerender?

SimpleCmds / Adding support for AfterEffects CC 2018

« Last post by jburk on October 18, 2017, 10:13:58 PM »

We've added support today for AfterEffects CC 2018, and for those customers running Qube 6.10, you don't have to wait for us to release a new version in order to take advantage of this.

To get access to submitting jobs for CC 2018, install the attached ae_versions.py module into the AfterEffects (ArtistView) or aerender (WranglerView) directory located in either application's File->Open AppUI Dir, then restart AV or WV.

This will only be possible in Qube 6.10, earlier versions will not support this ae_versions module.

SimpleCmds / Re: set environment variables with simpleCMD

« Last post by wingart on August 25, 2017, 10:25:58 PM »

thanks, i will give that a try.

SimpleCmds / Re: set environment variables with simpleCMD

« Last post by jburk on August 24, 2017, 08:12:15 PM »

You can do this in the existing preSubmit() function in mayabatch.py:

Code: [Select]

def preSubmit(cmd, job):
    # Handle renderer-specific callbacks
    if cmd.package['-renderer'] == 'mi':
        return preSubmit_mi(cmd, job)
    elif cmd.package['-renderer'] == 'turtlebake':
        return preSubmit_turtlebake(cmd, job)
    
    job['env'] = {
        'foo': 'bar',
        'foobar': 'bat'
    }

Pages: 1 2 3 [4] 5 6 ... 10