Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Certainly you need to find where your certbot is installed, which is your immediate problem. After that, you can try to figure out why a simple certbot renew doesn't work--it should. Next, if you're stopping Apache, what's going to serve the challenge token when Let's Encrypt asks for it?
It looks like you've used the certbot-auto (or even the older letsencrypt-auto) wrapper script to install and maintain your certbot instance. However, the certbot-auto wrapper script has been deprecated in favor of other installation methods.
From your output, it seems your Google Cloud instance is running CentOS, correct? Probably CentOS 7, looking at your Apache version (2.4.6), correct? Is that a virtual machine to which you have root access? If so, you might want to follow the official installation guide for CentOS 7: Certbot Instructions | Certbot