Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 11348 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

EM Console throws errors when updating CID's

longbow

Hi, as of July 1 at 11 am EM console has shown errors for my update manager.  I am using a samba share on a Linux server for my CID.  no changes were made to the smb.conf file and before July 1 everything worked perfectly.

EM Console 5.2.2

Recommended subscription with windows and mac os

errors from update manager details:

Computer name WS217
Computer description
Operating system Windows Server 2012
Service pack
Domain/workgroup ***-NET
IP address 192.168.1.217
Time of last binary update 7/8/2014 4:08:08 PM
Time of last protection data update 7/8/2014 4:08:08 PM

Software subscriptions status Software subscriptionMaintained in Last successful downloadError codeError description
Recommended \\WS217\SophosUpdate7/8/2014 4:53:39 PM

Outstanding alerts and errors

Update manager status Date/time Code Description
7/8/2014 4:55:12 PM 80040404 Threat detection data update failed.
7/8/2014 4:46:20 PM 80040401 Software update failed.

History

Update manager status Date/time Code Description
7/8/2014 4:55:12 PM 80040404 Threat detection data update failed.
7/8/2014 4:50:31 PM 80040404 Threat detection data update failed.
7/8/2014 4:46:20 PM 80040401 Software update failed.

Errors from the log file:

7/8/2014 4:54:56 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 4:53:04 PM Error Decoding of product release Sophos Anti-Virus for Mac OS X 10.4+ version RECOMMENDED was not done because the synchronization failed.
7/8/2014 4:53:02 PM Error Version information for product 'Sophos Anti-Virus for Mac OS X 10.4+' was not gathered by dispatcher 'DispatcherSupplements-2014-07-08T21-51-47-3', as the last synchronization of that product failed.
7/8/2014 4:53:02 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 4:50:31 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::last_write_time
7/8/2014 4:46:18 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 4:44:35 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 4:29:33 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 4:03:29 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 3:49:20 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 3:49:16 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 3:36:51 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 3:36:01 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 3:23:05 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 3:17:33 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 3:03:24 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 2:54:24 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 2:41:57 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 2:41:22 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 2:28:21 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 2:26:58 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 2:13:09 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 2:03:15 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 1:50:40 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 1:50:35 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 1:37:48 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 1:36:43 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 1:23:04 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
7/8/2014 1:14:54 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove
7/8/2014 1:02:14 PM Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::remove

any idea what could be wrong?

:51736


This thread was automatically locked due to age.
  • 0 
    ...unexpected error. Details: boost::filesystem::...

     'Boost' for SUM should generally point you to permissions and file access problems.  Locked files, files that are corrupt/have corrupt permissions.

    Good test:  ensure an update is currently not in progress.  Rename the folder containing the files that SUM is trying to overwrite (like adding .old) and create a new folder with the same name next to it.  Then force an update.

    :51756
  • 0

    I tried that, even tried a differnt server.  but I think I might have figured it out.  Let me do a little more testing and I'll get back with the results.

    :51774
  • 0

    After running a few test, I think the problem was with using IPv6 addressing and an older version of Samba.  

    I just started using IPv6 a few weeks ago, but I never would of thought it would cause problems.  Sure enough when I switched off IPv6 and used IPv4 it worked...

    Looked at the Samba change change logs and noticed this little gem:

    BUG 10464: samba4 services not binding on IPv6 addresses causing
      connection delays.

    Upgraded to the latest version of Samba and switched back to IPv6, and it worked.  

    Not real sure that bug in Samba was the problem, but upgrading Samba seemed to fix the issue.

    :51780
  • 0

    well that really didnt fix it after all.  so ive forced it to use IPv4 by using the ipaddress instead of a DNS name.  maybe its a bug in Sophos? Maybe a bug in Samba? who knows. 

    :51784
  • 0

    Hello longbow,

    a bug in Sophos? ... a bug in Samba?

    a bug in Windows? AFAIK boost uses the Windows API and most operations just pass the path (in the case UNC) to it. If accessing the share (or another share on the Linux server) over IPv6 works with Explorer then it's likely not the Samba server ...

    Christian

    :51814