1. Basic Troubleshooting: Checking Logs
2. Troubleshooting: Restarting Wilkins Service to Resolve Common Issues
1. Basic Troubleshooting: Checking Logs
Before reviewing the logs, it’s important to note that all computers running a dimensioner use the Ubuntu operating system. This is a form of Linux that hosts the primary Wilkins software. To diagnose any issue, you must log into Ubuntu on the dimensioner to see its real-time status and examine any error messages in the logs.
- Access the Remote Computer
- All dimensioners run on Ubuntu, so the first step is to access the remote machine where the dimensioner is running.
- Open the Terminal
- Once inside the system, open a terminal to execute diagnostic commands, press Ctrl+Alt+T or look for the “Terminal” icon.
- Check the Dimensioner Runner Status
- Run the following command to verify if the runner process has started successfully: docker logs dimensioner-runner -f
- If the process starts correctly, you should see an output similar to Image, indicating that the startup was successful.
- If the runner encounters an error, further troubleshooting will be required (covered in another section).
- Retrieve Detailed Dimensioner Logs
- If the runner is running successfully, execute the following command to get more detailed logs about the dimensioner’s connections and functionality: docker logs dimensioner -f
- This command provides insights into the dimensioner’s status, including camera, scale, and other hardware connections.
- If any issues are detected in this step (such as camera or scale errors), further investigation will be necessary.
- If the runner is running successfully, execute the following command to get more detailed logs about the dimensioner’s connections and functionality: docker logs dimensioner -f
2. Troubleshooting: Restarting Wilkins Service to Resolve Common Issues
Many dimensioner issues can be resolved by restarting the Wilkins service. Follow these steps to execute the restart properly.
2.1. Why Restarting Wilkins Helps?
The Wilkins service manages the core functionalities of the dimensioner, including:
- Communication with sensors (cameras and scales).
- Data synchronization with Wilkins and Magaya.
- Processing and storing measurement results.
When experiencing issues such as:
- The dimensioner not responding.
- Errors in measurement processing.
- Camera or scale detection failures.
- Connection issues with Wilkins or Magaya.
A simple restart of the Wilkins service can often restore functionality without further troubleshooting.
2.2. Restarting Wilkins Service
To restart the Wilkins service, follow these steps:
- Open the Terminal on the dimensioner’s CPU.
- Type the following command and press Enter:
systemctl restart wilkins
This command stops and restarts the Wilkins service, reinitializing its processes.
2.3. Verify the Restart
After running the restart command:
- Wait a few seconds for the service to fully restart.
- Check the status of the dimensioner by running:
docker logs dimensioner-runner -f - Ensure there are no new errors and that the sensors (cameras and scales) are detected correctly.
2.4. What to Do If the Issue Persists?
If restarting Wilkins does not solve the issue, consider:
- Checking logs for specific errors.
- Restarting the CPU to fully reset hardware components.
- Inspecting physical connections of cameras and scales.
- Escalating the issue if necessary.
Important: While restarting Wilkins is a quick fix for many issues, it does not resolve hardware failures or network-related problems. If issues persist after a restart, further investigation is needed.