Kernel log analyzer - plex errors

Plex Media Server NAS & Devices
1

not sure what to make of these errors from the qnap diagnostic - kernel log analyzer.

Plex Transcoder[17435]: segfault at 18 ip007feec4605634 sp007fffa8454ff0 error 4 in libavcodec.so.58[7feec43c0+3e0] – Count:0
Plex Transcoder[24222]: segfault at 18 ip007fcd58864634 sp007ffea7099490 error 4 in libavcodec.so.58[7fcd58620+3e0] – Count:0
Plex Media Scan[31845]: segfault at 0 ip004f816f sp007ffff36c5bf0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[5229]: segfault at 0 ip004f816f sp007fff0c5d8 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[21668]: segfault at 0 ip004f816f sp007ffce0f7d970 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[26805]: segfault at 0 ip004f816f sp007fffe7dbd470 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[11432]: segfault at 0 ip004f816f sp007ffc904ac0f0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[27976]: segfault at 0 ip004f816f sp007fff0ce95470 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Transcoder[26074]: segfault at 18 ip007f4d1a12c634 sp007fffbf26be60 error 4 in libavcodec.so.58[7f4d19ef0+3e0] – Count:0
Plex Media Scan[22415]: segfault at 0 ip004f816f sp007ffcb7b2f5e0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[28578]: segfault at 0 ip004f816f sp007fff033e4540 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Serv[23429]: segfault at 7f0a312d2032 ip007fbdaf99def4 sp007fbcf540cad8 error 4 in libc-2.21.so[7fbdaf920+190] – Count:0
Plex Media Scan[5946]: segfault at 0 ip004f816f sp007ffee5706 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[6024]: segfault at 0 ip004f816f sp007ffcc2110680 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[30373]: segfault at 0 ip004f816f sp007fffe71555a0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[30647]: segfault at 0 ip004f816f sp007ffd3d8b6060 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[16145]: segfault at 0 ip004f816f sp007fff1ea1f error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[13421]: segfault at 0 ip004f816f sp007ffca33c7820 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[22417]: segfault at 0 ip004f816f sp007fffd28a4 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[11115]: segfault at 0 ip004f816f sp007ffe989f9b40 error 4 in Plex Media Scanner[430+3f0] – Count:0

2

Which version of PMS?

PMS 1.18.0 has corrected several of the Scanner “segfault” problems.

3

1.18.1.1788 i was given a little while back for testing with other issues.

should i try 1.18.0.1846 now?

4

Yes. Please keep the copy you were given handy but try the new 1.18.0. Several segfaults were corrected

5

ok ill give it a try shortly.

Can you give me some details on what these errors are

6

installed and run diag.

