Re: f33: systemd-resolved hang on ip query

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Can you pls get another stackframe and compare it ( it won't match 100%
> as differen apps go different way) with this bugreport:

It won't matter much, the next frame is in Varnish code.

Here is the pstack dump of dig:

> Thread 4 (Thread 0x7fee8a3e4640 (LWP 1768516) "isc-socket"):
> #0  0x00007fee8bf72c4e in epoll_wait () from /lib64/libc.so.6
> #1  0x00007fee8c0bb4cc in watcher () from /lib64/libisc.so.1107
> #2  0x00007fee8b9ae3f9 in start_thread () from /lib64/libpthread.so.0
> #3  0x00007fee8bf72903 in clone () from /lib64/libc.so.6
> Thread 3 (Thread 0x7fee8abe5640 (LWP 1768515) "isc-timer"):
> #0  0x00007fee8b9b49e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
> #1  0x00007fee8c0b3908 in isc_condition_waituntil () from /lib64/libisc.so.1107
> #2  0x00007fee8c0a525f in run.lto_priv () from /lib64/libisc.so.1107
> #3  0x00007fee8b9ae3f9 in start_thread () from /lib64/libpthread.so.0
> #4  0x00007fee8bf72903 in clone () from /lib64/libc.so.6
> Thread 2 (Thread 0x7fee8b3e6640 (LWP 1768514) "isc-worker0000"):
> #0  0x00007fee8b9b46c2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
> #1  0x00007fee8c0a22ea in run.lto_priv () from /lib64/libisc.so.1107
> #2  0x00007fee8b9ae3f9 in start_thread () from /lib64/libpthread.so.0
> #3  0x00007fee8bf72903 in clone () from /lib64/libc.so.6
> Thread 1 (Thread 0x7fee8b428c80 (LWP 1768513) "dig"):
> #0  0x00007fee8beaed8a in sigsuspend () from /lib64/libc.so.6
> #1  0x00007fee8c0a62eb in isc.app_ctxrun () from /lib64/libisc.so.1107
> #2  0x00007fee8c0a6f1f in isc_app_run () from /lib64/libisc.so.1107
> #3  0x000055dc25b87127 in main ()

> https://bugzilla.redhat.com/show_bug.cgi?id=1904415
>
> I see similarities there. I case of the BR, bind-libs and glic releases
> did not match as it looks ( a thesis so far, no hard facts ).

This looks like a different problem.

> Petr was so nice to supply a test procedure, i suggest that you use it also.

I'll try to strace stuff to to see what's going on, but I can only
assume that this BZ is not trying to resolve ip addresses through
systemd-resolved.

Thanks for the pointers,
Dridi
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux