Community
Smoke Forum
Welcome to Autodesk’s Smoke Forums. Share your knowledge, ask questions, and explore popular Smoke topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Backburner issues

15 REPLIES 15
Reply
Message 1 of 16
Anonymous
2488 Views, 15 Replies

Backburner issues

Mac OS 10.9.5
Smoke 2015.0.3
Mac Pro Late 2013 trashcan
Promise Pegasus R6 T2
I know this is an ancient machine running ancient software, but I'm not in post anymore and just use the software to help out a non profit where I volunteer.
Backburner will not connect to Smoke in the app nor allow any output and will not show green in the Service Monitor.  In Terminal, the hostname shows the correct computer name.  When I ping the "hostname.local", I get the computers ip back.  When I ping "hostname", I get the ip for Google Chrome's settings page.
I checked the usr/discreet/Network/backburner.xml and the manager name is "localhost" and the server name is the hostname.
I have the network IP address set over ethernet to "DCHP with manual address" with no connection issues.

Tags (3)
15 REPLIES 15
Message 2 of 16
yann.laforest
in reply to: Anonymous

Hi,

 

The first thing I would recommend is setting the server to localhost in the backburner.xml, then restart the backburner manager and server, and see if the issue persists.

 

Also, can you check if the workstation resolves the localhost IP as 127.0.0.1 (ping localhost)?

 

 

Let us know,

 

 

Best,

Yann

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 3 of 16
Anonymous
in reply to: yann.laforest

Yes, localhost does ping 127.0.0.1
And to confirm, you want me change the server name to "localhost" in addition to having the manager name as "localhost"?

Message 4 of 16
yann.laforest
in reply to: Anonymous

Thanks.

 

Yes,

 

Both server and manager should be set to localhost.

 

Please give a try and let us know how it goes.

 

 

Best,

Yann

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 5 of 16
Anonymous
in reply to: yann.laforest

I got the backburner.xml changed and backburner is still non op.

local_XML.jpg
I have Robert Adams' log utility.  Would a set of logs help?

Message 6 of 16
yann.laforest
in reply to: Anonymous

Thanks for letting me know.

 

Can you share the backburner.log and backburnerServer.log files located in /opt/Autodesk/backburner/Network?

 

 

Best,

Yann

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 7 of 16
Anonymous
in reply to: yann.laforest

Certainly...

Message 8 of 16
yann.laforest
in reply to: Anonymous

Thanks,

 

It seems that the Backburner manager is trying to send jobs to a server that is no longer available.

 

Can you open Safari or Chrome, type localhost, go to Backburner Web Monitor, select your manager, delete all servers associated to it, restart both services from the Service Monitor tool and see if the issue persists?

 

 

 

 

Thanks,

Yann

 

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 9 of 16
Anonymous
in reply to: yann.laforest

For the web tools, what is the usename and password derived?

Message 10 of 16
yann.laforest
in reply to: Anonymous

Password is backburner - backburner.

 

 

Best,

Yann

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 11 of 16
Anonymous
in reply to: yann.laforest

There are NO servers showing up and the manager dropdown has nothing even after refresh

Message 12 of 16
yann.laforest
in reply to: Anonymous

Hi,

 

Please contact me offline at yann.laforest@autodesk.com, and we will try to sort it out.

 

 

Best,

Yann

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 13 of 16
Peter_Tresize
in reply to: Anonymous

I don't know if this could work as a temporary export solution, but I noticed in Smoke 205 there is a foreground publish option. In a situation when backburner isn't working, would this work as a way to at least export a DPX sequence?

Message 14 of 16

Thanks for suggesting Peter.

 

It turned out that Backburner was not working because of a network configuration issue.

 

 

 

Best,

Yann

Yann Laforest

Program Manager Data Analytics - Autodesk EMS
10 rue Duke Street
Montréal (Québec) Canada H3C 2L7
Message 15 of 16
Anonymous
in reply to: Anonymous

Would this function as a way to at least export a DPX sequence in the event that backburner isn't working?

Message 16 of 16
slabrie
in reply to: Anonymous

Yes.  Background Export uses Backburner to manage the task.  If you enable Export In Foreground option in Media Export, the export tasks will not be managed by Backburner.

 

Give it a try and let us know.

Stéphane Labrie
Senior Product Owner
Flame Family

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Technology Administrators


Autodesk Design & Make Report