There seems to be a problem with the recent .090

OpenXP doesn't like it. :(



--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Re: nl problem
By: Ogg to All on Fri Mar 31 2023 08:17 am

There seems to be a problem with the
recent .090

OpenXP doesn't like it. :(

NL problem? Recent .090?

... que?

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Imzadi Box -*- box.imzadi.de (420:2/1)

Hello Phigan!

** On Saturday 01.04.23 - 09:48, Phigan wrote to Ogg:

NL problem? Recent .090?

... que?

Yup. Nodelist problem. Had to delete it to get my OpenXP to
resume normal operations.

--

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Re: nl problem
By: Ogg to Phigan on Sat Apr 01 2023 07:45 pm

Yup. Nodelist problem. Had to delet
it to get my OpenXP to
resume normal operations.

Ah, soz, my head was entirely someplace
else :). What system do you need to use
OpenXP with?

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Imzadi Box -*- box.imzadi.de (420:2/1)

Hello Phigan!

Ah, soz, my head was entirely someplace
else :). What system do you need to use
OpenXP with?

OpenXP operates in Windows and Linux.

A nodelist isn't specifically required for most echom messaging
operations, so I can live without it.


--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Re: nl problem
By: Ogg to Phigan on Sun Apr 02 2023 09:20 pm

OpenXP operates in Windows and Linux.

Soz again, that's not what I meant.. You are using OpenXP with a BBS, right? Which software are you using?

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Imzadi Box -*- box.imzadi.de (420:2/1)

Hello Phigan!

OpenXP operates in Windows and Linux.

Soz again, that's not what I meant.. You are using OpenXP with a BBS, right?

No.

Which software are you using?

OpenXP is a standalone point messaging program. It doesn't need
to be associated with any "bbs software".


--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Re: nl problem
By: Ogg to Phigan on Mon Apr 03 2023 02:48 pm

OpenXP is a standalone point messagi
program. It doesn't need
to be associated with any "bbs
software".

Ahh, gotcha. Thanks for the
clarification. I tried some offline
readers back in the day, but never got
the hang of them I guess.

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Imzadi Box -*- box.imzadi.de (420:2/1)

Hello Phigan!

Ahh, gotcha. Thanks for the
clarification. I tried some offline
readers back in the day, but never got
the hang of them I guess.

I built this site for it, and include some screenshots:

https://openxp.kolico.ca/

--

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Am 31.03.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:

Hallo Ogg,

There seems to be a problem with the recent .090
OpenXP doesn't like it. :(

Sorry for the late answer, I don't read mails every day...

I've just checked, and in my OpenXP installation, the 090 nodelist is
being used.

I also removed the nodelist from OpenXP and re-added WEEDNET.090 and
it got accepted...

Do you have any more information on the problem?
Does the debuglog.txt in the .openxp directory say anything?

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box -*- WeedNet FTN hub (420:2/1.1)

Hello acn!

I also removed the nodelist from OpenXP and re-added WEEDNET.090 and
it got accepted...

Do you have any more information on the problem?
Does the debuglog.txt in the .openxp directory say anything?

My debuglog.txt only tracks data per session. That means, the
next time I launch OpenXP (which I've done since then) there is
a fresh new debuglox.txt file. So, there is no record of the
problem. When I've encountered a "problem with nodelist" error
in the past in othernets, I've just learned to delete the
nodelist and install the next one manually.


--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Am 06.04.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:

Hallo Ogg,

My debuglog.txt only tracks data per session. That means, the
next time I launch OpenXP (which I've done since then) there is
a fresh new debuglox.txt file. So, there is no record of the
problem. When I've encountered a "problem with nodelist" error
in the past in othernets, I've just learned to delete the
nodelist and install the next one manually.

Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box -*- WeedNet FTN hub (420:2/1.1)

Hello acn!

Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).

When I deleted 090, I didn't reactivate the auto nodelist
update part. I'll activate 097 and see what happens next time.
Will there be another nodelist delivery next week?

--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Am 07.04.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:

Hallo Ogg,

When I deleted 090, I didn't reactivate the auto nodelist
update part. I'll activate 097 and see what happens next time.

I hope that it'll work!

Will there be another nodelist delivery next week?

Yes, nodelists will be sent out every friday at 7am CET (via a cronjob
*g*), even if there are no changes.

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box -*- WeedNet FTN hub (420:2/1.1)

Hello acn,

07 Apr 23 11:34, you wrote to Ogg:

Am 06.04.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:

Hallo Ogg,

My debuglog.txt only tracks data per session. That means, the
next time I launch OpenXP (which I've done since then) there is
a fresh new debuglox.txt file. So, there is no record of the
problem. When I've encountered a "problem with nodelist" error
in the past in othernets, I've just learned to delete the
nodelist and install the next one manually.

Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).

the problem is that the header is not updated:

097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006 : 20189


Regards,
--
dp

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 6d 9h 3m 25s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (420:2/3)

Am 13.04.23 schrieb Roon@420:2/3 in WEED_GENERAL:

Hallo Roon,

Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).

the problem is that the header is not updated:

097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006 : 20189

I've looked at the makenl documentation and found the setting
"forcesubmit 1".
I've changed the configuration and so next week the file should
contain also the right day number.

But nevertheless, I'm using the same nodelist in the same software and
I didn't get any errors over all the time...

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box -*- WeedNet FTN hub (420:2/1.1)

Hello Roon!

** On Thursday 13.04.23 - 17:02, Roon wrote to acn:

the problem is that the header is not updated:

097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006 : 20189

Anything after a ; is a comment, no? so, anything on that line
wouldn't matter, no?
--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Hello Ogg,

14 Apr 23 21:26, you wrote to me:

Hello Roon!

** On Thursday 13.04.23 - 17:02, Roon wrote to acn:

the problem is that the header is not updated:

097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006
: 20189

Anything after a ; is a comment, no? so, anything on that line
wouldn't matter, no?

it seems that nodelist compilers are using that line.
i realized that because my Qnode/2 were not using nodelists higher than 006 and tryed to figure out why. and this was the only thing i've found.

Regards,
--
dp

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 8d 7h 52m 28s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (420:2/3)

Hello Roon!

** On Saturday 15.04.23 - 15:53, Roon wrote to Ogg:

Anything after a ; is a comment, no? so, anything on that line
wouldn't matter, no?

it seems that nodelist compilers are using that line.
i realized that because my Qnode/2 were not using nodelists higher than
006 and tryed to figure out why. and this was the only thing i've found.

I could try to replace the number in that line manually. What
should it be?

Meanwhile the recent .104 nodelist causes the same error.

Both .097 and .104 have the first line the same:

;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number
006 : 20189

Instead of 20189, what should that be as well?

--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Am 16.04.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:

Hallo Ogg,

it seems that nodelist compilers are using that line.
i realized that because my Qnode/2 were not using nodelists higher than
006 and tryed to figure out why. and this was the only thing i've found.

I could try to replace the number in that line manually. What
should it be?

Meanwhile the recent .104 nodelist causes the same error.

Both .097 and .104 have the first line the same:

;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number
006 : 20189

Instead of 20189, what should that be as well?

I recompiled the nodelist from last friday with a new option in
makenl's configuration, so that this line also gets recreated every
time.

The line for .104 would be now:

;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189

So the checksum (20189) stays the same :)

The next file, .Z11 with .111, will be sent out on friday.

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box -*- WeedNet FTN hub (420:2/1.1)

Hello acn!

** On Monday 17.04.23 - 13:03, acn wrote to Ogg:

The line for .104 would be now:

;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189

So the checksum (20189) stays the same :)

The next file, .Z11 with .111, will be sent out on friday.

All set and ready for the next one. A few mysteries of
behaviour were uncovered in how OPX operates wrt previous
nodelist files found in /FILES. Now, the processing is set to
delete the .Z## file once it has been processed.

--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Hello acn!

** On Monday 17.04.23 - 13:03, acn wrote to Ogg:

The line for .104 would be now:

;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189

The correct text would be good!

..then the header for http://kolico.ca/ftn/weednet/ would
look right! :D

--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Hello acn!

** On Monday 17.04.23 - 13:03, acn wrote to Ogg:

The line for .104 would be now:

;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189

So the checksum (20189) stays the same :)

The next file, .Z11 with .111, will be sent out on friday.

It all worked this time. But I see that you are not interested
in updating the first line. :(

I suppose it's simpler that way if there are absolutely no
changes.

--
../|ug

--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)

Am 22.04.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:

Hallo Ogg,

The line for .104 would be now:
;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189
So the checksum (20189) stays the same :)
The next file, .Z11 with .111, will be sent out on friday.

It all worked this time. But I see that you are not interested
in updating the first line. :(

That's a lie! Sorry, but that's absolutely not true.

I tried changing a setting in makenl (I've set 'forcesubmit' to 1),
but I have to admit that I'm absolutely no expert in this things.

So, if you know how to setup makenl to achieve this, just tell me how
to do it.

I thought that setting 'forcenl 1' would solve the problem, but it
didn't.

Maybe I have to change my script for checking, compiling, adding to
the filebase and hatching the nodelist further.

I suppose it's simpler that way if there are absolutely no
changes.

As I wouldn't have to change my setup, it would be :)
(and I have not heard from anyone that the 'problem' caused any
problems)

But I'm open for ideas.

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box -*- WeedNet FTN hub (420:2/1.1)

Hello acn!

It all worked this time. But I see that you are not
interested in updating the first line. :(

That's a lie! Sorry, but that's absolutely not true.

I tried changing a setting in makenl (I've set
'forcesubmit' to 1), but I have to admit that I'm
absolutely no expert in this things.

So, if you know how to setup makenl to achieve this, just
tell me how to do it.

The last time I managed a net segment of my own and makenl was
back in the mid 90's. I don't remember its features or
capabilities or if it can manage the first comment line.

But I am sure some sysops here could illuminate.

I suppose it's simpler that way if there are absolutely no
changes.

As I wouldn't have to change my setup, it would be :) (and
I have not heard from anyone that the 'problem' caused any
problems)

No worries. It's just a comment line, and wouldn't affect
operations. The "problem", as we have learned, was how I had
OpenXP setup here to handle new incoming nodelist deliveries.

But I'm open for ideas.

I can ask at least one sysop who manages a segment on another
net how he does it.


--- OpenXP 5.0.57
* Origin: Watch WEEDnet grow, http://kolico.ca/ftn/weednet (420:2/1.10)