File attached. However, I don't see any smoking gun.
Nothing in t/log
[ec2-user@ip-172-31-131-251 Mail-SpamAssassin-4.0.1]$ ls -lR t/log
t/log:
total 0
Nothing big in iptables
[ec2-user@ip-172-31-131-251 Mail-SpamAssassin-4.0.1]$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- ip-10-8-0-0.ec2.internal/24 anywhere
ACCEPT all -- anywhere anywhere state
RELATED,ESTABLISHED
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Tnx, Tuc
On Wed, Apr 3, 2024 at 3:31 PM Bill Cole <
sausers-20150...@billmail.scconsult.com> wrote:
> On 2024-04-03 at 14:01:44 UTC-0400 (Wed, 3 Apr 2024 14:01:44 -0400)
> Scott Ellentuch <tuct...@gmail.com>
> is rumored to have said:
>
> > Hi,
> >
> > Ok, deleted the directory and started again.
> >
> > Test Summary Report
> > -------------------
> > t/spamd_client.t (Wstat: 26624 Tests: 4 Failed: 0)
> > Non-zero exit status: 104
> > Parse errors: Bad plan. You planned 52 tests but ran 4.
> > Files=217, Tests=3765, 890 wallclock secs ( 1.21 usr 0.19 sys +
> > 271.62
> > cusr 25.51 csys = 298.53 CPU)
> > Result: FAIL
> > Failed 1/217 test programs. 0/3765 subtests failed.
> > make: *** [test_dynamic] Error 255
> >
> > Script file attached.
>
> This error appears to be a problem launching a spamd instance from the
> test harness, verifying its PID, and getting responses from it. You can
> get more details logged by clearing the test logs and re-running just
> the one test file which displays the problem:
>
> rm -r t/log
> make test TEST_FILES="t/spamd_client.t" TEST_VERBOSE=1
>
> That should provide the precise command used to launch spamd and
> hopefully a clue about why it failed. There may also be useful
> information logged under t/log/ after a failed test.
>
> One possibility is a local packet filter (iptables, nftables, etc.)
> blocking the port spamd uses for testing. That is rare because it
> selects an unused high port on the loopback interface for the test run,
> but if you have a very tight network security policy in place, that can
> fail. SELinux and AppArmor can also interfere.
>
>
> >
> > Thanks Tuc
> >
> > On Wed, Apr 3, 2024 at 10:46 AM Bill Cole <
> > sausers-20150...@billmail.scconsult.com> wrote:
> >
> >> On 2024-04-02 at 18:18:09 UTC-0400 (Tue, 2 Apr 2024 18:18:09 -0400)
> >> Scott Ellentuch <tuct...@gmail.com>
> >> is rumored to have said:
> >>
> >>> Hi,
> >>>
> >>> Trying to install SA 4.0.1 from scratch. Tried via CPAN, that didn't
> >>> go
> >>> well, so trying from tarball. (Enabled SSL when doing Makefile.PL)
> >>
> >> NEVER run 'make' as root except when you're ready to commit with
> >> 'make
> >> install' unless you're doing it on a sacrificial system.
> >>
> >> Think about how unsafe it could be...
> >>
> >> These test failures look like you did that. I am flattered that you
> >> trust the SpamAssassin team that much, but don't, please. We are only
> >> human. In the past there have been bugs in the test suite that have
> >> polluted the running config of the system if run as root. It is
> >> possible
> >> in principle for there to still be such bugs.
> >>
> >>> I'm on Amazon Linux 2 , 4.0.1 SA, and not sure what other info I can
> >>> give.
> >>> I installed every perl module it wanted.
> >>
> >> FWIW, non-root 'make test' has been clean for PMC members on a wide
> >> range of systems, so a real test failure would be both a shock and a
> >> serious problem. If this is happening with a normal user running
> >> 'make
> >> test' we definitely need to
> >> address it.
> >>
> >>>
> >>> The final summary is -
> >>> Test Summary Report
> >>> -------------------
> >>> t/spamc_optL.t (Wstat: 2560 Tests: 18 Failed: 10)
> >>> Failed tests: 2, 5-8, 10, 12, 15-16, 18
> >>> Non-zero exit status: 10
> >>> t/spamd_client.t (Wstat: 3584 Tests: 52 Failed: 14)
> >>> Failed tests: 35, 37-42, 44, 46-51
> >>> Non-zero exit status: 14
> >>> Files=217, Tests=3807, 904 wallclock secs ( 1.21 usr 0.22 sys +
> >>> 273.72
> >>> cusr 26.33 csys = 301.48 CPU)
> >>> Result: FAIL
> >>> Failed 2/217 test programs. 24/3807 subtests failed.
> >>> make: *** [test_dynamic] Error 255
> >>>
> >>> During the run it seems to output :
> >>>
> >>> t/spamd_client.t .................. 32/52
> >>> # Failed test at t/spamd_client.t line 152.
> >>> ERROR: Bayes dump returned an error, please re-run with -D for more
> >>> information
> >>> t/spamd_client.t .................. 37/52
> >>> # Failed test at t/spamd_client.t line 157.
> >>> Not found: spam in database = 1 0 non-token data: nspam at
> >>> t/spamd_client.t line 158.
> >>>
> >>> # Failed test at t/SATest.pm line 926.
> >>>
> >>> # Failed test at t/spamd_client.t line 161.
> >>> ERROR: Bayes dump returned an error, please re-run with -D for more
> >>> information
> >>>
> >>> # Failed test at t/spamd_client.t line 165.
> >>> Not found: ham in database = 0 0 non-token data: nham at
> >>> t/spamd_client.t
> >>> line 166.
> >>>
> >>> # Failed test at t/SATest.pm line 926.
> >>> Not found: spam in database = 0 0 non-token data: nspam at
> >>> t/spamd_client.t line 166.
> >>>
> >>> # Failed test at t/SATest.pm line 926.
> >>> t/spamd_client.t .................. 44/52
> >>> # Failed test at t/spamd_client.t line 172.
> >>> ERROR: Bayes dump returned an error, please re-run with -D for more
> >>> information
> >>>
> >>> # Failed test at t/spamd_client.t line 177.
> >>> Not found: ham in database = 1 0 non-token data: nham at
> >>> t/spamd_client.t
> >>> line 178.
> >>>
> >>> # Failed test at t/SATest.pm line 926.
> >>>
> >>> # Failed test at t/spamd_client.t line 181.
> >>> ERROR: Bayes dump returned an error, please re-run with -D for more
> >>> information
> >>> t/spamd_client.t .................. 49/52
> >>> # Failed test at t/spamd_client.t line 185.
> >>> Not found: ham in database = 0 0 non-token data: nham at
> >>> t/spamd_client.t
> >>> line 186.
> >>>
> >>> # Failed test at t/SATest.pm line 926.
> >>> Not found: spam in database = 0 0 non-token data: nspam at
> >>> t/spamd_client.t line 186.
> >>>
> >>> # Failed test at t/SATest.pm line 926.
> >>> t/spamd_client.t .................. 52/52 # Looks like you failed 14
> >>> tests
> >>> of 52.
> >>> t/spamd_client.t .................. Dubious, test returned 14 (wstat
> >>> 3584,
> >>> 0xe00)
> >>> Failed 14/52 subtests
> >>>
> >>> Any indications as to the issue?
> >>>
> >>> Thanks, Tuc
> >>
> >>
> >> --
> >> Bill Cole
> >> b...@scconsult.com or billc...@apache.org
> >> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> >> Not Currently Available For Hire
> >>
>
>
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
>
Script started on Wed 03 Apr 2024 08:36:02 PM UTC
]0;ec2-user@ip-172-31-131-251:/usr/local/src/Mail-SpamAssassin-4.0.1[?1034h[ec2-user@ip-172-31-131-251
Mail-SpamAssassin-4.0.1]$ rm -r t/log
]0;ec2-user@ip-172-31-131-251:/usr/local/src/Mail-SpamAssassin-4.0.1[ec2-user@ip-172-31-131-251
Mail-SpamAssassin-4.0.1]$ make test TEST_FILES="
t/spamd_client.t" TEST_VERBOSE=1
"/usr/bin/perl" build/mkrules --exit_on_no_src --src rulesrc --out rules
--manifest MANIFEST --manifestskip MANIFEST.SKIP
no source directory found: exiting
"/usr/bin/perl" build/preprocessor -Mvars -DVERSION="4.000001"
-DPREFIX="/usr/local" -DDEF_RULES_DIR="/usr/local/share/spamassassin"
-DLOCAL_RULES_DIR="/etc/mail/spamassassin"
-DLOCAL_STATE_DIR="/var/lib/spamassassin"
-DINSTALLSITELIB="/usr/local/share/perl5" -DCONTACT_ADDRESS="the administrator
of that system" -DRE2C_BIN="re2c" -Msharpbang -Mconditional
-DPERL_BIN=""/usr/bin/perl"" -DPERL_WARN="" -DPERL_TAINT="" -m755
-isa-update.raw -osa-update
cp sa-update blib/script/sa-update
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/sa-update
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')"
t/spamd_client.t
t/spamd_client.t ..
1..52
ok 1
/usr/bin/perl SATest.pl -Mredirect
-Olog/spamd_client.AP0XfI/d.spamd_client/spamd.err.1
-olog/spamd_client.AP0XfI/d.spamd_client/spamd.out.1 -- /usr/bin/perl -T -w
-I/usr/local/src/Mail-SpamAssassin-4.0.1/blib/lib
-I/usr/local/src/Mail-SpamAssassin-4.0.1/blib/arch -I/usr/local/lib64/perl5
-I/usr/local/share/perl5 -I/usr/lib64/perl5/vendor_perl
-I/usr/share/perl5/vendor_perl -I/usr/lib64/perl5 -I/usr/share/perl5
../spamd/spamd.raw -D -x -s stderr -C log/spamd_client.AP0XfI/localrules
--siteconfigpath log/spamd_client.AP0XfI/siterules -p 47802 -A 127.0.0.1 -i
127.0.0.1 -L -s log/spamd_client.AP0XfI/d.spamd_client/spamd.err.1.timestamped
-r log/spamd_client.AP0XfI/spamd.pid &
[1712176581] Found PID 14313 in pidfile
ok 2
ok 3
ok 4
error reading from spamd (10): Connection reset by peer at
/usr/local/src/Mail-SpamAssassin-4.0.1/blib/lib/Mail/SpamAssassin/Client.pm
line 641, <GEN3> line 3.
# Looks like your test exited with 104 just after 4.
Dubious, test returned 104 (wstat 26624, 0x6800)
Failed 48/52 subtests
Test Summary Report
-------------------
t/spamd_client.t (Wstat: 26624 Tests: 4 Failed: 0)
Non-zero exit status: 104
Parse errors: Bad plan. You planned 52 tests but ran 4.
Files=1, Tests=4, 7 wallclock secs ( 0.01 usr 0.00 sys + 0.07 cusr 0.03
csys = 0.11 CPU)
Result: FAIL
Failed 1/1 test programs. 0/4 subtests failed.
make: *** [test_dynamic] Error 104
]0;ec2-user@ip-172-31-131-251:/usr/local/src/Mail-SpamAssassin-4.0.1[ec2-user@ip-172-31-131-251
Mail-SpamAssassin-4.0.1]$ exit
exit
Script done on Wed 03 Apr 2024 08:36:33 PM UTC
