starred/nbfc-hirschmann
1
0
Fork 0
mirror of https://github.com/hirschmann/nbfc.git synced 2026-04-25 16:45:53 +03:00
Code Issues 90 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #163] How can I load easily a config after each reboot without write the command again under Linux ? #150

New issue
Closed
opened 2026-02-26 00:31:52 +03:00 by kerem · 22 comments
kerem commented 2026-02-26 00:31:52 +03:00
Owner
Copy link

Originally created by @kevincaradant on GitHub (Jan 4, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/163

Hi

When I reboot the computer, my config seems to be lost

Is it a way to force it to works after a reboot ?

I'm under Ubuntu 16.10 64 bits

At the begin, it works and some minutes after, the fan starts again and nbfc.exe status give me : connection failed. The service seems to be stopped and I have to start it again at the hand ...
Any idea ?

Thank you

This is the problem:
sudo service nbfc status
image

sudo service nbfc start
sudo service nbfc status

image

Originally created by @kevincaradant on GitHub (Jan 4, 2017). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/163 Hi When I reboot the computer, my config seems to be lost Is it a way to force it to works after a reboot ? I'm under Ubuntu 16.10 64 bits At the begin, it works and some minutes after, the fan starts again and nbfc.exe status give me : `connection failed.` The service seems to be stopped and I have to start it again at the hand ... Any idea ? Thank you This is the problem: `sudo service nbfc status` ![image](https://cloud.githubusercontent.com/assets/6093175/21689193/e41cae3e-d36f-11e6-8469-43874c62e728.png) ``` sudo service nbfc start sudo service nbfc status ``` ![image](https://cloud.githubusercontent.com/assets/6093175/21689275/2440798c-d370-11e6-8272-a5d0432159d5.png)
kerem 2026-02-26 00:31:52 +03:00
  • closed this issue
  • added the
    question
         label
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 6, 2017):

I can't reproduce this error. Does it occur after every reboot?

Until this problem is solved, you can try to fix it by configuring the service to restart on failure.
Add this line to the [Service] section of the nbfc.service file:
Restart=on-failure

<!-- gh-comment-id:270992604 --> @hirschmann commented on GitHub (Jan 6, 2017): I can't reproduce this error. Does it occur after every reboot? Until this problem is solved, you can try to fix it by configuring the service to restart on failure. Add this line to the [Service] section of the _nbfc.service_ file: `Restart=on-failure`
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 6, 2017):

Yes, it happens after each reboot (4 reboots) , (4 fails). I created a workaround with a new service which call my sh script and inside it I added some commands and I added the command service nbfc start in more. That's seems to work even if it's not really good as answer but in my case it's not a problem.

If you need more information, tell me where I have to look because I don't know where to search ')

<!-- gh-comment-id:271004351 --> @kevincaradant commented on GitHub (Jan 6, 2017): Yes, it happens after each reboot (4 reboots) , (4 fails). I created a workaround with a new service which call my sh script and inside it I added some commands and I added the command `service nbfc start` in more. That's seems to work even if it's not really good as answer but in my case it's not a problem. If you need more information, tell me where I have to look because I don't know where to search ')
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 25, 2017):

I fixed the error from your screenshot with 13d7c44e11
You can build NBFC from the latest sources if you want to test it.

<!-- gh-comment-id:275170021 --> @hirschmann commented on GitHub (Jan 25, 2017): I fixed the error from your screenshot with 13d7c44e11b3743c962bf2b3275cdd7374efb51f You can build NBFC from the latest sources if you want to test it.
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 25, 2017):

Ah perfect, In fact NBFC has never work correctly with me before because I had only 0 or 100% fanspeed ( critical temp). The different steps was ignored :/

Now everything works without any workaround

Thank you :)

<!-- gh-comment-id:275187486 --> @kevincaradant commented on GitHub (Jan 25, 2017): Ah perfect, In fact NBFC has never work correctly with me before because I had only 0 or 100% fanspeed ( critical temp). The different steps was ignored :/ Now everything works without any workaround Thank you :)
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 26, 2017):

Sorry my mistake. Today the bug is here again.

CF:
image

image

I don't know why today :(

