EROFS error when hitting lambda function endpoint

Question

I have deployed my expressjs code to lambda using claudiajs.When I hit the API endpoint generated every alternate request gives me internal server error.I checked the logs and found this

 "errorType": "Error",
    "errorMessage": "EROFS: read-only file system, mkdir '/var/task/logs'",
    "code": "EROFS",
    "stack": [
        "Error: EROFS: read-only file system, mkdir '/var/task/logs'"
    ],
    "cause": {
        "errorType": "Error",
        "errorMessage": "EROFS: read-only file system, mkdir '/var/task/logs'",
        "code": "EROFS",
        "stack": [
            "Error: EROFS: read-only file system, mkdir '/var/task/logs'"
        ],
        "errno": -30,
        "syscall": "mkdir",
        "path": "/var/task/logs"
    },
    "isOperational": true,
    "errno": -30,
    "syscall": "mkdir",
    "path": "/var/task/logs"
}

I am not able to figure out what could be the issue and why is it occurring only on alternate requests and not every request.How do I go on about it? Any help would be appreciated.

Possible duplicate of [Getting error AWS Lambda : EROFS: read-only file system, open '/var/task/assets/docs.zip'](https://stackoverflow.com/questions/53810516/getting-error-aws-lambda-erofs-read-only-file-system-open-var-task-assets) — Alexandr Lihonosov, Sep 05 '19 at 12:27

score 0 · Answer 1 · answered Sep 05 '19 at 12:16

Lambda dosen't allow you to write the space allocated to you.

Since, you are trying to create a directory may be to write logs, so its giving you the error.

To write application logs with lambda you can use AWS Cloudwatch log streaming.

https://www.npmjs.com/package/lambda-log

score 0 · Answer 2 · answered Sep 05 '19 at 12:25

0

You can use /tmp directory for some temporary files, but there is also a limit 512Mb.

Check these links:

AWS Lambda Limits

Accessing Amazon CloudWatch Logs for AWS Lambda

answered Sep 05 '19 at 12:25

Alexandr Lihonosov

978
8
23

EROFS error when hitting lambda function endpoint

2 Answers2