How to load squid was Re:localhost

Bart Silverstrim bsilver at chrononomicon.com
Mon Feb 11 00:42:32 UTC 2008



NoOp wrote:
> On 02/10/2008 02:41 PM, Bart Silverstrim wrote:
> 
>> Yes, I've run into cases where screwing up hostnames can cause fun 
>> problems.  In the times I've set up Squid, though, it usually was more 
>> tolerant of that error or at least have errors logged to the logs Squid 
>> keeps that would point out DNS/hostname-related errors, or at least 
>> setting it to your own host IP seemed to work.
>>
> 
> Looks to be a larger problem. Just for grins I decided to install squid
> on my test laptop - the one where hostname -f works & the one that is a
> pretty much stock Ubuntu Gnome 7.10 w/2.6.22.14-generic. Got the following:
> 
> $ sudo apt-get install squid
> [sudo] password for <user>:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following extra packages will be installed:
>   squid-common
> Suggested packages:
>   squidclient squid-cgi logcheck-database resolvconf winbind
> The following NEW packages will be installed:
>   squid squid-common
> 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
> Need to get 1116kB of archives.
> After unpacking 6156kB of additional disk space will be used.
> Do you want to continue [Y/n]? y
> Get:1 http://us.archive.ubuntu.com gutsy-updates/main squid-common
> 2.6.14-1ubuntu2.1 [474kB]
> Get:2 http://us.archive.ubuntu.com gutsy-updates/main squid
> 2.6.14-1ubuntu2.1 [642kB]
> Fetched 1116kB in 7s (141kB/s)
> 
> Preconfiguring packages ...
> Selecting previously deselected package squid-common.
> (Reading database ... 129738 files and directories currently installed.)
> Unpacking squid-common (from .../squid-common_2.6.14-1ubuntu2.1_all.deb) ...
> Selecting previously deselected package squid.
> Unpacking squid (from .../squid_2.6.14-1ubuntu2.1_i386.deb) ...
> Setting up squid-common (2.6.14-1ubuntu2.1) ...
> Setting up squid (2.6.14-1ubuntu2.1) ...
> Creating squid spool directory structure
> FATAL: Could not determine fully qualified hostname.  Please set
> 'visible_hostname'
> 
> Squid Cache (Version 2.6.STABLE14): Terminated abnormally.
> CPU Usage: 0.016 seconds = 0.012 user + 0.004 sys
> Maximum Resident Size: 0 KB
> Page faults with physical i/o: 0
> Aborted (core dumped)
>  * Restarting Squid HTTP proxy squid
>          * Creating squid spool directory structure
> FATAL: Could not determine fully qualified hostname.  Please set
> 'visible_hostname'
> 
> Squid Cache (Version 2.6.STABLE14): Terminated abnormally.
> CPU Usage: 0.016 seconds = 0.016 user + 0.000 sys
> Maximum Resident Size: 0 KB
> Page faults with physical i/o: 0
> Aborted (core dumped)
> FATAL: Could not determine fully qualified hostname.  Please set
> 'visible_hostname'
> 
> Squid Cache (Version 2.6.STABLE14): Terminated abnormally.
> CPU Usage: 0.020 seconds = 0.012 user + 0.008 sys
> Maximum Resident Size: 0 KB
> Page faults with physical i/o: 0
> Aborted (core dumped)
> 
> Nothing in logs other than sys.log with the "Could not determine fully
> qualified hostname.  Please set 'visible_hostname'"
> 
> The laptop has a fixed IP (192.168 range), so it wouldn't be anything
> related to dhcp etc.
> 
> Re-loop to https://bugs.launchpad.net/ubuntu/+source/squid/+bug/12709
> that the author of
> https://bugs.launchpad.net/ubuntu/+source/squid/+bug/97505
> referred to.
> 
> Don't know how you can pre-edit /etc/squid.conf if squid doesn't install...
> 
> Can anyone else replicate? If so, perhaps we need to revisit/refile
> 12709 or add on to 97505.

I'm sorry if I'm missing it, but what did you set the visible_hostname 
directive to in squid.conf?

That is one thing that you can't pre-edit, so it does have to be set first.




More information about the ubuntu-users mailing list