Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grpc warnings :: The number of channel for the target googleads.googleapis.com:443 is maxed out bounded #1072

Open
fruwolt opened this issue Feb 13, 2025 · 1 comment
Labels
question Further information is requested triage Need triage

Comments

@fruwolt
Copy link

fruwolt commented Feb 13, 2025

[DO NOT INCLUDE ANY PERSONAL OR SENSITIVE DATA - MAKE SURE TO REDACT CONTENT WHEN NECESSARY]

Your question:
Hi all,

recently i stumbled upon following messages/warnings in our logs:

php-fpm WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
php-fpm I0000 00:00:1739374474.868171 15 channel.c:275] [Warning] The number of channel for the target googleads.googleapis.com:443 is maxed out bounded.
php-fpm I0000 00:00:1739374474.868233 15 channel.c:277] [Warning] Target upper bound: 1. Current size: 1.
php-fpm I0000 00:00:1739374474.868248 15 channel.c:280] [Warning] Target googleads.googleapis.com:443 will not be persisted.
php-fpm I0000 00:00:1739374475.100462 15 call_credentials.c:168] GRPC_PHP: call credentials plugin function - begin
php-fpm I0000 00:00:1739374475.174927 15 call_credentials.c:171] GRPC_PHP: call credentials plugin function - end

This is logged for requests we're running to e.g. fetch performance data of our client ads accounts (within mcc) like clicks, impressions etc of campaigns for specific days)
We're on v17 of the php ads api library.

We create a GoogleAdsClient that way:
$googleAdsClient = (new GoogleAdsClientBuilder())
->from($configuration) // no connection options set currently
->withLogLevel(LogLevel::WARNING)
->withOAuth2Credential((new OAuth2TokenBuilder())->from($configuration)->build())
->withLoginCustomerId($ourMccCustomerId)
->build();

and re-use it for all consecutive requests for a single account (if relevant).

Is there anything you can suggest to fix this?

Regards
Frank

@fruwolt fruwolt added question Further information is requested triage Need triage labels Feb 13, 2025
@fiboknacky
Copy link
Member

Hello Frank,

That error seems to happen in the grpc layer. Could you file an issue in its Issue Tracker? Based on the error message, we probably need to adjust the target upper bound.

In the meantime, would it be possible for you to try your code in non-PHP-FPM environment, like a normal PHP CLI mode?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested triage Need triage
Projects
None yet
Development

No branches or pull requests

2 participants