Project

General

Profile

Bug #55851

Unable to run alert source 'HasUpdate'

Added by Alain Dumas about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Waiting for feedback
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Got this email alert in RC1. Is this related ?

Unable to run alert source 'HasUpdate'
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/alert.py", line 358, in _run_source
alerts = (await alert_source.check()) or []
File "/usr/local/lib/python3.6/site-packages/middlewared/alert/base.py", line 96, in check
return await self.middleware.run_in_thread(self.check_sync)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 943, in run_in_thread
return await self.loop.run_in_executor(executor, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/../alert/source/update.py", line 32, in check_sync
path = self.middleware.call_sync("notifier.get_update_location")
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1073, in call_sync
return fut.result()
File "/usr/local/lib/python3.6/concurrent/futures/_base.py", line 425, in result
return self._get_result()
File "/usr/local/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
raise self._exception
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 997, in _call
return await run_method(methodobj, *args)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 943, in run_in_thread
return await self.loop.run_in_executor(executor, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/www/freenasUI/middleware/notifier.py", line 1603, in get_update_location
syspath = c.call('systemdataset.config')['path']
File "/usr/local/www/freenasUI/middleware/notifier.py", line 1603, in get_update_location
syspath = c.call('systemdataset.config')['path']
File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py", line 447, in call
raise CallTimeout("Call timeout")
middlewared.client.client.CallTimeout: Call timeout

Related issues

Related to FreeNAS - Bug #56778: New alerts: * Unable to run alert source 'HasUpdate'Closed

History

#1 Updated by Dru Lavigne about 3 years ago

  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information from Author

Alain: please attach a debug (System -> Advanced -> Save debug) to this ticket.

#2 Updated by Alain Dumas about 3 years ago

  • File debug.tgz added

Here it is. Thanks.

#3 Updated by Dru Lavigne about 3 years ago

  • Assignee changed from Release Council to William Grzybowski
  • Reason for Blocked deleted (Need additional information from Author)

#4 Updated by William Grzybowski about 3 years ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Waiting for feedback

How often does that happen? Was it a single time?

#5 Updated by Alain Dumas about 3 years ago

Happened twice on the same day. Same day I scrub my pools.

#6 Updated by William Grzybowski about 3 years ago

We have not seem on our systems before.

Please let us know once this happens again. If its related when the system is under load (scrubs) or whatnot.

#7 Updated by Dru Lavigne about 3 years ago

  • Related to Bug #56778: New alerts: * Unable to run alert source 'HasUpdate' added

#8 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug.tgz)

#9 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Blocked to Closed
  • Target version changed from Backlog to N/A
  • Private changed from Yes to No

Alain: closing out for now. Please add a comment to this ticket if the issue reoccurs.

Also available in: Atom PDF