On Tue, Nov 29, 2022 at 09:40:14AM -0500, Greg Troxel wrote:
>
> I am pretty sure the hardware is OK, but I can't really run memtest86 as
> it is a VPS.
Memtester is userland, should be on most distributions: apt install memtester
You can give it parameter of how much memory you have free, and
Is it very very common to find VPSs running on PC Motherboards, not server
Mobos... so no ECC
It is also very common in VPSs to overclock RAM, so stability is not its main
virtue..
Ask them Greg, and demand details and proofs of real hw being used.
Pedro.
On Tuesday, November 29, 2022 at
Henrik K writes:
>> I see occasional coredumps (as in perl.core). It is often enough to be
>> annoying (beyond worrisome that it happens at all), but not reproducible
>> and no apparent pattern.
>
> Try memtester/memtest86, atleast if it's not a proper server with ECC
> memory..
I am pretty
> It doesn't finish any other rules and doesn't display final results at all.
>
> And then I start it simply again and everything is fine.
>
> Has anybody else seen this odd behavior?
I've seen it a few times when running in a VM that didn't have enough
memory available. The clue for me was
Henrik's ideas are very good. I would also question the hardware too. KAM
On Tue, Nov 29, 2022, 08:28 Henrik K wrote:
> On Tue, Nov 29, 2022 at 07:34:51AM -0500, Greg Troxel wrote:
> >
> > Wolfgang Breyha writes:
> >
> > > It doesn't finish any other rules and doesn't display final results
On Tue, Nov 29, 2022 at 07:34:51AM -0500, Greg Troxel wrote:
>
> Wolfgang Breyha writes:
>
> > It doesn't finish any other rules and doesn't display final results at all.
> >
> > And then I start it simply again and everything is fine.
> >
> > Has anybody else seen this odd behavior?
>
> I see
Wolfgang Breyha writes:
> It doesn't finish any other rules and doesn't display final results at all.
>
> And then I start it simply again and everything is fine.
>
> Has anybody else seen this odd behavior?
I see occasional coredumps (as in perl.core). It is often enough to be
annoying
Hi!
I had this occasionally with 3.4.x and now on 4.x-trunk as well...
If I start spamassassin on commandline to check certain EML files with
spamassassin -D Nov 29 12:48:32.283 [828333] dbg: dns: dns reply to 25959/IN/A/...:
> NXDOMAIN
> Nov 29 12:48:32.283 [828333] dbg: async: calling
