The category exists and is receiving valid messages from an older
version of the python scribe client. Here's the relevant code
snippet:
http://pastebin.com/BWNxPh6H
...i just added that TypeError except clause as a stop-gap to get
newer scribe clients working, but looks like that won't do it.
>>TNonblockingServer client died: No more data to read.
>
> Not sure about this one. Will probably go away when scribe has the right
> configuration
>
> Gautam
>
>
On 1/12/11 4:09 PM, "birdsong" <david.b...@gmail.com> wrote:
>I'm using the exact same code as the scribe_cat example, but the
>server is not writing my messages to the output file and the error
>logs from scribed show:
>
>[Thu Jan 13 00:08:17 2011] "log entry has invalid category <>"
This usually indicates the category you are trying to send is not
mentioned in the scribe config.
You can add a store for your category, add
your category to the "categories=" list of an existing store or specify a
default store
(category=default) which will accept all unrecognized categories. Have a
look
https://github.com/facebook/scribe/blob/master/examples/example2central.con
f for examples.
In the above case though, looks like you are sending an empty category?
Normally the log message should be "log entry has invalid category
<category name>"
>TNonblockingServer client died: No more data to read.
Gautam
Yeah, I can trigger that error with the older clients by supplying an
unconfigured category (with no default). The newer clients always
show an empty category ...which I'm sure is telling. I have a tcpdump
of the new clients and I see my category, but no idea of where the
category should be positioned in the raw tcp stream.
I'll try building a new server and send messages to it with this client.