Skip to content
English
  • There are no suggestions because the search field is empty.

Collect Hub logs for troubleshooting

Collect logs while reproducing the problem. Download them before restarting the Hub: locally stored logs are cleared on reboot and automatically after three days.

[Step] 1. Enable Hub logging, reproduce the problem and download the logs

  1. Open the Hub console and go to System > Logging.
  2. Choose a log level: Errors and print job information, Errors only, or All details.
  3. Save. Use All details when detailed troubleshooting is needed; it produces the most data.
  4. Reproduce the problem.
  5. Select Show Logs to inspect the messages, or Download Logs to save them as a .log file.
  6. Return to the normal log level after troubleshooting.

The default level is Errors and print job information. Delete All Logs clears the Hub’s locally stored messages.

Hub System page showing log level, Show logs, Download logs and the syslog server field.
Choose the log level and download logs under System. The syslog destination is below the local logging controls.

[/Step]

[Step] 2. Enter your syslog server’s address and port under Logging

Enter the syslog destination under System > Logging and save. TCP and UDP are supported. For example:

tcp://192.168.149.222:1468

Use your own server address and port. Leave the field empty to disable forwarding.

[/Step]

[Step] 3. Insert an empty FAT32 USB stick, restart and reproduce the problem

  1. Use a completely empty USB stick formatted as FAT32.
  2. Connect it to the Hub.
  3. Restart the Hub by disconnecting and reconnecting power.
  4. Reproduce the issue.
  5. Remove the USB stick and connect it to your workstation to copy the log file.

Do not place a factory-reset file on a USB stick used for logging.

On firmware 2.5.18 and later, logs are stored on external USB storage when it is connected; otherwise, internal storage is used.

[/Step]

Send useful context with the logs

When contacting ezeep support through the website chat, include the Hub’s MAC address, firmware version, the problem, the affected printer and when it happened. Include the steps that reproduce it.