(Flame2019.1 Linux) cannot open projects, flame can not start wiretap ifffs serv

[Anonymous]

I am having trouble with our Linux Flame 2019.1 . It used to run normally, but since yesterday we are unable to open any project and the terminal says:

"Could not start local Wiretap "IFFFS" Service".

another strange thing that may or may not be related to the problem:

the startup of flame takes longer than usual and it says something about "Syncolor Transforms"

[debbie.hoffman]

Hi!

If you run vic from a Terminal do you get any errors?

Run vic as follows:

/opt/Autodesk/io/bin/vic -v -a

Thanks,

Debbie

[Anonymous]

Just tried vic. Did not give me any errors. Just removed a few frames from the framestore!

Any other ideas?

[debbie.hoffman · Accepted solution]

First can you please verify if the IP address in /etc/hosts is correct?

Second, is it possible that your /opt/Autodesk/cfg/network.cfg file might have been manually modified to force Flame's services to a network interface that does not exist for example "en2"?

Third, if the IP is good in the hosts file and network.cfg is right, check the storage configuration:

1. Open the Flame Setup app and go to the Media Storage tab.

2. Are there any entries in that list that are no longer connected to your machine?

3. If so, click "Manual Edit". The configuration file opens in a text editor.

4. Find the [Partition], Name= and Path= lines that correspond to the missing drive.

5. Add a # sign before each of these three lines to disable them. For example:

#[Partition7]
#Name=AutodeskMediaStorage
#Path=/Volumes/storage/Autodesk Media Storage

6. Close the text editor. Confirm that you want to save changes. 

7. The drive should no longer appear in the Media Storage tab. Click Apply to save the new configuration.

8. Open the Service Monitor app and restart the Stone+Wire and Wiretap Server services.

[Anonymous]

Checked /etc/hosts, found wrong ip(!!!) but fixing it did not resolve the issues 😞


network.cfg seems to be fine.


Storage configuration seems to be fine as well

[gagnona]

ifffsWiretapServer.log and flame20191__app.log in /opt/Autodesk/log might provide some useful clues.

Andre

[Anonymous]

We just had a professional log onto our system remotely and we figured out the issue. it had something to do with an incorrrectly configured /etc/hosts file.  don`t know why it was working before and then suddenly decided to stop, though...

anyway it seems we now have a working flame workstation again!

thanks for all your replies and suggestions!!

all the best

[Anonymous]

edit:  it seems i did not fix it properly, but the remote expert did!

[debbie.hoffman]

Nice to know it is working for you now! Thanks for the update!