Re: [users@httpd] Thruk reports /var/tmp/live.sock: No such file or directory inspite of the file being present

Hi Daniel, Please find the details which are as below :- [root@e2e-14-53 ~]# namei -mx /var/tmp/live.sock f: /var/tmp/live.sock Dr-xr-xr-x / drwxr-xr-x var drwxrwxrwt tmp srw-rw-rw- live.sock [root@e2e-14-53 ~]# namei -mol /var/tmp/live.sock f: /var/tmp/live.sock dr-xr-xr-x root root / dr

Re: [users@httpd] ProxyPass not working?

Matching slashes worked! Thanks. On Fri, Nov 25, 2016 at 11:00 AM, Daniel wrote: > Please match slashes when using proxypass and proxypassreverse otherwise > expect the unexpected. > > ProxyPass / http://localhost:8080/lophyda.com/ > > 2016-11-25 16:10 GMT+01:00 Lou DeGenaro : > >> I posted the

Re: [users@httpd] Thruk reports /var/tmp/live.sock: No such file or directory inspite of the file being present

may be worth checking with namei command to see the permissions are correct for the whole path not just the end socket file. namei -mx /var/tmp/live.sock or namei -mol /var/tmp/live.sock Also what does the httpd error log say? 2016-11-25 19:35 GMT+01:00 Kaushal Shriyan : > > > On Fri, Nov 25,

Re: [users@httpd] Thruk reports /var/tmp/live.sock: No such file or directory inspite of the file being present

On Fri, Nov 25, 2016 at 11:56 PM, Daniel wrote: > If apache is supposed to interact with that socket file, the user it runs > as at least should be in the nagios group looking at how you configured its > permissions, or you could change its ownership to nagios:www-data (or > however the user http

Re: [users@httpd] Thruk reports /var/tmp/live.sock: No such file or directory inspite of the file being present

If apache is supposed to interact with that socket file, the user it runs as at least should be in the nagios group looking at how you configured its permissions, or you could change its ownership to nagios:www-data (or however the user httpd uses is named) 2016-11-25 19:19 GMT+01:00 Kaushal Shriy

[users@httpd] Thruk reports /var/tmp/live.sock: No such file or directory inspite of the file being present

Hi, I am running thruk (version is thruk-2.12-1.x86_64) which is a web interface for nagios 4.2.3 and running httpd-2.4.6-40.el7.centos.4.x86_64 on CentOS Linux release 7.2.1511 (Core) While accessing thruk web interface http://thruk.mydomain.com/thruk/cgi-bin/status.cgi?host=all&_=1480078344275

Re: [users@httpd] ProxyPass not working?

Please match slashes when using proxypass and proxypassreverse otherwise expect the unexpected. ProxyPass / http://localhost:8080/lophyda.com/ 2016-11-25 16:10 GMT+01:00 Lou DeGenaro : > I posted the entire configuration file. Isn't that what /bin/cat does? > > Why do you suggest that DNS is no

Re: [users@httpd] ProxyPass not working?

I posted the entire configuration file. Isn't that what /bin/cat does? Why do you suggest that DNS is not configured correctly? I use GoDaddy to send my IP address to my router, and my router forwards the IP address:80 to my apache2 server. Which part of networking and Apache configuration do I

RE: [users@httpd] ProxyPass not working?

I don’t understad where did you that URL from Do you see anywhere in the configuration file /lophyda.comlophyda.com/ ? ServerName lophyda.com – means that you should access the webserver with that address If you don’t have DNS configured correctly then you should se

Re: [users@httpd] ProxyPass not working?

HTTP Status 404 - /lophyda.comlophyda.com/ root@HAL9000:/etc/apache2/sites-enabled# cat lophyda.com.conf ServerName lophyda.com ProxyPass / http://localhost:8080/lophyda.com ProxyPassReverse / http://localhost:8080/lophyda.com LogLevel warn On Fri, Nov 25, 2016 at 8:44 AM, A

RE: [users@httpd] ProxyPass not working?

ProxyPreserveHost is kind of useless in your case Take a look at https://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypass This should work ServerName lophyda.com ProxyPass / http://localhost:8080/lophyda.com ProxyPassReverse / http://localh

Re: [users@httpd] ProxyPass not working?

Still trying. On ubuntu 16.04. I have tomcat installed. Visiting localhost:8080 yields normal tomcat welcome page. Visiting localhost:8080/lophyda.com yields my website welcome page, as expected. I have apache2 installed. Visiting localhost:80 yields normal apache welcome page. Visiting lophy