Send Netdot-devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."


Today's Topics:

   1. [Netdot - Bug #1790] FATAL - Could not get a valid        iptree4
      from cache ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Tue, 25 Mar 2014 14:00:11 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1790] FATAL - Could not get a
        valid   iptree4 from cache
To: [email protected], [email protected]
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1790 has been updated by casey ransom.


I happened to hit the bug as well. We are still running 1.0.4 and verified that 
we are getting the same results from iptree.pl as Matej and Alen.  Is there any 
other workaround for the missing byte?
----------------------------------------
Bug #1790: FATAL - Could not get a valid iptree4 from cache
https://osl.uoregon.edu/redmine/issues/1790#change-3159

Author: Alen F
Status: New
Priority: Urgent
Assignee: Alen F
Category: Netdot
Target version: 1.0.5
Resolution: 


Hello,

since Upgrade to 1.5 this error is on add/delete etc.

IP Tree Update not solve the problem.

kind regards



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel


End of Netdot-devel Digest, Vol 84, Issue 6
*******************************************

Reply via email to