Critical alert

Erfhh

Cadet
Joined
Mar 9, 2023
Messages
2
Since yesterday, an alert apeard and it seems to slow down everything :

Failed to check for alert Smartd: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/plugins/alert.py", line 776, in __run_source alerts = (await alert_source.check()) or [] File "/usr/lib/python3/dist-packages/middlewared/alert/base.py", line 223, in check return await self.middleware.run_in_thread(self.check_sync) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1252, in run_in_thread return await self.run_in_executor(self.thread_pool_executor, method, *args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1249, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs)) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3/dist-packages/middlewared/alert/source/smartd.py", line 22, in check_sync if not self.middleware.call_sync("service.started", "smartd"): File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1405, in call_sync return self.run_coroutine(methodobj(*prepared_call.args)) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1445, in run_coroutine return fut.result() File "/usr/lib/python3.9/concurrent/futures/_base.py", line 433, in result return self.__get_result() File "/usr/lib/python3.9/concurrent/futures/_base.py", line 389, in __get_result raise self._exception File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1318, in nf return await func(*args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1186, in nf res = await f(*args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/service.py", line 201, in started state = await service_object.get_state() File "/usr/lib/python3/dist-packages/middlewared/plugins/service_/services/base.py", line 37, in get_state return await self.middleware.run_in_thread(self._get_state_sync) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1252, in run_in_thread return await self.run_in_executor(self.thread_pool_executor, method, *args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1249, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs)) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/service_/services/base.py", line 40, in _get_state_sync unit = self._get_systemd_unit() File "/usr/lib/python3/dist-packages/middlewared/plugins/service_/services/base.py", line 69, in _get_systemd_unit unit.load() File "/usr/lib/python3/dist-packages/pystemd/base.py", line 89, in load unit_xml = self.get_introspect_xml() File "/usr/lib/python3/dist-packages/pystemd/base.py", line 75, in get_introspect_xml bus.call_method( File "pystemd/dbuslib.pyx", line 442, in pystemd.dbuslib.DBus.call_method pystemd.dbusexc.DBusTimedOutError: [err -110]: b"Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)"​

Please, I don't understand even a speck of this.
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925

Erfhh

Cadet
Joined
Mar 9, 2023
Messages
2

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
I'm, "Core only" and have to leave it to others to comment relative to Scale, but I think you need to describe your pools and shares setup at least, and their current status. Also, what were you doing, if anything, that may have initiated the alert you are reporting?
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
The most likely explanation is your boot disk has been corrupted. All the way at the bottom of that long chain of errors is this:

Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)​

Systemd is the service that starts other services. If it's not running, your system will be very bent out of shape. Did you disable all overclocking in your BIOS? That's the only reason I can see for your M.2 boot drive going south: running the PCI-e clock out of spec.
 
Top