• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ERROR: uv_custom_poll_cb: bad file descriptor
#1
Hi guys,
I keep getting this error message 'uv_custom_poll_cb: bad file descriptor' on sendmail as well as on pushover en pushbullet.
Very frustrating. Can't find it's meaning. Search all forum, but can't find a solution either. What am I missing here?
Running last stable: 8.0.4 on last Raspbian 9 (stretch)

Is it some packed I need to install? Can it be some setting?

Relevant config part:
Code:
"rules": {
    "door-close-sendmail": {
        "rule": "IF door.state IS off THEN sendmail TO my@email.com SUBJECT Testing MESSAGE Test",
        "active": 1
    },
    "door-open-pushbullet": {
        "rule": "IF door.state IS on THEN pushbullet TITLE Garage BODY Garage TOKEN my-token-code TYPE note",
        "active": 1
    },
    "door-open-pushover": {
        "rule": "IF door.state IS on THEN pushover TITLE Garage MESSAGE Garage TOKEN my-token-code USER my-user-key",
        "active": 1
    }
},
"settings": {
    "smtp-sender": "my@email.com",
    "smtp-host": "smtp.myprovider.com",
    "smtp-port": 465,
    "smtp-user": "my_user",
    "smtp-password": "my_password",
    "gpio-platform": "raspberrypi1b2"
},

pilight-daemon: INFO: executed rule: door-close-sendmail
pilight-daemon: DEBUG: rule #1 door-close-sendmail was parsed in 0.003671 seconds
pilight-daemon: ERROR: uv_custom_poll_cb: bad file descriptor
 
Reply
#2
I will bughunt that sendmail error this weekend i think. Thanks for reporting!
 
Reply
#3
Can you post the output of:
Code:
ping smtp.myprovider.com
ping api.pushbullet.com
where ofc the url should match your real provider.
 
Reply
#4
Code:
pi@raspberrypi:~ $ ping smtp.xs4all.nl
PING smtp.xs4all.nl(smtp.xs4all.net (2001:888:0:15::25)) 56 data bytes
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=1 ttl=61 time=7.79 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=2 ttl=61 time=5.88 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=3 ttl=61 time=6.70 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=4 ttl=61 time=13.7 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=5 ttl=61 time=6.02 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=6 ttl=61 time=5.75 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=7 ttl=61 time=17.4 ms
64 bytes from smtp.xs4all.net (2001:888:0:15::25): icmp_seq=8 ttl=61 time=10.6 ms
^C
--- smtp.xs4all.nl ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7004ms
rtt min/avg/max/mdev = 5.754/9.247/17.431/4.053 ms

Code:
pi@raspberrypi:~ $ ping api.pushbullet.com
PING api.pushbullet.com(ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013)) 56 data bytes
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=2 ttl=56 time=1046 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=3 ttl=56 time=6.94 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=4 ttl=56 time=377 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=6 ttl=56 time=7.00 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=7 ttl=56 time=8.96 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=8 ttl=56 time=6.85 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=9 ttl=56 time=7.16 ms
64 bytes from ams16s22-in-x13.1e100.net (2a00:1450:400e:803::2013): icmp_seq=10 ttl=56 time=6.56 ms
^C
--- api.pushbullet.com ping statistics ---
10 packets transmitted, 8 received, 20% packet loss, time 9098ms
rtt min/avg/max/mdev = 6.565/183.530/1046.782/348.111 ms, pipe 2
 
Reply
#5
Just as i though. Both server switched to ipv6 by default. pilight does not yet support ipv6. The same issue applies to smtp.gmail.com. I will prioritize ipv6 knowing this.
 
Reply
#6
(12-07-2017, 05:51 PM)curlymo Wrote: Just as i though. Both server switched to ipv6 by default. pilight does not yet support ipv6. The same issue applies to smtp.gmail.com. I will prioritize ipv6 knowing this.

Thanks!

(I am sure I did a Thread Subscription (email notification) on this, but I didn't receive a notification... Edit: just read on the forum update topic that it should be fixed)
 
Reply
#7
(12-07-2017, 05:51 PM)curlymo Wrote: Just as i though. Both server switched to ipv6 by default. pilight does not yet support ipv6. The same issue applies to smtp.gmail.com. I will prioritize ipv6 knowing this.

I disabled IPv6 on my Raspberry, hoped this would solve the problem for now, but it didn't. (ping output is ipv4 now, as expected). Now when parsing a sendmail rule the cpu gets really (>98%) high and don't go back to normal.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  error pilightsend, recieve and control hansipi 2 422 11-04-2018, 03:46 PM
Last Post: hansipi
  Error with loading LPF firmware Rschnauzer 14 6,850 02-10-2018, 04:21 PM
Last Post: Rschnauzer
  generic_dimmer error / or not visible in 8.0.5 terrar 13 1,485 01-16-2018, 10:04 PM
Last Post: terrar
  pilight does no longer start because of hardware error stratege-0815 2 965 12-27-2017, 11:16 PM
Last Post: stratege-0815
  [Solved] Error manual compiling Thuurke 2 1,142 09-02-2017, 05:06 PM
Last Post: Thuurke
  ERROR: config is not in a valid json format Sisko4 6 1,484 03-27-2017, 08:24 AM
Last Post: Sisko4
  Setup.sh CMAKE error ripper121 0 767 02-09-2017, 09:22 AM
Last Post: ripper121
  http GET request error 404 Not Found pelipeli 7 2,065 12-02-2016, 01:55 PM
Last Post: pilino1234
  PNG File in webgui jurkla 2 1,176 11-07-2016, 12:02 PM
Last Post: ColdScythe
  sendmail - pilight terminates after smtp error wo_rasp 8 2,428 08-17-2016, 09:13 AM
Last Post: wo_rasp

Forum Jump:


Browsing: 1 Guest(s)