Page MenuHomePhabricator

[Bug] PAWS server not starting
Closed, ResolvedPublic

Description

What happened?

I am unable to start the PAWS server for my DreamRimmer bot. The event logs are as follows:

Server requested
2025-07-26T13:16:22.704957Z [Normal] Successfully assigned prod/jupyter--44ream-52immer-20bot to paws-127b-rpchztfjt2jb-node-1
2025-07-26T13:18:25Z [Warning] Unable to attach or mount volumes: unmounted volumes=[home], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
Spawn failed: Timeout

What should have happened?

The server should start normally.

Event Timeline

I am having the exact same problem. I attach my logs too. I noticed it happening from last night UTC+0

Server requested
2025-07-26T13:43:47.132809Z [Normal] Successfully assigned prod/jupyter--43easeless-20-57atcher to paws-127b-rpchztfjt2jb-node-1
2025-07-26T13:45:50Z [Warning] Unable to attach or mount volumes: unmounted volumes=[home], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition

I also face this very same problem though.

Server requested
2025-07-28T05:44:09.669446Z [Normal] Successfully assigned prod/jupyter--4fctra-42ot to paws-127b-rpchztfjt2jb-node-1
2025-07-28T05:46:12Z [Warning] Unable to attach or mount volumes: unmounted volumes=[home], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
Spawn failed: Timeout

Pppery raised the priority of this task from Medium to Needs Triage.Jul 28 2025, 5:59 AM

Priority should generally not be set unless you or your team plan to work on fixing the task. See https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities

taavi subscribed.

It seems like there is an individual PAWS worker (paws-127b-rpchztfjt2jb-node-1) that was having trouble talking to the NFS server hosting user home directories. I'm still looking into why it was failing there, but in the meantime I've taken it out of service which should hide the error from you.

Worker fixed by a reboot. Will investigate more if this happens again.

Please create a new task for the unrelated issue rather than reusing a months-old one.