mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #1113] Connection refused #952
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#952
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @justablob on GitHub (Apr 7, 2021).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1113
Describe the bug
When running any command, nbfc just returns
Connection refused. Tried with both sudo and no sudo. nbfc.service is definitely enabled and up, sinceservice nbfc statusshows it as running. Restarting the service with systemd does nothing, but starting the service manually withnbfcservice.shdoes, and after that, nbfc works like it should. What's weird is that if you kill nbfc usingsudo killall mono, then restart the systemd service, nbfc will keep working normally.To Reproduce
Connection refusedExpected behavior
It should work 🤷🏻♂️
System information
Lenovo ThinkPad T490s
Ubuntu 20.04.02 LTS
NBFC 1.6.3.0
Mono 6.12.0.122
Log: https://hatebin.com/dvepjwtwpq
Systemd log: https://hatebin.com/upndtobjqv
Additional context
I'm using a slightly modified version of the T430s config, but this isn't the problem because the other ThinkPad configs result in the same issue.
There's been a few issues about the same thing but none of the solutions there fixed anything.
@mohamadali-halwani commented on GitHub (Apr 22, 2021):
Can you show me the output of
ls -la /opt/nbfc?@justablob commented on GitHub (May 1, 2021):
Weirdly, since I updated to 21.04, I can't reproduce the issue myself anymore. Close?
@BachoSeven commented on GitHub (May 1, 2021):
Sure, feel free to close the issue if it's not an issue anymore.