ALT Linux Bugzilla
– Attachment 5524 Details for
Bug 27592
ntpd отваливается на отсутствующем IPv6
New bug
|
Search
|
[?]
|
Help
Register
|
Log In
[x]
|
Forgot Password
Login:
[x]
|
EN
|
RU
strace log
ntp.strace (text/plain), 6.18 KB, created by
Dmitry Chistikov
on 2012-08-02 14:51:09 MSK
(
hide
)
Description:
strace log
Filename:
MIME Type:
Creator:
Dmitry Chistikov
Created:
2012-08-02 14:51:09 MSK
Size:
6.18 KB
patch
obsolete
># strace -e socket,close -f -- ntpd -d >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >socket(PF_NETLINK, SOCK_RAW, 0) = 4 >close(4) = 0 >socket(PF_NETLINK, SOCK_RAW, 0) = 4 >close(4) = 0 >close(3) = 0 >socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3 >close(3) = 0 >socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(3) = 0 >close(4) = 0 >Process 1696 attached >[pid 1696] socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5 >[pid 1696] close(5) = 0 >[pid 1696] socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5 >[pid 1696] close(5) = 0 >[pid 1696] close(5) = 0 >[pid 1696] close(5) = 0 >[pid 1696] close(3) = 0 >ntp engine ready >[pid 1696] close(-1) = -1 EBADF (Bad file descriptor) >[pid 1696] close(-1) = -1 EBADF (Bad file descriptor) >[pid 1695] socket(PF_NETLINK, SOCK_RAW, 0) = 4 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 4 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 4 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 4 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family not supported by protocol) >[pid 1695] socket(PF_NETLINK, SOCK_RAW, 0) = 4 >[pid 1695] close(4) = 0 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 4 >[pid 1695] close(4) = 0 >[pid 1695] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4 >[pid 1695] close(4) = 0 >[pid 1696] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 >[pid 1696] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 >[pid 1696] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6 >[pid 1696] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 7 >reply from 62.117.85.58: offset -47.174654 delay 0.194807, next query 7s >reply from 87.236.27.66: offset -47.177346 delay 0.196659, next query 6s >reply from 89.111.168.177: offset -47.126772 delay 0.293456, next query 8s >reply from 193.169.32.218: offset -47.102328 delay 0.349378, next query 9s >reply from 87.236.27.66: offset -47.211384 delay 0.120012, next query 6s >reply from 89.111.168.177: offset -47.218017 delay 0.103421, next query 9s >reply from 193.169.32.218: offset -47.237290 delay 0.077482, next query 7s >reply from 87.236.27.66: offset -47.211538 delay 0.112634, next query 7s >reply from 193.169.32.218: offset -47.148638 delay 0.244812, next query 9s >reply from 89.111.168.177: offset -47.250541 delay 0.027867, next query 9s >peer 87.236.27.66 now valid >reply from 87.236.27.66: offset -47.234884 delay 0.059862, next query 8s >peer 193.169.32.218 now valid >reply from 193.169.32.218: offset -46.883684 delay 0.758360, next query 6s >peer 89.111.168.177 now valid >reply from 89.111.168.177: offset -47.244079 delay 0.029670, next query 6s >reply from 87.236.27.66: offset -47.244832 delay 0.032955, next query 8s >reply from 193.169.32.218: offset -47.190685 delay 0.138113, next query 9s >reply from 89.111.168.177: offset -47.076372 delay 0.363992, next query 8s >reply from 87.236.27.66: offset -46.971269 delay 0.569380, next query 5s >reply from 87.236.27.66: offset -47.009260 delay 0.486885, next query 34s >reply from 62.117.85.58: offset -46.877573 delay 0.728483, next query 5s >no reply from 193.169.32.218 received in time, next query 646s >peer 193.169.32.218 now invalid >[pid 1696] close(6) = 0 >no reply from 89.111.168.177 received in time, next query 654s >peer 89.111.168.177 now invalid >[pid 1696] close(7) = 0 >no reply from 62.117.85.58 received in time, next query 637s >[pid 1696] close(3) = 0 >reply from 87.236.27.66: offset -47.214468 delay 0.040653, next query 33s >adjusting local clock by -47.244832s >skiping very first adjtimex >reply from 87.236.27.66: offset -47.206680 delay 0.020368, next query 32s >reply from 87.236.27.66: offset -47.080266 delay 0.239706, next query 33s >no reply from 87.236.27.66 received in time, next query 615s >peer 87.236.27.66 now invalid >[pid 1696] close(5) = 0 >[pid 1696] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 >reply from 193.169.32.218: offset -46.725214 delay 0.355345, next query 8s >[pid 1696] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 >reply from 89.111.168.177: offset -46.473178 delay 0.848611, next query 6s >reply from 193.169.32.218: offset -46.753683 delay 0.286625, next query 6s >[pid 1696] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family not supported by protocol) >fatal: client_query socket: Address family not supported by protocol >[pid 1696] +++ exited with 1 +++ >--- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1696, si_status=1, si_utime=0, si_stime=2} (Child exited) --- >dispatch_imsg in main: pipe closed >Lost child: child exited >Terminating >+++ exited with 1 +++
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 27592
: 5524 |
5525
|
5529