.\"// Copyright (c) 2001,2002 RIPE NCC .\"// .\"// All Rights Reserved .\"// .\"// Permission to use, copy, modify, and distribute this software and its .\"// documentation for any purpose and without fee is hereby granted, .\"// provided that the above copyright notice appear in all copies and that .\"// both that copyright notice and this permission notice appear in .\"// supporting documentation, and that the name of the author not be .\"// used in advertising or publicity pertaining to distribution of the .\"// software without specific, written prior permission. .\"// .\"// THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING .\"// ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS; IN NO EVENT SHALL .\"// AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY .\"// DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN .\"// AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF .\"// OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. .\"// .\"// .\"// Copyright (c) 1994 by the University of Southern California .\"// and/or the International Business Machines Corporation. .\"// All rights reserved. .\"// .\"// Permission to use, copy, modify, and distribute this software and .\"// its documentation in source and binary forms for lawful .\"// non-commercial purposes and without fee is hereby granted, provided .\"// that the above copyright notice appear in all copies and that both .\"// the copyright notice and this permission notice appear in supporting .\"// documentation, and that any documentation, advertising materials, .\"// and other materials related to such distribution and use acknowledge .\"// that the software was developed by the University of Southern .\"// California, Information Sciences Institute and/or the International .\"// Business Machines Corporation. The name of the USC or IBM may not .\"// be used to endorse or promote products derived from this software .\"// without specific prior written permission. .\"// .\"// NEITHER THE UNIVERSITY OF SOUTHERN CALIFORNIA NOR INTERNATIONAL .\"// BUSINESS MACHINES CORPORATION MAKES ANY REPRESENTATIONS ABOUT .\"// THE SUITABILITY OF THIS SOFTWARE FOR ANY PURPOSE. THIS SOFTWARE IS .\"// PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, .\"// INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF .\"// MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND .\"// NON-INFRINGEMENT. .\"// .\"// IN NO EVENT SHALL USC, IBM, OR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY .\"// SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, WHETHER IN CONTRACT, .\"// TORT, OR OTHER FORM OF ACTION, ARISING OUT OF OR IN CONNECTION WITH, .\"// THE USE OR PERFORMANCE OF THIS SOFTWARE. .\"// .\"// Questions concerning this software should be directed to .\"// info-ra@isi.edu. .\"// .\"// Author(s): Cengiz Alaettinoglu .\" .\" .TH IRRToolSet 1 local .SH NAME IRRToolSet error and warning messages .SH DESCRIPTION .PP The goal of this document is to clarify the possible errors you may encounter when using IRRToolSet. Some of these errors are listed on the manual pages for the tools. If you didn't find the error on the manual page of the tool you were using, please refer to this page. Some errors wuth obvious explanation are listed here for reference, but to not have any documentation. Still, if description is unclear or unsufficient, please report to irrtoolset@ripe.net. .SH IRR communication errors .PP .B Command errors .PP .PD 0 .P Error: unknown irr protocol , using irrd .P known protocols: irrd(rawhoisd), ripe(bird), ripe_perl .PD 1 .RS .PP The protocol specified with "-protocol" option is unknown or not supported. Use one of the known protocols to connect to IRR server. This option is case-insensitive. This is important which protocol to use, because some client/server protocols are incompatible, and you can get wrong result. Check IRR server documentation and use the protocols which are compatible with it. Please note that there are 3 protocols supported, and the rest are aliases (rawhoisd is the same as irrd and bird is the same as ripe). ripe_perl should be used with old ripe server. .PP .RE .B System errors .PP Error: gethostbyname () failed. .PP Error: socket() failed. .PP Error: connect() failed. .PP Error: fgets() failed. .PP Error: fread() failed. .PP Error: fwrite() failed. .PP Connection to \:\ failed! .RS .PP There could be several reasons for this error: host is unreachable, or some packet filtering is on and you can't send the packets, or the server may be not responding. Check your network setup and host reachability. .PP .RE Warning: setsockopt SO_KEEPALIVE failed! .RS .PP All protocols supported by IRRToolSet are using persistent connection to the IRR server. When the socket for IRR connection is created, SO_KEEPALIVE option is set to enable persistent connection (client has to keep checking if the destination is still alive). See setsockopt(2) manual page for details about possible failures. .PP .RE .B IRR-specific errors .PP Error: setting source to \ failed. .RS .PP One (or several) sources from list are not found on IRR server. If the source setting for IRR server failed, the source list will be default one. Check IRR server documentation for the proper command to get the list of all available sources and default sources. This check is only implemented for irrd(rawhoisd). If you mistyped the source name, re-run the program using "-s " option. .PP .RE Error: current source setting is \. .RS .PP This is rather informational message, preceeded by error message about failed sources setting. It shows the source list which is used currently by the program for querying. If you want to modify this list, use "-s " option. .PP .RE Warning: irrd(rawhoisd) does not yet support rtr-set expansion. .RS .PP Although as-set and route-set expansion is an internal feature of irrd, rtr-set expansion is not implemented yet. In IRRToolSet it is done by external functions, but it still works. So you can safely ignore this warning, this is just a reminder to keep an eye on irrd development and update the code to use internal feature when it is implemented. .PP .RE Warning: key not found error for query .RS .PP Object not found in the database for specified sources. specifies the actual query to the server which returned to objects. The reason can be: .PD 0 .IP \(bu 2 object, source or host name are mistyped and therefore object cannot be found; .IP \(bu 2 this is true error and you're referencing non-existent object, which is supposed to be in the database; check your objects and policy description. .PD 1 .PP .RE Warning: no byte count error for query \. .RS .PP irrd server returns the length of the reply for successful queries with "A". The program is expecting it if query is successful. If it is not received, the warning is issued. This error can also indicate protocol/server incompatibility (for example, RIPE whois server with irrd protocol). Please check IRR server documentation for details. .PP .RE Warning: no end of data line error for query \. .RS .PP After a successful query irrd server issues special "end of data" command, "C". If it is not received after bytes of data, the program complains. This can indicate that query was broken, or incomplete, or some other server error occured. Please check IRR server documentation for details or ask IRR server administration for help. .PP .RE .SH RPSL parser errors .B Lexer errors .PP Error: unknown class .RS .PP Wrong first attribute of the object. This attribute is considered RPSL class name, and determines the object type. The rest of object's attributes can have any order, but the first one should be on the first place. .PP .RE Error: unknown attribute of class .RS .PP Wrong attribute of the object. The attribute is a string followed by ":" which describes the type of data after ":". Object consists of "attribute:value" pairs. For more information on RPSL classes, see RFC 2622. .PP .RE Error: Non-ASCII character encountered .PP Error: unterminated string encountered .PP Error: octal escape sequence is out of bounds .PP Error: bad octal escape sequence .PP Warning: attribute of class is now obsolete. .RS .PP This attribute is described in RPSL dictionary as valid RPSL attribute, but it is now obsoleted and should not be used any longer. See RFC 2622 for more information about RPSL attributes. .PP .RE .B Parser errors .PP Error: syntax error .RS .PP String starts with non-attribute or object is incomplete. .PP .RE Error: "changed: " expected .RS .PP Wrong "changed" attribute. is e-mail address in RFC 822 format, is a date. .PP .RE Error: argument to should match .RS .PP Syntax for some RPSL attributes is defined by regular expressions. The error indicates that attribute's value didn't match the regular expression. .PP .RE Error: argument to should be .RS .PP Generic RPSL attributes have fixed syntax, and exact match is expected. .PP .RE Error: argument to should be blob sequence. .RS .PP Indicates a syntax error in "auth" attribute specification. .PP .RE Warning: unknown protocol , BGP4 assumed. .RS .PP Unknown protocol specified in import/export policy. Defaults to BGP4. The known protocols are listed in RFC 2622, Dictionary section. .PP .RE Error: from expected. .RS .PP Syntax error in "import" attribute specification. See RFC2622 for more details about "import" attribute syntax. .RE .PP Error: to expected. .RS .PP Syntax error in "export" attribute specification. The syntax for "export" attribute is symmetrical for import, with changes: from->to, accept->announce. For more details see RFC2622. .PP .RE .PP Error: badly formed filter/action or keyword NETWORKS/ACTION missing. .RS .PP Syntax error in "default" attibute specification The syntax for "default" attribute is: .PD 0 .P default: to [action ] .P [networks ] .P For more details see RFC2622. .PD 1 .PP .RE Error: TO missing. .RS .PP Syntax error in "default" attribute specification. Please see "default" attribute syntax above. .PP .RE .PP Error: badly formed filter. .RS .PP Syntax error in RPSL filter specification. RPSL filter is an expression over AS-number, prefixes, AS-sets, range operators etc. When applying to a set of routes, it returns the resulting set of routes matched by this filter. There are several types of RPSL filters - prefix filters, AS_path filters, etc. For more details, see RFC2622. .PP .RE .PP Error: in action specification. .RS .PP Syntax error in action specification. "Action" keyword specifies the action to be executed if the route is matched by the filter. The general "action" syntax is: .PD 0 .P action (); .P | action ; .P For more details see RFC2622. .PD 1 .RE .PP Error: integer mask length expected. .RS .PP The integer mask length is a number of bits taken by network number. .PP .RE .PP Error: MASKLEN expected. .RS .PP Syntax error in "ifaddr" attribute specification. The syntax for "ifaddr" attribute is: .PD 0 .P ifaddr: masklen [action ] .PD 1 .RE .PP Error: MASKLEN [] expected. .RS .PP Syntax error in "ifaddr" specification. See "ifaddr" attribute syntax above. .PP .RE .PP Error: unknown protocol . .RS .PP Unknown protocol in peer specification. Known protocols are: BGP4 (default), OSPF, RIP, IGRP, IS-IS, STATIC, RIPng, DVMRP, PIM-DM, PIM-SM, CBT, MOSPF. .PP .RE Error: protocol does not have option