Printable View
I have just inherited a squid proxy server (on linux)that i have never worked or had any experience on. I came in this morning the internet had stopped. after a couple of reboots reboot it works for about 30 mins each time and then stops. If I restart the services it will restart. With my lack of experience, although I am learning quickly I'm not sure how to fix this.
Any help gatefully received
Paul
Well maybe you could follow up on your two other posts on the same subject? Where I did post some advice?
http://www.edugeek.net/forums/intern...king-help.html
I was just thinking I've seen this before, recently, more than once.Quote:
Originally Posted by pete
I have tried the advice given, but not sure what the logs mean was hoping perhaps as this is supposed to be a helping site, someone might take a look at the logs for me to help me out. perhaps this is not a site that helps people anymore
I was also advised to re post to this area by Geoff
3 posts? Just re-post in your old post. And if you want people to look at your logs then perhaps its a good idea to firstly, state that in your post, and secondly, post your logs so people can view them.Quote:
Originally Posted by wellscs
Your 3 posts have said exactly the same in each. We're a very helping community, but unfortunately I left my Crystal ball at home today.
Attachment 3510
Attachment 3511
Attachment 3512
I have attached some log files
Thanks
Looks like you've run out of space on the disk / partition that the log files are stored on.
Ok, I'm no guru with Squid or *nix but it appears to be that your cache is full and this might be causing it. I've found this site - see if this is useful.Quote:
Originally Posted by wellscs
RE: [squid-users] squid tries to rebuild cache but fails... - Unix Linux Forum
runningwill show you if your disk(s) are full.Code:df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 71G 68G 0 100% /
varrun 1013M 344K 1013M 1% /var/run
varlock 1013M 0 1013M 0% /var/lock
udev 1013M 68K 1013M 1% /dev
devshm 1013M 12K 1013M 1% /dev/shm
lrm 1013M 38M 976M 4% /lib/modules/2.6.24-16-generic/volatile
gvfs-fuse-daemon 71G 68G 0 100% /root/.gvfs
/dev/sdc1 233G 59M 233G 1% /media/disk
the 1st line: /dev/sda1 is full - you need to clean up your logs a bit - sorry I can't be of more help but I've just started using Squid myself. I'm sure Geoff will be along in a minute with a quick fix.Quote:
Originally Posted by wellscs
Yep, your root partition /dev/sha1 which contains the root of your filesystem / is full. You'll need to do some cleaning up. My guess is that it's full of old logfiles. Take a look into log rotation for automatic management of your log files.
Thanks for all your replies, seems we are getting somwhere. remembering Im a compl:)ete novice at this can someone help me with the code to empty/ rotate/compact my log files
Thanks to everyone again
To ensure it is squid, (and not, say dansguardian as well), cd into /var/logs and use:
Which will give you the space consumed by each directory / log.Code:du -h --max-depth=1
I'm assuming you're using Ubuntu (by the presence of gvfs-daemon).
From a terminal, issue:
If you care about the logs (ideally you should), plug in a removable hard disk and copy the squid logs to it - there's not enough space to compress them on your drive at the moment. If you're running the gnome desktop it should automount the usb drive.Code:sudo /etc/init.d/squid stop
Once the squid log is copied somewhere else, su to root temporarily by using:
then typeCode:sudo -s
to zero the contents of the file, but keep it and the permissions in place. Type exit to discard root credentials then type:Code:> /var/log/squid/access.log
Your squid box will now run ok for a while, but you need to get log rotation sorted or this will happen again.Code:sudo /etc/init.d/squid start
NB: It's very rare I remember to check pms - posting in thread is the best way to attract my attention.