<!-- gh-comment-id:275439535 --> @kevincaradant commented on GitHub (Jan 26, 2017): Sorry my mistake. Today the bug is here again. CF: ![image](https://cloud.githubusercontent.com/assets/6093175/22340719/b45dd01c-e3ee-11e6-924d-aee59f374b89.png) ![image](https://cloud.githubusercontent.com/assets/6093175/22340766/d72eb78c-e3ee-11e6-8d47-51808d2f9772.png) I don't know why today :(
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 26, 2017):

Looks like NBFC times out when trying to access either the EC or the temperature sensors.
Have you tried the workaround I posted in https://github.com/hirschmann/nbfc/issues/163#issuecomment-270992604 yet?

<!-- gh-comment-id:275499176 --> @hirschmann commented on GitHub (Jan 26, 2017): Looks like NBFC times out when trying to access either the EC or the temperature sensors. Have you tried the workaround I posted in https://github.com/hirschmann/nbfc/issues/163#issuecomment-270992604 yet?
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 26, 2017):

Indeed, I forgot your workaround after the new installation.
It works, I can see the service failed and just after restart itself and become "activated"
It's like if the service wants to start before to have the OS ready.

<!-- gh-comment-id:275521834 --> @kevincaradant commented on GitHub (Jan 26, 2017): Indeed, I forgot your workaround after the new installation. It works, I can see the service failed and just after restart itself and become "activated" It's like if the service wants to start before to have the OS ready.
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 27, 2017):

I think it's more like the service tries to start before the hardware (probably the EC) is ready.
The solution to this problem is to retry starting the service, so I will implement the solution from #163

Thanks for helping me to solve this problem :)

<!-- gh-comment-id:275703219 --> @hirschmann commented on GitHub (Jan 27, 2017): I think it's more like the service tries to start before the hardware (probably the EC) is ready. The solution to this problem is to retry starting the service, so I will implement the solution from #163 Thanks for helping me to solve this problem :)
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 27, 2017):

You're welcome :). It's perfect and very very useful this NBFC. I let you to close this issue when you think it's necessary

<!-- gh-comment-id:275705085 --> @kevincaradant commented on GitHub (Jan 27, 2017): You're welcome :). It's perfect and very very useful this NBFC. I let you to close this issue when you think it's necessary
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@jpick commented on GitHub (Jan 27, 2017):

Hello hirschmann,
hello kevincaradant,

I think I have a similar problem. I cannot start the nbfc service under my linux distro.
I have an Asus UX410 running under Fedora 25.

I've build nbfc like that :

$ git clone --depth 1 https://github.com/hirschmann/nbfc.git
$ mozroots --import --sync
$ nuget restore
$ xbuild /t:Build /p:Configuration=ReleaseLinux NoteBookFanControl.sln

$ su -
# cd /opt
# cp -r /home/jp/nbfc/Linux/bin/ReleaseLinux nbfc
# cp /home/jp/nbfc/Linux/nbfc*.service /etc/systemd/system/
# cp /home/jp/Asus\ Zenbook\ UX410UAK.xml nbfc/Configs/

But I cannot start the service !
I get the same error message as kevincaradant :

# systemctl start nbfc
# systemctl status nbfc
● nbfc.service - NoteBook FanControl service
   Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since ven. 2017-01-27 18:46:57 CET; 1s ago
  Process: 7250 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS)
 Main PID: 7253 (code=exited, status=1/FAILURE)

janv. 27 18:46:56 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service...
janv. 27 18:46:56 asus.intra.pick.fr systemd[1]: nbfc.service: PID file /run/nbfc.pid not readable (yet?) after start: No such file or directory
janv. 27 18:46:56 asus.intra.pick.fr systemd[1]: Started NoteBook FanControl service.
janv. 27 18:46:57 asus.intra.pick.fr mono[7253]: NbfcService: Exception has been thrown by the target of an invocation.
janv. 27 18:46:57 asus.intra.pick.fr mono[7253]: NbfcService: Object reference not set to an instance of an object
janv. 27 18:46:57 asus.intra.pick.fr systemd[1]: nbfc.service: Main process exited, code=exited, status=1/FAILURE
janv. 27 18:46:57 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state.
janv. 27 18:46:57 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'exit-code'.

Any idea ?
What is the meaning of the message "NbfcService: Exception has been thrown by the target of an invocation" ?

Thank you,

<!-- gh-comment-id:275729257 --> @jpick commented on GitHub (Jan 27, 2017): Hello hirschmann, hello kevincaradant, I think I have a similar problem. I cannot start the nbfc service under my linux distro. I have an Asus UX410 running under Fedora 25. I've build nbfc like that : ``` $ git clone --depth 1 https://github.com/hirschmann/nbfc.git $ mozroots --import --sync $ nuget restore $ xbuild /t:Build /p:Configuration=ReleaseLinux NoteBookFanControl.sln $ su - # cd /opt # cp -r /home/jp/nbfc/Linux/bin/ReleaseLinux nbfc # cp /home/jp/nbfc/Linux/nbfc*.service /etc/systemd/system/ # cp /home/jp/Asus\ Zenbook\ UX410UAK.xml nbfc/Configs/ ``` But I cannot start the service ! I get the same error message as kevincaradant : ``` # systemctl start nbfc # systemctl status nbfc ● nbfc.service - NoteBook FanControl service Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since ven. 2017-01-27 18:46:57 CET; 1s ago Process: 7250 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS) Main PID: 7253 (code=exited, status=1/FAILURE) janv. 27 18:46:56 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service... janv. 27 18:46:56 asus.intra.pick.fr systemd[1]: nbfc.service: PID file /run/nbfc.pid not readable (yet?) after start: No such file or directory janv. 27 18:46:56 asus.intra.pick.fr systemd[1]: Started NoteBook FanControl service. janv. 27 18:46:57 asus.intra.pick.fr mono[7253]: NbfcService: Exception has been thrown by the target of an invocation. janv. 27 18:46:57 asus.intra.pick.fr mono[7253]: NbfcService: Object reference not set to an instance of an object janv. 27 18:46:57 asus.intra.pick.fr systemd[1]: nbfc.service: Main process exited, code=exited, status=1/FAILURE janv. 27 18:46:57 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state. janv. 27 18:46:57 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'exit-code'. ``` Any idea ? What is the meaning of the message "NbfcService: Exception has been thrown by the target of an invocation" ? Thank you,
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 27, 2017):

Hi

Interesting, we have the same computer.
I don't know what this means. As mentioned before, it's maybe the hardware which is not completely ready when nbfc service wants to start but a good workaround is simply to do:
https://github.com/hirschmann/nbfc/issues/163#issuecomment-270992604

So add:
Restart=on-failure

This line in the service file located in
/etc/systemd/system/nbfc.service

And you have to get this:

[Unit]
Description=NoteBook FanControl service

[Service]
ExecStart=/opt/nbfc/start-nbfcservice.sh
Type=forking
Restart=on-failure
PIDFile=/run/nbfc.pid
TimeoutStopSec=20

[Install]
WantedBy=multi-user.target

Let me know if the suggested fix works as expected.
When the service failed to start, it will try again few seconds after to fail and that works in my case

<!-- gh-comment-id:275731432 --> @kevincaradant commented on GitHub (Jan 27, 2017): Hi Interesting, we have the same computer. I don't know what this means. As mentioned before, it's maybe the hardware which is not completely ready when nbfc service wants to start but a good workaround is simply to do: https://github.com/hirschmann/nbfc/issues/163#issuecomment-270992604 So add: `Restart=on-failure` This line in the service file located in `/etc/systemd/system/nbfc.service` And you have to get this: ``` [Unit] Description=NoteBook FanControl service [Service] ExecStart=/opt/nbfc/start-nbfcservice.sh Type=forking Restart=on-failure PIDFile=/run/nbfc.pid TimeoutStopSec=20 [Install] WantedBy=multi-user.target ``` Let me know if the suggested fix works as expected. When the service failed to start, it will try again few seconds after to fail and that works in my case
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 27, 2017):

@jpick
Thats's not the same error. You haven't selected a config, that's why the service refuses to start.
Also, you haven't enabled the service, which means it will not start automatically.

See https://github.com/hirschmann/nbfc/wiki/First-steps, steps 3 and 5.

<!-- gh-comment-id:275731993 --> @hirschmann commented on GitHub (Jan 27, 2017): @jpick Thats's not the same error. You haven't selected a config, that's why the service refuses to start. Also, you haven't enabled the service, which means it will not start automatically. See https://github.com/hirschmann/nbfc/wiki/First-steps, steps 3 and 5.
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 27, 2017):

Ok so my bad, it's not a problem of timeout. forget my answer @jpick :)

<!-- gh-comment-id:275732156 --> @kevincaradant commented on GitHub (Jan 27, 2017): Ok so my bad, it's not a problem of timeout. forget my answer @jpick :)
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@jpick commented on GitHub (Jan 27, 2017):

I just try to add "Restart=on-failure" but without succes.
The nbfc.service start :

# systemctl start nbfc
# systemctl status nbfc
● nbfc.service - NoteBook FanControl service
   Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled)
   Active: active (running) since ven. 2017-01-27 19:09:07 CET; 83ms ago
  Process: 7716 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS)
 Main PID: 7719 (mono)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/nbfc.service
           └─7719 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -m:NbfcService /opt/nbfc/NbfcService.exe -l:/run/nbfc.pid

janv. 27 19:09:07 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service...
janv. 27 19:09:07 asus.intra.pick.fr systemd[1]: nbfc.service: PID file /run/nbfc.pid not readable (yet?) after start: No such file or directory
janv. 27 19:09:07 asus.intra.pick.fr systemd[1]: Started NoteBook FanControl service.

but 5 seconds after, it fail with another error message :

# systemctl status nbfc
● nbfc.service - NoteBook FanControl service
   Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit-hit) since ven. 2017-01-27 19:09:08 CET; 1s ago
  Process: 7716 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS)
 Main PID: 7719 (code=exited, status=1/FAILURE)

janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'exit-code'.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Service hold-off time over, scheduling restart.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: Stopped NoteBook FanControl service.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Start request repeated too quickly.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: Failed to start NoteBook FanControl service.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state.
janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'start-limit-hit'.
<!-- gh-comment-id:275734492 --> @jpick commented on GitHub (Jan 27, 2017): I just try to add "Restart=on-failure" but without succes. The nbfc.service start : ``` # systemctl start nbfc # systemctl status nbfc ● nbfc.service - NoteBook FanControl service Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled) Active: active (running) since ven. 2017-01-27 19:09:07 CET; 83ms ago Process: 7716 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS) Main PID: 7719 (mono) Tasks: 3 (limit: 4915) CGroup: /system.slice/nbfc.service └─7719 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -m:NbfcService /opt/nbfc/NbfcService.exe -l:/run/nbfc.pid janv. 27 19:09:07 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service... janv. 27 19:09:07 asus.intra.pick.fr systemd[1]: nbfc.service: PID file /run/nbfc.pid not readable (yet?) after start: No such file or directory janv. 27 19:09:07 asus.intra.pick.fr systemd[1]: Started NoteBook FanControl service. ``` but 5 seconds after, it fail with another error message : ``` # systemctl status nbfc ● nbfc.service - NoteBook FanControl service Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit-hit) since ven. 2017-01-27 19:09:08 CET; 1s ago Process: 7716 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS) Main PID: 7719 (code=exited, status=1/FAILURE) janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'exit-code'. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Service hold-off time over, scheduling restart. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: Stopped NoteBook FanControl service. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Start request repeated too quickly. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: Failed to start NoteBook FanControl service. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state. janv. 27 19:09:08 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'start-limit-hit'. ```
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 27, 2017):

@jpick , Your initial problem isn't the same as me.
Do you have follow the link from here: https://github.com/hirschmann/nbfc/issues/163#issuecomment-275731993 ?

<!-- gh-comment-id:275735604 --> @kevincaradant commented on GitHub (Jan 27, 2017): @jpick , Your initial problem isn't the same as me. Do you have follow the link from here: https://github.com/hirschmann/nbfc/issues/163#issuecomment-275731993 ?
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@jpick commented on GitHub (Jan 27, 2017):

@hirschmann, I forget to mention I had enabled the service.

Even if I reenable the service :

# systemctl enable nbfc --now
# mono nbfc.exe config -a "Asus Zenbook UX410UAK"
Connection refused

I still get the same error :

# systemctl start nbfc
[root@asus nbfc]# systemctl status nbfc
● nbfc.service - NoteBook FanControl service
   Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled)
   Active: active (running) since ven. 2017-01-27 19:21:22 CET; 16ms ago
  Process: 7903 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS)
 Main PID: 7906 (mono)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/nbfc.service
           └─7906 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -m:NbfcService /opt/nbfc/NbfcService.exe -l:/run/nbfc.pid

janv. 27 19:21:22 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service...
janv. 27 19:21:22 asus.intra.pick.fr systemd[1]: nbfc.service: PID file /run/nbfc.pid not readable (yet?) after start: No such file or directory
janv. 27 19:21:22 asus.intra.pick.fr systemd[1]: Started NoteBook FanControl service.

# systemctl status nbfc
● nbfc.service - NoteBook FanControl service
   Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled)
   Active: activating (start) since ven. 2017-01-27 19:21:23 CET; 1ms ago
 Main PID: 7916 (code=exited, status=1/FAILURE); Control PID: 7923 (start-nbfcservi)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/nbfc.service
           └─7923 /bin/bash /opt/nbfc/start-nbfcservice.sh

janv. 27 19:21:23 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service...

# systemctl status nbfc
● nbfc.service - NoteBook FanControl service
   Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit-hit) since ven. 2017-01-27 19:21:24 CET; 3s ago
  Process: 7923 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS)
 Main PID: 7926 (code=exited, status=1/FAILURE)

janv. 27 19:21:23 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'exit-code'.
janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Service hold-off time over, scheduling restart.
janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: Stopped NoteBook FanControl service.
janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Start request repeated too quickly.
janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: Failed to start NoteBook FanControl service.
janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state.
janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'start-limit-hit'.
<!-- gh-comment-id:275736367 --> @jpick commented on GitHub (Jan 27, 2017): @hirschmann, I forget to mention I had enabled the service. Even if I reenable the service : ``` # systemctl enable nbfc --now # mono nbfc.exe config -a "Asus Zenbook UX410UAK" Connection refused ``` I still get the same error : ``` # systemctl start nbfc [root@asus nbfc]# systemctl status nbfc ● nbfc.service - NoteBook FanControl service Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled) Active: active (running) since ven. 2017-01-27 19:21:22 CET; 16ms ago Process: 7903 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS) Main PID: 7906 (mono) Tasks: 3 (limit: 4915) CGroup: /system.slice/nbfc.service └─7906 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -m:NbfcService /opt/nbfc/NbfcService.exe -l:/run/nbfc.pid janv. 27 19:21:22 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service... janv. 27 19:21:22 asus.intra.pick.fr systemd[1]: nbfc.service: PID file /run/nbfc.pid not readable (yet?) after start: No such file or directory janv. 27 19:21:22 asus.intra.pick.fr systemd[1]: Started NoteBook FanControl service. # systemctl status nbfc ● nbfc.service - NoteBook FanControl service Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled) Active: activating (start) since ven. 2017-01-27 19:21:23 CET; 1ms ago Main PID: 7916 (code=exited, status=1/FAILURE); Control PID: 7923 (start-nbfcservi) Tasks: 0 (limit: 4915) CGroup: /system.slice/nbfc.service └─7923 /bin/bash /opt/nbfc/start-nbfcservice.sh janv. 27 19:21:23 asus.intra.pick.fr systemd[1]: Starting NoteBook FanControl service... # systemctl status nbfc ● nbfc.service - NoteBook FanControl service Loaded: loaded (/etc/systemd/system/nbfc.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit-hit) since ven. 2017-01-27 19:21:24 CET; 3s ago Process: 7923 ExecStart=/opt/nbfc/start-nbfcservice.sh (code=exited, status=0/SUCCESS) Main PID: 7926 (code=exited, status=1/FAILURE) janv. 27 19:21:23 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'exit-code'. janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Service hold-off time over, scheduling restart. janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: Stopped NoteBook FanControl service. janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Start request repeated too quickly. janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: Failed to start NoteBook FanControl service. janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Unit entered failed state. janv. 27 19:21:24 asus.intra.pick.fr systemd[1]: nbfc.service: Failed with result 'start-limit-hit'. ```
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@jpick commented on GitHub (Jan 27, 2017):

Oups, I found my issue. There was a typo in my .xml configuration file !

$ mono /opt/nbfc/nbfc.exe status
Service enabled		: True
Read-only		: False
Selected config name	: Asus Zenbook UX410UAK
Temperature		: 35

Fan display name	: Fan #1
Auto control enabled	: True
Critical mode enabled	: False
Current fan speed	: 0.00
Target fan speed	: 0.00
Fan speed steps		: 10

Sorry again for the confusion.

<!-- gh-comment-id:275763923 --> @jpick commented on GitHub (Jan 27, 2017): Oups, I found my issue. There was a typo in my .xml configuration file ! ``` $ mono /opt/nbfc/nbfc.exe status Service enabled : True Read-only : False Selected config name : Asus Zenbook UX410UAK Temperature : 35 Fan display name : Fan #1 Auto control enabled : True Critical mode enabled : False Current fan speed : 0.00 Target fan speed : 0.00 Fan speed steps : 10 ``` Sorry again for the confusion.
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@jpick commented on GitHub (Jan 27, 2017):

@hirschmann : I suggest to add in the First steps wiki page a mention of the location of the main configuration file /etc/NbfcService/NbfcServiceSettings.xml.

It takes me two hours to understand (thanks to strace) that my mono-service was loading the wrong Configs/.xml file. :-)

<!-- gh-comment-id:275775376 --> @jpick commented on GitHub (Jan 27, 2017): @hirschmann : I suggest to add in the [First steps](https://github.com/hirschmann/nbfc/wiki/First-steps) wiki page a mention of the location of the main configuration file `/etc/NbfcService/NbfcServiceSettings.xml`. It takes me two hours to understand (thanks to strace) that my mono-service was loading the wrong Configs/.xml file. :-)
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 28, 2017):

Good idea. Maybe it's somewhat exaggerated, but I have created an overview of important files and dirs, see https://github.com/hirschmann/nbfc/wiki/Files-and-directories-overview
:)

<!-- gh-comment-id:275849319 --> @hirschmann commented on GitHub (Jan 28, 2017): Good idea. Maybe it's somewhat exaggerated, but I have created an overview of important files and dirs, see https://github.com/hirschmann/nbfc/wiki/Files-and-directories-overview :)
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@kevincaradant commented on GitHub (Jan 28, 2017):

No it's perfect. I lost time to get every files as you mentioned in the new wiki page. So it's really a good idea :)

<!-- gh-comment-id:275850226 --> @kevincaradant commented on GitHub (Jan 28, 2017): No it's perfect. I lost time to get every files as you mentioned in the new wiki page. So it's really a good idea :)
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@jpick commented on GitHub (Jan 28, 2017):

Thank you hirschmann !

<!-- gh-comment-id:275870494 --> @jpick commented on GitHub (Jan 28, 2017): Thank you hirschmann !
kerem commented 2026-02-26 00:31:52 +03:00
Author
Owner
Copy link

@hirschmann commented on GitHub (Jan 31, 2017):

Enabled restart on failure: 47e6bcdd53

<!-- gh-comment-id:276523444 --> @hirschmann commented on GitHub (Jan 31, 2017): Enabled restart on failure: 47e6bcdd5338bf33e534044b82baaf5173cdf6c5
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
stable
beta
1.6.3
1.6-beta2
1.6-beta1
1.5.3-beta
1.5.0
1.4.5-beta
1.4.4-beta
1.4.2
1.3.4
1.1.1.19
1.1.0.17
1.0.0.0
Labels
Clear labels   
Stale

   
bug

   
config

   
discussion

   
duplicate

   
enhancement

   
experimental

   
feature

   
help-wanted

   
info

   
invalid

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
up-for-grabs

   
wontfix
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nbfc-hirschmann#150
No description provided.