Plex Transcoder[17435]: segfault at 18 ip007feec4605634 sp007fffa8454ff0 error 4 in libavcodec.so.58[7feec43c0+3e0] – Count:0
Plex Transcoder[24222]: segfault at 18 ip007fcd58864634 sp007ffea7099490 error 4 in libavcodec.so.58[7fcd58620+3e0] – Count:0
Plex Media Scan[31845]: segfault at 0 ip004f816f sp007ffff36c5bf0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[5229]: segfault at 0 ip004f816f sp007fff0c5d8 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[21668]: segfault at 0 ip004f816f sp007ffce0f7d970 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[26805]: segfault at 0 ip004f816f sp007fffe7dbd470 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[11432]: segfault at 0 ip004f816f sp007ffc904ac0f0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[27976]: segfault at 0 ip004f816f sp007fff0ce95470 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Transcoder[26074]: segfault at 18 ip007f4d1a12c634 sp007fffbf26be60 error 4 in libavcodec.so.58[7f4d19ef0+3e0] – Count:0
Plex Media Scan[22415]: segfault at 0 ip004f816f sp007ffcb7b2f5e0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[28578]: segfault at 0 ip004f816f sp007fff033e4540 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Serv[23429]: segfault at 7f0a312d2032 ip007fbdaf99def4 sp007fbcf540cad8 error 4 in libc-2.21.so[7fbdaf920+190] – Count:0
Plex Media Scan[5946]: segfault at 0 ip004f816f sp007ffee5706 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[6024]: segfault at 0 ip004f816f sp007ffcc2110680 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[30373]: segfault at 0 ip004f816f sp007fffe71555a0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[30647]: segfault at 0 ip004f816f sp007ffd3d8b6060 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[16145]: segfault at 0 ip004f816f sp007fff1ea1f error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[13421]: segfault at 0 ip004f816f sp007ffca33c7820 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[22417]: segfault at 0 ip004f816f sp007fffd28a4 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[11115]: segfault at 0 ip004f816f sp007ffe989f9b40 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[17558]: segfault at 0 ip004f816f sp007ffc3023bc90 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[2609]: segfault at 0 ip004f816f sp007fffed5ca230 error 4 in Plex Media Scanner[430+3f0] – Count:0
vjbod_cloud_uti[31317]: segfault at 18 ip007fc660fb5f75 sp007ffd8bd20370 error 4 in libc-2.21.so[7fc660f30+190] – Count:0
vjbod_cloud_uti[31397]: segfault at 18 ip007f26ed4a9f75 sp007ffc2bf70 error 4 in libc-2.21.so[7f26ed430+190] – Count:0
vjbod_cloud_uti[31]: segfault at 18 ip007fa9c60dcf75 sp007fffc80befc0 error 4 in libc-2.21.so[7fa9c6060+190] – Count:0
vjbod_cloud_uti[31614]: segfault at 18 ip007f7fb3dddf75 sp007fff0c4e97b0 error 4 in libc-2.21.so[7f7fb3d60+190] – Count:0
vjbod_cloud_uti[4302]: segfault at 18 ip007f137cde2f75 sp007ffea48ee710 error 4 in libc-2.21.so[7f137cd60+190] – Count:0
vjbod_cloud_uti[4641]: segfault at 18 ip007f3cbe387f75 sp007fffb96cd150 error 4 in libc-2.21.so[7f3cbe310+190] – Count:0
vjbod_cloud_uti[18297]: segfault at 18 ip007fc0603d7f75 sp007ffd94939620 error 4 in libc-2.21.so[7fc060360+190] – Count:0
vjbod_cloud_uti[18488]: segfault at 18 ip007f1fa8b7df75 sp007fffc1145410 error 4 in libc-2.21.so[7f1fa8b00+190] – Count:0
vjbod_cloud_uti[24349]: segfault at 18 ip007f6d1db14f75 sp007ffeb0d4f1f0 error 4 in libc-2.21.so[7f6d1da90+190] – Count:0
vjbod_cloud_uti[24526]: segfault at 18 ip007fd3cef75 sp007ffcdbca51d0 error 4 in libc-2.21.so[7fd350+190] – Count:0
vjbod_cloud_uti[29178]: segfault at 18 ip007f1b87610f75 sp007ffecbb0ef60 error 4 in libc-2.21.so[7f1b87590+190] – Count:0
vjbod_cloud_uti[29257]: segfault at 18 ip007f069ada8f75 sp007ffe43594cd0 error 4 in libc-2.21.so[7f069ad30+190] – Count:0
vjbod_cloud_uti[2222]: segfault at 18 ip007f4d6f23af75 sp007fffb4775c70 error 4 in libc-2.21.so[7f4d6f1c0+190] – Count:0
vjbod_cloud_uti[2276]: segfault at 18 ip007f0fca236f75 sp007ffd35aeb7c0 error 4 in libc-2.21.so[7f0fca100+190] – Count:0
vjbod_cloud_uti[11566]: segfault at 18 ip007fdee91a6f75 sp007fffb051f470 error 4 in libc-2.21.so[7fdee9100+190] – Count:0
vjbod_cloud_uti[11630]: segfault at 18 ip007f8f2ce37f75 sp007ffeeb38dfd0 error 4 in libc-2.21.so[7f8f2cdc0+190] – Count:0
vjbod_cloud_uti[16126]: segfault at 18 ip007fbefe8adf75 sp007ffef4ea7d90 error 4 in libc-2.21.so[7fbefe830+190] – Count:0
vjbod_cloud_uti[16196]: segfault at 18 ip007f6a6064ff75 sp007ffdc65e4750 error 4 in libc-2.21.so[7f6a605d0+190] – Count:0
vjbod_cloud_uti[25553]: segfault at 18 ip007fb869521f75 sp007ffd2e0f2740 error 4 in libc-2.21.so[7fb8694a0+190] – Count:0
vjbod_cloud_uti[25604]: segfault at 18 ip007f587b55cf75 sp007ffd0559a8e0 error 4 in libc-2.21.so[7f587b4e0+190] – Count:0
vjbod_cloud_uti[28575]: segfault at 18 ip007f3ef96a9f75 sp007fffe9d295a0 error 4 in libc-2.21.so[7f3ef9630+190] – Count:0
vjbod_cloud_uti[28689]: segfault at 18 ip007f088b039f75 sp007ffec3692b90 error 4 in libc-2.21.so[7f088afc0+190] – Count:0
vjbod_cloud_uti[307]: segfault at 18 ip007f059f16ef75 sp007ffed1f11750 error 4 in libc-2.21.so[7f059f0f0+190] – Count:0
vjbod_cloud_uti[375]: segfault at 18 ip007f58eff7af75 sp007ffd3b1627c0 error 4 in libc-2.21.so[7f58eff00+190] – Count:0
vjbod_cloud_uti[3698]: segfault at 18 ip007f8eb7266f75 sp007fff5c8bc error 4 in libc-2.21.so[7f8eb7100+190] – Count:0
vjbod_cloud_uti[3909]: segfault at 18 ip007f16c2ef2f75 sp007ffc04c42910 error 4 in libc-2.21.so[7f16c2e70+190] – Count:0

7

I’m not entirely convinced that’s the Scanner.

Do previous versions work without segfaulting?

Do you have date/time entries ?

Also, please advise which QTS version firmware and model ?

8

i havent tried running that with any other versions.
The log doesnt list any date/time

Model name TS-EC1680U
Firmware version 4.4.1.1081 Build 20191005

9

only date/time is listed like this.

kernel_log
kernel_log925×540 159 KB

10

Back away from that firmware. I had to. 4.4.1.0998 works better

You’ll also find your RAID storage back to where it belongs.

I spoke with QNAP at length on Friday and current version has a lot of problems.

11

what do you mean by this?

12

4.4.1.0998 build 20190715 so thats the BETA 3

13

On my TVS-1282, RAID volume performance plummeted from to approx 250 MB/sec.
Individual disks reported throughput in the 25-30 MB/sec range. It was disastrous.

I have attached my qcli_storage -tT force=1 results here for you to see what I am not back to on the (yes) “Beta 3” firmware.

Back on Beta3 firmware, I have a properly stable and functional unit. PMS now functions correctly as do all the other apps.

[~] # qcli_storage -Tt force=1  
fio test command for physical disk: /sbin/fio --filename=test_device --direct=1 --rw=read --bs=1M --runtime=15 --name=test-read --ioengine=libaio --iodepth=32 &>/tmp/qcli_storage.log
fio test command for RAID: /sbin/fio --filename=test_device --direct=0 --rw=read --bs=1M --runtime=15 --name=test-read --ioengine=libaio --iodepth=32 &>/tmp/qcli_storage.log
Start testing!
Performance test is finished 100.000%...
Enclosure  Port  Sys_Name      Throughput    RAID        RAID_Type    RAID_Throughput   Pool  
NAS_HOST   1     /dev/sda      537.02 MB/s   /dev/md1    RAID 1       1.04 GB/s         288   
NAS_HOST   2     /dev/sdb      536.48 MB/s   /dev/md1    RAID 1       1.04 GB/s         288   
NAS_HOST   3     /dev/sde      535.40 MB/s   --          --           --                --    
NAS_HOST   4     /dev/sdc      126.62 MB/s   /dev/md3    Single       131.71 MB/s       290   
NAS_HOST   5     /dev/sdf      531.64 MB/s   /dev/md4    Single       537.26 MB/s       291   
NAS_HOST   6     /dev/sdd      109.14 MB/s   /dev/md5    Single       110.65 MB/s       292   
NAS_HOST   7     /dev/sdh      198.03 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   8     /dev/sdg      190.60 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   9     /dev/sdn      188.83 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   10    /dev/sdm      187.18 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   11    /dev/sdk      201.48 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   12    /dev/sdl      188.81 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   13    /dev/sdi      192.05 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
NAS_HOST   14    /dev/sdj      194.79 MB/s   /dev/md2    RAID 5       1.12 GB/s         289   
[~] #

Additionally, many other system services were erratic. I was also forced to HARD POWER-OFF the unit 3 times, while rebooting it daily. This is unacceptable in the Linux world.

14

the file system tests i have also been running and testing lately myself, which are fine, and so far the 2 latest fw have been fine.

do you run ssd cache by chance?

ill prepare to downgrade to beta 3 and run the diag test again and see if those errors go away, so give me about 30 min to do this and ill let you know.

15

The two previous firmware were solid. Only 4.4.1.1081 (formal release) is a disaster and maybe unique to the TVS-1282

I do not run SSD cache as it serves no real purpose on a system with CACHEDEV1 already on M.2
and 32 GB of memory for buffer caching the inode tables in RAM (read only) for files I access.

16

Yep no purpose then, just mentioned it as there are performance issues with those running ssd cache. I myself run it using 4x1tb m.2 and I’ve been running different tests with it

Anyway, currently the system is installing this beta 3 and we’ll see what happens with this diagnostic test again. Will let you know the outcome on that very soon

17

For me, startup and shutdown time was also horrific . I cannot believe an i7-7700 at this clock speed requires at least 2x longer than a 2015 Atom C2538 CPU at 2.4 Ghz to boot.

That is seriously messed up and huge gripe at QNAP. “Let’s add some more sleep statements” thinking

18

well i still get these on beta 3

though i have plex disabled atm, so is that normal it would still show these errors?

Plex Transcoder[17435]: segfault at 18 ip007feec4605634 sp007fffa8454ff0 error 4 in libavcodec.so.58[7feec43c0+3e0] – Count:0
Plex Transcoder[24222]: segfault at 18 ip007fcd58864634 sp007ffea7099490 error 4 in libavcodec.so.58[7fcd58620+3e0] – Count:0
Plex Media Scan[31845]: segfault at 0 ip004f816f sp007ffff36c5bf0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[5229]: segfault at 0 ip004f816f sp007fff0c5d8 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[21668]: segfault at 0 ip004f816f sp007ffce0f7d970 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[26805]: segfault at 0 ip004f816f sp007fffe7dbd470 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[11432]: segfault at 0 ip004f816f sp007ffc904ac0f0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[27976]: segfault at 0 ip004f816f sp007fff0ce95470 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Transcoder[26074]: segfault at 18 ip007f4d1a12c634 sp007fffbf26be60 error 4 in libavcodec.so.58[7f4d19ef0+3e0] – Count:0
Plex Media Scan[22415]: segfault at 0 ip004f816f sp007ffcb7b2f5e0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[28578]: segfault at 0 ip004f816f sp007fff033e4540 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Serv[23429]: segfault at 7f0a312d2032 ip007fbdaf99def4 sp007fbcf540cad8 error 4 in libc-2.21.so[7fbdaf920+190] – Count:0
Plex Media Scan[5946]: segfault at 0 ip004f816f sp007ffee5706 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[6024]: segfault at 0 ip004f816f sp007ffcc2110680 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[30373]: segfault at 0 ip004f816f sp007fffe71555a0 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[30647]: segfault at 0 ip004f816f sp007ffd3d8b6060 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[16145]: segfault at 0 ip004f816f sp007fff1ea1f error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[13421]: segfault at 0 ip004f816f sp007ffca33c7820 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[22417]: segfault at 0 ip004f816f sp007fffd28a4 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[11115]: segfault at 0 ip004f816f sp007ffe989f9b40 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[17558]: segfault at 0 ip004f816f sp007ffc3023bc90 error 4 in Plex Media Scanner[430+3f0] – Count:0
Plex Media Scan[2609]: segfault at 0 ip004f816f sp007fffed5ca230 error 4 in Plex Media Scanner[430+3f0] – Count:0
vjbod_cloud_uti[31317]: segfault at 18 ip007fc660fb5f75 sp007ffd8bd20370 error 4 in libc-2.21.so[7fc660f30+190] – Count:0
vjbod_cloud_uti[31397]: segfault at 18 ip007f26ed4a9f75 sp007ffc2bf70 error 4 in libc-2.21.so[7f26ed430+190] – Count:0
vjbod_cloud_uti[31]: segfault at 18 ip007fa9c60dcf75 sp007fffc80befc0 error 4 in libc-2.21.so[7fa9c6060+190] – Count:0
vjbod_cloud_uti[31614]: segfault at 18 ip007f7fb3dddf75 sp007fff0c4e97b0 error 4 in libc-2.21.so[7f7fb3d60+190] – Count:0
vjbod_cloud_uti[4302]: segfault at 18 ip007f137cde2f75 sp007ffea48ee710 error 4 in libc-2.21.so[7f137cd60+190] – Count:0
vjbod_cloud_uti[4641]: segfault at 18 ip007f3cbe387f75 sp007fffb96cd150 error 4 in libc-2.21.so[7f3cbe310+190] – Count:0
vjbod_cloud_uti[18297]: segfault at 18 ip007fc0603d7f75 sp007ffd94939620 error 4 in libc-2.21.so[7fc060360+190] – Count:0
vjbod_cloud_uti[18488]: segfault at 18 ip007f1fa8b7df75 sp007fffc1145410 error 4 in libc-2.21.so[7f1fa8b00+190] – Count:0
vjbod_cloud_uti[24349]: segfault at 18 ip007f6d1db14f75 sp007ffeb0d4f1f0 error 4 in libc-2.21.so[7f6d1da90+190] – Count:0
vjbod_cloud_uti[24526]: segfault at 18 ip007fd3cef75 sp007ffcdbca51d0 error 4 in libc-2.21.so[7fd350+190] – Count:0
vjbod_cloud_uti[29178]: segfault at 18 ip007f1b87610f75 sp007ffecbb0ef60 error 4 in libc-2.21.so[7f1b87590+190] – Count:0
vjbod_cloud_uti[29257]: segfault at 18 ip007f069ada8f75 sp007ffe43594cd0 error 4 in libc-2.21.so[7f069ad30+190] – Count:0
vjbod_cloud_uti[2222]: segfault at 18 ip007f4d6f23af75 sp007fffb4775c70 error 4 in libc-2.21.so[7f4d6f1c0+190] – Count:0
vjbod_cloud_uti[2276]: segfault at 18 ip007f0fca236f75 sp007ffd35aeb7c0 error 4 in libc-2.21.so[7f0fca100+190] – Count:0
vjbod_cloud_uti[11566]: segfault at 18 ip007fdee91a6f75 sp007fffb051f470 error 4 in libc-2.21.so[7fdee9100+190] – Count:0
vjbod_cloud_uti[11630]: segfault at 18 ip007f8f2ce37f75 sp007ffeeb38dfd0 error 4 in libc-2.21.so[7f8f2cdc0+190] – Count:0
vjbod_cloud_uti[16126]: segfault at 18 ip007fbefe8adf75 sp007ffef4ea7d90 error 4 in libc-2.21.so[7fbefe830+190] – Count:0
vjbod_cloud_uti[16196]: segfault at 18 ip007f6a6064ff75 sp007ffdc65e4750 error 4 in libc-2.21.so[7f6a605d0+190] – Count:0
vjbod_cloud_uti[25553]: segfault at 18 ip007fb869521f75 sp007ffd2e0f2740 error 4 in libc-2.21.so[7fb8694a0+190] – Count:0
vjbod_cloud_uti[25604]: segfault at 18 ip007f587b55cf75 sp007ffd0559a8e0 error 4 in libc-2.21.so[7f587b4e0+190] – Count:0
vjbod_cloud_uti[28575]: segfault at 18 ip007f3ef96a9f75 sp007fffe9d295a0 error 4 in libc-2.21.so[7f3ef9630+190] – Count:0
vjbod_cloud_uti[28689]: segfault at 18 ip007f088b039f75 sp007ffec3692b90 error 4 in libc-2.21.so[7f088afc0+190] – Count:0
vjbod_cloud_uti[307]: segfault at 18 ip007f059f16ef75 sp007ffed1f11750 error 4 in libc-2.21.so[7f059f0f0+190] – Count:0
vjbod_cloud_uti[375]: segfault at 18 ip007f58eff7af75 sp007ffd3b1627c0 error 4 in libc-2.21.so[7f58eff00+190] – Count:0
vjbod_cloud_uti[3698]: segfault at 18 ip007f8eb7266f75 sp007fff5c8bc error 4 in libc-2.21.so[7f8eb7100+190] – Count:0
vjbod_cloud_uti[3909]: segfault at 18 ip007f16c2ef2f75 sp007ffc04c42910 error 4 in libc-2.21.so[7f16c2e70+190] – Count:0
vjbod_cloud_uti[430]: segfault at 18 ip007f1d1d69cf75 sp007fffc406b error 4 in libc-2.21.so[7f1d1d620+190] – Count:0
vjbod_cloud_uti[449]: segfault at 18 ip007f279ef70f75 sp007fff6d9f9640 error 4 in libc-2.21.so[7f279eef0+190] – Count:0
vjbod_cloud_uti[703]: segfault at 18 ip007f9367ac9f75 sp007ffda8483430 error 4 in libc-2.21.so[7f9367a50+190] – Count:0
vjbod_cloud_uti[697]: segfault at 18 ip007f53d6827f75 sp007ffe653a77e0 error 4 in libc-2.21.so[7f53d67b0+190] – Count:0

19

The last 8 segfaults are errors from vjbod_cloud_uti in libc, with the error 4 message: “The cause was a user-mode read resulting in no page being found.”

kernel log output 
vjbod_cloud_uti[307]: segfault at 18 ip007f059f16ef75 sp007ffed1f11750 error 4 in libc-2.21.so[7f059f0f0+190] – Count:0
vjbod_cloud_uti[375]: segfault at 18 ip007f58eff7af75 sp007ffd3b1627c0 error 4 in libc-2.21.so[7f58eff00+190] – Count:0
vjbod_cloud_uti[3698]: segfault at 18 ip007f8eb7266f75 sp007fff5c8bc error 4 in libc-2.21.so[7f8eb7100+190] – Count:0
vjbod_cloud_uti[3909]: segfault at 18 ip007f16c2ef2f75 sp007ffc04c42910 error 4 in libc-2.21.so[7f16c2e70+190] – Count:0


vjbod_cloud_uti[430]: segfault at 18 ip007f1d1d69cf75 sp007fffc406b error 4 in libc-2.21.so[7f1d1d620+190] – Count:0
vjbod_cloud_uti[449]: segfault at 18 ip007f279ef70f75 sp007fff6d9f9640 error 4 in libc-2.21.so[7f279eef0+190] – Count:0
vjbod_cloud_uti[703]: segfault at 18 ip007f9367ac9f75 sp007ffda8483430 error 4 in libc-2.21.so[7f9367a50+190] – Count:0
vjbod_cloud_uti[697]: segfault at 18 ip007f53d6827f75 sp007ffe653a77e0 error 4 in libc-2.21.so[7f53d67b0+190] – Count:0

Let’s look at the (Instruction Pointer - Base Address) to see the location in libc of the issue:

hex math 
7f059f16ef75 - 7f059f0f0000 = 0x7EF75
7f58eff7af75 - 7f58eff00000 = 0x7AF75
7f8eb7266f75 - 7f8eb7100000 = 0x166F75
7f16c2ef2f75 - 7f16c2e70000 = 0x82F75

7f1d1d69cf75 - 7f1d1d620000 = 0x7CF75
7f279ef70f75 - 7f279eef0000 = 0x80F75
7f9367ac9f75 - 7f9367a50000 = 0x79F75
7f53d6827f75 - 7f53d67b0000 = 0x77F75

addr2line shows that a lot of those calls are string manipulation:

output of that command 
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x7EF75
strcmp
??:?
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x7AF75
cfree
??:?
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x166F75
??
??:0
[~] # 
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x82F75
strspn
??:?
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x7CF75
__default_morecore
??:?
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x80F75
strncmp
??:?
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x79F75
_IO_str_seekoff
??:?
[~] # addr2line -e /lib/libc-2.21.so -fCi 0x77F75
_IO_str_seekoff
??:?

The article on stackoverflow that I followed.


Useful to us? I don’t know, but the gdb info was a good read.

1 Like
20

so what or where do you think this issue is coming from