You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.
When running Premiumizer on freeNas 9.10 it crashes with the following stack trace:
Traceback (most recent call last):
File "./Premiumizer.py", line 1411, in <module>
seconds=active_interval, replace_existing=True, max_instances=1, coalesce=True)
File "/virtualenv/lib/python2.7/site-packages/apscheduler/schedulers/base.py", line 366, in add_job
'trigger': self._create_trigger(trigger, trigger_args),
File "/virtualenv/lib/python2.7/site-packages/apscheduler/schedulers/base.py", line 848, in _create_trigger
return self._create_plugin_instance('trigger', trigger, trigger_args)
File "/virtualenv/lib/python2.7/site-packages/apscheduler/schedulers/base.py", line 833, in _create_plugin_instance
return plugin_cls(**constructor_kwargs)
File "/virtualenv/lib/python2.7/site-packages/apscheduler/triggers/interval.py", line 37, in __init__
self.timezone = astimezone(timezone)
File "/virtualenv/lib/python2.7/site-packages/apscheduler/util.py", line 77, in astimezone
'Unable to determine the name of the local timezone -- you must explicitly '
ValueError: Unable to determine the name of the local timezone -- you must explicitly specify the name of the local timezone. Please
refrain from using timezones like EST to prevent problems with daylight saving time. Instead, use a locale based timezone name (suc
h as Europe/Helsinki).`
This looks like an apscheduler bug but i am not sure.
Update:
Ok i found the reason, its a problem with tzlocal. Its unable to read the correct time zone on freeBSD systems.
There is a pull request here but it has not been accepted yet.
The text was updated successfully, but these errors were encountered:
When running Premiumizer on freeNas 9.10 it crashes with the following stack trace:
This looks like an apscheduler bug but i am not sure.
Update:
Ok i found the reason, its a problem with tzlocal. Its unable to read the correct time zone on freeBSD systems.
There is a pull request here but it has not been accepted yet.
The text was updated successfully, but these errors were encountered: