timer:timerfd_settime: Bad file descriptor

IPoE related questions
brodayga
Posts: 93
Joined: 23 Oct 2014, 06:13

timer:timerfd_settime: Bad file descriptor

Post by brodayga » 13 Mar 2018, 07:25

Добрый день.
53d53606ba52032b4ae81c4c967316816053efcc
IPOE L2 shared
radius
conlimit

Был в аптайме больше месяца.
выдал в core.log

Code: Select all

timer:timerfd_settime: Bad file descriptor
И остановился.
Не подскажете куда смотреть?

dimka88
Posts: 404
Joined: 13 Oct 2014, 05:51
Contact:

Re: timer:timerfd_settime: Bad file descriptor

Post by dimka88 » 13 Mar 2018, 11:28

Добрый день, для начала https://accel-ppp.org/wiki/doku.php?id= ... 0%B5%D1%82
И посмотрите в dmesg, была запись о segfault?

brodayga
Posts: 93
Joined: 23 Oct 2014, 06:13

Re: timer:timerfd_settime: Bad file descriptor

Post by brodayga » 13 Mar 2018, 13:11

В том то и дело что везде пусто.

dimka88
Posts: 404
Joined: 13 Oct 2014, 05:51
Contact:

Re: timer:timerfd_settime: Bad file descriptor

Post by dimka88 » 14 Mar 2018, 06:39

RAM не битый? Сколько каналов RAM?

brodayga
Posts: 93
Joined: 23 Oct 2014, 06:13

Re: timer:timerfd_settime: Bad file descriptor

Post by brodayga » 14 Mar 2018, 13:02

Машина не упала, судя по пустому dmesg аксел просто завершил работу. При проблемах с памятью...
Обновлю до последней из гита посмотрю. тем более что судя по логам исправлена проблема с radreqlimit

dimka88
Posts: 404
Joined: 13 Oct 2014, 05:51
Contact:

Re: timer:timerfd_settime: Bad file descriptor

Post by dimka88 » 14 Mar 2018, 19:10

я немного не уверен, что мыслю именно в правильном направлении.
Покажите вывод

Code: Select all

 ulimit -a
ну и логов кусочек интервал время вывода ошибки -30 секунд

brodayga
Posts: 93
Joined: 23 Oct 2014, 06:13

Re: timer:timerfd_settime: Bad file descriptor

Post by brodayga » 14 Mar 2018, 19:56

Code: Select all

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 15558
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 15558
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

brodayga
Posts: 93
Joined: 23 Oct 2014, 06:13

Re: timer:timerfd_settime: Bad file descriptor

Post by brodayga » 14 Mar 2018, 20:05

