Closed Optiqus closed 3 years ago
[Optiqus]
/usr/local/bin/ezstream -c /etc/ezstream/ezstream.xml ezstream[31038]: /etc/ezstream/ezstream.xml: world readable Segmentation Error How to solve the problem?
Perhaps 'valgrind /usr/local/bin/ezstream -c /etc/ezstream/ezstream.xml' can provide some insight into why it segfaults.
-- Happy hacking Petter Reinholdtsen
root@irather:~# valgrind /usr/local/bin/ezstream -c /etc/ezstream/ezstream.xml ==10007== Memcheck, a memory error detector ==10007== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==10007== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==10007== Command: /usr/local/bin/ezstream -c /etc/ezstream/ezstream.xml ==10007== ezstream[10007]: /etc/ezstream/ezstream.xml: world readable ==10007== Invalid read of size 1 ==10007== at 0x4C2EDA2: strlen (vg_replace_strmem.c:454) ==10007== by 0x58A63AD: strdup (strdup.c:41) ==10007== by 0x116321: xstrdup_c (xalloc.c:75) ==10007== by 0x115E1D: util_strrcasecmp (util.c:231) ==10007== by 0x10AE8A: main (ezstream.c:797) ==10007== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==10007== ==10007== ==10007== Process terminating with default action of signal 11 (SIGSEGV) ==10007== Access not within mapped region at address 0x0 ==10007== at 0x4C2EDA2: strlen (vg_replace_strmem.c:454) ==10007== by 0x58A63AD: strdup (strdup.c:41) ==10007== by 0x116321: xstrdup_c (xalloc.c:75) ==10007== by 0x115E1D: util_strrcasecmp (util.c:231) ==10007== by 0x10AE8A: main (ezstream.c:797) ==10007== If you believe this happened as a result of a stack ==10007== overflow in your program's main thread (unlikely but ==10007== possible), you can try to increase the size of the ==10007== main thread stack using the --main-stacksize= flag. ==10007== The main thread stack size used in this run was 8388608. ==10007== ==10007== HEAP SUMMARY: ==10007== in use at exit: 45,266 bytes in 170 blocks ==10007== total heap usage: 732 allocs, 562 frees, 245,967 bytes allocated ==10007== ==10007== LEAK SUMMARY: ==10007== definitely lost: 0 bytes in 0 blocks ==10007== indirectly lost: 0 bytes in 0 blocks ==10007== possibly lost: 0 bytes in 0 blocks ==10007== still reachable: 45,266 bytes in 170 blocks ==10007== suppressed: 0 bytes in 0 blocks ==10007== Rerun with --leak-check=full to see details of leaked memory ==10007== ==10007== For counts of detected and suppressed errors, rerun with: -v ==10007== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Segmentation Error
@Optiqus, thanks for the report. Please make sure to change your source client password, if the one provided in this report is the real one.
The workaround for your issue is to either remove the <name/>
from your intake, or configure it properly in your <stream/>
. The fix will be a proper error message instead of a crash.
FYI: there is an inconsistency in your configuration file. The intake type is "file", but the filename looks like a playlist and not a single media file.
Fixed in develop.
I am also getting random segfaults and I do not have
The issue here is understood and fixed in 1.0.2. If you're still having issues, it's a separate problem and I need more information in a separate bug report. Thanks!
Collected the latest version of ezstream from the source code. Did not use the options in ./configure. Starting ezstream fails: /usr/local/bin/ezstream -c /etc/ezstream/ezstream.xml ezstream[31038]: /etc/ezstream/ezstream.xml: world readable Segmentation Error How to solve the problem? Debian GNU/Linux 9 Linux 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64 GNU/Linux
Compile from source code: