[BUG] Error opening plugin module; module='cloud_auth'

Open
#23 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
centos, docker, linux

Research direction

Reproduce the failure in the linuxserver/syslog-ng container using the documented syslog-ng command and package/etc/conf.d/conflib/syslog/app-syslog-vmware_vsphere.conf. Investigate why the cloud_auth plugin cannot load its relocation symbol in the stated CentOS 7 environment. Done means syntax checking completes without the cloud_auth error.

Written by the indexing model from the issue text.

Description

bug work-in-progress
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

When using syslog-ng -s -f <filename> to check the syntax of files the following error is being generated

Error opening plugin module; module='cloud_auth', error='Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found'

Expected Behavior

Syntax checking to occur without error

Steps To Reproduce
  1. curl -LO https://github.com/splunk/splunk-connect-for-syslog/archive/refs/tags/v3.19.1.tar.gz
  2. gunzip v3.19.1.tar.gz
  3. tar -xf v3.19.1.tar
  4. cd splunk-connect-for-syslog-3.19.1/
  5. syslog-ng -s -f ./package/etc/conf.d/conflib/syslog/app-syslog-vmware_vsphere.conf
Environment
- OS: centos7
- How docker service was installed: yum
CPU architecture

x86-64

Docker creation
docker container run -itd --rm --name sc4s linuxserver/syslog-ng:latest

docker exec -it sc4s bash
Container logs
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...
crond[168]: crond (busybox 1.36.1) started, log level 5
[ls.io-init] done.
Dominant language
Dockerfile
Stars
86
Forks
9
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxserver/docker-syslog-ng

All issues in linuxserver/docker-syslog-ng

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.