Exporting the BuildBee log - BuildBee Support

Exporting the BuildBee log


To help diagnose an issue you may be having, a member of our support team may ask you to send us a log of the messages being sent between your BuildBee and 3D printer. This is a great way to capture the full story after an error has occurred.


Step 1 - Access the maintenance console

- Access your list of printers
- Make sure your BuildBee CloudDock is connected to the Internet (either in the 'READY' or 'DISCONNECTED' state) and open up the BuildBee maintenance console.

If the maintenance console cannot be reached, move to step 3.

Step 2 - Generate and download the log file

- Select 'SYSTEM INFO':


BuildBee maintenance console system info


- Select 'DOWNLOAD LOGS'. Only click the button once, it usually takes a moment for BuildBee to generate the log file.



BuildBee download logs


- If nothing happens, the download has been blocked by your browser's popup blocker. Simply allow popups for the current page and the download will resume.

- Once it is downloaded, you may see a message similar to the one below (for older versions of BuildBee). Your browser is only showing this message because it doesn't recognise tar.gz as a common file type. It is simply a file that has been compressed twice using different formats, which is common on Linux machines.



log dump tar gz

Submit a support request with the log file attached and we will open it up and see if we can diagnose your issue!

Step 3 - If the printer is inaccessible

If the printer's maintenance console cannot be accessed, it's possible to get the log files written to a USB drive.

We recommend using a USB drive from a known manufacturer (e.g. Toshiba), formatted to FAT32, without any partitions. Promotional USB drives are not reliable for this process.

- Remove ALL cables from the BuildBee CloudDock (no power, no USB cable).




- Insert the USB drive into the BuildBee CloudDock.



- Plug the power supply into the BuildBee CloudDock with the USB drive inserted. 

Do not connect the printer yet.



- The CloudDock will place a log dump .ZIP file in the root folder of the USB drive (not within any other folders).
Submit a support request with the log file attached and we will open it up and see if we can diagnose your issue!

    • Related Articles

    • Getting started with BuildBee Desktop

      BuildBee Desktop can be used as a host for your 3D printer to make it available remotely, to setup and maintain BuildBee CloudDocks or to access other BuildBee apps. BuildBee Desktop - Installation - Go to the download page and click the download ...
    • Updating your BuildBee CloudDock

      Most BuildBee updates happen automatically and will be available when you log in or refresh your page. However, larger updates to the BuildBee CloudDock device must be manually triggered. Step 1 - Access your list of printers Your account will need ...
    • Get Started with BuildBee

      Congratulations! You’re the proud new owner of our latest and greatest CloudDock! With this awesome piece of technology, you can control your 3D printer over the Internet. BuildBee is comprised of two products. Firstly, a physical control box called ...
    • BuildBee model upload failures

      If a model you upload to BuildBee fails to upload successfully, it is easy to identify and fix. Step 1 - Confirm if your upload failed - Firstly, your model will fail to produce a preview image: - Secondly, if you attempt to print the model it will ...
    • Cancelling a print

      Sometimes you may need to cancel one of your prints before it has a chance to finish.  You will need the correct right enabled for your account to do this (Enterprise users). Step 1 - Access your printer list - Log in to your BuildBee account. - ...