headers
Jeffrey M. Vinocur | 4 Mar 2007 22:22

Re: No articles are seen through the news clients

On Wed, 28 Feb 2007, Hirantha Wijayawardena wrote:

> I'm trying to setup INN for last couple of days, still not seeing a posted
> article on Thunderbird/Outlook Express. I'm on Redhat ES 4 with inn-2.3.5
> rpm installations. I am newbie to the news and INN.

I am confused about your intended configuration.  A normal basic INN 
configuration would not require the use of mailpost at all.

Regardless, I think you should look in the news log files to see if you 
can find an error message.

--

-- 
Jeffrey M. Vinocur
jeff <at> litech.org
Permalink | Reply | 3 comments |
headers
Hirantha | 5 Mar 2007 06:31

Re: No articles are seen through the news clients

Hi Jeffrey,

Thanks for the reply.

 From my basic configuration I could do only post but I dont see posted 
messages through news clients. I can see the the post is working through 
/var/log/news/news.notice:

Feb 27 16:05:44 rhel4 nnrpd[31926]: 192.168.128.230 connect
Feb 27 16:05:44 rhel4 nnrpd[31926]: 192.168.128.230 post ok 
<es11i0$v5m$1 <at> rhel4.informatics.lk>
Feb 27 16:05:44 rhel4 nnrpd[31926]: 192.168.128.230 posts received 1 
rejected 0
Feb 27 16:05:44 rhel4 nnrpd[31926]: 192.168.128.230 times user 0.019 
system 0.026 elapsed 0.285

and all posted messages are laying in the /var/spool/news/incoming/ 
directory:

-rw-rw-r--  1 news news  638 Feb 27 15:07 45e3fbf1PwCa7F
-rw-rw-r--  1 news news  646 Feb 27 16:05 45e40980G8NaYG
-rw-rw-r--  1 news news  629 Mar  5 10:49 45eba85erOf4h6

There is no error messages in the log files.

I have set
news:    "|/usr/lib/news/bin/mailpost -d localhost local.test"

Then posted messages are looping continually; /var/log/maillog:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jeffrey M. Vinocur | 6 Mar 2007 03:58

Re: No articles are seen through the news clients

On Mon, 5 Mar 2007, Hirantha wrote:

> Feb 27 16:05:44 rhel4 nnrpd[31926]: 192.168.128.230 post ok 
> <es11i0$v5m$1 <at> rhel4.informatics.lk>
> 
> and all posted messages are laying in the /var/spool/news/incoming/ 
> directory:
> 
> -rw-rw-r--  1 news news  638 Feb 27 15:07 45e3fbf1PwCa7F
> -rw-rw-r--  1 news news  646 Feb 27 16:05 45e40980G8NaYG
> -rw-rw-r--  1 news news  629 Mar  5 10:49 45eba85erOf4h6

Okay, this is definitely a problem.  You should forget about all of the 
mailpost stuff for now and try to get simple posting to work first.

A couple random ideas...

What is "spoolfirst" in inn.conf set to?

Is there definitely an innd running at the time you make these posts?

--

-- 
Jeffrey M. Vinocur
jeff <at> litech.org
Permalink | Reply | 1 comment |
headers
Hirantha | 6 Mar 2007 07:45

Re: No articles are seen through the news clients - SOLVED

Hi Jeffery,

I forget mailpost and did re-installation again and with the basic 
configurations. wow! it worked.

Thanks a lot for your tips and attention to this post, it is really 
appreciated.

Thanks and regards

- Hirantha

Jeffrey M. Vinocur wrote:
> On Mon, 5 Mar 2007, Hirantha wrote:
>
>   
>> Feb 27 16:05:44 rhel4 nnrpd[31926]: 192.168.128.230 post ok 
>> <es11i0$v5m$1 <at> rhel4.informatics.lk>
>>
>> and all posted messages are laying in the /var/spool/news/incoming/ 
>> directory:
>>
>> -rw-rw-r--  1 news news  638 Feb 27 15:07 45e3fbf1PwCa7F
>> -rw-rw-r--  1 news news  646 Feb 27 16:05 45e40980G8NaYG
>> -rw-rw-r--  1 news news  629 Mar  5 10:49 45eba85erOf4h6
>>     
>
> Okay, this is definitely a problem.  You should forget about all of the 
> mailpost stuff for now and try to get simple posting to work first.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
newsmaster | 6 Mar 2007 15:16

Using block device as cnfs buffer under FreeBSD.

Hello,

FreeBSD 6.2, inn-2.4.3, compiled with large files support.

Can I use block device (drive) directly as cnfs buffer? As far as I see, no.

In errlog:

innd: SERVER cant initalize storage manager: one or more storage methods failed initialization

And that's it. How can I see more debug information to be sure that problem is in FreeBSD? It works with files,
but does not with block devices (ad3, ad3s1 were tried, chown news:news was also made on them). FreeBSD
supports mmap(), but I don't know about block devices.

Is there any disadvantage using one (or several) big file instead of direct drive device?

Thank you for answers.
Permalink | Reply | 5 comments |
headers
Russ Allbery | 6 Mar 2007 20:18
Picon
Favicon
Gravatar

