nod32smfi issues

Discussion in 'NOD32 version 2 Forum' started by Zhen-Xjell, Jul 7, 2004.

Thread Status:
Not open for further replies.
  1. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    I started using this and noticed that if the socket is not available the following errors occur:

    Jul 7 14:40:17 bugsbunny sm-mta[21989]: i67IeHiC021989: Milter (nod32smfi): to error state
    Jul 7 14:40:17 bugsbunny sm-mta[21989]: i67IeHiC021989: Milter: initialization failed, temp failing commands


    It also appears that any emails trying to go thru sendmail are lost and not queued anywhere (checked via sendmail -bp).

    What's the story on this?

    There doesn't appear to be a command to check the version info, unless I missed it somewhere.

    Strings is unable to give me that data either.

    How can I ensure that the socket won't fail again? Losing email like this is not very good.
     
  2. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Also found this in the messages file:

    Jul 7 14:58:50 bugsbunny nod32smfi: nod32smfi, mi_rd_cmd: read returned -1: Connection reset by peer
    Jul 7 14:58:50 bugsbunny nod32smfi: nod32smfi: private data not NULL


    ??
     
  3. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    I cannot believe this bug... at midnight here are the beginning errors:

    Jul 8 00:44:09 bugsbunny sm-mta[19750]: i684i9am019750: Milter (nod32smfi): to error state
    Jul 8 00:44:09 bugsbunny sm-mta[19750]: i684i9am019750: Milter (nod32smfi): init failed to open
    Jul 8 00:44:09 bugsbunny sm-mta[19750]: i684i9am019750: Milter (nod32smfi): to error state
    Jul 8 00:44:12 bugsbunny sm-mta[19752]: i684iChT019752: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:44:12 bugsbunny sm-mta[19752]: i684iChT019752: Milter (nod32smfi): to error state
    Jul 8 00:44:12 bugsbunny sm-mta[19752]: i684iChT019752: Milter (nod32smfi): init failed to open
    Jul 8 00:44:12 bugsbunny sm-mta[19752]: i684iChT019752: Milter (nod32smfi): to error state
    Jul 8 00:52:23 bugsbunny sm-mta[20062]: i684qNCS020062: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:52:23 bugsbunny sm-mta[20062]: i684qNCS020062: Milter (nod32smfi): to error state
    Jul 8 00:52:23 bugsbunny sm-mta[20062]: i684qNCS020062: Milter (nod32smfi): init failed to open
    Jul 8 00:52:23 bugsbunny sm-mta[20062]: i684qNCS020062: Milter (nod32smfi): to error state
    Jul 8 00:52:36 bugsbunny sm-mta[20065]: i684qaQu020065: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:52:36 bugsbunny sm-mta[20065]: i684qaQu020065: Milter (nod32smfi): to error state
    Jul 8 00:52:36 bugsbunny sm-mta[20065]: i684qaQu020065: Milter (nod32smfi): init failed to open
    Jul 8 00:52:36 bugsbunny sm-mta[20065]: i684qaQu020065: Milter (nod32smfi): to error state
    Jul 8 00:52:44 bugsbunny sm-mta[20067]: i684qipv020067: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:52:44 bugsbunny sm-mta[20067]: i684qipv020067: Milter (nod32smfi): to error state
    Jul 8 00:52:44 bugsbunny sm-mta[20067]: i684qipv020067: Milter (nod32smfi): init failed to open
    Jul 8 00:52:44 bugsbunny sm-mta[20067]: i684qipv020067: Milter (nod32smfi): to error state
    Jul 8 00:52:54 bugsbunny sm-mta[20068]: i684qsY2020068: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:52:54 bugsbunny sm-mta[20068]: i684qsY2020068: Milter (nod32smfi): to error state
    Jul 8 00:52:54 bugsbunny sm-mta[20068]: i684qsY2020068: Milter (nod32smfi): init failed to open
    Jul 8 00:52:54 bugsbunny sm-mta[20068]: i684qsY2020068: Milter (nod32smfi): to error state
    Jul 8 00:53:21 bugsbunny sm-mta[20085]: i684rLIK020085: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:53:21 bugsbunny sm-mta[20085]: i684rLIK020085: Milter (nod32smfi): to error state
    Jul 8 00:53:21 bugsbunny sm-mta[20085]: i684rLIK020085: Milter (nod32smfi): init failed to open
    Jul 8 00:53:21 bugsbunny sm-mta[20085]: i684rLIK020085: Milter (nod32smfi): to error state
    Jul 8 00:53:25 bugsbunny sm-mta[20084]: i684rOB5020084: Milter (nod32smfi): timeout before data read
    Jul 8 00:53:25 bugsbunny sm-mta[20084]: i684rOB5020084: Milter (nod32smfi): to error state
    Jul 8 00:53:25 bugsbunny sm-mta[20084]: i684rOB5020084: Milter (nod32smfi): init failed to open
    Jul 8 00:53:25 bugsbunny sm-mta[20084]: i684rOB5020084: Milter (nod32smfi): to error state
    Jul 8 00:53:59 bugsbunny sm-mta[20114]: i684rxeQ020114: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:53:59 bugsbunny sm-mta[20114]: i684rxeQ020114: Milter (nod32smfi): to error state
    Jul 8 00:53:59 bugsbunny sm-mta[20114]: i684rxeQ020114: Milter (nod32smfi): init failed to open
    Jul 8 00:53:59 bugsbunny sm-mta[20114]: i684rxeQ020114: Milter (nod32smfi): to error state
    Jul 8 00:54:12 bugsbunny sm-mta[20127]: i684sCHi020127: Milter (nod32smfi): read returned -1: Connection reset by [209.213.221.9]
    Jul 8 00:54:12 bugsbunny sm-mta[20127]: i684sCHi020127: Milter (nod32smfi): to error state
    Jul 8 00:54:12 bugsbunny sm-mta[20127]: i684sCHi020127: Milter (nod32smfi): init failed to open
    Jul 8 00:54:12 bugsbunny sm-mta[20127]: i684sCHi020127: Milter (nod32smfi): to error state
    Jul 8 00:54:59 bugsbunny sm-mta[20222]: i684sxFr020222: Milter (nod32smfi): read returned -1: Connection reset by akelos.net
    Jul 8 00:54:59 bugsbunny sm-mta[20222]: i684sxFr020222: Milter (nod32smfi): to error state
    Jul 8 00:54:59 bugsbunny sm-mta[20222]: i684sxFr020222: Milter (nod32smfi): init failed to open
    Jul 8 00:54:59 bugsbunny sm-mta[20222]: i684sxFr020222: Milter (nod32smfi): to error state
    Jul 8 00:55:03 bugsbunny sm-mta[20224]: i684t3ZC020224: Milter (nod32smfi): write(O) returned -1, expected 17: Broken pipe
    Jul 8 00:55:03 bugsbunny sm-mta[20224]: i684t3ZC020224: Milter (nod32smfi): to error state
    Jul 8 00:55:03 bugsbunny sm-mta[20224]: i684t3ZC020224: Milter (nod32smfi): init failed to open

    And this going on to:

    Jul 8 01:36:17 bugsbunny sm-mta[21902]: i685aGAO021902: Milter (nod32smfi): timeout before data read
    Jul 8 01:36:17 bugsbunny sm-mta[21902]: i685aGAO021902: Milter (nod32smfi): to error state
    Jul 8 01:36:17 bugsbunny sm-mta[21902]: i685aGAO021902: Milter (nod32smfi): init failed to open
    Jul 8 01:36:17 bugsbunny sm-mta[21902]: i685aGAO021902: Milter (nod32smfi): to error state
    Jul 8 01:36:49 bugsbunny sm-mta[21904]: i685an8V021904: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:36:49 bugsbunny sm-mta[21904]: i685an8V021904: Milter (nod32smfi): to error state
    Jul 8 01:37:18 bugsbunny sm-mta[21746]: i685WFbo021746: Milter (nod32smfi): write(Q) returned -1, expected 5: Broken pipe
    Jul 8 01:37:18 bugsbunny sm-mta[21746]: i685WFbo021746: Milter (nod32smfi): to error state
    Jul 8 01:37:23 bugsbunny sm-mta[21918]: i685bNKc021918: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:37:23 bugsbunny sm-mta[21918]: i685bNKc021918: Milter (nod32smfi): to error state
    Jul 8 01:37:52 bugsbunny sm-mta[21935]: i685bqFl021935: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:37:52 bugsbunny sm-mta[21935]: i685bqFl021935: Milter (nod32smfi): to error state
    Jul 8 01:38:02 bugsbunny sm-mta[21936]: i685c2IZ021936: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:02 bugsbunny sm-mta[21936]: i685c2IZ021936: Milter (nod32smfi): to error state
    Jul 8 01:38:11 bugsbunny sm-mta[21945]: i685cBYr021945: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:11 bugsbunny sm-mta[21945]: i685cBYr021945: Milter (nod32smfi): to error state
    Jul 8 01:38:12 bugsbunny sm-mta[21955]: i685cC52021955: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:12 bugsbunny sm-mta[21955]: i685cC52021955: Milter (nod32smfi): to error state
    Jul 8 01:38:14 bugsbunny sm-mta[21934]: i685cEMV021934: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:14 bugsbunny sm-mta[21934]: i685cEMV021934: Milter (nod32smfi): to error state
    Jul 8 01:38:15 bugsbunny sm-mta[21938]: i685cFkn021938: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:15 bugsbunny sm-mta[21938]: i685cFkn021938: Milter (nod32smfi): to error state
    Jul 8 01:38:32 bugsbunny sm-mta[21972]: i685cWmk021972: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:32 bugsbunny sm-mta[21972]: i685cWmk021972: Milter (nod32smfi): to error state
    Jul 8 01:38:47 bugsbunny sm-mta[21973]: i685clCh021973: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:38:47 bugsbunny sm-mta[21973]: i685clCh021973: Milter (nod32smfi): to error state
    Jul 8 01:39:07 bugsbunny sm-mta[22006]: i685d7x1022006: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:39:07 bugsbunny sm-mta[22006]: i685d7x1022006: Milter (nod32smfi): to error state
    Jul 8 01:39:29 bugsbunny sm-mta[22022]: i685dTFY022022: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:39:29 bugsbunny sm-mta[22022]: i685dTFY022022: Milter (nod32smfi): to error state
    Jul 8 01:39:30 bugsbunny sm-mta[22023]: i685dU9m022023: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:39:30 bugsbunny sm-mta[22023]: i685dU9m022023: Milter (nod32smfi): to error state
    Jul 8 01:39:31 bugsbunny sm-mta[22024]: i685dViP022024: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:39:31 bugsbunny sm-mta[22024]: i685dViP022024: Milter (nod32smfi): to error state
    Jul 8 01:39:46 bugsbunny sm-mta[22025]: i685dkgD022025: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:39:46 bugsbunny sm-mta[22025]: i685dkgD022025: Milter (nod32smfi): to error state
    Jul 8 01:39:58 bugsbunny sm-mta[22030]: i685dwgY022030: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:39:58 bugsbunny sm-mta[22030]: i685dwgY022030: Milter (nod32smfi): to error state
    Jul 8 01:40:07 bugsbunny sm-mta[22045]: i685e7le022045: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:40:07 bugsbunny sm-mta[22045]: i685e7le022045: Milter (nod32smfi): to error state
    Jul 8 01:40:11 bugsbunny sm-mta[22046]: i685eBMK022046: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:40:11 bugsbunny sm-mta[22046]: i685eBMK022046: Milter (nod32smfi): to error state
    Jul 8 01:40:48 bugsbunny sm-mta[22070]: i685em4u022070: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:40:48 bugsbunny sm-mta[22070]: i685em4u022070: Milter (nod32smfi): to error state
    Jul 8 01:41:07 bugsbunny sm-mta[22071]: i685f7E5022071: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:41:07 bugsbunny sm-mta[22071]: i685f7E5022071: Milter (nod32smfi): to error state
    Jul 8 01:41:17 bugsbunny sm-mta[22072]: i685fH0A022072: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:41:17 bugsbunny sm-mta[22072]: i685fH0A022072: Milter (nod32smfi): to error state
    Jul 8 01:42:06 bugsbunny sm-mta[22105]: i685g6Su022105: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:42:06 bugsbunny sm-mta[22105]: i685g6Su022105: Milter (nod32smfi): to error state
    Jul 8 01:42:12 bugsbunny sm-mta[22106]: i685gC5X022106: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 01:42:12 bugsbunny sm-mta[22106]: i685gC5X022106: Milter (nod32smfi): to error state
    Jul 8 01:42:35 bugsbunny sm-mta[22107]: i685gZ38022107: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe


    All the way thru to:


    Jul 8 10:55:07 bugsbunny sm-mta[12780]: i68Et75t012780: Milter (nod32smfi): to error state
    Jul 8 10:55:10 bugsbunny sm-mta[12781]: i68EtAVf012781: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:10 bugsbunny sm-mta[12781]: i68EtAVf012781: Milter (nod32smfi): to error state
    Jul 8 10:55:23 bugsbunny sm-mta[12782]: i68EtNTa012782: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:23 bugsbunny sm-mta[12782]: i68EtNTa012782: Milter (nod32smfi): to error state
    Jul 8 10:55:27 bugsbunny sm-mta[12783]: i68EtR0M012783: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:27 bugsbunny sm-mta[12783]: i68EtR0M012783: Milter (nod32smfi): to error state
    Jul 8 10:55:35 bugsbunny sm-mta[12784]: i68EtZ8v012784: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:35 bugsbunny sm-mta[12784]: i68EtZ8v012784: Milter (nod32smfi): to error state
    Jul 8 10:55:36 bugsbunny sm-mta[12785]: i68EtaTA012785: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:36 bugsbunny sm-mta[12785]: i68EtaTA012785: Milter (nod32smfi): to error state
    Jul 8 10:55:44 bugsbunny sm-mta[12790]: i68EtiZk012790: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:44 bugsbunny sm-mta[12790]: i68EtiZk012790: Milter (nod32smfi): to error state
    Jul 8 10:55:49 bugsbunny sm-mta[12792]: i68Etn07012792: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:49 bugsbunny sm-mta[12792]: i68Etn07012792: Milter (nod32smfi): to error state
    Jul 8 10:55:52 bugsbunny sm-mta[12791]: i68EtqgQ012791: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:55:52 bugsbunny sm-mta[12791]: i68EtqgQ012791: Milter (nod32smfi): to error state
    Jul 8 10:56:07 bugsbunny sm-mta[12827]: i68Eu7WK012827: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:56:07 bugsbunny sm-mta[12827]: i68Eu7WK012827: Milter (nod32smfi): to error state
    Jul 8 10:56:21 bugsbunny sm-mta[12829]: i68EuLXO012829: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:56:21 bugsbunny sm-mta[12829]: i68EuLXO012829: Milter (nod32smfi): to error state
    Jul 8 10:56:22 bugsbunny sm-mta[12830]: i68EuMWG012830: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:56:22 bugsbunny sm-mta[12830]: i68EuMWG012830: Milter (nod32smfi): to error state
    Jul 8 10:56:27 bugsbunny sm-mta[12831]: i68EuRbp012831: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:56:27 bugsbunny sm-mta[12831]: i68EuRbp012831: Milter (nod32smfi): to error state
    Jul 8 10:56:30 bugsbunny sm-mta[12845]: i68EuUuP012845: Milter (nod32smfi): local socket name /var/run/nod32smfi.sock unsafe
    Jul 8 10:56:30 bugsbunny sm-mta[12845]: i68EuUuP012845: Milter (nod32smfi): to error state


    Running this:

    grep "local socket name /var/run/nod32smfi.sock unsafe"| wc -l

    Gives me a total of 3057 lines.

    I can't run the website like this. I need help here. I opened tickets yesterday at nod32.com but as yet haven't received a reply.
     
  4. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    And oh, the nod32smfi socket was not there, even though the pid was. Why does it keep dying like this?
     
  5. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    64,314
    Location:
    Texas

    Zhen-Xjell

    Have you tried calling them here in the U.S.?
     
  6. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    No I haven't, there are no technical support numbers listed at their site (none I could find).
     
  7. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    64,314
    Location:
    Texas

    Maybe if you call one of these numbers, you can get something started. Sounds like you are in a bind.

    Eset
     
  8. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Thanks, I'll give it a try after lunch.
     
  9. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    And while the socket exists, these are the errors that get logged:

    Jul 8 11:07:30 bugsbunny sm-mta[13563]: i68F7TwX013563: Milter read(nod32smfi): timeout before data read
    Jul 8 11:07:30 bugsbunny sm-mta[13563]: i68F7TwX013563: Milter (nod32smfi): to error state
    Jul 8 11:14:27 bugsbunny sm-mta[13972]: i68FEQM0013972: Milter read(nod32smfi): timeout before data read
    Jul 8 11:14:27 bugsbunny sm-mta[13972]: i68FEQM0013972: Milter (nod32smfi): to error state
    Jul 8 11:14:27 bugsbunny sm-mta[13972]: i68FEQM0013972: Milter (nod32smfi): init failed to open
    Jul 8 11:14:27 bugsbunny sm-mta[13972]: i68FEQM0013972: Milter (nod32smfi): to error state
    Jul 8 11:25:24 bugsbunny sm-mta[14672]: i68FPNmX014672: Milter read(nod32smfi): timeout before data read
    Jul 8 11:25:24 bugsbunny sm-mta[14672]: i68FPNmX014672: Milter (nod32smfi): to error state
     
  10. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    From syslog messages:


    Jul 8 00:26:48 bugsbunny nod32smfi: nod32smfi: private data not NULL
    Jul 8 00:28:03 bugsbunny nod32smfi: nod32smfi: private data not NULL
    Jul 8 00:42:11 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 00:42:12 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 00:42:55 bugsbunny nod32smfi: nod32smfi: private data not NULL
    Jul 8 00:44:09 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 01:07:00 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 01:11:11 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 01:26:12 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 01:33:29 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 01:36:00 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), try again
    Jul 8 01:36:15 bugsbunny nod32smfi: nod32smfi: accept() returned invalid socket (Too many open files), abort
    Jul 8 10:56:30 bugsbunny nod32smfi: nod32smfi shutdown failed
    Jul 8 10:56:31 bugsbunny nod32smfi: nod32smfi startup succeeded
    Jul 8 10:58:21 bugsbunny nod32smfi: nod32smfi: private data not NULL
    Jul 8 11:07:30 bugsbunny nod32smfi: nod32smfi, mi_rd_cmd: read returned -1: Connection reset by peer
    Jul 8 11:07:30 bugsbunny nod32smfi: nod32smfi: private data not NULL
    Jul 8 11:14:27 bugsbunny nod32smfi: nod32smfi, mi_rd_cmd: read returned -1: Connection reset by peer
    Jul 8 11:14:47 bugsbunny nod32smfi: nod32smfi: private data not NULL
    Jul 8 11:15:23 bugsbunny nod32smfi: nod32smfi: private data not NULL



    And nod32d.log.. notice, no processing from midnight to 10 hours later:

    2004-07-08 00:38:09 -0500 1089262063: agent=smfi, msgid=<200407080438.i684c9xk019527@bugsbunny.laudanski.com>, object="email message", name="mail", virus="is OK", action="", info="", lines=0
    2004-07-08 10:58:21 -0500 1089299276: agent=smfi, msgid=<200407081458.i68EwLif012921@bugsbunny.laudanski.com>, object="email message", name="mail", virus="is OK", action="", info="", lines=0
     
  11. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    I did call before lunch, and was told I'd be called back. Nothing to date.
     
  12. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Oh whoa is me.
     
  13. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Can you send a email to support@nod32.com they will have you fixed up quick smart, or will at least get a start on the problem...

    Cheers :D
     
  14. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    A NOD32 tech replied to me here on Friday, I replied back and have heard nothing since. I opened NOD32 tickets last week, and have heard nothing since. I have dropped Yvette multiple emails at NOD32 and no one from tech has gotten back to me. This is painful.
     
  15. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Just for kicks, email to support@nod32.com:

     
  16. jan

    jan Former Eset Moderator

    Joined:
    Oct 25, 2002
    Posts:
    804
    Paul,

    here is the reply:

    Sorry, our Linux developer is overloaded, but he has an idea, where the problem could be - I'll give you an update tomorrow.

    Rgds.,

    jan
     
  17. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Ok, have you also seen my other thread with the .nup errors?
     
  18. jan

    jan Former Eset Moderator

    Joined:
    Oct 25, 2002
    Posts:
    804
    >Ok, have you also seen my other thread with the .nup errors?

    I sent you an e-mail with some sugggestions.

    Rgds.,

    jan
     
  19. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Shoot..

    upgraded from 2.11.x to 2.13.1 after Mark told me this problem should now be resolved. And it isn't.

    A list of failures:

    http://blog.castlecops.com/a/2005/02/nod32smfi_failu.html

    nod32smfi ran for about 4 or 5 hours before it crashed.

    :(

    I sent a reply back to Mark at Eset. Please lets get this resolved.
     
  20. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,411
    Hello,

    please check your sendmail config. file /etc/mail/sendmail.cf and make sure long enough timeouts are set for nod32smfi:
    Xnod32smfi, S=local:/var/run/nod32smfi.sock, F=T, T=S:2m;R:2m;E:5m
     
  21. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
  22. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,411
    It depends on how large files are scanned and what HW configuration you have.
     
  23. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Hi Marcos, can you guide me in that configuration process? The mail server is a dual Xeon CPU with 4 GB RAM. Files can be any size which are sent.

    EDIT:

    How they are scanned:

    I have the most paranoid settings in the cfg file.
     
  24. Zhen-Xjell

    Zhen-Xjell Security Expert

    Joined:
    Feb 8, 2002
    Posts:
    1,397
    Location:
    Ohio
    Just a friendly neighborhood bump.
     
  25. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,411
    Hi,
    if you don't know where to add a reference to nod32smfi in the senmail config. file, please send it to me so that I can have a look at it and let you know then.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.