…debug during first run as it helps in troubleshooting. When the system is configured and declared as stable, information log level will be sufficient. If you prefer saving log information into a database instead of a file, see the Database configuration chapter before changing the directive server.logging.destination = database. # IP address and port for server listening server.bind_ip = 0.0.0.0…
Search: troubleshooting
6 results
…add-language-pack=<path> – Add custom LID language pack from specified directory. Language pack name will be same as dirctory name. delete-language-pack – Delete custom LID language pack Support hwgen[=<file>] – Create machine HW profile file report – Create SPE report useful for troubleshooting and diagnostics. Report contains configuration, logs, licences and hardware profile of current computer. Migration from legacy version upgrade…
…Quick Start Guide Using the Application Interpretation of Results Description of Other Inbuilt Tools Troubleshooting In case of any problems or questions, please first search the manual for relevant keywords. If you don’t find an answer in the manual, contact our support. You can also browse the FAQ section or use the search function of the Partner Portal and look…
…can be useful to use a shared license file to simplify the maintenance. Logging server.logging.level # Server logging # Level (trace, debug, information, warning, error, fatal) server.logging.level = debug Controls the logging verbosity. Follows the Apache Commons Logging levels – trace is the most verbose log output, fatal is the least verbose. Default value is debug. For troubleshooting or first…
Good understanding of SPE directory structure helps to better understand the inner workings of SPE and simplifies troubleshooting. It’s also useful for expert-level tuning of parameters of individual technologies and optimizing SPE configuration e.g. for deployments with shared resources, or deployments in virtualized environments, etc. The SPE directory structure looks like this (the tree depth is limited for better readability):…
…may cause the initialization to actually take longer than if only single thread would be used. The downside of multi-threaded initialization is somehow messy log file ;-), since the messages are written to the log as they come, making the eventual troubleshooting more difficult (nevertheless, each such message is marked by corresponding thread number). Therefore this configuration is more suitable…