Re: Using block device as cnfs buffer under FreeBSD.

newsmaster <newsmaster <at> alkar.net> writes:

> FreeBSD 6.2, inn-2.4.3, compiled with large files support.

> Can I use block device (drive) directly as cnfs buffer? As far as I see, no.

> In errlog:

> innd: SERVER cant initalize storage manager: one or more storage methods failed initialization

> And that's it. How can I see more debug information to be sure that
> problem is in FreeBSD?

news.notice will hopefully have more detailed messages, at least including
the errno information.  Usually the problem is that mmap isn't supported
on block devices (it's somewhat rare for this to be supported).

> Is there any disadvantage using one (or several) big file instead of
> direct drive device?

It may be slightly slower due to the inode overhead, but in practice it's
probably not noticable.

--

-- 
Russ Allbery (rra <at> stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Bill Davidsen | 7 Mar 2007 00:11

Re: Using block device as cnfs buffer under FreeBSD.

newsmaster <at> alkar.net wrote:
> Hello,
>
> FreeBSD 6.2, inn-2.4.3, compiled with large files support.
>
> Can I use block device (drive) directly as cnfs buffer? As far as I see, no.
>
> In errlog:
>
> innd: SERVER cant initalize storage manager: one or more storage methods failed initialization
>
> And that's it. How can I see more debug information to be sure that problem is in FreeBSD? It works with
files, but does not with block devices (ad3, ad3s1 were tried, chown news:news was also made on them).
FreeBSD supports mmap(), but I don't know about block devices.
>   
I am not enough expert in BSD (particularly all the flavors) to know if 
mmap(slice) works, but there should be other error messages. You might 
just turn of mmap in the config and use file i/o for everything, to see 
that works or you have other problems.

I would not guess if i/o using file calls on raw devices would be faster 
or slower than inode overhead.
> Is there any disadvantage using one (or several) big file instead of direct drive device?
>
> Thank you for answers.
>
>
>   

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
newsmaster | 7 Mar 2007 11:33

Re: Using block device as cnfs buffer under FreeBSD.

На Tue, 06 Mar 2007 11:18:58 -0800
Russ Allbery <rra <at> stanford.edu> записано:

> newsmaster <newsmaster <at> alkar.net> writes:
> 
> > FreeBSD 6.2, inn-2.4.3, compiled with large files support.
> 
> > Can I use block device (drive) directly as cnfs buffer? As far as I
> > see, no.
> 
> > In errlog:
> 
> > innd: SERVER cant initalize storage manager: one or more storage
> > methods failed initialization
> 
> > And that's it. How can I see more debug information to be sure that
> > problem is in FreeBSD?
> 
> news.notice will hopefully have more detailed messages, at least
> including the errno information.  Usually the problem is that mmap
> isn't supported on block devices (it's somewhat rare for this to be
> supported).

I'm sorry, there was a little problem with syslog configuration. Now I see:

innd: CNFS-sm: CNFSinitdisks: mmap for /dev/da3s1 offset 0 l
en 131072 failed: Invalid argument

What does it mean?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Russ Allbery | 7 Mar 2007 23:03
Picon
Favicon
Gravatar

Re: Using block device as cnfs buffer under FreeBSD.

newsmaster <newsmaster <at> alkar.net> writes:
> Russ Allbery <rra <at> stanford.edu> записано:

>> news.notice will hopefully have more detailed messages, at least
>> including the errno information.  Usually the problem is that mmap
>> isn't supported on block devices (it's somewhat rare for this to be
>> supported).

> I'm sorry, there was a little problem with syslog configuration. Now I see:

> innd: CNFS-sm: CNFSinitdisks: mmap for /dev/da3s1 offset 0 l
> en 131072 failed: Invalid argument

> What does it mean?

Almost certainly "sorry, mmap isn't supported on block devices."  That's
the message that you usually get if it isn't.

--

-- 
Russ Allbery (rra <at> stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
Permalink | Reply | 0 comments |
headers
Bjoern A. Zeeb | 8 Mar 2007 09:05

Re: Using block device as cnfs buffer under FreeBSD.

On Tue, 6 Mar 2007, newsmaster <at> alkar.net wrote:

> Hello,
>
> FreeBSD 6.2, inn-2.4.3, compiled with large files support.
>
[cnfs on slice vs. fs]
> Is there any disadvantage using one (or several) big file instead of direct drive device?

considering that you'll most likely not have more than n<8 cnfs
buffers - if you want to go with disks/arrays or slices (and even
if it is n<64) - if you are thinking of optimizing out the fs you
are certainly not going to run INN for your high performance really
big news servers but some self coded really damn fast software;-) /SCNR

Just go with the fs. It will save you lots of trouble and you will not
notice it on modern hardware, one would use for a big, fast news server.
INN and FreeBSD are doing a good job in such configurations...

The only optimization I might go with would be:
you may want to consider newfsing it with only few inodes because you
will not need millions of inodes for n cnfs buffers - if you are going
to use one partition for cnfs buffers only.

The first thing that's usually going to explode will be history
anyway...

--

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
(Continue reading)

Permalink | Reply | 0 comments |

Gmane