Mailing List CGatePro@mail.stalker.com Message #92479
From: Daniel Rechsteiner <drechsteiner@goeast.ch>
Subject: Re: Cloudmark FreeBSD 4.x
Date: Thu, 06 Sep 2007 15:54:09 +0200
To: CGatePro@mail.stalker.com <CGatePro@mail.stalker.com>
X-Mailer: CommuniGate Pro MAPI Connector 1.2.5/1.2.12
I had the same problem with those error messages a few days ago. Despite them Cloudmark works normally.

About the long initialization time: You can set the following in cartridge.cfg:

download micro-updates before init = no

That way Cloudmark initializes immediately, but uses the old data until the new 30MB file is downloaded. So the filter quality might be lower for a few minutes.

Cheers
Daniel

 

> -----Ursprüngliche Nachricht-----
> Von: Technical Support, Stalker Labs [mailto:support@stalker.com]
> Gesendet: Mittwoch, 5. September 2007 14:20
> Betreff: Re: Cloudmark FreeBSD 4.x
>
> Hello,
>   Jeff Wark on 04.09.2007 21:40 wrote:
>
> > Greetings.
> >
> > I was just trying to upgrade to Cloudmark v1.5 from v1.3 on
> a FreeBSD
> > 4.x system.
> >
> > The error I am getting right now is:
> >
> > * CGPCloudmark plugin version 1.5 FreeBSD-Intel build
> 22-Nov-2006 started
> > * Initializing the Engine, please wait...
> > * 2:CORE: Could not insert key into cfg src: micro-update invalid
> > session interval
> > * 2:CORE: Could not insert key into cfg src: micro-update
> degraded mode
> > duration
> > * 1:CORE: Encountered 2 parameter insertion errors while
> parsing ACF file
> > * 2:CORE: Could not insert key into cfg src: micro-update invalid
> > session interval
> > * 2:CORE: Could not insert key into cfg src: micro-update
> degraded mode
> > duration
> > * 1:CORE: Encountered 2 parameter insertion errors while
> parsing ACF file
> > * 2:CORE: Could not insert key into cfg src: micro-update invalid
> > session interval
> > * 2:CORE: Could not insert key into cfg src: micro-update
> degraded mode
> > duration
> > * 1:CORE: Encountered 2 parameter insertion errors while
> parsing ACF file
>
> I got a report about these errors from one user, but these
> errors do not
> affect Cloudmark's functionality, i.e. it works after it's
> initialized.
>
>
> > Admittedly, this is not in the actual directory of
> /var/CommuniGate.  I
> > tried that first, along with copying the libcmae.so to /usr/lib but
> > received the same error.  Since this is a production
> server, I wanted to
> > get back to the functioning 1.3 version as soon as possible.
> >
> > After running for a couple minutes, the micro_updates
> directory looks
> > like this:
> > -rw-r--r--  1 root  mail       153 Sep  4 12:36 1.ipl
> > -rw-r--r--  1 root  mail       195 Sep  4 12:36 1.mfl
> > -rw-r--r--  1 root  mail        67 Sep  4 12:29 10.awl
> > -rw-r--r--  1 root  mail  25347853 Sep  4 12:31 1139019.hs2.z.aes
> > -rw-r--r--  1 root  mail         0 Sep  4 12:38 1139121-zdata.txt
> > -rw-r--r--  1 root  mail      1887 Sep  4 12:29 15.acf
> > -rw-r--r--  1 root  mail      4379 Sep  4 12:36 168.rplv1
> > -rw-r--r--  1 root  mail     52411 Sep  4 12:36 181.cats
> > -rw-r--r--  1 root  mail      7619 Sep  4 12:36 26.dpl
> > -rw-r--r--  1 root  mail       131 Sep  4 12:36 4.mpl
> > with the 1139121-zdata.txt file incrementing every second or so.
> >
> >
> > The CommuniGate logs look like this when I switch to the
> 1.5 version:
> >
> > *snip*
> > 13:12:07.44 4 EXTFILTER(Cloudmark) inp(73): * CGPCloudmark plugin
> > version 1.5 FreeBSD-Intel build 22-Nov-2006 started
> > 13:12:07.44 4 EXTFILTER(Cloudmark) inp(41): * Initializing
> the Engine,
> > please wait...
> > 13:12:08.03 4 EXTFILTER(Cloudmark) out(12): 7742 INTF 3\n
> > 13:12:08.03 4 EXTFILTER(Cloudmark) inp(82): * 2:CORE: Could
> not insert
> > key into cfg src: micro-update invalid session interval
>
> [...]
>
> > 13:12:11.06 3 EXTFILTER(Cloudmark) processing delayed: REJECTED The
> > engine is not initialized yet, please wait...
> > 13:12:12.09 4 EXTFILTER(Cloudmark) out(29): 7749 FILE
> Queue/59788001.msg\n
>
> You just have waited for 5 seconds, this is obviously not enough to
> download a 30+ megabyte update and initialize.
>
> Try deleting everything from micro_updates and waiting for it to
> complete the initializatin process. The
> micro_updates/*.hs2.z.aes should
> reach more than 30 megs in size.
>
>
>
> > I don't remember the 1.3 giving any trouble like that
> during testing.  
> > Any ideas?
> >
> > Jeff Wark
> > TBayTel Internet
> >
> > #############################################################
> > This message is sent to you because you are subscribed to
> >  the mailing list <CGatePro@mail.stalker.com>.
> > To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
> > To switch to the DIGEST mode, E-mail to
> <CGatePro-digest@mail.stalker.com>
> > To switch to the INDEX mode, E-mail to
> <CGatePro-index@mail.stalker.com>
> > Send administrative queries to  <CGatePro-request@mail.stalker.com>
>
>
> --
> Sincerely,
> Roman
>
> ==============================================================
> =========
> When answering to letters sent to you by the tech.support staff, make
> sure the original message you have received is included into
> your reply.
>



Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster