-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Unable to detect php-fpm
service with port
resource
#847
Comments
ℹ️ I didn't have any issues to validate many other services: |
Does tcp6:9000 work? If it does, the doc explains it a bit. |
Yes it works ! My apologies, I didn't check well my server state, may be this could help someone else, if no IP is defined in the ; /etc/php/8.2/fpm/pool.d/www.conf
listen = "9082"
listen.allowed_clients = 127.0.0.1 # This IPV4 address confused me sudo sockstat -l
USER PROCESS PID PROTO SOURCE ADDRESS FOREIGN ADDRESS STATE
root php-fpm8.2 37132 tcp6 :::9082 :::* LISTEN Adding the IPV4 loopback IP force it on tcp4: ; /etc/php/8.2/fpm/pool.d/www.conf
- listen = "9082"
+ listen = "127.0.0.1:9082"
listen.allowed_clients = 127.0.0.1 # This IPV4 address confused me sudo sockstat -l
USER PROCESS PID PROTO SOURCE ADDRESS FOREIGN ADDRESS STATE
root php-fpm8.2 41486 tcp4 127.0.0.1:9082 *:* LISTEN As a goss user the confusing point for me was this note in the documentation:
Because 🎉 Also as a Thanks for your help @aelsabbahy ! I also would like to congratulate you for this product, the alternative to |
Describe the bug
I have an issue when trying to ensure that a
php-fpm
service is listening withport
resource.How To Reproduce
I have the issue on a compute instance but it's seems to be reproductible in a docker container…
Start a docker container with php:8.2-fpm and take a shell in it:
Install
netcat
&goss
:Ensure service is listening with netcat:
I ran goss with the following spec file:
Expected Behavior
Detect port as
listening: true
.Actual Behavior
Running the add port command doesn't help:
Environment:
v0.4.2
Linux (Debian 11/12)
The text was updated successfully, but these errors were encountered: