Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] collectd segfaults on launch
@ 2021-03-12 14:11 xandkar
  2021-03-12 20:09 ` ericonr
                   ` (15 more replies)
  0 siblings, 16 replies; 17+ messages in thread
From: xandkar @ 2021-03-12 14:11 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

New issue by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413

Description:
### System

* xuname:  
  `Void 5.10.23_1 x86_64 AuthenticAMD uptodate rFFFF`
* package:  
  `collectd-5.12.0_3`

### Expected behavior

Collectd service starts without crashing.

### Actual behavior

Collectd segfaults on start.

### Steps to reproduce the behavior

Install package:
```
# xbps-install collectd
```

Watch dmesg in terminal A:
```
# dmesg --follow
```

Enable collectd service in terminal B
```
# ln -s /etc/sv/collectd /var/service/
```

Observe segfault messages in terminal A, such as:
```
...
[  336.630494] collectd[6990]: segfault at 14 ip 00007f79c4ec4c99 sp 00007fffedc6adf0 error 4 in libc-2.32.so[7f79c4e06000+14a000]
[  336.630497] Code: 39 d5 0f 8e d1 01 00 00 48 63 c2 eb 15 0f 1f 40 00 8d 56 01 48 83 c0 01 89 13 39 c5 0f 8e b7 01 00 00 49 8b 0c c4 89 c6 89 c2 <80> 39 2d 75 e2 80 79 01 00 74 dc 8b 03 89 53 30 e9 26 fe ff ff 66
...
```

ATTN: @stpx 

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
@ 2021-03-12 20:09 ` ericonr
  2021-03-12 23:35 ` xandkar
                   ` (14 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: ericonr @ 2021-03-12 20:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-797726150

Comment:
Did you start using the service now or is it happening after the latest update? It could be having some issues after the OpenSSL switch.

Do you still have anything from libressl on your system? What do `xbps-query -s libssl` and `xbps-query -s libcrypto` show?

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
  2021-03-12 20:09 ` ericonr
@ 2021-03-12 23:35 ` xandkar
  2021-03-13  0:01 ` ericonr
                   ` (13 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-12 23:35 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-797814109

Comment:
Looks like I did have `libcrypto46` lingering[1], so I just removed it, but the problem persists.

```
$ xbps-query -s libssl
[*] libssl1.1-1.1.1j_2 Toolkit for Secure Sockets Layer and Transport Layer Security - SSL/TLS library

