Help on Varnish configuration problem on Centos 6.5
Per Buer
perbu at varnish-software.com
Thu May 22 14:28:04 CEST 2014
Normally Varnish runs on port 80 for production environment so clients can
connect to the default HTTP port.
Apache is typically moved to port 8080 but it can of course be any port.
On Thu, May 22, 2014 at 1:50 PM, Joao Rios <jprr773 at gmail.com> wrote:
> Thank you Per Buer,
> I admit I am a newbie and this is my first attemp to install Varnish, and
> I need to read more about Varnish :)
>
> So Varnish need to be installed on a different port when apache is running
> on port 80, and normally what ports are used?
> Thank you
>
>
>
>
>
> On Thu, May 22, 2014 at 12:46 PM, Per Buer <perbu at varnish-software.com>wrote:
>
>> Varnish is not running. When it doesn't start you can check syslog. It
>> will probably say something like "can't bind to port".
>>
>> The reason is obvious (for me at least :-).
>>
>> tcp 0 0 0.0.0.0:80 <http://0.0.0.0/>
>> 0.0.0.0:* LISTEN 7866/httpd
>>
>> You have apache running on port 80 so Varnish can't bind to the port.
>>
>>
>> On Thu, May 22, 2014 at 1:19 PM, Joao Rios <jprr773 at gmail.com> wrote:
>>
>>> Well, if I : # ps -ef | grep varnishd ,
>>>
>>> I get this:
>>>
>>> root 13560 13314 0 14:18 pts/3 00:00:00 grep varnishd
>>>
>>>
>>>
>>> On Thu, May 22, 2014 at 12:10 PM, Joao Rios <jprr773 at gmail.com> wrote:
>>>
>>>> Hi James,
>>>> Thank you so much for the reply.
>>>> I don't think Varnish is running on port 80.
>>>>
>>>> When I execute this: netstat -tulpn , I get:
>>>>
>>>> Active Internet connections (only servers)
>>>> Proto Recv-Q Send-Q Local Address Foreign
>>>> Address State PID/Program name
>>>> tcp 0 0 0.0.0.0:3306 0.0.0.0:*
>>>> LISTEN 30222/mysqld
>>>> tcp 0 0 0.0.0.0:587 0.0.0.0:*
>>>> LISTEN 18407/exim
>>>> tcp 0 0 0.0.0.0:110 0.0.0.0:*
>>>> LISTEN 18340/dovecot
>>>> tcp 0 0 127.0.0.1:783 0.0.0.0:*
>>>> LISTEN 18599/spamd.pid --m
>>>> tcp 0 0 0.0.0.0:143 0.0.0.0:*
>>>> LISTEN 18340/dovecot
>>>> tcp 0 0 0.0.0.0:2095 0.0.0.0:*
>>>> LISTEN 1463/cpsrvd (SSL) -
>>>> tcp 0 0 0.0.0.0:80 0.0.0.0:*
>>>> LISTEN 7866/httpd
>>>> tcp 0 0 0.0.0.0:2096 0.0.0.0:*
>>>> LISTEN 1463/cpsrvd (SSL) -
>>>> tcp 0 0 0.0.0.0:465 0.0.0.0:*
>>>> LISTEN 18407/exim
>>>> tcp 0 0 37.61.236.139:49619 0.0.0.0:*
>>>> LISTEN 13118/pure-ftpd (ID
>>>> tcp 0 0 37.61.235.212:53 0.0.0.0:*
>>>> LISTEN 13054/named
>>>> tcp 0 0 37.61.236.139:53 0.0.0.0:*
>>>> LISTEN 13054/named
>>>> tcp 0 0 127.0.0.1:53 0.0.0.0:*
>>>> LISTEN 13054/named
>>>> tcp 0 0 0.0.0.0:21 0.0.0.0:*
>>>> LISTEN 13118/pure-ftpd (ID
>>>> tcp 0 0 0.0.0.0:47926 0.0.0.0:*
>>>> LISTEN 4224/sshd
>>>> tcp 0 0 127.0.0.1:953 0.0.0.0:*
>>>> LISTEN 13054/named
>>>> tcp 0 0 0.0.0.0:25 0.0.0.0:*
>>>> LISTEN 18407/exim
>>>> tcp 0 0 0.0.0.0:443 0.0.0.0:*
>>>> LISTEN 7866/httpd
>>>> tcp 0 0 0.0.0.0:2077 0.0.0.0:*
>>>> LISTEN 25872/cpdavd - acce
>>>> tcp 0 0 0.0.0.0:2078 0.0.0.0:*
>>>> LISTEN 25872/cpdavd - acce
>>>> tcp 0 0 0.0.0.0:993 0.0.0.0:*
>>>> LISTEN 18340/dovecot
>>>> tcp 0 0 0.0.0.0:2082 0.0.0.0:*
>>>> LISTEN 1463/cpsrvd (SSL) -
>>>> tcp 0 0 0.0.0.0:995 0.0.0.0:*
>>>> LISTEN 18340/dovecot
>>>> tcp 0 0 0.0.0.0:2083 0.0.0.0:*
>>>> LISTEN 1463/cpsrvd (SSL) -
>>>> tcp 0 0 0.0.0.0:2086 0.0.0.0:*
>>>> LISTEN 1463/cpsrvd (SSL) -
>>>> tcp 0 0 127.0.0.1:199 0.0.0.0:*
>>>> LISTEN 4360/snmpd
>>>> tcp 0 0 0.0.0.0:2087 0.0.0.0:*
>>>> LISTEN 1463/cpsrvd (SSL) -
>>>> tcp 0 0 :::587
>>>> :::* LISTEN 18407/exim
>>>> tcp 0 0 :::80
>>>> :::* LISTEN 7866/httpd
>>>> tcp 0 0 :::465
>>>> :::* LISTEN 18407/exim
>>>> tcp 0 0 :::21
>>>> :::* LISTEN 13118/pure-ftpd (ID
>>>> tcp 0 0 :::47926
>>>> :::* LISTEN 4224/sshd
>>>> tcp 0 0 :::25
>>>> :::* LISTEN 18407/exim
>>>> tcp 0 0 :::443
>>>> :::* LISTEN 7866/httpd
>>>> udp 0 0 0.0.0.0:161 0.0.0.0:*
>>>> 4360/snmpd
>>>> udp 0 0 37.61.235.212:53 0.0.0.0:*
>>>> 13054/named
>>>> udp 0 0 37.61.236.139:53 0.0.0.0:*
>>>> 13054/named
>>>> udp 0 0 127.0.0.1:53 0.0.0.0:*
>>>> 13054/named
>>>> udp 0 0 37.61.235.212:123 0.0.0.0:*
>>>> 1130/ntpd
>>>> udp 0 0 37.61.236.139:123 0.0.0.0:*
>>>> 1130/ntpd
>>>> udp 0 0 127.0.0.1:123 0.0.0.0:*
>>>> 1130/ntpd
>>>> udp 0 0 0.0.0.0:123 0.0.0.0:*
>>>> 1130/ntpd
>>>> udp 0 0 fe80::216:3eff:fead:d8c:123
>>>> :::* 1130/ntpd
>>>> udp 0 0 ::1:123
>>>> :::* 1130/ntpd
>>>> udp 0 0 :::123
>>>> :::* 1130/ntpd
>>>>
>>>>
>>>>
>>>>> Excerpts from Joao Rios's message of 2014-05-21 11:11:17 -0700:
>>>>> > I am trying to run Varnish 3.0.5 on Centos 6.5 with no sucess.
>>>>> > After installing the rpm and follow the installation procedures,
>>>>> > it seems the service fails to start:
>>>>> >
>>>>> > # service varnish restart
>>>>> > Stopping Varnish Cache: [FAILED]
>>>>> > Starting Varnish Cache: [ OK ]
>>>>>
>>>>> No, that indicates that it didn't stop Varnish (probably because it
>>>>> wasn't
>>>>> running), but it *started* it successfully.
>>>>>
>>>>> Have you verified that it is indeed not running (via ps, lsof, etc.)?
>>>>> - P
>>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> varnish-misc mailing list
>>> varnish-misc at varnish-cache.org
>>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>>
>>
>>
>>
>> --
>> <http://www.varnish-software.com/> *Per Buer*
>> CTO | Varnish Software
>> Phone: +47 958 39 117 | Skype: per.buer
>> We Make Websites Fly!
>>
>> Winner of the Red Herring Top 100 Global Award 2013
>>
>>
>>
>
--
<http://www.varnish-software.com/> *Per Buer*
CTO | Varnish Software
Phone: +47 958 39 117 | Skype: per.buer
We Make Websites Fly!
Winner of the Red Herring Top 100 Global Award 2013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20140522/693d184e/attachment-0001.html>
More information about the varnish-misc
mailing list