Tutorial: Troubleshooting with Syslog
Being a network-device, Querx depends on a correct network-configuration for much of its functionality. We have simplified the integration of Querx into networks as far as possible by supporting mDNS and DCHP. Should the device still not work as expected, it will usually suffice to consider the following hints:
- A default gateway needs to be configured, if the device is to be connected to the internet.
- A valid nameserver needs to be set up, in order to use services such as cloud-connectivity, sending emails or setting the device’s internal clock automatically.
If the problem persists, it will be necessary to determine its cause. Querx can help you narrow down the issue: If you have configured a Syslog server in the network settings, system messages are sent to the specified address.
Our tool Querx Hub is equipped with a simple Syslog server that captures output from Querx. This is a simple way to make use of Querx's Syslog functionality and is outlined below.
Querx Hub is available for download from the Tools section of the support page.
To learn more about the setup and the other possibilities Querx Hub offers, please have a look at our tutorial on Querx Hub.
Step 1: Determining your IP-address
For configuration you need the IP address of the PC on which Querx Hub was started.
Please open Querx Hub to begin.
- In the main menu, select the View item.
- Click on Syslog.
The Querx Hub Syslog window opens. In the status bar of this window the IP address of your computer is displayed. Please note this address or select it and copy it to the clipboard by pressing Ctrl+C.
If your computer is equipped with multiple network interfaces, additional IP addresses will be displayed here. In this case, use the IP of the interface that connects your computer to the network where the Querx device is located.
Step 2: Activating Querx Syslog output
The Querx web interface opens in your default browser. Click on Configuration in the upper area to get to the configuration area.
In the configuration area, select the Syslog item 1 in the Interfaces section of the menu.
- On the Syslog page, now enter the determined IP address of your computer from step 1 into the Syslog server field.
- Click on save. A restart is not necessary.
Step 3: Gathering system messages
Open Querx Hub and its Syslog window again as in step 1 (View > Syslog).
As long as the program is running, the incoming Syslog messages from Querx are collected here and displayed line by line.
For example, if you have problems sending or receiving emails, use the test feature of the email server and email recipients. System messages can also be caused by provoking alerts by adjusting the alert thresholds.
For failure diagnosis, leave the program open for half an hour without making any changes to the device.
Step 4: Evaluating error messages
querx332224 SMTP connect to egnitequerx.de:587 failedindicates a problem with the configuration of the email server, since it does not exist and is therefore not accessible.
Step 5: Sending Syslog messages via email
If you can not figure out the cause of the problem you are experiencing, we will gladly assist you. You can help us with this by sending us the Syslog messages gathered in the Syslog window.
Hit CTRL+A in the Syslog window to select all entries.
Copy the selected messages to the cache by hitting CTRL+C.
Paste the data into a text file by hitting CTRL+V. Send this file to: firstname.lastname@example.org
|[System name] SMTP authentication for [login] failed||The user could not be logged into the SMTP server.||Check the login data for your mail server.|
|[System name] Connecting SMTP failed||Querx was not able to connect to the mail server.||Check your default gateway and DNS servers.|
|[System name] Error connecting [cloud provider]||The cloud provider could not be reached.||Check your default gateway and DNS servers.|
|[System name] Error: Firmware upgrade failed||An error occurred while upgrading the firmware.||Make sure that you downloaded the correct firmware.|
|[System name] Low memory [number] bytes||The device's system memory is running low.||Check that you have not opened the web interface in too many browser tabs.|
|[System name] Failed to send SNMP trap||An SNMP trap failed to send.||Check your SNMP manager and the network configuration.|
|[System name] Failed to create SNMP session||Querx was not able to connect to the SNMP manager.||Check your SNMP manager and the network configuration.|
|[System name] DNS query for [address] failed||The name server could not be accessed.||Check your default gateway and your DNS servers.|
|[System name] Failed to send email||An email could not be sent.||Look for further error messages to narrow down the problem.|
|[System name] Failed to query time server [address]||Querx could not connect to the NTP time server.||Check default gateway, name servers and NTP server.|
|Unknown sensor||The sensor could not be detected.||Verify that the correct variant of the firmware is installed and up to date. If the error persists, then there could be a defect.|
|Failed to read [sensor]||There was an error reading a sensor.||Check whether the firmware is up to date. If the error persists, then there could be a defect in the hardware.|