PIXILAB Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
blocks:drivers:troubleshooting [2018-03-07 20:11]
admin [Increasing the Log Level] 		blocks:drivers:troubleshooting [2024-10-25 06:00] (current)
admin Bad link
Line 10: Line 10:
 If a driver doesn't work at all, check the log file of the computer running Blocks. This file is located here, under the home directory of the user under which Blocks is running: If a driver doesn't work at all, check the log file of the computer running Blocks. This file is located here, under the home directory of the user under which Blocks is running:
  
- PIXILAN-root/logs/latest.log+ PIXILAB-Blocks-root/logs/latest.log
  
 Open a terminal window ("Terminal" on MacOS or Linux and "Powershell" on Windows). Use the //cd// command to move into the "logs" directory mentioned above. Then type the following command on MacOS: Open a terminal window ("Terminal" on MacOS or Linux and "Powershell" on Windows). Use the //cd// command to move into the "logs" directory mentioned above. Then type the following command on MacOS:
Line 50: Line 50:
 ==== Increasing the Log Level ==== ==== Increasing the Log Level ====
  
-Most troubleshooting methods involve viewing Blocks log file. By default, this log file contains only errors encountered while running Blocks. In some cases, you may want to increase the verbosity of the logging. This can be done by adding the following lines to a file named //config.yml//, located in the //PIXILAN-root// directory in the home directory of the current user:+Most troubleshooting methods involve viewing Blocks log file. By default, this log file contains only errors encountered while running Blocks. In some cases, you may want to increase the verbosity of the logging. This can be done by adding the following lines to a file named //config.yml//, located in the //PIXILAB-Blocks-root// directory in the home directory of the current user:
  
 <code> <code>
Line 56: Line 56:
 logging: logging:
   loggers:   loggers:
-    pixi.pl.cortex.script.Script: INFO  # Verbose logging for scripts/drivers+    Script: INFO  # Verbose logging for scripts/drivers
 </code> </code>
  
Line 64: Line 64:
 ===== Viewing the Log Remotely ===== ===== Viewing the Log Remotely =====
  
-While a separate development computer is preferable for driver development, you may sometimes run into issues with a production server, requiring you to access its log file. If so, you can either access the server locally, viewing the log file as described above. Or you can access the log file remotely, as described [[blocks:server:advanced_server_configuration#viewing_logs|here]].+While a separate development computer is preferable for driver development, you may sometimes run into issues with a production server, requiring you to access its log file. If so, you can either access the server locally, viewing the log file as described above. Or you can access the log file remotely, as described [[blocks:server:advanced_server_configuration#viewing_logs_in_webmin|here]].
  
 ==== Archived Log Files ==== ==== Archived Log Files ====
Line 72: Line 72:
 ===== Reloading Changes Automatically ===== ===== Reloading Changes Automatically =====
  
-When you change drivers, you must normally restart Blocks for those changes to take effect. As this can make the development more time consuming, and alternative is to enable automatic reloading of scripts. This is also done in the //config.yml// file mentioned above, by adding the following lines:+When you change drivers, you must normally restart Blocks for those changes to take effect. As this can make the development more time consuming, an alternative is to enable automatic reloading of scripts. This is also done in the //config.yml// file mentioned above, by adding the following lines:
  
 <code> <code>