Sudden death on pppoe: tcflush failed: Bad file descriptor

Home Page Forums Network Management ZeroShell Sudden death on pppoe: tcflush failed: Bad file descriptor

This topic contains 3 replies, has 0 voices, and was last updated by  Pit 9 years, 6 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #42442

    Pit
    Member

    Hello,

    one of my pppoe connections stopped to work:

    01:20:07 pppd 2.4.3 started by root, uid 0
    01:20:07 Using interface ppp0
    01:20:07 Connect: ppp0 < --> /dev/pts/2
    01:20:38 LCP: timeout sending Config-Requests
    01:20:38 Connection terminated.
    01:20:38 Using interface ppp0
    01:20:38 Connect: ppp0 < --> /dev/pts/3
    01:20:43 tcflush failed: Bad file descriptor
    01:20:43 Exit.
    01:20:48 pppd 2.4.3 started by root, uid 0
    01:20:48 Using interface ppp0
    01:20:48 Connect: ppp0 < --> /dev/pts/2
    01:21:19 LCP: timeout sending Config-Requests
    01:21:19 Connection terminated.
    01:21:19 Using interface ppp0
    01:21:19 Connect: ppp0 < --> /dev/pts/3
    01:21:24 tcflush failed: Bad file descriptor
    01:21:24 Exit.
    01:21:29 pppd 2.4.3 started by root, uid 0
    01:21:29 Using interface ppp0
    01:21:29 Connect: ppp0 < --> /dev/pts/2
    01:22:00 LCP: timeout sending Config-Requests
    01:22:00 Connection terminated.
    01:22:00 Using interface ppp0
    01:22:00 Connect: ppp0 < --> /dev/pts/3
    01:22:05 tcflush failed: Bad file descriptor
    01:22:05 Exit.

    Any idea what is going wrong? Is there a chance to start the line again?

    Provider says that the modem syncs well.

    Thanks in advance

    Pit

    #50451

    Pit
    Member

    Some output at the shell may help:

    6019 ? S 0:00 /bin/sh /usr/sbin/pppoe-connect /tmp/pppoe-ppp0.conf

    15466 ? S 0:00 _ /usr/local/sbin/pppd pty /usr/sbin/pppoe -p /tmp/pppoe-ppp0.pid.pppoe -I ETH02 -T 80 -U -m 1412 noipdefault noaut

    15467 ? S 0:00 _ /usr/sbin/pppoe -p /tmp/pppoe-ppp0.pid.pppoe -I ETH02 -T 80 -U -m 1412

    15619 ? S 0:00 _ /usr/sbin/pppoe -p /tmp/pppoe-ppp0.pid.pppoe -I ETH02 -T 80 -U -m 1412

    6077 ? S 0:00 /bin/sh /usr/sbin/pppoe-connect /tmp/pppoe-ppp1.conf

    6096 ? S 0:00 _ /usr/local/sbin/pppd pty /usr/sbin/pppoe -p /tmp/pppoe-ppp1.pid.pppoe -I ETH03 -T 80 -U -m 1412 noipdefault noaut

    6101 ? S 0:00 _ /usr/sbin/pppoe -p /tmp/pppoe-ppp1.pid.pppoe -I ETH03 -T 80 -U -m 1412

    6116 ? S 0:00 /bin/sh /usr/sbin/pppoe-connect /tmp/pppoe-ppp2.conf

    6138 ? S 0:00 _ /usr/local/sbin/pppd pty /usr/sbin/pppoe -p /tmp/pppoe-ppp2.pid.pppoe -I ETH04 -T 80 -U -m 1412 noipdefault noaut

    6140 ? S 0:00 _ /usr/sbin/pppoe -p /tmp/pppoe-ppp2.pid.pppoe -I ETH04 -T 80 -U -m 1412

    There are two connections to ppp0.

    #50452

    Pit
    Member

    Some people in the cloud say, that there is an issue with syslog in ppp-2.4.3 and ppp-2.4.4. Downgrading to ppp-2.4.2 should solve the problem.
    Other people have a patch for ppp-2.4.4:

    https://bugzilla.redhat.com/show_bug.cgi?id=222295

    From
    http://forum.nag.ru/forum/index.php?s=&showtopic=39627&view=findpost&p=285712

    small patch:

    — ppp-2.4.4/pppd/main.c.orig 2006-06-04 07:52:50.000000000 +0400
    +++ ppp-2.4.4/pppd/main.c 2007-11-09 14:47:20.000000000 +0300
    @@ -1567,6 +1567,8 @@
    if (errfd == 0 || errfd == 1)
    errfd = dup(errfd);

    + closelog();
    +
    /* dup the in, out, err fds to 0, 1, 2 */
    if (infd != 0)
    dup2(infd, 0);
    @@ -1575,7 +1577,6 @@
    if (errfd != 2)
    dup2(errfd, 2);

    – closelog();
    if (log_to_fd > 2)
    close(log_to_fd);
    if (the_channel->close)

    To test if the syslog issue is the problem i need to disable syslog on ZS.

    Is there a way to do so?
    I tried to kill the prozesses but some magic starts syslogd/klogd again.

    #50453

    Pit
    Member

    Solved:

    Changed the modem -> all is well again.

    Knows someone a dictionary “error message human language” ? 🙂

    Thank’s for your regard.

    Pit

    #50454

    ppalias
    Member

    Not sure about the translation of error messages, maybe google can return something useful. Modems usually are number 1 thing to troubleshoot at failed connections, it seems for some reason that they fail very easily.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.