[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: server incorrectly believes IP address has changed

     On Tue, 20 Nov 2007 22:31:24 +0000 Robert Hogan <robert@xxxxxxxxxxxxxxx>

>On Tuesday 20 November 2007 21:34:16 you wrote:
>>      cached-routers and cached-routers.new are not the file names used in
>>, but rather cached-descriptors and cached-descriptors.new,
>> and in my original message, I wrote:
>>  ->     I restarted my tor server a couple of hours ago, and since then, =
>> has ->been acting very peculiarly.  Here are the notice-level log file
>> entries since ->startup.  Note that I deleted cached-descriptors and
>> cached-descriptors.new ->after shutting down tor and before shutting down
>> the system several hours prior ->to this startup.
>Ah, missed that. It looks like cached-routers is still a fallback though, s=
>if it is still there it will get read. In fact, if cached-routers *was* sti=

     It wasn't.  I got rid of cached-routers{,.new} after installing the first
version that used the new names.
>present  that would explain why the address was noticeably out of date.=20
>> >occasion my own *guess* would be that tor is using the old IP stored
>> > there,=3D =3D20
>> >especially since was your address at one point:
>> >=3D20
>> >http://www.google.com/search?hl=3D3Den&q=3D3Dmycroftsotherchild+66.225.4=
>> >t=3D nG=3D3DSearch
>>      Yes, the ISP has a limited list of IP addresses that it assigns, so
>> the same addresses do recur frequently.  In this case, I noted,
>>  ->Nov 20 06:29:37.282 [notice] Now checking whether ORPort
>> and DirPort are reachable... (this may take up to 20
>> minutes -- look for log messages indicating success) ->
>>  ->     Note that the above address was incorrect.  The correct address
>> was, and ->still is,  It has not changed since before the
>> system was ->rebooted.
>> >Whether it 's a good thing for Tor to just try the last known good
>> > address=3D =3D20
>> >rather than  figure it out all over again on the off-chance it may be out
>> > o=3D f=3D20
>> >date, I don't know.
>>      I thought the point of specifying a host+domain name in the "Address"
>> line was to get tor to *look it up in the name server net*.

     I still don't understand why tor did *not* look it up while starting.  If
it had looked up the name, it would have gotten the correct address.
     BTW, it is still running fine since I restarted it at 08:33 this morning
to get rid of the weird behavior, which I did without again deleting the
cached-descriptors{,.new} files.  What exactly does tor do differently about
its own address when those files are not present at startup?  I.e., what is
it doing differently in that situation that it fails to look up the IP address

Address mars.thruhere.net

that is in the torrc file while starting up?
     Note to Robert Hogan:  the copy addressed to you of my previous
message bounced.  Here are the errors, indented by a blank:

    ----- The following addresses had permanent fatal errors -----
     (reason: 550-Verification failed for <bennett@xxxxxxxxxx>)
    ----- Transcript of session follows -----
 ... while talking to roberthogan.net.:
 >>> DATA
 <<< 550-Verification failed for <bennett@xxxxxxxxxx>
 <<< 550-Called:
 <<< 550-Sent:     RCPT TO:<bennett@xxxxxxxxxx>
 <<< 550-Response: 550 5.7.1 <bennett@xxxxxxxxxx>... Access denied
 <<< 550 Sender verify failed
 550 5.1.1 <robert@xxxxxxxxxxxxxxx>... User unknown
 <<< 503-All RCPT commands were rejected with this error:
 <<< 503-Sender verify failed
 <<< 503 Valid RCPT command must precede DATA

                                  Scott Bennett, Comm. ASMELG, CFIAG
* Internet:       bennett at cs.niu.edu                              *
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *