You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed on the hedgehog this error when starting arkime in the logs:
arkime_mlockall_init(): WARNING: memlock in limits.conf must be unlimited or at least 4000000, currently 64
Although the limit is being set correctly in the security limits.conf, etc., this apparently did not take effect when being started from rc.local on startup.
Malcolm v5.0.1 is a patch release with minor bug and security fixes.
* Bugs addressed:
* Very large pcaps don't get proccesed idaholab#44
* pcap files with colon (:) in the name don't process correctly idaholab#2
* turning off AUTO_TAG feature disables tagging altogether idaholab#12
* recent debinterfaces release broke configure-interfaces.py idaholab#48
* opensearch indexes in yellow state idaholab#67
* arkime capture gives mlockall_init() warning on startup idaholab#66
* Security vulnerabilities addressed:
* mitigations for CVE-2021-44228 (log4shell) idaholab#68
* Other
* bumped Arkime from [v3.1.1 to v3.2.0](https://github.com/arkime/arkime/blob/v3.2.0/CHANGELOG#L25-L40)
* bumped OpenSearch to [v1.2.1](https://opensearch.org/blog/releases/2021/12/update-to-1-2-1/)
* switched from [elasticsearch](https://pypi.org/project/elasticsearch-dsl/) to [opensearch](https://pypi.org/project/opensearch-dsl/) python client libraries
* write contributor's guide for source code contributions/modifications idaholab#25
* handle new fields in ethernet/IP logs (cisagov/icsnpp-enip@c4ae505)
* use more recognizable dashboards logo for OpenSearch dashboards launcher in Malcolm ISO
* include patches used to build Arkime Dockerfile when building Arkime for hedgehog as well
* build Zeek spicy analyzers from their various repos rather than the zeek/spicy-analyzer meta-repo
I noticed on the hedgehog this error when starting arkime in the logs:
arkime_mlockall_init(): WARNING: memlock in limits.conf must be unlimited or at least 4000000, currently 64
Although the limit is being set correctly in the security limits.conf, etc., this apparently did not take effect when being started from rc.local on startup.
mmguero-dev/Malcolm@19d2a63 and mmguero-dev/Malcolm@a0aad3a address this issue in various startup scenarios.
The text was updated successfully, but these errors were encountered: