+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156
This I do not understand, as it is clearly configured under the echomail nodes.
+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156
This I do not understand, as it is clearly configured under the echomail nodes.
It seems there is a small error in the message text there which I've just fixed
up.
That error means that you have a password set in your entry for 46:1/156 but the PKT file itself did not have the password you configured.
(Or it means you have no active configuration for 46:1/156 but you've already
mentinoned that you do).
In the next build it will properly report "PKT password does not match password
set for 46:1/156".
... What was the best thing before sliced bread?
+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156
It ended up being that I had a PKT password set, but the hub did not. All good now =)+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156
I think it's saying that you don't have any configuration for 46:1/156 in your
node list. What is 46:1/156? your node or the hub node?
... My tagline could eat your tagline for breakfast
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,163 |
| Nodes: | 17 (0 / 17) |
| Uptime: | 459:15:24 |
| Calls: | 509,439 |
| Calls today: | 2 |
| Files: | 262,463 |
| U/L today: |
1 files (1,436K bytes) |
| D/L today: |
588 files (129M bytes) |
| Messages: | 470,610 |