question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't run CLI commands, or restart daemon. Working normally besides that?

See original GitHub issue

Expected behaviour:

flexget seems to be running properly (downloads etc working) but any command on cli crashes (except version checking)

Actual behaviour:

There is a FlexGet process already running for this config, sending execution there.
Traceback (most recent call last):
  File "/usr/local/bin/flexget", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/flexget/__init__.py", line 42, in main
    manager.start()
  File "/usr/local/lib/python2.7/dist-packages/flexget/manager.py", line 339, in start
    client = IPCClient(ipc_info['port'], ipc_info['password'], sync_request_timeout=self.options.timeout)
  File "/usr/local/lib/python2.7/dist-packages/flexget/ipc.py", line 171, in __init__
    channel, service=ClientService, config={'sync_request_timeout': sync_request_timeout})
  File "/usr/local/lib/python2.7/dist-packages/rpyc/utils/factory.py", line 44, in connect_channel
    return service._connect(channel, config)
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/service.py", line 100, in _connect
    self.on_connect(conn)
  File "/usr/local/lib/python2.7/dist-packages/flexget/ipc.py", line 108, in on_connect
    daemon_version = self._conn.root.version()
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/netref.py", line 155, in __getattribute__
    return syncreq(self, consts.HANDLE_GETATTR, name)
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/netref.py", line 75, in syncreq
    return conn.sync_request(handler, proxy, *args)
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 471, in sync_request
    return self.async_request(handler, *args, timeout=timeout).value
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/async_.py", line 97, in value
    raise self._obj
KeyError: '<flexget.ipc.DaemonService object at 0x7f232821ec68>'

========= Remote Traceback (1) =========
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 305, in _dispatch_request
    proxy = self._netref_factory(oid, clsname, modname)
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 541, in _handle_getattr
    #
  File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 499, in _access_attr
    """Fetches the root object (service) of the other party"""
  File "/usr/local/lib/python2.7/dist-packages/rpyc/lib/colls.py", line 86, in __getitem__
    return self._dict[key][0]
KeyError: <flexget.ipc.DaemonService object at 0x7f232821ec68>

Steps to reproduce:

  • Step 1: flexget check

Additional information:

  • FlexGet version: 2.17.19 You are on the latest release.
  • Python version: Python 2.7.12
  • Installation method: managed seedbox (unsure)
  • Using daemon (yes/no): yes
  • OS and version: Ubuntu 16.04.4 LTS
  • Link to crash log:

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
chestm007commented, Dec 13, 2018

@jacobkossman I’m having a little trouble reproducing this issue.

It looks to me like you might still have the daemon running with the old version, can you try restarting the daemon? flexget daemon stop; flexget daemon start and then retry executing commands?

0reactions
gazpachokingcommented, Dec 13, 2018

I think @chestm007 is probably right that your daemon needs to be restarted. This however probably won’t work via the cli commands, as they cause the crash. You may need to kill the daemon then start it up again. In the future, it is good practice to shut down the daemon before doing a flexget upgrade.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Bash-script as linux-service won't run, but executed from ...
The problem is that, when the script runs as a service, it does not run as "you": it does not have your environment....
Read more >
Varnish won't start as service but works fine from command line?
Execute bash -x /etc/init.d/varnish restart to find with what options varnish really tries to start, and then try running with them on cli....
Read more >
Azure Cloud Shell troubleshooting | Microsoft Learn
This article covers troubleshooting Cloud Shell common scenarios. ... To speed up start time, the cmdlet no longer runs automatically.
Read more >
How can I run a command which will survive terminal close?
One of the following 2 should work: $ nohup redshift &. or $ redshift & $ disown. See the following for a bit...
Read more >
Docker run reference
Docker run reference . Docker runs processes in isolated containers. A container is a process which runs on a host. The host...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found