Flexget error with daemon but no error when run manually

@The-red-pill wrote:

Hi There,

I am getting an error when i run the daemon in the background but if i kill it and run manually it works fine and downloads my torrents as it should.

Really don't know why - i am really guessing corrupt database - so how dangerous is it the run the reset command ?

PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

root@VINDEBIAN:~# python -V
Python 2.7.9

root@VINDEBIAN:~# flexget check
2017-05-16 23:13 WARNING  check                         Config line 13 is likely missing ':' at the end
2017-05-16 23:13 VERBOSE  check                         Pre-checked 15 configuration lines
2017-05-16 23:13 VERBOSE  check                         Checking config file `/root/.flexget/config.yml`
2017-05-16 23:13 VERBOSE  check                         Config passed check.

**ERROR MSG:**

2017-04-19 00:56 DEBUG    manager                       Traceback:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/flexget/task_queue.py", line 48, in run
    self.current_task.execute()
  File "/usr/local/lib/python2.7/dist-packages/flexget/task.py", line 72, in wrapper
    return func(self, *args, **kw)
  File "/usr/local/lib/python2.7/dist-packages/flexget/task.py", line 643, in execute
    self.manager.db_cleanup()
  File "/usr/local/lib/python2.7/dist-packages/flexget/manager.py", line 896, in db_cleanup
    fire_event('manager.db_cleanup', self, session)
  File "/usr/local/lib/python2.7/dist-packages/flexget/event.py", line 106, in fire_event
    result = event(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flexget/event.py", line 23, in __call__
    return self.func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/operate/status.py", line 145, in db_cleanup
    for status_task in session.query(StatusTask).all():
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2703, in all
    return list(self)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/loading.py", line 90, in instances
    util.raise_from_cause(err)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/loading.py", line 57, in instances
    for query_entity in query._entities
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 3700, in row_processor
    polymorphic_discriminator=self._polymorphic_discriminator
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/loading.py", line 302, in _instance_processor
    context.attributes, "memoized_setups", _none_set)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/path_registry.py", line 71, in get
    key = (key, self.path)
SystemError: unknown opcode
2017-04-19 00:57 DEBUG    scheduler                     executing tasks: [u'*']
2017-04-19 00:57 DEBUG    scheduler                     task finished executing: <task>
2017-04-19 00:57 INFO     manager       <task>           Running database cleanup.
2017-04-19 00:57 DEBUG    scheduler                     all tasks in schedule finished executing
2017-04-19 00:57 CRITICAL task_queue                    BUG: Unhandled exception during task queue run loop.
2017-04-19 00:57 CRITICAL manager                       An unexpected crash has occurred. Writing crash report to /root/.flexget/crash_report.2017.04.19.005710326704.log. Please verify you are running the latest version of flexget by using "flexget -V" from CLI or by using version_checker plugin at http://flexget.com/wiki/Plugins/version_checker. You are currently using version 2.10.31

The log is old but would be valid if i ran the daemon now in the background so i just run it manually for a while now.

Thank you!

Posts: 1

Participants: 1

Read full topic