Very shortly after startup, I received:
BerkeleyDB-ERROR: in start rebuildAddCorrections - syntax error at (eval
679) line 5, near "$main::$BDBerrLog "
Global symbol "$BDBerrLog" requires explicit package name (did you forget
to declare "my $BDBerrLog"?) at (eval 679) line 5.
- BDB:
On Fri, Oct 15, 2021 at 12:51 PM K Post <nntp.p...@gmail.com> wrote:
> Again, thanks.
> So are you recommending that $BDBerrLog stay at the default of 0 under
> normal circumstances, and only be changed to 1 if there appears to be
> something awry with one or more BDB actions?
>
> I've never seen anything written to any of the BDBError.txt files, but I
> certainly could have missed errors there - it's just not something I've
> monitored. I made the mistake of assuming, yes, assuming that errors would
> also go to maillog.txt - but as you pointed out, it's the BDB driver that
> would erroring, not ASSP. Is there a way / does it make sense / have you
> considered having ASSP use some magic to trap any BDB error or warning that
> may occur?
>
> On Fri, Oct 15, 2021 at 5:35 AM Thomas Eckardt <thomas.ecka...@thockar.com>
> wrote:
>
>> >If msvcrt is being used, would 512 open files ever not be enough?
>>
>> No, not in every case. This depends on the configuration and the workload.
>>
>> > $winSetMaxIO_DLL and $winSetMaxIO ....I can understand how to set them
>> for my set up.
>>
>> don't change them
>>
>> >Do you know if the Strawberry Perl installations....-DUSE_PERLIO?
>>
>> yes it is ...
>>
>> > I tried looking it up, but I'm coming up empty
>> ...... # Notice: PERLIO (perl compiled with -DUSE_PERLIO - *check with
>> :>perl -V*)
>>
>> :>perl -V
>> or
>> read perl/lib/Config_heavy.pl
>>
>>
>> >With BDBErrLog set to 0, I assume that any error with BDB files would
>> still be spit out to the maillog.txt file so we can be alerted that
>> something's wrong?
>>
>> assume ?????? . Read the perl POD for BekeleyDB.pm and the oracle
>> documentation for BerkeleyDB.
>> Who would need BDB-ENV -errfile if such errors could be catched elsewhere
>> easely?
>>
>> After (e.g.) a HASH %bar is tied to : memory, file, orderedtie,
>> BerkeleyDB, ODBC, ADO or any native RDBM
>> (oracle,db2,mysql,mariadb,mssql,postgre .....) - a simple call like
>>
>> $bar{$foo}
>>
>> accesses totaly different code (the driver). It is impossible to catch
>> all possible errors for all cases for all tied mechanism, after such a
>> call, to write them to maillog.txt. ASSP tries to do its best to catch as
>> much of the errors as possible and to recover from error conditions
>> automatically.
>> But errors may occure at software layers, which can't be accessed by assp.
>> ASSP catches all errors at init-time of BerkeleyDB (and recovers if
>> possible). If there occure errors at runtime for BerkeleyDB, someone can
>> enable 'BDBErrLog' to get the runtime errors recorded.
>>
>> Thomas
>>
>>
>>
>> Von: "K Post" <nntp.p...@gmail.com>
>> An: "ASSP development mailing list" <
>> assp-test@lists.sourceforge.net>
>> Datum: 14.10.2021 20:25
>> Betreff: Re: [Assp-test] fixes in assp 2.6.6 *SPAM-Evaporator*
>> build 21287
>> ------------------------------
>>
>>
>>
>> Whew you've been busy! Thank you.
>>
>> - If msvcrt is being used, would 512 open files ever not be enough?
>> I feel like I was getting the file issues when many links to BDB-error.txt
>> files were getting stuck open, so exceeding 512, but that was ultimately
>> because of my stupid griplist directory misconfiguration combined with bad
>> TLS early talkers. I guess I'm trying to understand why
>> $winSetMaxIO_DLL and $winSetMaxIO hidden params were necessary, so I can
>> understand how to set them for my set up.
>> - Do you know if the Strawberry Perl installations at
>> *https://strawberryperl.com/releases.html*
>> <https://strawberryperl.com/releases.html> compiled with DUSE_PERLIO?
>> I tried looking it up, but I'm coming up empty
>>
>> With BDBErrLog set to 0, I assume that any error with BDB files would
>> still be spit out to the maillog.txt file so we can be alerted that
>> something's wrong?
>>
>>
>>
>> On Thu, Oct 14, 2021 at 9:52 AM Thomas Eckardt <
>> *thomas.ecka...@thockar.com* <thomas.ecka...@thockar.com>> wrote:
>> Hi all,
>>
>> fixed in assp 2.6.6 *SPAM-Evaporator* build 21287:
>>
>> - If a folder was defined for the parameter 'griplist' (e.g.
>> grip/griplist) and this folder was not extisting, all griplist functions
>> were not working.
>> If a folder is now defined, it is created by assp.
>>
>> - If 'ConfigChangeSchedule' was used to change a hidden configuration
>> parameter, only the main thread (not any worker) was aware of the change.
>>
>> - If a mail subject contained a questionmark '?' in its text and the
>> subject header line was encoded 'Quoted Printable' and the questionmark was
>> not right MIME encoded
>> (instead it was written as '?') all internal functions related to the
>> mail subject were not working correctly
>>
>>
>> changed:
>>
>> - BerkeleyDB error logs (BDB-error.txt) are no longer permanently created
>> and locked
>> Instead there is a new hidden parameter 'BDBerrLog', which can be set
>> to 1 to monitor BDB-problems.
>>
>> our $BDBerrLog = 0; # (0/1) log BerkeleyDB errors in the related BDB-ENV
>> -errfile .../BDB-error.txt (default = 0)
>>
>> - The GUI-help text for 'noGriplistUpload', 'noGriplistDownload' and
>> 'gripValencePB' are updated - griplist functions are not changed
>>
>>
>>
>> added:
>> - If windows systems are running out of available open file descriptors
>> and the used perl installation is not compiled using the -DUSE_PERLIO
>> switch,
>> the following parameters can be used to increase the available file
>> descriptors for the assp process
>>
>> our $winSetMaxIO_DLL = 'msvcrt'; # the name of the microsoft
>> C-runtime-library used by perl and/or perl-modules (Win32 only !!!) -
>> default is msvcrt
>> # If your perl uses (is compiled
>> against) any other msvcrtXXX (for example: msvcrt160 or msvcrt100) - change
>> this value, if
>> # you want to set the maximum
>> open files limit in the msvcrtXXX.
>> # This value is ONLY used for
>> the below purpose ($winSetMaxIO), it has no other effect !
>>
>> our $winSetMaxIO = 0; # (0/1/ 512 * 2**N) set the
>> maximum open files limit (Win32 only !!!) in ($winSetMaxIO_DLL) msvcrt.dll
>> (_getmaxstdio , _setmaxstdio)
>> # 0 - use the default setting in
>> msvcrt.dll (normaly set to 512)
>> # 1 - find the maximum allowed
>> value between 512 and 8192 and set it
>> # 512 * 2**N - try to set the
>> value as high as possible up to the given maximum (min 512 , max 8192, in
>> 512 * 2**N [N=0..4])
>> # if the defined value
>> is less than the current maximum, the setting will not be changed
>> # Notice: PERLIO (perl compiled
>> with -DUSE_PERLIO - check with :>perl -V) may define a different max open
>> file limit for its
>> # IO's (defaults to 2048
>> because PERLIO_MAX_REFCOUNTABLE_FD=2048)
>> # - this limit is not
>> affected by this value
>>
>>
>>
>> Thomas
>>
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential, legally
>> privileged and protected in law and are intended solely for the use of the
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> *******************************************************
>>
>> _______________________________________________
>> Assp-test mailing list
>> *Assp-test@lists.sourceforge.net* <Assp-test@lists.sourceforge.net>
>> *https://lists.sourceforge.net/lists/listinfo/assp-test*
>> <https://lists.sourceforge.net/lists/listinfo/assp-test>
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>>
>>
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential, legally
>> privileged and protected in law and are intended solely for the use of the
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> *******************************************************
>>
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
