search

wwivbbs / wwiv

WWIV BBS Software v5
http://www.wwivbbs.org
Other
186 stars 71 forks source link

Funky network3 logging #1103

Closed wwiv closed 7 years ago

wwiv commented 7 years ago

Lots of renaming plus a " Missing Net or Node. Unable to parse address: 8304"

2016-11-29 20:21:33,555 INFO  network3 version 5.2.0.2314 (Nov 29 2016, 06:23:16)
2016-11-29 20:21:33,555 INFO  network3 starting at Tue Nov 29 20:21:33 2016
2016-11-29 20:21:33,555 INFO  command line: .10 
2016-11-29 20:21:33,555 INFO  NETWORK3 for network: WWIVnet-FTN
2016-11-29 20:21:33,555 INFO  Sending Feedback.
2016-11-29 20:21:33,570 INFO  Writing BBSDATA.NET...
2016-11-29 20:21:33,570 INFO  Writing BBSDATA.IND...
2016-11-29 20:21:33,570 INFO  Writing BBSDATA.ROU...
2016-11-29 20:21:33,586 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,586 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,602 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,602 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,617 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,617 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,633 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,633 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,648 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,648 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,664 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:21:33,664 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,588 INFO  network3 version 5.2.0.2314 (Nov 29 2016, 06:23:16)
2016-11-29 20:22:40,588 INFO  network3 starting at Tue Nov 29 20:22:40 2016
2016-11-29 20:22:40,588 INFO  command line: .1 Y 
2016-11-29 20:22:40,588 INFO  NETWORK3 for network: FidoNet
2016-11-29 20:22:40,604 INFO  Sending Feedback.
2016-11-29 20:22:40,604 INFO  Writing BBSDATA.NET...
2016-11-29 20:22:40,604 INFO  Writing BBSDATA.IND...
2016-11-29 20:22:40,604 INFO  Writing BBSDATA.ROU...
2016-11-29 20:22:40,619 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,619 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,619 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,635 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,635 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,650 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,650 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,666 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,666 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,682 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,682 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,697 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,697 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,713 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,728 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,728 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,744 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,744 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,760 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,760 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,775 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,775 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,791 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,791 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,806 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,806 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,822 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,822 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,838 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,853 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,853 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,869 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,869 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,884 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,884 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,900 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,900 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,900 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,916 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,916 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,931 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,931 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,931 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,947 ERROR Missing Net or Node. Unable to parse address: 8304
2016-11-29 20:22:40,947 ERROR Missing Net or Node. Unable to parse address: 8304
2017-01-14 20:18:47,644 INFO  network3 version 5.2.0.2430 (Dec 30 2016, 16:52:01)
2017-01-14 20:18:47,691 INFO  network3 starting at Sat Jan 14 20:18:47 2017
2017-01-14 20:18:47,691 INFO  command line: /? 
2017-06-08 14:50:42,441 INFO  network3 version 5.3.0.2532 (Mar  4 2017, 14:53:15)
2017-06-08 14:50:42,457 INFO  network3 starting at Thu Jun  8 14:50:42 2017
2017-06-08 14:50:42,457 INFO  command line: .4 Y 
2017-06-08 14:50:42,457 INFO  NETWORK3 for network: WWIVnet
2017-06-08 14:50:43,128 INFO  I am the nc, my node # is @1
2017-06-08 14:50:43,128 INFO  Writing BBSDATA.NET...
2017-06-08 14:50:43,143 INFO  Writing BBSDATA.IND...
2017-06-08 14:50:43,143 INFO  Writing BBSDATA.ROU...
2017-06-08 14:50:43,143 INFO  Writing BBSDATA.REG...
2017-06-08 14:50:43,159 INFO  renamed file to: M:\WS\FILENET\p1-3-0.net
2017-06-08 14:50:43,159 INFO  renamed file to: M:\WS\FILENET\p1-3-1.net
2017-06-08 14:50:43,159 INFO  renamed file to: M:\WS\FILENET\p1-3-2.net
2017-06-08 14:50:43,174 INFO  renamed file to: M:\WS\FILENET\p1-3-3.net
2017-06-08 14:50:43,174 INFO  renamed file to: M:\WS\FILENET\p1-3-4.net
2017-06-08 14:50:43,174 INFO  renamed file to: M:\WS\FILENET\p1-3-5.net
2017-06-08 14:50:43,190 INFO  renamed file to: M:\WS\FILENET\p1-3-6.net
2017-06-08 14:50:43,190 INFO  renamed file to: M:\WS\FILENET\p1-3-7.net
2017-06-08 14:50:43,206 INFO  renamed file to: M:\WS\FILENET\p1-3-8.net
2017-06-08 14:50:43,206 INFO  renamed file to: M:\WS\FILENET\p1-3-9.net
2017-06-08 14:50:43,221 INFO  renamed file to: M:\WS\FILENET\p1-3-10.net
2017-06-08 14:50:43,221 INFO  renamed file to: M:\WS\FILENET\p1-3-11.net
2017-06-08 14:50:43,221 INFO  renamed file to: M:\WS\FILENET\p1-3-12.net
2017-06-08 14:50:43,237 INFO  renamed file to: M:\WS\FILENET\p1-3-13.net
2017-06-08 14:50:43,237 INFO  renamed file to: M:\WS\FILENET\p1-3-14.net
2017-06-08 14:50:43,237 INFO  Sending Feedback.
2017-06-08 14:50:43,783 INFO  Writing type 2/0 message to packet: local.net; title: WWIVnet analysis on 06/08/17
2017-06-08 14:50:43,798 INFO  network3 exiting at Thu Jun  8 14:50:43 2017

2017-11-12 19:10:48,288 INFO  network3 version 5.3.0.2621 (Nov  8 2017, 06:43:25)
2017-11-12 19:10:48,288 INFO  network3 starting at Sun Nov 12 19:10:48 2017
2017-11-12 19:10:48,288 INFO  command line: --v=0 .0 Y 
2017-11-12 19:10:48,288 INFO  NETWORK3 for network: WWIVnet-Legacy
2017-11-12 19:10:48,288 ERROR ERROR: bbslist.net didn't parse.
2017-11-12 19:10:48,288 INFO  network3 exiting at Sun Nov 12 19:10:48 2017

2017-11-12 19:11:27,695 INFO  network3 version 5.3.0.2621 (Nov  8 2017, 06:43:25)
2017-11-12 19:11:27,695 INFO  network3 starting at Sun Nov 12 19:11:27 2017
2017-11-12 19:11:27,695 INFO  NETWORK3 for network: WWIVnet-Legacy
2017-11-12 19:11:27,695 ERROR ERROR: bbslist.net didn't parse.
2017-11-12 19:11:27,695 INFO  network3 exiting at Sun Nov 12 19:11:27 2017

2017-11-12 19:14:39,612 INFO  NETWORK3 version 5.3.0.2621 (Nov  8 2017, 06:43:25)
2017-11-12 19:14:39,612 INFO  NETWORK3 starting at Sun Nov 12 19:14:39 2017
2017-11-12 19:14:39,612 INFO  command line: .4 Y 
2017-11-12 19:14:39,612 INFO  NETWORK3 for network: WWIVnet
2017-11-12 19:14:39,628 INFO  I am the nc, my node # is @1
2017-11-12 19:14:39,628 INFO  Writing BBSDATA.NET...
2017-11-12 19:14:39,643 INFO  Writing BBSDATA.IND...
2017-11-12 19:14:39,643 INFO  Writing BBSDATA.ROU...
2017-11-12 19:14:39,643 INFO  Writing BBSDATA.REG...
2017-11-12 19:14:39,659 INFO  renamed file to: M:\WS\FILENET\p1-3-0.net
2017-11-12 19:14:39,674 INFO  renamed file to: M:\WS\FILENET\p1-3-1.net
2017-11-12 19:14:39,690 INFO  renamed file to: M:\WS\FILENET\p1-3-2.net
2017-11-12 19:14:39,690 INFO  renamed file to: M:\WS\FILENET\p1-3-3.net
2017-11-12 19:14:39,706 INFO  renamed file to: M:\WS\FILENET\p1-3-4.net
2017-11-12 19:14:39,706 INFO  renamed file to: M:\WS\FILENET\p1-3-5.net
2017-11-12 19:14:39,721 INFO  renamed file to: M:\WS\FILENET\p1-3-6.net
2017-11-12 19:14:39,721 INFO  renamed file to: M:\WS\FILENET\p1-3-7.net
2017-11-12 19:14:39,737 INFO  renamed file to: M:\WS\FILENET\p1-3-8.net
2017-11-12 19:14:39,737 INFO  renamed file to: M:\WS\FILENET\p1-3-9.net
2017-11-12 19:14:39,752 INFO  renamed file to: M:\WS\FILENET\p1-3-10.net
2017-11-12 19:14:39,768 INFO  renamed file to: M:\WS\FILENET\p1-3-11.net
2017-11-12 19:14:39,768 INFO  renamed file to: M:\WS\FILENET\p1-3-12.net
2017-11-12 19:14:39,784 INFO  renamed file to: M:\WS\FILENET\p1-3-13.net
2017-11-12 19:14:39,784 INFO  renamed file to: M:\WS\FILENET\p1-3-14.net
2017-11-12 19:14:39,799 INFO  renamed file to: M:\WS\FILENET\p1-3-15.net
2017-11-12 19:14:39,815 INFO  renamed file to: M:\WS\FILENET\p1-3-16.net
2017-11-12 19:14:39,815 INFO  renamed file to: M:\WS\FILENET\p1-3-17.net
2017-11-12 19:14:39,830 INFO  renamed file to: M:\WS\FILENET\p1-3-18.net
2017-11-12 19:14:39,846 INFO  renamed file to: M:\WS\FILENET\p1-3-19.net
2017-11-12 19:14:39,846 INFO  renamed file to: M:\WS\FILENET\p1-3-20.net
2017-11-12 19:14:39,862 INFO  renamed file to: M:\WS\FILENET\p1-3-21.net
2017-11-12 19:14:39,877 INFO  renamed file to: M:\WS\FILENET\p1-3-22.net
2017-11-12 19:14:39,893 INFO  renamed file to: M:\WS\FILENET\p1-3-23.net
2017-11-12 19:14:39,908 INFO  renamed file to: M:\WS\FILENET\p1-3-24.net
2017-11-12 19:14:39,908 INFO  renamed file to: M:\WS\FILENET\p1-3-25.net
2017-11-12 19:14:39,924 INFO  renamed file to: M:\WS\FILENET\p1-3-26.net
2017-11-12 19:14:39,940 INFO  Sending Feedback.
2017-11-12 19:14:40,064 INFO  Writing type 2/0 message to packet: local.net; title: WWIVnet analysis on 11/12/17
2017-11-12 19:14:40,064 INFO  NETWORK3 exiting at Sun Nov 12 19:14:40 2017
wwiv commented 7 years ago

Looks like the Missing Net or Node. Unable to parse address: 8304 is because some nECHO_TAG.net file has a wwiv node number in it instead of just FTN addresses. I think I found it and improved the error message to include the file it was reading.

wwiv commented 7 years ago

The renamed file to: is just because you have lots of S.net outbound files lying around that all get renamed to P.net files so they'll get re-processed incase any network routing changes. I'll change the message to include the original filename (if possible), so the logging makes sense.

MarkHofmann11 commented 7 years ago

True - the issue is 4.24a doesn't use an FTN address in the Nxxxxx.net files. In order to work with WWIVTOSS, I have Fidonet style networks that all have fake WWIV style nodes (8304). At the current time, NETWORK3 is unable to process them due to this. It seems this needs an IF legacy WWIV, then don't use FTN style address checking or something to that effect.

On Thu, Nov 16, 2017 at 10:53 PM, Rushfan notifications@github.com wrote:

Looks like the Missing Net or Node. Unable to parse address: 8304 is because some nECHO_TAG.net file has a wwiv node number in it instead of just FTN addresses. I think I found it and improved the error message to include the file it was reading.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/wwivbbs/wwiv/issues/1103#issuecomment-345138453, or mute the thread https://github.com/notifications/unsubscribe-auth/AMl_uXFjS0zGHl9GcgDF6BaG5ARevO_0ks5s3QM0gaJpZM4QbJ6I .