Skip to content

Could not connect to nano service. Path: /dev/shm/check-point/cp-nano-http-transaction-handler-3_secondary, Error: No such file or directory #66

Description

@mendark123

Hello,
I have this scenario:
I have NPMPlus with openappsec with token. But after last update at npmplus i get this error on npmplus container:
|2026-05-25T22:57:46.787: init_signaling_socket@ngx_cp_initializer.c:447 [uid 3 | pid 292] <session id 63> | Paired affinity disabled, sending target_core=-1 to service
|2026-05-25T22:57:46.795: init_signaling_socket@ngx_cp_initializer.c:476 [uid 3 | pid 292] <session id 63> | Successfully connected on client socket 7
|2026-05-25T22:57:46.795: init_signaling_socket@ngx_cp_initializer.c:501 [uid 3 | pid 292] <session id 63> | Could not connect to nano service. Path: /dev/shm/check-point/cp-nano-http-transaction-handler-3_secondary, Error: No such file or directory

And also openappsec didn't work.
Also i get this error when i start npmplus container:
|2026-05-25T21:51:37.211: remove_attachment_metadata_file@ngx_cp_initializer.c:141 [uid | pid 292] | Attachment metadata file does not exist: /dev/shm/attachment-metadata
entering fini worker. is_timer_active=0, ngx_exiting=1

Thank you

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions