You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Using user:group juicefs:juicefs to start gateway. Get error trying to create lock. The service starts, but continues to complain that it cannot create the lock file. Which may lead to data corruption?
Dec 01 13:57:44 sgp1 systemd[1]: Started JuiceFS S3 Gateway.
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.462108 juicefs[2545041] <INFO>: Meta address: redis://sgp1.jackal-godzilla.ts.net:6379 [interface.go:504]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.468388 juicefs[2545041] <INFO>: Ping redis latency: 537.065µs [redis.go:3515]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.471914 juicefs[2545041] <INFO>: Data use s3://sedlund-jfs/sedlund-jfs/(encrypted) [gateway.go:230]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.472696 juicefs[2545041] <INFO>: Disk cache (/var/cache/juicefs/5cf44ea1-3e99-4ead-af09-029d332c28f5/): capacity (100 GiB), free ratio 10%, used ratio - [space 59.9%, inode NaN%], max pending pages 15 [disk_cache.go:144]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.476417 juicefs[2545041] <INFO>: Create session 321 OK with version: 1.2.1+2024-08-30.cd871d19ba57 [base.go:398]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.477769 juicefs[2545041] <INFO>: Prometheus metrics listening on 127.0.0.1:9567 [mount.go:135]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.595852 juicefs[2545041] <ERROR>: failed to open the file to be locked: .minio.sys/config_lock error permission denied [gateway.go:1300]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.595969 juicefs[2545041] <WARNING>: failed to get lock [gateway.go:1211]
Dec 01 13:57:44 sgp1 juicefs[2545041]: Endpoint: http://sgp1.jackal-godzilla.ts.net:9000
Dec 01 13:57:44 sgp1 juicefs[2545041]: Browser Access:
Dec 01 13:57:44 sgp1 juicefs[2545041]: http://sgp1.jackal-godzilla.ts.net:9000
Dec 01 13:57:44 sgp1 juicefs[2545041]: Object API (Amazon S3 compatible):
Dec 01 13:57:44 sgp1 juicefs[2545041]: Go: https://docs.min.io/docs/golang-client-quickstart-guide
Dec 01 13:57:44 sgp1 juicefs[2545041]: Java: https://docs.min.io/docs/java-client-quickstart-guide
Dec 01 13:57:44 sgp1 juicefs[2545041]: Python: https://docs.min.io/docs/python-client-quickstart-guide
Dec 01 13:57:44 sgp1 juicefs[2545041]: JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide
Dec 01 13:57:44 sgp1 juicefs[2545041]: .NET: https://docs.min.io/docs/dotnet-client-quickstart-guide
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.609699 juicefs[2545041] <ERROR>: failed to open the file to be locked: .minio.sys/config_lock error permission denied [gateway.go:1300]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.609918 juicefs[2545041] <ERROR>: failed to open the file to be locked: .minio.sys/config_lock error permission denied [gateway.go:1300]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.610005 juicefs[2545041] <WARNING>: failed to get lock [gateway.go:1211]
Dec 01 13:57:44 sgp1 juicefs[2545041]: 2024/12/01 06:57:44.610860 juicefs[2545041] <WARNING>: failed to get lock [gateway.go:1211]
Dec 01 13:57:44 sgp1 juicefs[2545041]: IAM initialization complete
Dec 01 14:02:44 sgp1 juicefs[2545041]: 2024/12/01 07:02:44.613336 juicefs[2545041] <WARNING>: failed to get lock [gateway.go:1211]
Dec 01 14:07:44 sgp1 juicefs[2545041]: 2024/12/01 07:07:44.616880 juicefs[2545041] <WARNING>: failed to get lock [gateway.go:1211]
sedlund
changed the title
gateway: unable to create lockfile when running as user service
gateway: unable to create lockfile when running as service
Dec 1, 2024
What happened:
Using user:group juicefs:juicefs to start gateway. Get error trying to create lock. The service starts, but continues to complain that it cannot create the lock file. Which may lead to data corruption?
WorkingDirectory
causes juicefs to start within/run/juicefs
(which isRuntimeDirectory
)I also set a home directory for user
juicefs
which is not ideal.What you expected to happen:
Starts and is able to create its lock file.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
JuiceFS version (use
juicefs --version
) or Hadoop Java SDK version:juicefs version 1.2.1+2024-08-30.cd871d19ba57
Cloud provider or hardware configuration running JuiceFS:
OS (e.g
cat /etc/os-release
):NixOS 25.05.20241128.970e93b (Warbler) x86_64
Kernel (e.g.
uname -a
):Linux 6.6.61
Object storage (cloud provider and region, or self maintained):
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
locally via tailscale
Others:
The text was updated successfully, but these errors were encountered: