Skip to content
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.

Error. Socket doesn't exit. Is daemon running? #54

Open
creotiv opened this issue Nov 14, 2020 · 13 comments
Open

Error. Socket doesn't exit. Is daemon running? #54

creotiv opened this issue Nov 14, 2020 · 13 comments

Comments

@creotiv
Copy link

creotiv commented Nov 14, 2020 •
edited
Loading

Installed driver and client, updated initramfs, rebooted, tried razer-cli, and got "Error. Socket doesn't exit. Is daemon running?"

Ubuntu 20.04
Linux 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ RUST_BACKTRACE=full /usr/share/razercontrol/daemon
Sysfs ready! Starting daemon
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/driver_sysfs.rs:11:15
stack backtrace:
   0:     0x559e66eb4984 - backtrace::backtrace::libunwind::trace::ha716b483344307d4
                               at /usr/src/rustc-1.43.0/vendor/backtrace/src/backtrace/libunwind.rs:86
   1:     0x559e66eb4984 - backtrace::backtrace::trace_unsynchronized::h73191aaca03de050
                               at /usr/src/rustc-1.43.0/vendor/backtrace/src/backtrace/mod.rs:66
   2:     0x559e66eb4984 - std::sys_common::backtrace::_print_fmt::h515542a6f0149e5c
                               at src/libstd/sys_common/backtrace.rs:78
   3:     0x559e66eb4984 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd3babec5fee3351
                               at src/libstd/sys_common/backtrace.rs:59
   4:     0x559e66ecf90c - core::fmt::write::ha5eb378c8b683563
                               at src/libcore/fmt/mod.rs:1063
   5:     0x559e66eb46c7 - std::io::Write::write_fmt::h7525b2825ed7383d
                               at src/libstd/io/mod.rs:1426
   6:     0x559e66eaa9b5 - std::sys_common::backtrace::_print::hfec26b72b492a55c
                               at src/libstd/sys_common/backtrace.rs:62
   7:     0x559e66eaa9b5 - std::sys_common::backtrace::print::h05570acc7a135366
                               at src/libstd/sys_common/backtrace.rs:49
   8:     0x559e66eaa9b5 - std::panicking::default_hook::{{closure}}::h9278410915688d73
                               at src/libstd/panicking.rs:204
   9:     0x559e66eaa6a6 - std::panicking::default_hook::hd3a187a77f7140a0
                               at src/libstd/panicking.rs:224
  10:     0x559e66eab002 - std::panicking::rust_panic_with_hook::hb04c51c9d1a7c747
                               at src/libstd/panicking.rs:470
  11:     0x559e66eaabeb - rust_begin_unwind
                               at src/libstd/panicking.rs:378
  12:     0x559e66ecf201 - core::panicking::panic_fmt::h2e8e792413b965d4
                               at src/libcore/panicking.rs:85
  13:     0x559e66ecf14d - core::panicking::panic::h871cd04a3fc0d7bc
                               at src/libcore/panicking.rs:52
  14:     0x559e66e8f687 - std::sync::once::Once::call_once::{{closure}}::h5a9ed73db4b1462c
  15:     0x559e66eab7a8 - std::sync::once::Once::call_inner::h01ecfd1b80695d2a
                               at src/libstd/sync/once.rs:416
  16:     0x559e66e878ba - daemon::main::h696c292ce84e4186
  17:     0x559e66e97e43 - std::rt::lang_start::{{closure}}::h5385d5de9b7693b8
  18:     0x559e66eaaad3 - std::rt::lang_start_internal::{{closure}}::ha76aba2c161a67a4
                               at src/libstd/rt.rs:52
  19:     0x559e66eaaad3 - std::panicking::try::do_call::hb203df4ff1d5ed94
                               at src/libstd/panicking.rs:303
  20:     0x559e66eb8b67 - __rust_maybe_catch_panic
                               at src/libpanic_unwind/lib.rs:86
  21:     0x559e66eabd5c - std::panicking::try::h785999c549ea777b
                               at src/libstd/panicking.rs:281
  22:     0x559e66eabd5c - std::panic::catch_unwind::hbc99eda2c23b3349
                               at src/libstd/panic.rs:394
  23:     0x559e66eabd5c - std::rt::lang_start_internal::h58283c2b5ed737c9
                               at src/libstd/rt.rs:51
  24:     0x559e66e88062 - main
  25:     0x7fc972b1d0b3 - __libc_start_main
  26:     0x559e66e7d1be - _start
  27:                0x0 - <unknown>
@creotiv
Copy link
Author

creotiv commented Nov 17, 2020

I have Razer Blade Advanced 2019, and seems the problem that DKMS driver doesnt find any devices

creotiv@creotiv:/sys/module/razercontrol/drivers/hid:Razer laptop System control driver$ ls
bind  module  new_id  uevent  unbind

@phelps-sg
Copy link
Contributor

Same problem on Ubuntu 20.04.2 kernel 5.8.0-41 with Blade 15 Base 2020 edition

@QuiiBz
Copy link

QuiiBz commented Feb 4, 2021

Same problem here w/ Razer blade 15 Base 2020. The daemon is running, but looks like it can't find sysfs:

sudo systemctl status razerdaemon.service
* razerdaemon.service - Razer laptop control daemon
     Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: dis>
     Active: active (running) since Thu 2021-02-04 14:29:42 CET; 13s ago
   Main PID: 21084 (daemon)
      Tasks: 1 (limit: 19023)
     Memory: 200.0K
     CGroup: /system.slice/razerdaemon.service
             `-21084 /usr/share/razercontrol/daemon

Feb 04 14:29:46 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:47 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:48 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:49 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:50 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:51 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:52 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:53 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:54 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:55 arch daemon[21084]: Waiting for sysfs to be ready```

@QuiiBz
Copy link

QuiiBz commented Feb 4, 2021

Same problem here w/ Razer blade 15 Base 2020. The daemon is running, but looks like it can't find sysfs:

sudo systemctl status razerdaemon.service
* razerdaemon.service - Razer laptop control daemon
     Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: dis>
     Active: active (running) since Thu 2021-02-04 14:29:42 CET; 13s ago
   Main PID: 21084 (daemon)
      Tasks: 1 (limit: 19023)
     Memory: 200.0K
     CGroup: /system.slice/razerdaemon.service
             `-21084 /usr/share/razercontrol/daemon

Feb 04 14:29:46 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:47 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:48 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:49 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:50 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:51 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:52 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:53 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:54 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:55 arch daemon[21084]: Waiting for sysfs to be ready```

Solved by rebuilding with the latest version and rebooting the system. @phelps-sg Could you try this way?

@phelps-sg
Copy link
Contributor

Same problem here w/ Razer blade 15 Base 2020. The daemon is running, but looks like it can't find sysfs:

sudo systemctl status razerdaemon.service
* razerdaemon.service - Razer laptop control daemon
     Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: dis>
     Active: active (running) since Thu 2021-02-04 14:29:42 CET; 13s ago
   Main PID: 21084 (daemon)
      Tasks: 1 (limit: 19023)
     Memory: 200.0K
     CGroup: /system.slice/razerdaemon.service
             `-21084 /usr/share/razercontrol/daemon

Feb 04 14:29:46 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:47 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:48 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:49 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:50 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:51 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:52 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:53 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:54 arch daemon[21084]: Waiting for sysfs to be ready
Feb 04 14:29:55 arch daemon[21084]: Waiting for sysfs to be ready```

Solved by rebuilding with the latest version and rebooting the system. @phelps-sg Could you try this way?

I was already on latest version in main branch. I also tried rebuilding against the v1.3.0 release, and then rebooting, but same problem.

@mike-lloyd03
Copy link

mike-lloyd03 commented Feb 6, 2021 •
edited
Loading

I have the same problem. Razer Blade 2020 Advanced. Running on Manjaro KDE. Daemon was installed with the Manjaro Software Update.

$ systemctl status razerdaemon.service 

● razerdaemon.service - Razer laptop control daemon
     Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sat 2021-02-06 10:19:52 PST; 44s ago
    Process: 523 ExecStart=/usr/share/razercontrol/daemon (code=exited, status=1/FAILURE)
   Main PID: 523 (code=exited, status=1/FAILURE)

Feb 06 10:19:45 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:46 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:47 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:48 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:49 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:50 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:51 kratos daemon[523]: Waiting for sysfs to be ready
Feb 06 10:19:52 kratos daemon[523]: Timed out waiting for sysfs after a minute!
Feb 06 10:19:52 kratos systemd[1]: razerdaemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 06 10:19:52 kratos systemd[1]: razerdaemon.service: Failed with result 'exit-code'.

@phelps-sg
Copy link
Contributor

Note that there appear to be two different failure modes in the above reports:

  1. Option::unwrap() on a None value
  2. Timed out waiting for sysfs after a minute!

As per the OP I am experiencing 1:

RUST_BACKTRACE=full /usr/share/razercontrol/daemon
Sysfs ready! Starting daemon
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/driver_sysfs.rs:21:14
stack backtrace:
   0:     0x55ec68bb593c - std::backtrace_rs::backtrace::libunwind::trace::h87bbdc8ae314e5a4
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/../../backtrace/src/backtrace/libunwind.rs:96
   1:     0x55ec68bb593c - std::backtrace_rs::backtrace::trace_unsynchronized::h779de2081f0fe77d
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/../../backtrace/src/backtrace/mod.rs:66
   2:     0x55ec68bb593c - std::sys_common::backtrace::_print_fmt::h7f9f27f2b4d4cdf1
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/backtrace.rs:79
   3:     0x55ec68bb593c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf95d19d7937b7307
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/backtrace.rs:58
   4:     0x55ec68bde93f - core::fmt::write::h31ddd5324183dd8d
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/core/src/fmt/mod.rs:1082
   5:     0x55ec68baf327 - std::io::Write::write_fmt::h6553ae225ae21934
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/io/mod.rs:1514
   6:     0x55ec68bc93e0 - std::sys_common::backtrace::_print::h6d7cde6fb59a3272
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/backtrace.rs:61
   7:     0x55ec68bc93e0 - std::sys_common::backtrace::print::h024fb5a1f254b027
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/backtrace.rs:48
   8:     0x55ec68bc93e0 - std::panicking::default_hook::{{closure}}::h008654930ff7c19c
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:200
   9:     0x55ec68bc913e - std::panicking::default_hook::h611ef89f1ca4afb7
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:219
  10:     0x55ec68bc99c3 - std::panicking::rust_panic_with_hook::h4dfeaf97568ec250
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:569
  11:     0x55ec68bb5d79 - std::panicking::begin_panic_handler::{{closure}}::hf55586f621f9c415
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:476
  12:     0x55ec68bb5a8c - std::sys_common::backtrace::__rust_end_short_backtrace::hbddda20e4c1f6fd7
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/backtrace.rs:153
  13:     0x55ec68bc95d2 - rust_begin_unwind
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:475
  14:     0x55ec68bde5f1 - core::panicking::panic_fmt::he4c3f055751e8cea
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/core/src/panicking.rs:85
  15:     0x55ec68bde53d - core::panicking::panic::hdb4ebd5c0dcce155
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/core/src/panicking.rs:50
  16:     0x55ec68b85c30 - std::sync::once::Once::call_once::{{closure}}::hdab72874dd3e223c
  17:     0x55ec68bbb7b5 - std::sync::once::Once::call_inner::h2ab717bd4630065d
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sync/once.rs:421
  18:     0x55ec68b89986 - daemon::main::hbf1019e3af7e563c
  19:     0x55ec68b97633 - std::sys_common::backtrace::__rust_begin_short_backtrace::hf7094a1450cc37c6
  20:     0x55ec68b97649 - std::rt::lang_start::{{closure}}::h82b6dafccc6059fe
  21:     0x55ec68bc9d1c - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h198b3348bc6fe6ff
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/core/src/ops/function.rs:259
  22:     0x55ec68bc9d1c - std::panicking::try::do_call::hb35a1579447c1de7
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:373
  23:     0x55ec68bc9d1c - std::panicking::try::h5fe941721b9f82d8
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:337
  24:     0x55ec68bc9d1c - std::panic::catch_unwind::h5184cddbb930bb79
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panic.rs:379
  25:     0x55ec68bc9d1c - std::rt::lang_start_internal::ha12a50f31e33d94f
                               at /build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/rt.rs:51
  26:     0x55ec68b8a0e2 - main
  27:     0x7fcaf14480b3 - __libc_start_main
  28:     0x55ec68b7f0ae - _start
  29:                0x0 - <unknown>

@CasperBruning
Copy link

Did someone find a fix to make it work? or has someone a different software to control Fans/RGB

@phelps-sg
Copy link
Contributor

Did someone find a fix to make it work? or has someone a different software to control Fans/RGB

I have now got it working. The problem was incompatibility with openrazer. I removed the following package:

sudo apt remove openrazer-driver-dkms

This is documented in driver/README.md which states:

If you have openrazer installed, you must remove it from your system.

phelps-sg added a commit to phelps-sg/razer-laptop-control that referenced this issue Apr 17, 2021
@phelps-sg
Update README.md
af6a4c0 
Edited readme to clarify step by step instructions and in particular inserted explicit instructions to remove openrazer module.  Hopefully this will help prevent users mistakenly installing the module alongside openrazer as per later comments in issue rnd-ash#54.
This was referenced Apr 17, 2021
Merged
Merged
@CasperBruning
Copy link

CasperBruning commented May 10, 2021 •
edited
Loading

Did someone find a fix to make it work? or has someone a different software to control Fans/RGB

I have now got it working. The problem was incompatibility with openrazer. I removed the following package:

sudo apt remove openrazer-driver-dkms

This is documented in driver/README.md which states:

If you have openrazer installed, you must remove it from your system.

I didn't have openrazer installed. But still get the same issue: Error. Socket doesn't exit. Is daemon running?
it seems to be the sysfs problem

@jarbus
Copy link
Contributor

jarbus commented May 20, 2021 •
edited
Loading

Same issue with base 15 2021, don't have openrazer installed. Seems to be an issue with the daemon

[I] ➜ sudo systemctl status razerdaemon.service 
× razerdaemon.service - Razer laptop control daemon
     Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2021-05-20 09:51:09 EDT; 2min 42s ago
    Process: 439 ExecStart=/usr/share/razercontrol/daemon (code=exited, status=1/FAILURE)
   Main PID: 439 (code=exited, status=1/FAILURE)
        CPU: 4ms

May 20 09:51:02 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:03 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:04 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:05 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:06 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:07 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:08 archlinux daemon[439]: Waiting for sysfs to be ready
May 20 09:51:09 archlinux daemon[439]: Timed out waiting for sysfs after a minute!
May 20 09:51:09 archlinux systemd[1]: razerdaemon.service: Main process exited, code=exited, status=1/FAILURE
May 20 09:51:09 archlinux systemd[1]: razerdaemon.service: Failed with result 'exit-code'.

Edit: after re-running mkinitcpio I get the following:

[I] ➜ sudo systemctl status razerdaemon.service
● razerdaemon.service - Razer laptop control daemon
     Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2021-05-20 09:56:58 EDT; 24s ago
   Main PID: 399 (daemon)
      Tasks: 1 (limit: 18965)
     Memory: 1.1M
        CPU: 3ms
     CGroup: /system.slice/razerdaemon.service
             └─399 /usr/share/razercontrol/daemon

May 20 09:57:13 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:14 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:15 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:16 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:17 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:18 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:19 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:20 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:21 archlinux daemon[399]: Waiting for sysfs to be ready
May 20 09:57:22 archlinux daemon[399]: Waiting for sysfs to be ready

Which seems to be related to #45

@lexizz
Copy link

lexizz commented Aug 16, 2021

Same issue with Blade Stealth 13 (Late 2020). I haven't openrazer installed.

@theboringkid
Copy link

I fixed it by uninstalling it, and then compiling it myself (See issue #56 for a guide, it really isn't complicated, but you need to replace sudo update-initramfs -u with sudo mkinitcpio if you are running Arch (or maybe on other Distros as well, but I only know that you need to replace it in arch since I am using Arch)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@creotiv @phelps-sg @lexizz @jarbus @QuiiBz @mike-lloyd03 @CasperBruning @theboringkid