Squid Proxy WARNING! Your cache is running out of filedescriptors error and solution

Pusing dengan squid, sebenarnya masalahnya apa. Kemaren salah routing sekarang apa lagi yah ..??$#@$
Lihat di /var/log/squid/cache.log ternyata ada error warning:
WARNING ! Your cache is running out of filedescriptors

solusi dari om google sbb :

Untuk melihat status max_filedesc di redhat ketik command berikut :

# squidclient -p 8080 mgr:info

Untuk melakukan menambahkan nilai max_filedesc lakukan langkah sebagai berikut :
1. Stop service squid
# service ssquid stop

2. edit file /etc/squid/squid.conf. Pada baris max_filedesc tambahkan nilai 4096. Keluar dan exit
# vi /etc/squid/squid.conf

3. start squid service

# service squid start

Scheduler Restart PC Windows XP

Hasil identifikasi terhadap probe SMARTI, ternyata musti direstart.
Waduh .. windows ... windows ... payah. Dari pada dikerjain oleh windows baiknya buat scheduler restart aja lah.
1. Masuk ke System Tools --> Scheduled Task
2. Create new scheduled task di jam 02:00 AM
3. Buat template running command prompt, kemudian edit comandnya
" C:\WINDOWS\system32\shutdown -r -t 01"

Melakukan fsck di linux

Pagi ini ada masalah dengan Server Intranet. Error read file system.
Solusi sementara :

root@intrabali proc]# more /proc/mounts
rootfs / rootfs rw 0 0
/proc /proc proc rw,nodiratime 0 0
none /dev tmpfs rw 0 0
/dev/root / ext3 rw 0 0
none /dev tmpfs rw 0 0
/proc /proc proc rw,nodiratime 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
/sys /sys sysfs rw 0 0
none /dev/pts devpts rw 0 0
none /dev/shm tmpfs rw 0 0
/dev/sda2 /home ext3 rw 0 0
/dev/sda7 /home1 ext3 ro 0 0
/dev/sda6 /usr ext3 rw 0 0
/dev/sda5 /var ext3 rw 0 0

Kemudian lakukan fsck

[root@intrabali proc]# fsck.ext3 /dev/sda7e2fsck 1.35 (28-Feb-2004)/dev/sda7 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may causeSEVERE filesystem damage.
Do you really want to continue (y/n)? yes
/home11: recovering journal/home11 contains a file system with errors, check forced.Pass 1: Checking inodes, blocks, and sizesError reading block 1245209 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error? yes
Force rewrite? yes
Deleted inode 37465154 has zero dtime. Fix? yes