AssertException: S raised in StringBuffer_clear at src/util/StringBuffer.c:263

[Jonathan Thomson]

Hi

I’ve just done a periodic refresh of my monit instances (I have two, one running on a x86_64 Debian Buster VM and the other a Raspberry Pi 4 Buster host) and the Raspberry Pi install is exhibiting the above error (the x86_64 version is up).

The error thrown when I run monit -vI is as follows;

Starting Monit 5.27.0 daemon with http interface at [0.0.0.0]:2812

Starting Monit HTTP server at [0.0.0.0]:2812

Monit HTTP server started

'http://hostname.myhost.uk' Monit 5.27.0 started

Cannot open proc file '/proc/1/attr/current' -- No such file or directory

AssertException: S

 raised in StringBuffer_clear at src/util/StringBuffer.c:263

Aborted

OS of “good” install:

user@goodhost:~/monit$ hostnamectl
   Static hostname: goodhost.domain.uk
         Icon name: computer-vm
           Chassis: vm
        Machine ID: xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxX
           Boot ID: xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxX
    Virtualization: vmware
  Operating System: Debian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.0-8-amd64
      Architecture: x86-64

OS of “failed” install:

user@badhost:~/code/monit $ hostnamectl
   Static hostname: badhost.domain.uk
         Icon name: computer
        Machine ID: xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxX
           Boot ID: xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxX
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.97-v7l+
      Architecture: arm

‌

[Tildeslash]

Hi Jonathan,

please can you send the following data to [e-mail]?

• monit configuration of the failed host
• full output from “monit -vI” until crash

‌

[Jonathan Thomson]

Hey

Will send you the config shortly but the output above is all that is emitted, also tried with -vv and same output. Monit crashes almost immediately. I did have the 120 second wait in my monitrc file and with that it waits for that period then crashes.

[Jonathan Thomson]

Config sent as requested - the file contains my monitrc file and the contents of /etc/monit.d/ in the one file.

Just for reference, the only thing which I changed in the file between upgrades was uncommenting the idfile and statefile lines - without these monit failed with another error (although on my “good” instance it is running with the same monitrc as the one which doesn’t work).

[Tildeslash]

fix issue #895

→ <<cset a2d24923e9f3>>

[Tildeslash]

fix issue #895

→ <<cset 437983caa453>>

[Jonathan Thomson]

Confirmed working, many thanks for the quick resolution.