Dsg function crashing - lscpu: command not found - error: signal: segmentation fault

Keyrus · September 12, 2023, 10:42am

Hi,

Here are the links to the last build of the website on a deferred generated page (DSG).

https://65001b42860af03295867f2d–km-dsg-test.netlify.app/en/en/services/customer-experience/

I keep seing an error in the DSG function,

Sep 12, 10:09:22 AM: /bin/sh: lscpu: command not found

error: signal: segmentation fault

Netlify DSG function

Sep 12, 10:09:00 AM: /bin/sh: lscpu: command not found
Sep 12, 10:09:01 AM: Downloading datastore from CDN (https://65001b42860af03295867f2d--km-dsg-test.netlify.app/a179e844-fd98-4238-9578-c2693b17a132-data.mdb -> /tmp/gatsby/.cache/data/datastore/data.mdb)
Sep 12, 10:09:05 AM: Downloaded datastore from CDN
Sep 12, 10:09:06 AM: RequestId: b613cd92-120d-45fa-aa16-638997a35caf Error: Runtime exited with error: signal: segmentation fault
Runtime.ExitError
Sep 12, 10:09:06 AM: b613cd92 Duration: 4460.50 ms	Memory Usage: 681 MB	
Sep 12, 10:09:06 AM: INIT_START Runtime Version: nodejs:18.v12	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:0bdff101a7b4e0589af824f244deb93200e4663c2a8d7d0148b76cd00c48777a
Sep 12, 10:09:06 AM: 2023-09-12T08:09:06.681Z	undefined	INFO	Preparing Gatsby filesystem {
  from: '/var/task/.cache',
  to: '/tmp/gatsby/.cache',
  rewrites: [
    [ '/var/task/.cache/caches', '/tmp/gatsby/.cache/caches' ],
    [
      '/var/task/.cache/caches-lmdb',
      '/tmp/gatsby/.cache/caches-lmdb'
    ],
    [ '/var/task/.cache/data', '/tmp/gatsby/.cache/data' ]
  ]
}
Sep 12, 10:09:08 AM: /bin/sh: lscpu: command not found
Sep 12, 10:09:09 AM: Downloading datastore from CDN (https://65001b42860af03295867f2d--km-dsg-test.netlify.app/a179e844-fd98-4238-9578-c2693b17a132-data.mdb -> /tmp/gatsby/.cache/data/datastore/data.mdb)
Sep 12, 10:09:13 AM: Downloaded datastore from CDN
Sep 12, 10:09:13 AM: RequestId: 10e17b35-4ec4-4ca4-bef6-d63a553f659a Error: Runtime exited with error: signal: segmentation fault
Runtime.ExitError
Sep 12, 10:09:13 AM: 10e17b35 Duration: 4654.90 ms	Memory Usage: 685 MB	
Sep 12, 10:09:13 AM: INIT_START Runtime Version: nodejs:18.v12	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:0bdff101a7b4e0589af824f244deb93200e4663c2a8d7d0148b76cd00c48777a
Sep 12, 10:09:14 AM: 2023-09-12T08:09:14.030Z	undefined	INFO	Preparing Gatsby filesystem {
  from: '/var/task/.cache',
  to: '/tmp/gatsby/.cache',
  rewrites: [
    [ '/var/task/.cache/caches', '/tmp/gatsby/.cache/caches' ],
    [
      '/var/task/.cache/caches-lmdb',
      '/tmp/gatsby/.cache/caches-lmdb'
    ],
    [ '/var/task/.cache/data', '/tmp/gatsby/.cache/data' ]
  ]
}
Sep 12, 10:09:15 AM: /bin/sh: lscpu: command not found
Sep 12, 10:09:16 AM: Downloading datastore from CDN (https://65001b42860af03295867f2d--km-dsg-test.netlify.app/a179e844-fd98-4238-9578-c2693b17a132-data.mdb -> /tmp/gatsby/.cache/data/datastore/data.mdb)
Sep 12, 10:09:20 AM: Downloaded datastore from CDN
Sep 12, 10:09:21 AM: RequestId: 6720712e-cb6f-4d61-abc3-f28995e795e3 Error: Runtime exited with error: signal: segmentation fault
Runtime.ExitError
Sep 12, 10:09:21 AM: 6720712e Duration: 4672.57 ms	Memory Usage: 679 MB	
Sep 12, 10:09:21 AM: INIT_START Runtime Version: nodejs:18.v12	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:0bdff101a7b4e0589af824f244deb93200e4663c2a8d7d0148b76cd00c48777a
Sep 12, 10:09:21 AM: 2023-09-12T08:09:21.380Z	undefined	INFO	Preparing Gatsby filesystem {
  from: '/var/task/.cache',
  to: '/tmp/gatsby/.cache',
  rewrites: [
    [ '/var/task/.cache/caches', '/tmp/gatsby/.cache/caches' ],
    [
      '/var/task/.cache/caches-lmdb',
      '/tmp/gatsby/.cache/caches-lmdb'
    ],
    [ '/var/task/.cache/data', '/tmp/gatsby/.cache/data' ]
  ]
}
Sep 12, 10:09:22 AM: /bin/sh: lscpu: command not found
Sep 12, 10:09:23 AM: Downloading datastore from CDN (https://65001b42860af03295867f2d--km-dsg-test.netlify.app/a179e844-fd98-4238-9578-c2693b17a132-data.mdb -> /tmp/gatsby/.cache/data/datastore/data.mdb)
Sep 12, 10:09:27 AM: Downloaded datastore from CDN
Sep 12, 10:09:28 AM: RequestId: 24e0799c-ca65-40f6-bd05-cda6f6966b2f Error: Runtime exited with error: signal: segmentation fault
Runtime.ExitError
Sep 12, 10:09:28 AM: 24e0799c Duration: 4276.19 ms	Memory Usage: 680 MB	
Sep 12, 10:09:28 AM: INIT_START Runtime Version: nodejs:18.v12	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:0bdff101a7b4e0589af824f244deb93200e4663c2a8d7d0148b76cd00c48777a
Sep 12, 10:09:28 AM: 2023-09-12T08:09:28.317Z	undefined	INFO	Preparing Gatsby filesystem {
  from: '/var/task/.cache',
  to: '/tmp/gatsby/.cache',
  rewrites: [
    [ '/var/task/.cache/caches', '/tmp/gatsby/.cache/caches' ],
    [
      '/var/task/.cache/caches-lmdb',
      '/tmp/gatsby/.cache/caches-lmdb'
    ],
    [ '/var/task/.cache/data', '/tmp/gatsby/.cache/data' ]
  ]
}
Sep 12, 10:09:29 AM: /bin/sh: lscpu: command not found
Sep 12, 10:09:30 AM: Downloading datastore from CDN (https://65001b42860af03295867f2d--km-dsg-test.netlify.app/a179e844-fd98-4238-9578-c2693b17a132-data.mdb -> /tmp/gatsby/.cache/data/datastore/data.mdb)

hrishikesh · September 16, 2023, 11:26am

We’re seeing this happen with a few other users and it’s already being investigated. We’d let you know once we have more info.

GoGet · September 20, 2023, 3:44pm

Hi,

Same thing happening here for me too.

I was trying to upgrade our site to Gatsby V5 and it is specifically failing on that build.

Previous build still running on V4 has no issue.

Only notable change is switching over from gatsby-plugin-netlify to gatsby-adapter-netlify.

Here is a screenshot of our error if it helps with investigation.

Thanks

hrishikesh · September 23, 2023, 5:07pm

So far we’ve identified the issue, but we have no ETA yet on if/when this would be fixed.

Kkr85 · September 25, 2023, 3:45pm

Hi!
Unfortuntaley this started happening to me as well and it affects SSR too. I can also confirm what GoGet mentioned that it works fine on Gatsby 4 but not on Gatsby 5. Our company site is already on Gatsby 5 and we’re trying to switch some pages to SSR but this problems keeps us from doing so.

Is there any news on this? Or any possible workaround?

audrey · September 28, 2023, 12:27am

Howdy @Kkr85 and welcome!

As Hrishikesh mentioned, our developers have identified the problem, but unfortunately, we don’t have an estimated time for when a fix will be implemented. We’ll keep you posted as soon as we have more information to share. Thank you for your patience!