>last ditch effort
>free up space upon cleanup somehow
assp does NOT care about disk space !
(only the rebuild task shows some informational disk space values)
>Strange that spam wound up in discarded though right?
but if the disk is full, assp may be unable to write any new file and
updated file (incl. the assp.cfg, stats, sync, tmp) to disk - which leads
in to a destroyed configuration
if configuration values are missing in the assp.cfg (possibly partly
written), these values may be set to defaults at startup or recovered from
a backup (*.bak....)
assp tries to do its best to recover a destroyed assp.cfg (in several
ways), but a 'disk full' condition prevent this and the overall result in
the assp folder is (may be) very unexpected
release change backups of the assp.cfg are stored in the 'backup.config'
folder - compare the last backup with your current config file
if you know, everything in the assp folder is OK except the assp.cfg,
configuration changes will fix every issue caused by the disk fault
---------------------------------------------------------------------
On Sun, Sep 5, 2021 at 4:02 AM Thomas Eckardt <thomas.ecka...@thockar.com>
wrote:
The state of the assp folders and files (also the assp.cfg !!!) may be
unexpected after a 'disk full' condition happened.
I recommend to restore a known good state.
------------------------------------------------------------------
So the problem would has been solved at Sun, Sep 5, 2021 - but at least at
Mon, Sep 6, 2021 in the morning.
Seems you think, you can manage this using your own strategy - good luck!
But keep in mind: bad conditions in any file caused by the fault, can lead
in to bad behavior or crashes of assp in future (possibly in months or in
years, depends on the config, GUI actions, configuration changes, perl
module changes ..................)
Thomas
Von: "K Post" <nntp.p...@gmail.com>
An: "ASSP development mailing list" <assp-test@lists.sourceforge.net>
Datum: 08.09.2021 22:37
Betreff: Re: [Assp-test] Logging Options: Log filled with SEGV
warnings
looking okay here now. Strange that spam wound up in discarded
though right? Is that something that ASSP does as an emergency last ditch
effort when a disk fills? Move the old spam to discarded in an attempt to
free up space upon cleanup somehow?
On Sun, Sep 5, 2021 at 4:02 AM Thomas Eckardt <thomas.ecka...@thockar.com>
wrote:
The state of the assp folders and files (also the assp.cfg !!!) may be
unexpected after a 'disk full' condition happened.
I recommend to restore a known good state.
Thomas
Von: "K Post" <nntp.p...@gmail.com>
An: "ASSP development mailing list" <
assp-test@lists.sourceforge.net>
Datum: 04.09.2021 15:54
Betreff: Re: [Assp-test] Logging Options: Log filled with SEGV
warnings
also, while I've got you.... This isn't the first time a filling log has
filled the data drive.
A couple times, after moving the huge log, I've noticed that my
messages/spam corpus suddenly only has the files that hit after the log
cleanup. I always later find that the spam folder has been moved to the
discarded folder (as a spam subfolder).
There is a chance that I carelessly dragged it there once, but multiple
times seems too coincidental. Does ASSP do this intentionally when a
full drive is detected? not-spam and the others are always intact, it's
been the spam folder. It's easy to restore, but I need to remember that it
happened. The ASSP service starts up quite happily with no files in spam,
and it's generally only after seeing that the rebuild ran quicker than
usual overnight that I realize there's virtually nothing in spam.
Thanks again.
On Sat, Sep 4, 2021 at 2:43 AM Thomas Eckardt <thomas.ecka...@thockar.com>
wrote:
fixed in assp 2.6.6 *SPAM-Evaporator* build 21198:
....
- invalid UTF8 characters in a mail subject may caused SEGV errors in
'Win32::Unicode::Dir' on windows systems
I hoped I had fixed it. New generated files should not cause the SEGV, but
old filenames may cause it.
set
Regular Expression to Identify skipped Log Lines* (noLogLineRe)
to
signal SEGV in
>I just don't know if putting a drive letter in the config is another
option.
No, this will not work. But links will work on windows.
>I have everything on my C drive in c:\ASSP\logs.
Is there any good reason to this at a production system???
Thomas
Von: "K Post" <nntp.p...@gmail.com>
An: "ASSP development mailing list" <
assp-test@lists.sourceforge.net>
Datum: 03.09.2021 22:11
Betreff: Re: [Assp-test] Logging Options: Log filled with SEGV
warnings
Thanks James.
The same idea on Windows with a symbolic link should work fine. I just
don't know if putting a drive letter in the config is another option.
My real concern is the SEGV fauls going nuts.
On Fri, Sep 3, 2021 at 2:14 PM James Moe via Assp-test <
assp-test@lists.sourceforge.net> wrote:
On 2021-09-03 09:11, K Post wrote:
> 1) Can the logfile configuration be set to use a different disk?
>
This was relatively easy on linux. I do not know if Windows has a
similar
functionality. Basically the ASSP log directories are re-directed to
another
area with more space.
ASSPDIR="/usr/local/bin/assp2";
ASSPDATA="/data01/var/assp";
assp_mount () {
echo "Mounting assp volumes..."
mount --bind ${ASSPDATA}/okmail ${ASSPDIR}/okmail
mount --bind ${ASSPDATA}/discarded ${ASSPDIR}/discarded
mount --bind ${ASSPDATA}/quarantine ${ASSPDIR}/quarantine
mount --bind ${ASSPDATA}/spam-yes ${ASSPDIR}/spam-yes
mount --bind ${ASSPDATA}/spam-not ${ASSPDIR}/spam-not
mount --bind ${ASSPDATA}/logs ${ASSPDIR}/logs
}
--
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
Think.
_______________________________________________
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
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
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
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
