When you
$ telnet downloads.nessus.org 443
does it connect alright?
Jon Barnhardt wrote:
> My bad, forgot to run it as root...
>
> now I see this added in:
>
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 8379 attached
> Process 8373 suspended
> [pid 8379] connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110)
> = -1 ENOENT (No such file or directory)
> [pid 8379] connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110)
> = -1 ENOENT (No such file or directory)
> [pid 8379] connect(4, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("208.67.222.222")}, 28) = 0
> [pid 8379] connect(4, {sa_family=AF_INET, sin_port=htons(443),
> sin_addr=inet_addr("91.121.66.143")}, 16) = -1 EINPROGRESS (Operation now in
> progress)
> Process 8373 resumed
> Process 8379 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 8380 attached
> Process 8373 suspended
> Process 8373 resumed
> Process 8380 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 8381 attached
> Process 8373 suspended
> [pid 8381] connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110)
> = -1 ENOENT (No such file or directory)
> [pid 8381] connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110)
> = -1 ENOENT (No such file or directory)
> [pid 8381] connect(4, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("208.67.222.222")}, 28) = 0
> [pid 8381] connect(4, {sa_family=AF_INET, sin_port=htons(443),
> sin_addr=inet_addr("91.121.66.143")}, 16) = -1 EINPRO
>
>
> ----- Original Message -----
> Hmm, that's it? One of the child procs should be trying to connect to
> the IP I mentioned (downloads.nessus.org).
>
> Mine looks like this (see near the bottom for the connect in question):
>
> [EMAIL PROTECTED]:~# strace -f -etrace=connect
> /opt/nessus/sbin/nessus-update-plugins
> Process 23882 attached
> [pid 23882] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
> 110) = -1 ENOENT (No such file or dir
> ectory)
> [pid 23882] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
> 110) = -1 ENOENT (No such file or dir
> ectory)
> [pid 23882] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
> 110) = -1 ENOENT (No such file or dir
> ectory)
> [pid 23882] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
> 110) = -1 ENOENT (No such file or dir
> ectory)
> Process 23882 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23883 attached
> Process 23883 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23884 attached
> Process 23884 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23885 attached
> Process 23885 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23886 attached
> Process 23881 suspended
> Process 23881 resumed
> Process 23886 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23887 attached
> Process 23881 suspended
> [pid 23887] connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
> 110) = -1 ENOENT (No such file or dir
> ectory)
> [pid 23887] connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
> 110) = -1 ENOENT (No such file or dir
> ectory)
> [pid 23887] connect(4, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("<edited out>")}, 28) = 0
> [pid 23887] connect(4, {sa_family=AF_INET, sin_port=htons(443),
> sin_addr=inet_addr("91.121.66.143")}, 16) = -1
> EINPROGRESS (Operation now in progress)
> Process 23881 resumed
> Process 23887 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23889 attached
> Process 23881 suspended
> Process 23881 resumed
> Process 23889 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23890 attached
> Process 23881 suspended
> Process 23881 resumed
> Process 23890 detached
> --- SIGCHLD (Child exited) @ 0 (0) ---
> Process 23881 detached
>
> Maybe strace's -f option is different in Ubuntu -- you want to follow
> forks. Seems unlikely but...
>
>
>
> Jon Barnhardt wrote:
>
>> When I run the strace command I get the following:
>>
>> Process 8341 attached
>> [pid 8341] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
>> 110) = -1 ENOENT (No such file or directory)
>> [pid 8341] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
>> 110) = -1 ENOENT (No such file or directory)
>> [pid 8341] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
>> 110) = -1 ENOENT (No such file or directory)
>> [pid 8341] connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"},
>> 110) = -1 ENOENT (No such file or directory)
>> Process 8340 suspended
>> Process 8340 resumed
>> Process 8341 detached
>> --- SIGCHLD (Child exited) @ 0 (0) ---
>>
>> btw: nessus.org resolves to 66.240.11.101
>>
>> thanks
>>
>> _________________
>> Jon
>>
>>
>>
>>
>> ----- Original Message -----
>> Are you sure this isn't a network problem? Looks like my
>> nessus-update-plugins is hitting 91.121.66.143:443. Are you able to get
>> there with something like lynx or telnet?
>>
>> # strace -f -etrace=connect /path/to/nessus-update-plugins
>>
>> will show you the IP it's trying if for some reason it's different than
>> mine.
>>
>> Jon Barnhardt wrote:
>>
>>
>>> Hi all,
>>>
>>> I have been trying to update my nessus plugin feed for a couple of days now
>>> with no success.
>>>
>>> Here is the recap:
>>>
>>> Was running Ubuntu 6.10 and everything was working fine.
>>> I upgraded Ubuntu to version 7.10 and ran the nessus .deb file for gutsy
>>> (7.10) nessus version 3.2.1.
>>> I then registered the feed using the activation code provided via new
>>> registration.
>>>
>>> When I try to run: sudo nessus-update-plugins
>>>
>>> I receive:
>>> An unknown HTTP error has occured (http error code: 404)
>>> Could not retrieve the plugins MD5
>>> Aborting
>>>
>>> If I run: sudo nessus-fetch --check
>>>
>>> I get:
>>> nessus-fetch is not configured to receive a plugin feed.
>>>
>>>
>>> Any ideas?
>>> thanks in advance.
>>>
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
