Hello Heimir,

I believe this is solved (since we spoke on the phone about it), but I
wan't to complete the thread to help others (more below)...

Monday, July 17, 2006, 1:07:32 PM, you wrote:

> I just switched to persistent mode and now I get this in the log file.

>     20060717170332    -INITIALIZING-    0    0    ERROR_RULE_AUTH    
> 73    0    0    0    0
>     20060717170333    Db64d018900003dac.smd    2907    343    Match
> 1021480    60    842    906    64
>     20060717170333    Db64d018900003dac.smd    2907    343    Match
> 1046209    60    1142    1159    64
>     20060717170333    Db64d018900003dac.smd    2907    343    Final
> 1021480    60    0    8437    64
>     20060717170333    Db64b020700003d93.smd    3484    141    Clean
> 0    0    0    7977    83
>     20060717170333    Db64c021000003d99.smd    3391    359    Clean
> 0    0    0    16025    65
>     20060717170333    Db64a01ed00003d91.smd    3250    437    Match
> 1050898    53    632    685    65
>     20060717170333    Db64a01ed00003d91.smd    3250    437    Final
> 1050898    53    0    8263    65

> I removed the serial number.


> My understanding is that auth 73 indicates authorization issue but it 
> still runs?
> I am a little confused.

The default mode for SNF uses "cellular peer-server techology". When
more than once instance of SNF is active then one of the instances
will tend to act as a server for others that become active during a
short period. Under moderate loads this allows the system to be much
more efficient with resources since the rulebase is loaded much less
frequently. The instances of SNF self-organize to share resources.

Persistent mode essentially tricks one of the instances into staying
alive forever so that all of the other instances can act as clients.
There are a few other tricks added as well to make things much more
efficient.

HOWEVER - if the persistent instance fails to launch or goes down for
some reason then the remaining instances revert to peer-server mode as
a fail-safe. In the log above it seems that the new persistent
instance was not configured correctly and so it failed
(ERROR_RULE_AUTH). The other instances continued to process messages
normally (though I can see very slowly due to the load and the failed
persistent instance!).

Hope this helps,

_M

-- 
Pete McNeil
Chief Scientist,
Arm Research Labs, LLC.


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to