Failed to mount flist due to invalid digit in pid file

[scottyeager]

A user reported seeing the following error regarding their VM which went offline (node 6656):

"contract_id": 1438139,
...
"message": "failed to mount flist: 6629-1438139-vm1: ro mount of flist fail ed: exit status 1",

I found the following upon querying node logs:

2025-11-20 05:32:54.617	[+] provisiond: 2025-11-20T13:32:54Z error failed to deploy workload error="failed to mount flist: 6629-1438139-vm1: ro mount of flist failed: exit status 1" deployment=1438139 name=vm1 twin=6629 type=zmachine
2025-11-20 05:32:54.592	[+] networkd: 2025-11-20T13:32:54Z info Removing tap interface tap-name=6BbBJY9pevnrY
2025-11-20 05:32:54.567	[+] networkd: 2025-11-20T13:32:54Z info Removing tap interface tap-name=AnWWYi6j5DwUv
2025-11-20 05:32:54.546	[+] networkd: 2025-11-20T13:32:54Z info Removing tap interface tap-name=MDvzKHTK1vizU
2025-11-20 05:32:54.545	[+] storaged: 2025-11-20T13:32:54Z warn failed to delete qgroup error="stderr: ERROR: unable to destroy quota group: Device or resource busy\n: exit status 1" group-id=0/7203
2025-11-20 05:32:54.513	[+] storaged: 2025-11-20T13:32:54Z info Deleting volume rootfs:6629-1438139-vm1
2025-11-20 05:32:54.487	[+] flistd: 2025-11-20T13:32:54Z error failed to start 0-fs daemon error="exit status 1" out="2025-11-20 13:32:54,486 ERROR [rfs] failed to parse pid_file contents 40290\n: invalid digit found in string\nfailed to mount in under 5 seconds, please check logs for more information\n" storage= url=https://hub.grid.tf/scott.3bot/scottyeager-nextcloud-grid-latest.flist

I'm not sure what the source of the issue might be, but this is fairly serious because it can prevent a VM from booting up again after node power loss.

[scottyeager]

There's another instance in the same log range I linked above, for contract id 1438147.

[ashraffouda]

the invalid digit error is from rfs I will handle that in rfs. but this happened because that mountpoint was not ready for some reason. now I'm checking this too to see if it is an issue or not

[scottyeager]

I found two more instances by searching across the node logs.

Node 1327:

2025-12-01 17:14:18.902	
[+] flistd: 2025-12-01T17:14:18Z error failed to start 0-fs daemon error="exit status 1" out="2025-12-01 17:14:18,901 ERROR [rfs] failed to parse pid_file contents 2421\n: invalid digit found in string\nfailed to mount in under 5 seconds, please check logs for more information\n" storage= url=https://hub.threefold.me/tf-autobuilder/traefik-2.9.9.flist

Node 989:

2025-12-01 17:14:04.150	
[+] flistd: 2025-12-01T17:14:04Z error failed to start 0-fs daemon error="exit status 1" out="2025-12-01 17:14:04,149 ERROR [rfs] failed to parse pid_file contents 2446\n: invalid digit found in string\nfailed to mount in under 5 seconds, please check logs for more information\n" storage= url=https://hub.threefold.me/tf-autobuilder/traefik-2.9.9.flist