$ xbps-query -s libcrypto
[*] libcrypto1.1-1.1.1j_2 Toolkit for Secure Sockets Layer and Transport Layer Security - crypto library
[*] libcrypto46-3.1.5_2   Version of the TLS/crypto stack forked from OpenSSL - crypto library
```

This was the first time I installed the package/service, so I never had it in a working state (on Void).

[1]: I now remember installing it manually to run something which was linked to it.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
  2021-03-12 20:09 ` ericonr
  2021-03-12 23:35 ` xandkar
@ 2021-03-13  0:01 ` ericonr
  2021-03-13  1:20 ` xandkar
                   ` (12 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: ericonr @ 2021-03-13  0:01 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-797820988

Comment:
Can you try to run it in the command line and see if it also segfaults? I couldn't reproduce the issue locally. Does your `/etc/collectd.conf` have anything that might be relevant?

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (2 preceding siblings ...)
  2021-03-13  0:01 ` ericonr
@ 2021-03-13  1:20 ` xandkar
  2021-03-14 14:00 ` xandkar
                   ` (11 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-13  1:20 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-797841081

Comment:
Same result when executed directly. `/etc/collectd.conf` is as it came from the package - unmodified.

Now I'm wondering if it could be related to the CPU (I have AMD Ryzen 9 5950X) - will try tomorrow with a fresh install on an Intel-chipped laptop.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (3 preceding siblings ...)
  2021-03-13  1:20 ` xandkar
@ 2021-03-14 14:00 ` xandkar
  2021-03-14 14:43 ` ericonr
                   ` (10 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-14 14:00 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-798912858

Comment:
Tried with a fresh install on Celeron N4000 laptop. It doesn't segfault, but exits immediately with status code 1.
I enabled socklog and ran directly as:

-  `collectd -ft` -> exit code 0 :heavy_check_mark: 
- `collectd -fT` -> exit code 1 :x: 

Commented-out all plugins except syslog from `/etc/collectd.conf`, but result is the same.

Log messages just say that plugins are `successfully loaded`, one by one.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (4 preceding siblings ...)
  2021-03-14 14:00 ` xandkar
@ 2021-03-14 14:43 ` ericonr
  2021-03-14 15:10 ` leahneukirchen
                   ` (9 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: ericonr @ 2021-03-14 14:43 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-798919556

Comment:
IIRC I had to uncomment the localhost line for it to "run", just as `collectd -f`. And it didn't exit or anything.

At a guess, it may be trying to do something funky with the amount of available CPU cores.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (5 preceding siblings ...)
  2021-03-14 14:43 ` ericonr
@ 2021-03-14 15:10 ` leahneukirchen
  2021-03-14 17:45 ` xandkar
                   ` (8 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: leahneukirchen @ 2021-03-14 15:10 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 211 bytes --]

New comment by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-798924061

Comment:
Please install `collectd-dbg` and show a backtrace using gdb.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (6 preceding siblings ...)
  2021-03-14 15:10 ` leahneukirchen
@ 2021-03-14 17:45 ` xandkar
  2021-03-14 22:02 ` ericonr
                   ` (7 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-14 17:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3631 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-798948234

Comment:
So on the fresh machine I just installed all the packages that the original-problem-machine has and it now segfaults as well, so looks like some sort of a dependency conflict.

@ericonr Indeed, with the localhost line uncommented - it doesn't crash on either machine anymore! I reinstalled Void (on the Intel machine) again and now see the log line warning about failed  FQDNLookup in `/var/log/socklog/everything/current`, which I must've missed earlier.

Summary:
- localhost, base-pkgs -> ok :heavy_check_mark: 
- localhost, base-pkgs + extra-pkgs -> ok :heavy_check_mark: 
- no-localhost, base-pkgs -> error, but no segfault either :warning: 
- no-localhost, base-pkgs + extra-pkgs -> segfault :x: 

@leahneukirchen Thanks. Here you go:

```
Reading symbols from collectd...
Reading symbols from /usr/lib/debug//usr/bin/collectd...
(gdb) run
Starting program: /usr/bin/collectd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7eadc99 in _getopt_internal_r (argc=argc@entry=10, argv=argv@entry=0x7fffffffd930, optstring=optstring@entry=0x555555571657 "BhtTfC:P:", longopts=longopts@entry=0x0, longind=longind@entry=0x0, long_only=long_only@entry=0,
    d=0x7ffff7f8c3e0 <getopt_data>, posixly_correct=0) at getopt.c:517
517     getopt.c: No such file or directory.
(gdb) bt
#0  0x00007ffff7eadc99 in _getopt_internal_r (argc=argc@entry=10, argv=argv@entry=0x7fffffffd930, optstring=optstring@entry=0x555555571657 "BhtTfC:P:", longopts=longopts@entry=0x0, longind=longind@entry=0x0, long_only=long_only@entry=0,
    d=0x7ffff7f8c3e0 <getopt_data>, posixly_correct=0) at getopt.c:517
#1  0x00007ffff7eae011 in _getopt_internal (argc=argc@entry=10, argv=argv@entry=0x7fffffffd930, optstring=optstring@entry=0x555555571657 "BhtTfC:P:", longopts=longopts@entry=0x0, longind=longind@entry=0x0, long_only=long_only@entry=0, posixly_correct=0)
    at getopt.c:711
#2  0x00007ffff7eae053 in getopt (argc=argc@entry=10, argv=argv@entry=0x7fffffffd930, optstring=optstring@entry=0x555555571657 "BhtTfC:P:") at getopt.c:735
#3  0x000055555555b2b9 in read_cmdline (config=<synthetic pointer>, argv=0x7fffffffd930, argc=10) at src/daemon/collectd.c:310
#4  init_config (argc=10, argv=0x7fffffffd930) at src/daemon/collectd.c:396
#5  0x00007ffff5e7e15e in config_is_mdns_suffix () from /usr/lib/libnss_mdns.so.2
#6  0x00007ffff5e7e280 in ?? () from /usr/lib/libnss_mdns.so.2
#7  0x00007ffff7eb07e9 in gaih_inet (name=<optimized out>, name@entry=0x7fffffffe070 "citadel", service=service@entry=0x0, req=req@entry=0x7fffffffe0d0, pai=pai@entry=0x7fffffffdb18, naddrs=naddrs@entry=0x7fffffffdb14, tmpbuf=tmpbuf@entry=0x7fffffffdc10)
    at ../sysdeps/posix/getaddrinfo.c:838
#8  0x00007ffff7eb1425 in __GI_getaddrinfo (name=<optimized out>, name@entry=0x7fffffffe070 "citadel", service=<optimized out>, service@entry=0x0, hints=hints@entry=0x7fffffffe0d0, pai=pai@entry=0x7fffffffe0c8) at ../sysdeps/posix/getaddrinfo.c:2244
#9  0x000055555555b5f8 in init_hostname () at src/daemon/collectd.c:96
#10 init_global_variables () at src/daemon/collectd.c:135
#11 configure_collectd (config=<synthetic pointer>) at src/daemon/collectd.c:381
#12 init_config (argc=<optimized out>, argv=0x7fffffffe6c8) at src/daemon/collectd.c:406
#13 0x000055555555a771 in main (argc=<optimized out>, argv=<optimized out>) at src/daemon/cmd.c:167
(gdb)

```

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (7 preceding siblings ...)
  2021-03-14 17:45 ` xandkar
@ 2021-03-14 22:02 ` ericonr
  2021-03-15  9:07 ` xandkar
                   ` (6 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: ericonr @ 2021-03-14 22:02 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 185 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-798988130

Comment:
Can you show a list of the extra packages?

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (8 preceding siblings ...)
  2021-03-14 22:02 ` ericonr
@ 2021-03-15  9:07 ` xandkar
  2021-03-15  9:09 ` xandkar
                   ` (5 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-15  9:07 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 274 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-799247743

Comment:
@ericonr Here's a diff from base to base+extra (technically minus some stuff too): https://xandkar.net/tmp/base-to-base+extra.patch

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (9 preceding siblings ...)
  2021-03-15  9:07 ` xandkar
@ 2021-03-15  9:09 ` xandkar
  2021-03-15  9:16 ` xandkar
                   ` (4 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-15  9:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 221 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-799249254

Comment:
It's a diff of `xbps-query -l | awk '{print $2}' | sort -u` from each machine.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (10 preceding siblings ...)
  2021-03-15  9:09 ` xandkar
@ 2021-03-15  9:16 ` xandkar
  2021-03-15  9:16 ` xandkar
                   ` (3 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-15  9:16 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-799247743

Comment:
@ericonr Here's a diff of `xbps-query -l | awk '{print $2}' | sort -u` on each machine, from base to base+extra (technically minus some stuff too): https://xandkar.net/tmp/base-to-base+extra.patch

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (11 preceding siblings ...)
  2021-03-15  9:16 ` xandkar
@ 2021-03-15  9:16 ` xandkar
  2021-09-24 18:27 ` ericonr
                   ` (2 subsequent siblings)
  15 siblings, 0 replies; 17+ messages in thread
From: xandkar @ 2021-03-15  9:16 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 221 bytes --]

New comment by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-799249254

Comment:
It's a diff of `xbps-query -l | awk '{print $2}' | sort -u` from each machine.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (12 preceding siblings ...)
  2021-03-15  9:16 ` xandkar
@ 2021-09-24 18:27 ` ericonr
  2022-05-07  2:06 ` github-actions
  2022-05-10  2:47 ` [ISSUE] [CLOSED] " ericonr
  15 siblings, 0 replies; 17+ messages in thread
From: ericonr @ 2021-09-24 18:27 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-926837653

Comment:
I just noticed your `libnss_mdns` isn't from `nss-mdns`, but rather from `mDNSResponder`. Can you try uninstalling that package? It might be doing something wonky.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (13 preceding siblings ...)
  2021-09-24 18:27 ` ericonr
@ 2022-05-07  2:06 ` github-actions
  2022-05-10  2:47 ` [ISSUE] [CLOSED] " ericonr
  15 siblings, 0 replies; 17+ messages in thread
From: github-actions @ 2022-05-07  2:06 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/29413#issuecomment-1120110168

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: [ISSUE] [CLOSED] collectd segfaults on launch
  2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
                   ` (14 preceding siblings ...)
  2022-05-07  2:06 ` github-actions
@ 2022-05-10  2:47 ` ericonr
  15 siblings, 0 replies; 17+ messages in thread
From: ericonr @ 2022-05-10  2:47 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

Closed issue by xandkar on void-packages repository

https://github.com/void-linux/void-packages/issues/29413

Description:
### System

* xuname:  
  `Void 5.10.23_1 x86_64 AuthenticAMD uptodate rFFFF`
* package:  
  `collectd-5.12.0_3`

### Expected behavior

Collectd service starts without crashing.

### Actual behavior

Collectd segfaults on start.

### Steps to reproduce the behavior

Install package:
```
# xbps-install collectd
```

Watch dmesg in terminal A:
```
# dmesg --follow
```

Enable collectd service in terminal B
```
# ln -s /etc/sv/collectd /var/service/
```

Observe segfault messages in terminal A, such as:
```
...
[  336.630494] collectd[6990]: segfault at 14 ip 00007f79c4ec4c99 sp 00007fffedc6adf0 error 4 in libc-2.32.so[7f79c4e06000+14a000]
[  336.630497] Code: 39 d5 0f 8e d1 01 00 00 48 63 c2 eb 15 0f 1f 40 00 8d 56 01 48 83 c0 01 89 13 39 c5 0f 8e b7 01 00 00 49 8b 0c c4 89 c6 89 c2 <80> 39 2d 75 e2 80 79 01 00 74 dc 8b 03 89 53 30 e9 26 fe ff ff 66
...
```

ATTN: @stpx 

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2022-05-10  2:47 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-12 14:11 [ISSUE] collectd segfaults on launch xandkar
2021-03-12 20:09 ` ericonr
2021-03-12 23:35 ` xandkar
2021-03-13  0:01 ` ericonr
2021-03-13  1:20 ` xandkar
2021-03-14 14:00 ` xandkar
2021-03-14 14:43 ` ericonr
2021-03-14 15:10 ` leahneukirchen
2021-03-14 17:45 ` xandkar
2021-03-14 22:02 ` ericonr
2021-03-15  9:07 ` xandkar
2021-03-15  9:09 ` xandkar
2021-03-15  9:16 ` xandkar
2021-03-15  9:16 ` xandkar
2021-09-24 18:27 ` ericonr
2022-05-07  2:06 ` github-actions
2022-05-10  2:47 ` [ISSUE] [CLOSED] " ericonr

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).