Leonardo Bernardini

Just a note:

Configuration parameters are stored in the dispatcher.conf, this includes every parameter you’re able to configure through the “Configure Dispatcher” icon in Muster explorer.

Every kind of different data is stored in the database.

We are aware of the reaction speed. A big difference in Muster 5 is that now data resides on a SQL db, even when it’s configured to work with the in-process sqlite. Just to explain that using the same system, it will be impossible to reach the speed of version 4.X that works in RAM and dumps periodically the queue status. Using an SQL database gives maximum file tollerance with the support of a journaling system.

The just-released version 5.2 address some speed issues, the network protocoll react faster and we optimized lot of the internal queries. You’ll find a huge improvement in the submission and the reinit of a job as well as the selection logic speed that were the critical data operations in the past.

Regards.

Exit code 211 always means an error reading the job’s files. this may have multiple reasons, the most common is related to permission problems for the service, in that case, you’ve to check the Muster user (or any custom user you supplied during the installation) and be sure it’s able to map drives and access network resource.

When it happens on a random basis, the most common source of the problem is the “LIMITED” amount of concurrent access you actually have on your file sharing host. I.E. WinXP Professional allows only 5 concurrent connections from external hosts.

It may be possible that your file server has such kind of limit.

Regards.

Maya 6.5 has a bug in the commandline. the -rfb flag used by Muster is expected to be “-rbf”. If you plan to use version 6.5, you’ve to derive a new template from the default one and change the command line according.

We are not aware of such kind of problem even we didn’t test with Fedora Core 6. We’ll setup a test installation with this release to see if it’s a problem with this distro.

The broadcast presence function is required by the DISCOVERY function in the management console. If you’ve configured and discovered your hosts, there’s no need to keep it active.

By the way, it’s an UDP broadcast packet, so , there’s no way to route it elsewhere than your local network.

If you get a red dot, there’s an error reported by a renderclient. Take particular attention, when you publish a new template, it has a new template ID, it means that you’ve to reconfigure the PATHS for that particular template on each render client.

Having some log dumps may help everyone in this forum to understand what’s going on.