X25ds
November 14, 2025, 6:59pm
1
Hey dear folks!
Since the upgrade I’m getting a ton of errors with the following Content:
If I check the journal I found the following:
Nov 14 17:20:00 hostname systemd[1]: Starting sysstat-collect.service - system activity accounting tool…
Is this somehow an error?
Thanks a lot!
Best Regards
Huh, does this persist if you roll back to a previous boot? If not, might be worth a bug report - I don’t have an easy fix on top of head for why PIDs are missing other than trying a clean install & config import.
X25ds
November 15, 2025, 8:34am
3
Could it be this problem? There it seems to be resolved:
opened 03:01AM - 03 Jul 24 UTC
closed 04:18PM - 08 Jul 24 UTC
bug 🐛
journal
pid1
already-fixed
### systemd version the issue has been seen with
255.4-1ubuntu8.1
### Used dis… tribution
Ubuntu 24.04 LTS
### Linux kernel version used
6.8.0-36-generic
### CPU architectures issue was seen on
x86_64
### Component
journalctl, systemd
### Expected behaviour you didn't see
journal is getting several messages with this content:
here's a sample of one with json format
```
{
"_SYSTEMD_UNIT" : "init.scope",
"__CURSOR" : "s=9dc0d5781e8142708115b93507baef5f;i=93384;b=47ca632bdebc4e1ab399d8fbfa9b8bf4;m=8a403ba5f;t=61c4dc2308f02;x=8cc073751fc088c5>
"_BOOT_ID" : "47ca632bdebc4e1ab399d8fbfa9b8bf4",
"_PID" : "1",
"__MONOTONIC_TIMESTAMP" : "37111446111",
"CODE_FUNC" : "manager_dispatch_notify_fd",
"SYSLOG_IDENTIFIER" : "systemd",
"_SELINUX_CONTEXT" : "unconfined\n",
"MESSAGE" : "Cannot find unit for notify message of PID 859062, ignoring.",
"_CMDLINE" : "/sbin/init",
"_RUNTIME_SCOPE" : "system",
"TID" : "1",
"_HOSTNAME" : "multivac",
"_TRANSPORT" : "journal",
"_UID" : "0",
"_GID" : "0",
"__SEQNUM_ID" : "9dc0d5781e8142708115b93507baef5f",
"CODE_FILE" : "src/core/manager.c",
"_SOURCE_REALTIME_TIMESTAMP" : "1719970156285636",
"_EXE" : "/usr/lib/systemd/systemd",
"__SEQNUM" : "603012",
"__REALTIME_TIMESTAMP" : "1719970156285698",
"PRIORITY" : "4",
"_COMM" : "systemd",
"_MACHINE_ID" : "f03e0953bff947f09f8460dd8fe04788",
"SYSLOG_FACILITY" : "3",
"_SYSTEMD_SLICE" : "-.slice",
"_SYSTEMD_CGROUP" : "/init.scope",
"_CAP_EFFECTIVE" : "1ffffffffff",
"CODE_LINE" : "2745"
}
```
if I do journalctl -e and scroll I can see the following
```
Jul 03 01:55:10 multivac systemd[1]: Cannot find unit for notify message of PID 895075, ignoring.
Jul 03 01:55:51 multivac systemd[1]: Cannot find unit for notify message of PID 895976, ignoring.
Jul 03 01:56:39 multivac systemd[1]: Cannot find unit for notify message of PID 897126, ignoring.
Jul 03 01:56:44 multivac systemd[1]: Cannot find unit for notify message of PID 897177, ignoring.
Jul 03 01:58:02 multivac systemd[1]: Cannot find unit for notify message of PID 899057, ignoring.
Jul 03 01:59:10 multivac systemd[1]: Cannot find unit for notify message of PID 900547, ignoring.
Jul 03 01:59:57 multivac systemd[1]: Cannot find unit for notify message of PID 901668, ignoring.
Jul 03 02:00:00 multivac systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
Jul 03 02:00:00 multivac systemd[1]: sysstat-collect.service: Deactivated successfully.
Jul 03 02:00:00 multivac systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Jul 03 02:00:29 multivac systemd[1]: Cannot find unit for notify message of PID 902369, ignoring.
Jul 03 02:00:29 multivac systemd[1]: Cannot find unit for notify message of PID 902435, ignoring.
Jul 03 02:00:34 multivac systemd[1]: Cannot find unit for notify message of PID 902487, ignoring.
Jul 03 02:01:32 multivac systemd[1]: Cannot find unit for notify message of PID 903809, ignoring.
Jul 03 02:01:37 multivac systemd[1]: Cannot find unit for notify message of PID 903886, ignoring.
Jul 03 02:01:48 multivac systemd[1]: Cannot find unit for notify message of PID 904239, ignoring.
Jul 03 02:02:04 multivac systemd[1]: Cannot find unit for notify message of PID 904531, ignoring.
Jul 03 02:02:35 multivac systemd[1]: Cannot find unit for notify message of PID 905306, ignoring.
Jul 03 02:03:16 multivac systemd[1]: Cannot find unit for notify message of PID 906177, ignoring.
Jul 03 02:03:39 multivac systemd[1]: Cannot find unit for notify message of PID 906764, ignoring.
Jul 03 02:04:20 multivac systemd[1]: Cannot find unit for notify message of PID 907724, ignoring.
Jul 03 02:04:25 multivac systemd[1]: Cannot find unit for notify message of PID 907755, ignoring.
Jul 03 02:04:46 multivac systemd[1]: Cannot find unit for notify message of PID 908288, ignoring.
```
### Unexpected behaviour you saw
_No response_
### Steps to reproduce the problem
_No response_
### Additional program output to the terminal or log subsystem illustrating the issue
_No response_
Donno, I’d consider a TrueNAS ticket to validate; I don’t get those messages so I’m not going to assume everything is fine on your end.
X25ds
November 16, 2025, 8:53am
5
Rolled back to 25.04 yesterday, the syslog entries did go away.
So it is version specific; consider tossing a bug report to IX so if you do want to upgrade in the future there is a chance it gets fixed.
I recently upgraded to 25.10.0.1 and am finding the same log entries. Did anything change or is there a fix available?
sard
December 18, 2025, 6:29pm
8
Same on 25.10.1. But seems as if this can be ignored .
