154 155 156 SEEN-BY: 1/157 158 159 160 161 162 163 164 165 166 168 169
Looks like something burped here.. Maybe over two messages as well...
My plan is to netmail all NET 4 nodes and let them know the NET 4 HUB is shifting to a new instance hosted by myself. In preparation for the cut-over I am asking all NET 4 nodes to check the domain name they poll for the NET 4 HUB.
Please ensure you are polling net4.fsxnet.nz:24560
Please ensure you are polling net4.fsxnet.nz:24560
When we cut over to the new NET 4 HUB instance I will update the DNS records to point to the new HUB.
I plan to do this on 31 March (my time in New Zealand, or likely to be
30 March elsewhere in the world)... and when I do we will ensure the
file and echomail links to the 'old' HUB will be closed down. I'll then ask Dan to shutdown that server.
I'm picking if some sysops who run their BBS on 'auto' then login to
find no new traffic on fsxNet they may come calling to me then. We'll that's the thinking..
I am also aware that there are a number of inactive nodes in NET 4 and plan to prune them in early April once the cut over is done. In the meantime I have taken over NET 4 nodelist segment duties and marked a number of nodes a 'Down' that appear to be long inactive based on stats Dan's system is posting each day to the Stats echo.
On 17 Mar 2024 at 02:13p, Avon pondered and said...
Please ensure you are polling net4.fsxnet.nz:24560
another reminder if you are a NET 4 node please ensure you have the above domain name and port set up to poll the 21:4/100 HUB.
When we cut over to the new NET 4 HUB instance I will update the DNS
Just changed over Avon!! I am now polling net4.fsxnet.nz...
Al
On 27 Mar 2024 at 07:46p, Al DeRosa pondered and said...
thanks Al.
if you have any issues in the coming days when we cut over to the new
NET 4 HUB do let me know ..
On 17 Mar 2024 at 02:13p, Avon pondered and said...
Please ensure you are polling net4.fsxnet.nz:24560
another reminder if you are a NET 4 node please ensure you have the above domain name and port set up to poll the 21:4/100 HUB.
When we cut over to the new NET 4 HUB instance I will update the DNS records to point to the new HUB.
I plan to do this on 31 March (my time in New Zealand, or likely to b 30 March elsewhere in the world)... and when I do we will ensure the file and echomail links to the 'old' HUB will be closed down. I'll th ask Dan to shutdown that server.
this is coming the in the next few days.
I'm picking if some sysops who run their BBS on 'auto' then login to find no new traffic on fsxNet they may come calling to me then. We'll that's the thinking..
I am also aware that there are a number of inactive nodes in NET 4 an plan to prune them in early April once the cut over is done. In the meantime I have taken over NET 4 nodelist segment duties and marked a number of nodes a 'Down' that appear to be long inactive based on sta Dan's system is posting each day to the Stats echo.
..as is this :)
Final call, all NET 4 nodes.. ding ding...
OK folks I'm starting the change over process now, so this will mean some niggles for active NET 4 nodes over the coming 24 hours.
Shortly I will be de-linking NET 1 from the 'old' NET 4 HUB and updating the DNS records for net4.fsxnet.nz to point to the new of NET 4 instance
I will be running. I'll also link NET 1 to this new version of the NET 4 HUB.
Shortly I will be de-linking NET 1 from the 'old' NET 4 HUB and updating
If you're a NET 4 node and having issues getting hooked up to the new instance of the NET 4 HUB please email me avon@bbs.nz and I'll work with you to get hooked up.
In the coming 2 weeks once the cut over has occurred I plan to revisit
the NET 4 nodelist segment and prune it where necessary.
I'll also work to start posting some stats from the NET 4 system I have spun up but that's a secondary priority at the moment.
Sysop: | Gary Ailes |
---|---|
Location: | Pittsburgh, PA |
Users: | 132 |
Nodes: | 5 (0 / 5) |
Uptime: | 196:39:25 |
Calls: | 733 |
Files: | 2,171 |
Messages: | 81,894 |