soreceive: not M_DATA, found 131

From: Gary L. Burnore (gburnore_at_databasix.com)
Date: 06/04/04 

Date: Fri, 04 Jun 2004 14:13:51 -0400

Just started getting these on console this morning. NOTHING changed on
this server for years. The closest thing I find in google is a
conversation JPR had with someone about CPU2. May have been NIC
related, but the guy didn't say what the result of his testing found.

Error from syslog:

Jun 4 13:53:41 dtbsx WARNING: soreceive: unexpected message type
x00000083
Jun 4 13:53:42 dtbsx WARNING: soreceive: not M_DATA, found 131

Is this likely a dying NIC too?

Everything else works fine in and outbound.

Relevant Pages

  • Re: soreceive: not M_DATA, found 131
    ... >| this server for years. ... The closest thing I find in google is a ... >| conversation JPR had with someone about CPU2. ...
    (comp.unix.sco.misc)
  • Re: soreceive: not M_DATA, found 131
    ... | Just started getting these on console this morning. ... | this server for years. ... The closest thing I find in google is a ...
    (comp.unix.sco.misc)
  • Re: Internal exchange vs hosted exchange
    ... Google Mail vs. Exchange Server ... break down the costs on the website. ...
    (microsoft.public.windows.server.sbs)
  • Re: Giving an application a window icon in a sensible way
    ... it should be fairly obvious that a google search with the query "ant" ... A three letter query with a different, ... server etc ... In fact, the choice is to argue here, or to use ...
    (comp.lang.java.programmer)
  • Re: Best search engine for EEs?
    ... You can set your browser to discard them -- at will. ... when they slam me with ads like what happens here with Google, ... Note that even your DNS queries provide important information! ... You can intentionally opt to use their DNS server. ...
    (sci.electronics.design)