кусок лога последние 2 сек выше всё также штатно (30 секунд больше 1500 строк)
Спойлер
[2018-03-11 18:05:08]: info: ipoe351: recv [DHCPv4 Request xid=74c31c ciaddr=172.16.66.40 chaddr=70:4f:57:18:61:97 <Message-Type Request> <Max-Message-Size1024> <Client-ID 01704f57186197> <Host-Name TL-WR940N> <Vendor-Class 4d53465420352e30> <Request-List Subnet,Router,DNS,Domain-Name,Route,Vendor-Specific,44,46,47,Classless-Route,249> <Relay-Agent {Agent-Circuit-ID _0006001701000007} {Agent-Remote-ID 192.168.201.24}>]
[2018-03-11 18:05:08]: info: ipoe351: send [DHCPv4 Ack xid=74c31c ciaddr=172.16.66.40 yiaddr=172.16.66.40 chaddr=70:4f:57:18:61:97 <Message-Type Ack> <Server-ID 172.16.64.1> <Lease-Time 180> <T1 90> <Router 172.16.64.1> <Subnet 255.255.240.0> <DNS 10.0.0.20,10.0.0.21>]
[2018-03-11 18:05:08]: info: ipoe1503: recv [DHCPv4 Request xid=98c59442 ciaddr=172.16.64.158 chaddr=dc:a9:04:aa:ce:20 <Message-Type Request> <Request-ListSubnet,Classless-Route,Router,DNS,Domain-Name,119,252> <Max-Message-Size 1500> <Client-ID 01dca904aace20> <Lease-Time 7776000> <Host-Name iPhone-Madina> <Relay-Agent {Agent-Circuit-ID _000400460004} {Agent-Remote-ID _010e3139322e3136382e3230302e3730}>]
[2018-03-11 18:05:08]: info: ipoe1503: send [DHCPv4 Ack xid=98c59442 ciaddr=172.16.64.158 yiaddr=172.16.64.158 chaddr=dc:a9:04:aa:ce:20 <Message-Type Ack> <Server-ID 172.16.64.1> <Lease-Time 180> <T1 90> <Router 172.16.64.1> <Subnet 255.255.240.0> <DNS 10.0.0.20,10.0.0.21>]
[2018-03-11 18:05:08]: info: ipoe1745: recv [DHCPv4 Request xid=8f04a703 ciaddr=172.16.67.174 chaddr=60:e3:27:73:1a:63 <Message-Type Request> <Max-Message-Size 1024> <Client-ID 0160e327731a63> <Host-Name TL-WR841N> <Vendor-Class 4d53465420352e30> <Request-List Subnet,Router,DNS,Domain-Name,Route,Vendor-Specific,44,46,47,Classless-Route,249> <Relay-Agent {Agent-Circuit-ID _000400260005} {Agent-Remote-ID 192.168.208.38}>]
[2018-03-11 18:05:08]: info: ipoe1745: send [DHCPv4 Ack xid=8f04a703 ciaddr=172.16.67.174 yiaddr=172.16.67.174 chaddr=60:e3:27:73:1a:63 <Message-Type Ack> <Server-ID 172.16.64.1> <Lease-Time 180> <T1 90> <Router 172.16.64.1> <Subnet 255.255.240.0> <DNS 10.0.0.20,10.0.0.21>]
[2018-03-11 18:05:08]: info: ipoe: stop interface eth0.1206.2
[2018-03-11 18:05:08]: info: ipoe: remove vlan eth0.1206.2
[2018-03-11 18:05:08]: debug: eth0.1208.6: recv [DHCPv4 Request xid=372c491b chaddr=1c:74:0d:90:bc:d1 <Message-Type Request> <Max-Message-Size 1500> <Client-ID 011c740d90bcd1> <Vendor-Class 6e6468637063> <Host-Name Keenetic_Lite> <Request-List Subnet,Router,DNS,Domain-Name,Broadcast,Route,NTP,Vendor-Specific,44,Classless-Route,249> <Request-IP 172.17.30.0> <Server-ID 172.17.28.1> <Relay-Agent {Agent-Circuit-ID _000400060004} {Agent-Remote-ID 192.168.208.6}>]
[2018-03-11 18:05:08]: info: send [DHCPv4 Nak xid=372c491b chaddr=1c:74:0d:90:bc:d1 <Message-Type Nak>]
[2018-03-11 18:05:08]: info: ipoe1657: recv [DHCPv4 Request xid=14c57b89 ciaddr=172.16.69.206 chaddr=54:a0:50:db:f6:14 <Message-Type Request> <Client-ID 0154a050dbf614> <Max-Message-Size 1492> <Request-List Subnet,Router,DNS,Host-Name,Domain-Name,Broadcast,Route,NTP,249> <Vendor-Class 756468637020312e31372e34> <Relay-Agent {Agent-Circuit-ID _000600360100000c} {Agent-Remote-ID 192.168.204.54}>]
[2018-03-11 18:05:08]: info: ipoe1657: send [DHCPv4 Ack xid=14c57b89 ciaddr=172.16.69.206 yiaddr=172.16.69.206 chaddr=54:a0:50:db:f6:14 <Message-Type Ack> <Server-ID 172.16.64.1> <Lease-Time 180> <T1 90> <Router 172.16.64.1> <Subnet 255.255.240.0> <DNS 10.0.0.20,10.0.0.21>]
[2018-03-11 18:05:09]: debug: eth0.1209.30: recv [DHCPv4 Request xid=47be8987 ciaddr=172.17.71.235 chaddr=1c:b7:2c:7e:ad:14 <Message-Type Request> <Client-ID 011cb72c7ead14> <Max-Message-Size 1492> <Request-List Subnet,Router,DNS,Host-Name,Domain-Name,Broadcast,Route,NTP,249> <Vendor-Class 756468637020312e31372e34> <Relay-Agent {Agent-Circuit-ID _0004001e0001} {Agent-Remote-ID _010e3139322e3136382e3230392e3330}>]
[2018-03-11 18:05:09]: info: send [DHCPv4 Nak xid=47be8987 chaddr=1c:b7:2c:7e:ad:14 <Message-Type Nak>]
[2018-03-11 18:05:09]: info: send [DHCPv4 Nak xid=47be8987 chaddr=1c:b7:2c:7e:ad:14 <Message-Type Nak>]
[2018-03-11 18:05:09]: debug: vlan-mon: notify 42 14 0806 0
[2018-03-11 18:05:09]: info: ipoe: create vlan eth0.2013.14 parent eth0.2013
[2018-03-11 18:05:09]: info: ipoe: start interface eth0.2013.14 ()
[2018-03-11 18:05:09]: info: eth0.1207.65: recv [DHCPv4 Discover xid=473b8ed7 chaddr=d4:6e:0e:52:fd:13 <Message-Type Discover> <Max-Message-Size 1024> <Client-ID 01d46e0e52fd13> <Host-Name TL-WR841N> <Vendor-Class 4d53465420352e30> <Request-List Subnet,Router,DNS,Domain-Name,Vendor-Specific,44,46,47,Route,Classless-Route,249> <Relay-Agent {Agent-Circuit-ID _000400410003} {Agent-Remote-ID _010e3139322e3136382e3230372e3635}>]
[2018-03-11 18:05:09]: info: ipoe1543: create interface ipoe1543 parent eth0.1207.65
[2018-03-11 18:05:09]: debug: ipoe1543: radius(1): req_enter 1
[2018-03-11 18:05:09]: info: ipoe1543: send [RADIUS(1) Access-Request id=1 <User-Name "192.168.207.65:3"> <NAS-Identifier "ipoe3"> <NAS-IP-Address 10.0.0.4> <NAS-Port 801543> <NAS-Port-Id "ipoe1543"> <NAS-Port-Type Ethernet> <Calling-Station-Id "d4:6e:0e:52:fd:13"> <Called-Station-Id "eth0.1207.65"> <User-Password>]
ну содержимое core.log

Code: Select all

[2018-03-11 18:05:09.73]timer:timerfd_settime: Bad file descriptor

dimka88
Posts: 404
Joined: 13 Oct 2014, 05:51
Contact:

Re: timer:timerfd_settime: Bad file descriptor

Post by dimka88 » 15 Mar 2018, 07:31

brodayga wrote:
14 Mar 2018, 19:56

Code: Select all

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 15558
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 15558
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
Проконсультировался с ребятами, думаем закончились сокеты (open files 1024)
выполните

Code: Select all

ulimit -n 4048
ps:/ Вы RAM мониторете? Случайно не зафиксировали утечку памяти?

brodayga
Posts: 93
Joined: 23 Oct 2014, 06:13

Re: timer:timerfd_settime: Bad file descriptor

Post by brodayga » 19 Mar 2018, 10:39

Немного поискал по теме. Данная ошибка может вылезти только в том случае если пытаться изменить таймер который не создан(или уже удалён). Если была бы проблема с количеством файловых дескрипторов то ошибка вылезла на create
Спойлер
timerfd_create() can fail with the following errors:
EINVAL The clockid argument is neither CLOCK_MONOTONIC nor CLOCK_REAL-TIME;
EINVAL flags is invalid; or, in Linux 2.6.26 or earlier, flags is nonzero.
EMFILE The per-process limit of open file descriptors has been reached.
ENFILE The system-wide limit on the total number of open files has been reached.

ENODEV Could not mount (internal) anonymous inode device.
ENOMEM There was insufficient kernel memory to create the timer.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest