Opened 11 years ago
Last modified 2 years ago
#11437 closed Bug Report - General
thetvdb.py not using proxy — at Version 3
Reported by: | Owned by: | sphery | |
---|---|---|---|
Priority: | minor | Milestone: | needs_triage |
Component: | MythTV - Mythmetadatalookup | Version: | 0.25-fixes |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description (last modified by )
Using 0.25.3-fixes from 20130104 at 010e576 I'm finding that even though mythmetadatalookup's environment has an "http_proxy=" set, ttvdb.py is is ignoring that and still trying to fetch from the Internet directly.
Change History (3)
comment:1 follow-up: 2 Changed 11 years ago by
Status: | new → infoneeded_new |
---|---|
Version: | 0.23-fixes → 0.25-fixes |
comment:2 Changed 11 years ago by
Replying to wagnerrp:
'mythmetadatalookup' does not access the internet in any capacity. It calls external grabber scripts which in turn access the internet. Which grabber script in particular are you referring to?
That's not what strace is telling me here. I've followed the cloning of process/threads up the tree from the process that is making the direct connections. i.e.
connect(29, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, "2400:cb00:2048:1::be5d:fc6e", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28 <unfinished ...>
The process tree leading down to 24472 from the initial process is as follows:
32679 <... clone resumed> child_stack=0xae2f83e4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|C+++ LONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xae2f8ba8, {entry_number:6, base_addr:0xae2f8b40, limit+++ :1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xae2f8ba+++ 8) = 313 \_313 <... clone resumed> child_stack=0xadaf73e4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|C+++ LONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xadaf7ba8, {entry_number:6, base_addr:0xadaf7b40, limit+++ :1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xadaf7ba+++ 8) = 314 \_314 <... clone resumed> child_stack=0xacaf53e4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|C+++ LONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xacaf5ba8, {entry_number:6, base_addr:0xacaf5b40, limit+++ :1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xacaf5ba+++ 8) = 320 \_320 connect(29, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, "2400:cb00:2048:1::be5d:fc6e", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28 <unfinished ...> 320 <... connect resumed> ) = 0 ... 320 write(29, "GET /banners/seasonswide/79349-6"..., 264 <unfinished ...> 320 <... write resumed> ) = 264
None of those intervening processes invokes an execve() so they presumably are threads. One of those threads very much appears to be doing a direct grab.
'mythmetadatalookup' does not access the internet in any capacity. It calls external grabber scripts which in turn access the internet. Which grabber script in particular are you referring to?