# Functionbeat GCP pub/sub requiring storage entry point when only pub/sub is enabled **URL:** \ **Category:** Beats\ **Tags:** beats-module, functionbeat\ **Created:** [January 24, 2022, 4:33pm UTC](https://discuss.elastic.co/t/functionbeat-gcp-pub-sub-requiring-storage-entry-point-when-only-pub-sub-is-enabled/295254 "2022-01-24T16:33:10Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Sebastian\_Borys](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebastian_borys/32/100799_2.png) [@Sebastian\_Borys](https://discuss.elastic.co/u/Sebastian_Borys)\ **Post date:** [January 24, 2022, 5:10pm UTC](https://discuss.elastic.co/t/functionbeat-gcp-pub-sub-requiring-storage-entry-point-when-only-pub-sub-is-enabled/295254/2 "2022-01-24T17:10:39Z")
I wonder even if I manage to get this to run if I will run into this > [@Functionbeat missing package io/fs](https://discuss.elastic.co/t/functionbeat-missing-package-io-fs/284975/9): > > Hello @Edoardo_Tenani, Thanks a lot for your advice, it worked for the deployment part. functionbeat is properly deployed on GCP cloud function with Go 1.16. Unfortunately, after sending some traffic through the cloud function I still get the panic crash error. Same behaviour as before, the first message is properly delivered to my Elastic cloud cluster. I can see it in kibana. The second message always makes functionbeat to crash FATAL [functionbeat] instance/beat.go:171 Failed due to panic.… [GCP/FunctionBeat Errors [cannot find matching process for pid=1, name version already used] · Issue #25596 · elastic/beats · GitHub 1](https://github.com/elastic/beats/issues/25596) --- _[View the full topic](https://discuss.elastic.co/t/functionbeat-gcp-pub-sub-requiring-storage-entry-point-when-only-pub-sub-is-enabled/295254)._