Mirror in ERA 2.0.107 not updating automatically

Discussion in 'Other ESET Home Products' started by duijv023, Jul 15, 2008.

Thread Status:
Not open for further replies.
  1. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    Hi,

    Last week I configured ERA on a smallbusiness server with NOD32(XMON) v2.50. on wednesday July 9
    The mirror-folder is accessed by file sharing instead of HTTP.


    Situation is this:
    - ERA is configured to use the right username and password
    - ERA is configured to activate the mirror and ditribute updates for dutch and english versions of NOD32v2 and EAV3
    - update is configured for each 60 mins
    - when i look in ERA, i see that the virusdatabase is at 3267 (20080714) (so the update process is going well in my opinion)
    - when i emptied (during configuration) the mirror folder, it was filled again after clicking the "update now" button
    - but now we are a few days later, and clients do not update, because "you are using the latest definitions"
    - version of update.ver is now 12-7-2008, 22.37

    Hopefully one recognizes thiso_O

    Greetings from holland
     
  2. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    :D Problem fixed (easier than I thought):

    Although the "Eset Remote Administration service" was running, after restarting this service, the mirror updated immediately.
    I think I may have triggered this myself, because after install the ERAS, and ERAC, i did not reboot this server yet.

    Yeah... Lesson one: "If an application does not ask for a reboot, please do reboot the machine if possible"
    ...shame...shame...shame :oops:

    Greetings from Holland
     
  3. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    hmmm... Mirror has stopped syncing again.
    ERAS sees (=has?) the right virusdefinitions, but the mirror folder does not contain that definition set.
    So I emptied the mirror folder again, I restarted the service and now it is OK again.
    The service properties are already (automatically) set to restart the service in case of failure.
    Now i added the option that the service is resarted each 3 days.
    Hopefully that's good enough.

    But I wonder why this is neccessary?

    Greetings from a very wet, dark gray and windy Holland.
     
    Last edited: Jul 22, 2008
  4. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    OK - I saw in the other products topic the answer: upgrade to 2.0.110.

    As I downloaded my version recently from www.eset.com, I assumed it was an up-to-date version.
    However, it was apparenly not :( .
    I have installed the update, so I will check it out the next days.

    Perhaps this thread can be moved to other products tooo_O??

    Greetings from a very warm Holland
     
  5. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    Re: Mirror in ERA 2.0.107 (now 2.0.110) not updating automatically

    After upgrading the ERAS and ERAC to 2.0.110, I must say, I'm not sure how it goes now.
    The clients were stuck on defs 3300, although it should have been 3301 now.
    I emptied the mirror folder manually, and hit the "update now" button but after a few minutes the mirror folder was still empty.
    After restarting the ERAS service, the mirror was updated with 3301 within one minute!..

    As I read about something with defs. 3300 (see here)
    I wonder which problem i had, the one I mentioned earlier (this thread) or the defs 3300 issue.

    Greetings from a warm, but rainy Holland
     
    Last edited: Jul 28, 2008
  6. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    The problem is there again :mad: . At this time all mirror updating clients are still @ 3303 or 3304 defs.
    Strange!!! why are some clients @ 3303 and others @ 3304. The clients are the same, dutch EAV 3.0.667.0 versions with the same configs?
    I really don't get this o_O .

    Can please somebody at least tell me if this my personal problem or is this an issue that Eset is aware of ?!?!
    I smell some kind of radio silence, and to be honest: I don't like hearing nothing...

    Greetings from Holland
     
  7. Bakker

    Bakker Registered Member

    Joined:
    May 28, 2008
    Posts:
    90
    Well there has been a problem with ESET's update servers for the past few days. Are your clients updating from the internet or from the RA server? (Meaning did you change the update profile so they get updates from the server? (via http or smb?) and not just report to it?)
     
  8. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    No, i configured some clients to update automatically (direct from update servers). Those are updated as it should.
    But the ones updated by mirror do not update anymore ...
     
  9. Bakker

    Bakker Registered Member

    Joined:
    May 28, 2008
    Posts:
    90
    What definition version does your RA server have? (Tools - Server Options, General Tab) And what version do the clients have that no longer update?
     
  10. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    now the mirror is (after cleaning and service restart) filled with 3315 :D
    I will monitor this the following days.

    greetings from a warm Holland
     
Thread Status:
Not open for further replies.