New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
edit-config SEGFAULT #720
Comments
Hi Michal, I am trying to reproduce the issue. I had to make following modifications to successfully walk through all steps:
diff --git a/keystored/keystored.c b/keystored/keystored.c
index 45872df..87d7ef9 100644
--- a/keystored/keystored.c
+++ b/keystored/keystored.c
@@ -420,7 +420,7 @@ ks_privkey_load_cb(const char *UNUSED(xpath), const sr_node_t *input, const size
{
struct keystored_ctx *ctx = (struct keystored_ctx *)private_ctx;
pid_t pid;
- int ret, status, len, fd;
+ int ret = 0, status, len, fd;
char *priv_path = NULL, *pub_path = NULL;
FILE *privkey = NULL;
with these changes all steps passes and sysrepod survives
do you have any suggestions that might help to reproduce the issue? thanks, |
Hi Lukas,
I have now committed first version of instructions for server configuration, so please look at the beginning to learn how to enable it, because it is required here. Also, the XMLs are committed too now. If you have any problems, it would probably be best if we communicate directly, it has not been checked or tried by anyone but me. I will also mentioned that the first crash I experienced was after some additional Regards, |
Hi, I am still not able to reproduce the issue locally, however I've noticed one more thing: according to the logs sysrepo was sending Lukas |
Hi, no, in the branch I used there are no notifications yet. If you can't reproduce it, you can hardly debug it, so nevermind for now. If we learn more, I'll let you know. Regards, |
Hi,
I encountered a sysrepo crash, this is the output with
valgrind
:steps.zip
Steps to reproduce are included in the attachment, there are relatively complex. Also, when I tried running
sysrepo
withvalgrind
and connected to it with (started)netopeer2-server
, every few triessysrepo
got stuck and could have only been terminated by sending SIGKILL (which may hint a lock problem). The server then failed with:I have not investigated this further, but I can start a separate issue if you prefer.
Regards,
Michal
The text was updated successfully, but these errors were encountered: