There is no standard configuration config.js when cal

<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clip

Segfault on error s in configuration or runtime errors while parsing the configuration about struswebservice HOT 4 OPEN

andreasbaumann commented on August 24, 2024

Segfault on error s in configuration or runtime errors while parsing the configuration

from struswebservice.

Comments (4)

andreasbaumann commented on August 24, 2024

Seems like if the logfile cannot be written, a runtime exception is thrown. The error code assumes
there is always a strus message to be fetched, which is wrong.

from struswebservice.

andreasbaumann commented on August 24, 2024

Why should there be a second logging facility just for the requests:

        "logging" : {
                "level" : "debug",
                "file" : {
                        "name":         "./strusWebService.log",
                        "append":       true
                }
        },

        "debug" : {
                "log_requests": true,
                "struct_depth": 4,
                "request_file": "./requests.log",
                "protocol" : {
                        "pretty_print":         true,
                        "quit_enabled":         true,
                        "debug_enabled":        true
                }
        }

from struswebservice.

andreasbaumann commented on August 24, 2024

    "extensions" : {
            "directory" : "@STRUS_MODULE_PATH@",

is not even checked if directory is actually a vaild and accesible directory.

from struswebservice.

andreasbaumann commented on August 24, 2024

starting the logger should maybe not happen while parsing the configuration. The traditional approach
is to have a basic logger (for instance for stderr only) and then to replace it afterwards.

from struswebservice.

Related Issues (20)

valgrind shows tons of errors HOT 4
strusUtilities and strusRpcServer cannot run on the storages managed by the webservice HOT 3
have an auto-commit parameter for dumb clients HOT 2
cannot query only with restriction features HOT 1
better error reporting in log HOT 6
Busy after restart of web service HOT 3
Suddenly high memory usage HOT 11
CPU usage is pretty high HOT 2
crash in live system HOT 2
during startup there is a lock race HOT 1
multiple summarizers with same name HOT 4
segfault out of the blue HOT 2
high disk and memory usage HOT 3
config test fails HOT 1
Shutdown of strusWebService results in weird errors HOT 3
global index locking during commit blocks queries HOT 1
strusWebService stops on query with stack smashing error HOT 3
The strus webservice does not handle '*/*' as 'Accept' parameter correctly.
Transaction is disposed after an error in a request addressing it HOT 1

Segfault on error s in configuration or runtime errors while parsing the configuration about struswebservice HOT 4 OPEN

Comments (4)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent