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.

Sign up for GitHub

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

Jump to bottom

Invalid argument #3

Open
ZherebcovSergey opened this issue Apr 2, 2018 · 1 comment
Open

Invalid argument #3

ZherebcovSergey opened this issue Apr 2, 2018 · 1 comment

Comments

@ZherebcovSergey
Copy link

I got this error when there is no access to the collector.instrumentalapp.com service.

FastCGI sent in stderr: "PHP message: [2018-04-02 10:52:30] instrumental.ERROR: Exception caught: Argument 2 passed to Monolog\Logger::warn() must be of the type array, string given, called in .../php/vendor/instrumental/instrumental_agent/lib/Agent.php on line 440 #0 .../php/vendor/instrumental/instrumental_agent/lib/Agent.php(440): Monolog\Logger->warn('Couldn't resolv...', 'warn') #1 ../php/vendor/instrumental/instrumental_agent/lib/Agent.php(64): Instrumental\Agent->ipv4_address_for_host('collector.instr...', 8000) #2 .../php/vendor/instrumental/instrumental_agent/lib/Agent.php(333): Instrumental\Agent->connect() #3 .../php/vendor/instrumental/instrumental_" while reading response header from upstream,...
jason-o-matic added a commit that referenced this issue Apr 5, 2018
@jason-o-matic
Fix a monolog call that masked underlying exceptions
dde86d6 
When DNS resolution failed we logged a message. Unfortunately the
logger call had an incorrect argument and would then raise a new
exception.

This removes the bad argument and adds a test to verify the correct
message gets logged.

#3
@jason-o-matic jason-o-matic mentioned this issue Apr 5, 2018
Merged
@jason-o-matic
Copy link
Member

It looks like there was an error with logging the original exception. We've fixed this masking issue in v1.0.2 which we just released. Can you try updating to this newest version and giving it another shot? If it still errors this should give a better error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jason-o-matic @ZherebcovSergey