Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open PID file /run/lightningd/lightningd.pid #628

Closed
n-e-t-d-i-v-e-r opened this issue Dec 11, 2024 · 3 comments
Closed

Can't open PID file /run/lightningd/lightningd.pid #628

n-e-t-d-i-v-e-r opened this issue Dec 11, 2024 · 3 comments

Comments

@n-e-t-d-i-v-e-r
Copy link

n-e-t-d-i-v-e-r commented Dec 11, 2024

Not sure if I’m right here, but since Monday couldn’t start up CLN on my node. Getting following error:

● lightningd.service - c-lightning daemon on mainnet
     Loaded: loaded (/etc/systemd/system/lightningd.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-12-11 11:23:36 GMT; 445ms ago
    Process: 254827 ExecStartPre=/home/admin/config.scripts/cl.check.sh prestart mainnet (code=exited, status=0/SUCCESS)
    Process: 254844 ExecStartPost=/home/admin/config.scripts/cl.check.sh poststart mainnet (code=exited, status=0/SUCCESS)
   Main PID: 254845
      Tasks: 2 (limit: 9275)
     Memory: 127.3M
        CPU: 4.678s
     CGroup: /system.slice/lightningd.service
             ├─254968 python3 /usr/local/libexec/c-lightning/plugins/clnrest/clnrest.py
             └─254970 python3 /home/bitcoin/cl-plugins-available/plugins/backup/backup.py

Dec 11 11:23:29 raspberrypi systemd[1]: lightningd.service: Can't open PID file /run/lightningd/lightningd.pid (yet?) after start-post: No such file or directory
Dec 11 11:23:36 raspberrypi systemd[1]: lightningd.service: Supervising process 254845 which is not our child. We'll most likely not notice when it exits.
Dec 11 11:23:36 raspberrypi systemd[1]: Started lightningd.service - c-lightning daemon on mainnet.
Dec 11 11:23:36 raspberrypi sh[254845]: Plugin '/home/bitcoin/cl-plugins-available/plugins/backup/backup.py' returned an invalid response to the db_write hook: {"jsonrpc": "2.0", "id": "cln:db_write#18", "error": {"code": -32600, "message": "Error while processing db_write: [Errno 28] No space left on device", "traceback": "Traceback (most recen>
Dec 11 11:23:36 raspberrypi sh[254970]: object address  : 0x7f8a4d5540
Dec 11 11:23:36 raspberrypi sh[254970]: object refcount : 2
Dec 11 11:23:36 raspberrypi sh[254970]: object type     : 0xa10b00
Dec 11 11:23:36 raspberrypi sh[254970]: object type name: BrokenPipeError
Dec 11 11:23:36 raspberrypi sh[254970]: object repr     : BrokenPipeError(32, 'Broken pipe')
Dec 11 11:23:36 raspberrypi sh[254970]: lost sys.stderr

Is there a chance to fix this, without loosing my funds?

@n-e-t-d-i-v-e-r
Copy link
Author

n-e-t-d-i-v-e-r commented Dec 11, 2024

is the possible problem because I deleted file /run/lightningd/lightningd.pid , because I read it as a hint to fix the issue? If yes is there a way to «undel» this? or place a new/clean lightningd.pid somewhere?

and if I’ll make a backup, I’ll get this:

/home/admin/99clMenu.sh: line 4: echo: write error: No space left on device /home/admin/config.scripts/cl.hsmtool.sh: line 40: echo: write error: No space left on device /home/admin/config.scripts/cl.hsmtool.sh: line 368: echo: write error: No space left on device /home/admin/config.scripts/cl.hsmtool.sh: line 368: echo: write error: No space left on device /home/admin/config.scripts/cl.hsmtool.sh: line 368: echo: write error: No space left on device /home/admin/config.scripts/cl.hsmtool.sh: line 368: echo: write error: No space left on device /home/admin/config.scripts/cl.hsmtool.sh: line 368: echo: write error: No space left on device

@cdecker
Copy link
Contributor

cdecker commented Dec 16, 2024

The node is exiting because the backup plugin is configured as an important plugin, but it is exiting too because your disk is full. Please either compact the backup or create a new one. The Pid file is not needed (that's systemd complaining, not CLN as far as I can see)

@chrisguida
Copy link
Collaborator

@n-e-t-d-i-v-e-r closing this, feel free to reopen if you still need help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants