Skip to content
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

Segfault upon read #38

Closed
baasman opened this issue Oct 10, 2018 · 2 comments
Closed

Segfault upon read #38

baasman opened this issue Oct 10, 2018 · 2 comments

Comments

@baasman
Copy link

baasman commented Oct 10, 2018

This morning I kept running into the following error when using the following query:

    queries = [
        {
            'FindEntity': {
                '_ref': 1,
                'class': 'Study',
                'constraints': {
                    'AccessionNumber': ['==', accession_number],
                },
            },
        },
        {
            'FindEntity': {
                '_ref': 2,
                'class': 'Series',
                'link': {
                    'ref': 1
                }
            },
        },
        {
            'FindImage': {
                'link': {
                    'ref': 2
                },
            }
        }
    ]
Oct 10 10:15:38 ykmits1 chdi_run_server.sh: Connection received...
Oct 10 10:15:38 ykmits1 chdi_run_server.sh: ch_tx_total: 32 [ms]
Oct 10 10:15:38 ykmits1 chdi_run_server.sh: ch_tx_query: 32 [ms]
Oct 10 10:15:38 ykmits1 chdi_run_server.sh: ch_tx_send: 0 [ms]
**Oct 10 10:15:38 ykmits1 kernel: vdms[23044]: segfault at 1 ip 00007f3a84d60bfa sp 00007f3a77c9ce38 error 4 in libpmgd.so[7f3a84d25000+60000]**
Oct 10 10:15:38 ykmits1 chdi_run_server.sh: /data/vdms/vdms/chdi_run_server.sh: line 32: 23043 Segmentation fault      ./vdms 2>> $VDM_LOG_ERR
Oct 10 10:15:38 ykmits1 systemd: vdms.service: main process exited, code=exited, status=139/n/a
Oct 10 10:15:38 ykmits1 systemd: Unit vdms.service entered failed state.
Oct 10 10:15:38 ykmits1 systemd: vdms.service failed.

However, after rebuilding the db directory the problem went away.

@luisremis
Copy link
Contributor

We will include this fix soon, it is related to #12
Thanks!

@luisremis
Copy link
Contributor

Fix in #71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants