 | | | | | | |
| |
|
Hi all,
we are currently rebuilding the indexes of the LUGNET news server. This affects
display and performance of the news web pages, but does not affect the NNTP
access. We expect rebuild to complete by about 7 a.m. EDT, and reported search
issues will hopefully be resolved afterwards.
Also, we have been notified that some users may access the NNTP server using
port 8000. This is currently not supported and you are encouraged to move over
to using the "official" port 1119. If and when port 8000 will become available
again will be subject to another announcement.
We have received reports about some news headers no longer being set as they
used to be, the X-Real-Life header in particular (which is important for the
display behavior of posts written by registered users). This has been resolved
and should work fine after the reindexing is complete. Please note that the
posts created between June 17, 5:45 a.m. EDT and June 19, 3:00 a.m. EDT
(approx.) will not be corrected in terms of the X-Real-Life headers.
If you experience other unexpected behavior, please continue to let us know.
Thanks,
Jerry
| | | | | | | | | | | | | | | |
In lugnet.announce, Gereon Stein wrote:
[ ... snipped ... ]
>
> Also, we have been notified that some users may access the NNTP server using
> port 8000. This is currently not supported and you are encouraged to move over
> to using the "official" port 1119. If and when port 8000 will become available
> again will be subject to another announcement.
[ ... snipped ... ]
I always used port 8080 but that is not working now. I reset my connection to
use port 1119 but it isn't working either. Is anyone else having a problem with
port 1119?
Mike
| | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.admin.general, Mike Walsh wrote:
> In lugnet.announce, Gereon Stein wrote:
>
> [ ... snipped ... ]
>
> >
> > Also, we have been notified that some users may access the NNTP server using
> > port 8000. This is currently not supported and you are encouraged to move over
> > to using the "official" port 1119. If and when port 8000 will become available
> > again will be subject to another announcement.
>
>
> [ ... snipped ... ]
>
> I always used port 8080 but that is not working now. I reset my connection to
> use port 1119 but it isn't working either. Is anyone else having a problem with
> port 1119?
Mike, you got me here: 8080 is certainly no port I heard of so far (it's a
common "high" port for some webservers, but AFAIK only 8000 and 1119 are said to
have been used for NNTP client access).
Please tell me we have a misunderstanding here and you are talking about _web
browser_ access (which should work on the standard port 80 everyone is using).
Otherwise, please specify the client program you are using and I will try to
find out what's wrong. 1119 is definitely the NNTP server port and it positively
does work (I am using it heavily and lots of others are, too).
Please check that news.lugnet.com and www.lugnet.com point to the same IP
address now (212.112.227.14). If your DNS reports other addresses, this could as
well be causing the error.
As a side note, index rebuild appears to be successful, as searches are looking
significantly better now (rebuild is approx. 80% complete now and counting...)
Regards,
Jerry
| | | | | | | | | | | | | | | | | | | | | | | |
Ok, my apologies - I've learned a bit about history and news server ports used
by LUGNET :-)
Okay, from now on, ports 119, 1119, 8000 and 8080 are operational for NNTP
access again. I will be monitoring usage of the individual ports and if I find
any of them unused I will shut those down for security reasons again. I've heard
virtually noone uses the "standard" NNTP port much, but I'll let time show...
Just to be sure: If you can, please try to always use port 1119. Only if this
does not work, try 8000, 8080 or 119 (in that order please).
Thanks,
Jerry
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
Good morning,
thanks to feedback from some users I noticed that image display in the
LUGNET Guide did not work properly.
I have reinstalled the image set und fixed a couple of links - now
everything appears to be operational again.
Regards,
Jerry
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.admin.general, Gereon Stein wrote:
> Ok, my apologies - I've learned a bit about history and news server ports used
> by LUGNET :-)
>
> Okay, from now on, ports 119, 1119, 8000 and 8080 are operational for NNTP
> access again. I will be monitoring usage of the individual ports and if I find
> any of them unused I will shut those down for security reasons again. I've heard
> virtually noone uses the "standard" NNTP port much, but I'll let time show...
>
> Just to be sure: If you can, please try to always use port 1119. Only if this
> does not work, try 8000, 8080 or 119 (in that order please).
>
> Thanks,
>
> Jerry
Once the ports are finalised it would be worth updating this page.
http://news.lugnet.com/news/
Tim
| | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
"Gereon "Jerry" Stein" <gereon@zweistein.de> wrote in message
news:J13wDy.AuC@lugnet.com...
[ ... snipped ... ]
> >
>
> Mike, you got me here: 8080 is certainly no port I heard of so far (it's a
> common "high" port for some webservers, but AFAIK only 8000 and 1119 are
> said to
> have been used for NNTP client access).
Well, I was definitely using port 8080, yet another undocumented port?
> Please tell me we have a misunderstanding here and you are talking about
> _web
> browser_ access (which should work on the standard port 80 everyone is
> using).
Nope. Using Outlook Express for NNTP access.
>
> Otherwise, please specify the client program you are using and I will try
> to
> find out what's wrong. 1119 is definitely the NNTP server port and it
> positively
> does work (I am using it heavily and lots of others are, too).
As far as I can tell, my employer is blocking port 1119 but not 8080 (which
I used to use. I can connect to LUGNET via port 1119 from home or as I am
right now, from a hotel. Any chance you make port 8080 work?
[ ... snipped ... ]
Mike
--
Mike Walsh - mike_walsh at mindspring.com
http://www.ncltc.cc - North Carolina LEGO Train Club
http://www.carolinatrainbuilders.com - Carolina Train Builders
http://www.bricklink.com/store.asp?p=mpw - CTB/Brick Depot
| | | | | | | | | | | | | | | | | | | | | | | |
"Mike Walsh" <mike_walsh@mindspring.com> wrote in message
news:J18LK0.GDB@lugnet.com...
[ ... snipped ... ]
>
> As far as I can tell, my employer is blocking port 1119 but not 8080
> (which I used to use. I can connect to LUGNET via port 1119 from home or
> as I am right now, from a hotel. Any chance you make port 8080 work?
>
> [ ... snipped ... ]
[ ... snipped ... ]
Caught the other post about the ports, I have switched back to 8080 and am
now able to connect from work.
Mike
--
Mike Walsh - mike_walsh at mindspring.com
http://www.ncltc.cc - North Carolina LEGO Train Club
http://www.carolinatrainbuilders.com - Carolina Train Builders
http://www.bricklink.com/store.asp?p=mpw - CTB/Brick Depot
| | | | | | | | | | | | | | | | | | | | | | | |
Mike Walsh schrieb:
>
> As far as I can tell, my employer is blocking port 1119 but not 8080 (which
> I used to use. I can connect to LUGNET via port 1119 from home or as I am
> right now, from a hotel. Any chance you make port 8080 work?
Hi Mike,
I have enabled both port 8000 and 8080 (due to other user requests) for
NNTP. We are now monitoring port usage and will decide later on, which
one of these two is going to stay. Currently it's about 50:50, so the
result may well be we'll be keeping both online.
If you encounter any problems accessing the NNTP service, please let me
know; I have tested access on all ports without any issues.
Thanks,
Jerry
| | | | | | | | | | | | | | | | | |
Just to keep you all updated,
the rebuild of the search index is still under way - apparently there is quite a
lot to index after about 8 years of service ;-)
It seems that the issues some of you reported will be gone after the rebuild
completes. Normal article browsing (and posting) already works fine and the
search results that are returned right now look promising as well. Also, the
rebuild does not seem to have any negative effects on server performance.
Please keep us updated about any observations you make. It looks like we are
really close to a normal state of service again.
Thanks,
Jerry
| | | | | | |
