bob@omni.com (Bob Weissman) (10/12/90)
I have been getting *hundreds* of these messages every night from
expire. Can anyone tell me what they mean and how to get rid of them?
The lone colon in the message indicates the global char array
"filename" contains an empty string, making it difficult to track down
the source of these errors.
I did a "find" piped into "grep" looking for these strings and
am reasonably certain they don't actually occur inside any news
articles. Is this a date format anyone recognizes?
This is news version B 2.11.19 10/30/89 on a Sun 4/280 under SunOS
4.0.3, if that matters.
Oct 11 03:53 news expire: : Unparsable date "184482407"
Oct 11 03:53 news expire: : Unparsable date "184482408"
Oct 11 03:53 news expire: : Unparsable date "184482409"
Oct 11 03:53 news expire: : Unparsable date "184482411"
Oct 11 03:53 news expire: : Unparsable date "184482412"
Oct 11 03:53 news expire: : Unparsable date "184482414"
Oct 11 03:53 news expire: : Unparsable date "184482415"
Oct 11 03:53 news expire: : Unparsable date "184482416"
Oct 11 03:53 news expire: : Unparsable date "184482416"
Oct 11 03:53 news expire: : Unparsable date "184482417"
Oct 11 03:53 news expire: : Unparsable date "184482418"
Oct 11 03:53 news expire: : Unparsable date "184482418"
Oct 11 03:53 news expire: : Unparsable date "184482419"
Oct 11 03:53 news expire: : Unparsable date "184482420"
Oct 11 03:53 news expire: : Unparsable date "184482420"
Thanks,
--
Bob Weissman
Internet: bob@omni.com
UUCP: ...!{apple,decwrl,pyramid,sgi,uunet}!omni!bobhenry@zoo.toronto.edu (Henry Spencer) (10/12/90)
In article <4793@borabora.omni.com> bob@omni.com (Bob Weissman) writes: >I have been getting *hundreds* of these messages every night from >expire. Can anyone tell me what they mean and how to get rid of them? > ... > Oct 11 03:53 news expire: : Unparsable date "184482407" > Oct 11 03:53 news expire: : Unparsable date "184482408" Methinks you are running a current B inews/rnews with an old expire, or have made a configuration mistake that amounts to the same thing. A while ago, B News acquired the option of generating a C-News-style history file, with numeric dates, to permit use with C News expire. Sounds like you're using that with an expire that doesn't understand the new format. -- "...the i860 is a wonderful source | Henry Spencer at U of Toronto Zoology of thesis topics." --Preston Briggs | henry@zoo.toronto.edu utzoo!henry
ingoldsb@ctycal.UUCP (Terry Ingoldsby) (10/20/90)
In article <4793@borabora.omni.com>, bob@omni.com (Bob Weissman) writes: > I have been getting *hundreds* of these messages every night from > expire. Can anyone tell me what they mean and how to get rid of them? ... > Oct 11 03:53 news expire: : Unparsable date "184482407" We've been getting some peculiar messages about Unparsable dates at this site, too. I think I've seen the above format; I've also seen dates that look slightly more legit, but have 69 as the year. Also, are there any problems between B and C news. We (a B news site) get news from a C news site. The C news administrator gets oodles of messages on some days indicating we are sending them empty news batches. I have seen my station seem to send more data than I can account for (i.e. the Telebit shows major `send' for 10 minutes) when I'm sure no one has sent that much news out. Could we be returning Unparsable Date news packets? -- Terry Ingoldsby ctycal!ingoldsb@calgary.UUCP Land Information Services or The City of Calgary ...{alberta,ubc-cs,utai}!calgary!ctycal!ingoldsb
henry@zoo.toronto.edu (Henry Spencer) (10/25/90)
In article <502@ctycal.UUCP> ingoldsb@ctycal.UUCP (Terry Ingoldsby) writes: >> Oct 11 03:53 news expire: : Unparsable date "184482407" > >We've been getting some peculiar messages about Unparsable dates >at this site, too. I think I've seen the above format; I've also >seen dates that look slightly more legit, but have 69 as the year. As I think I mentioned before, the all-numeric date is from a C-News-format history file, which is now available (an option?) with B News. The 1969 dates are the result of someone's software ill-advisedly attempting to convert `-1' -- the error return from getdate() -- back into an ASCII date. Since Unix dates are relative to the start of 1970 GMT, converting -1 back to ASCII typically gives 31 Dec 1969 with a (local) time a few hours before midnight. >Also, are there any problems between B and C news. We (a B news >site) get news from a C news site. The C news administrator gets >oodles of messages on some days... There are lots of interoperating B and C sites without such problems, in fact it's the first I've heard of something like that happening. -- The type syntax for C is essentially | Henry Spencer at U of Toronto Zoology unparsable. --Rob Pike | henry@zoo.toronto.edu utzoo!henry