So maybe that’s the issue, have you installed all the drivers after installing Sierra? What model of Mac are you using?
1 Like
Macbook Pro, bought it 2015 (the latest model at the time). Ah ok so I need to install drivers as well… ok ok… I thought an upgrade to Sierra would sort all of that automaticlly! I am a fairly new mac user so I am not super experienced just yet!!
No problem. Make sure you have the latest nvidia driver for your card because Makerbot Desktop uses OpenGL 2.1
“Activity Monitor” is located in /Applications/Utilities and will display all processes, make sure Makerbot service is there.
1 Like
I cant seem to find Makerbot service inside the acitvity monitor. I will attach an image how it looks
UPDATE: Okay, now I can see it when I had the program opened. So updating the Nvidia driver might be the solution then maybe? I didnt even know mac had Nvidia to be honest with you! haha
2 Likes

Did you drag the Makerbot icon to the Applications icon during the setup installation?
1 Like
No I think that i didnt do that actually. If i remember it correctly i just installed it and then when that was done i did not drag it (because the box did not appear where it shows that you should drag it to applications) instead i pressed cmd + spacebar and searched for ‘makerbot’ and opened it that way. “Makerbot” is in the Application folder though now when i Look at it. Maybe I dragged it there the first time i installed it. (I have uninstalled it a few times).
Can you open background service log in the software? (conveyord.log)
1 Like
Hmm , i doont know quite what you mean. is that a file in the makerbot map?
When you open Makerbot Desktop go to Services->Show Background Service Log
or search for conveyord in All My Files
1 Like
When I search for it these show:
Check the dates, Right click on the latest one and open it with Console. On the left side menu go to User Diagnostic Reports. Do you see any Crashed Threads? with exception like EXC_BAD_ACCESS (SIGSEGV)
1 Like
obj/src/core/application.cpp:166: error
Application::Application(int *, char **, const QString &, const QString &, const MakerBot::Version &)
Fri Oct 7 21:39:04 2016
Exception : Unable to connect to: /var/tmp/conveyord.socket
obj/src/util/log.cpp:41: error
void logQtMessage(const QtMsgType, const QMessageLogContext &, const QString &)
Fri Oct 7 21:39:04 2016
QtWarningMsg: QSslSocket: cannot resolve TLSv1_2_server_method(?:0, ?)
obj/src/util/log.cpp:41: error
void logQtMessage(const QtMsgType, const QMessageLogContext &, const QString &)
Fri Oct 7 21:39:08 2016
QtWarningMsg: QSslSocket: cannot call unresolved function SSL_get0_next_proto_negotiated(?:0, ?)
should I look for thoe named “error”?
I also have the last two in my logs for SSL connection but don’t have the first one. When I open Makerbot Desktop, I can see /var/tmp/conveyord.socket in the terminal. Open your terminal and go to that folder, check if it’s there? conveyord.socket is a file
2 Likes
Ok if I write: sudo rm /var/tmp/conveyord.socket or sudo rm /var/tmp/conveyord.pid i get “No such file or directory”.
Inside my Library/LaunchDaemons i have a file called “com.makerbot.conveyor.plist” however.
Are you logged in as an Admin (root) to your mac? those are temporary files that should be re-created when you open Makerbot Desktop app if deleted. That first error was complaining about the conveyord.socket . Probably the background service or the app cannot create that file, or because the service is not running that file is not being created. Create that file manually like a text file and see if that first error goes away.
2 Likes
I am not sure how i should do that. Should I create it in the logs and inside the latest file there? Damn this is pretty hard
I expected it to be much easier. Myabe I should just downgrade to El capitan (it worked there before i updated to mac os sierra).
if you are not familiar with Linux then it’s going to be really hard to fix it. If there is nothing special in Sierra for you to use then go ahead and re-install El capitan 
2 Likes
Hi to all,
Happened to me in ubuntu. I have a temp fix that works every time. It may spark an idea for your OS X to get fixed.
- /var/lock/conveyor folder is NOT being created. -> Create it with 777 rights.
- /var/lock/conveyor/conveyord.socket is NOT being created. -> Create the file with 777 rights.
- Wait 5-8 seconds
- Stop “background service” from makerbot software.
- Wait 5-8 seconds
- Start “background service” from makerbot software.
- Wait 5-8 seconds
You will see the service would start and makerbot software would find the printer and show “printer ready”
Hope this helps.
Same problem. I reinstalled MakerBot for Mac. Now works fine.
Yes, same problem here, trying to start makerbot and slice with makerbot Software, i get the message backgroundservice not available and i could not do anything. i tried to reinstall an old version and also a newer version of makerbot, but nothing happened. Going back to an older OS on my mac is no solution for me. Any suggestions?