[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: A few issues with Skolelinux 5.0 : A late followup

Philipp Huebner skrev:

Hi,

On 03.03.2010 11:12, Joakim Seeberg wrote:

Hi, I have a few issues with my recent Skolelinux 5.0 setup.

Diskless-workstation:
When loging out of from a kde session konsole login appaers instead of
kdm with the message:

Mar  3 10:34:51 static01 kdm[2744]: X server for display :0 terminated
unexpectedly
Mar  3 10:34:51 static01 kdm[2744]: X server for display :0 terminated
unexpectedly
Mar  3 10:34:51 static01 kdm[2744]: Unable to fire up local display :0;
disabling.
Mar  3 10:34:51 static01 kdm[2744]: Unable to fire up local display :0;
disabling.

From konsole I can log in and do startx witout errors. No more logs for
now.

Is this hardware specific or has anyone else seen this?


My guess is this is hardware specific.

I found that others have this problem with sis chips when using lenny.
A workaround is to switch from kdm to gdm.



Squid:
squid has been running fine for at least 24 hours but now I get the
following when starting squid:
Mar  3 10:47:55 tjener squid[20366]: Squid Parent: child process 20369
started
Mar  3 10:47:55 tjener squid[20369]: The url_rewriter helpers are
crashing too rapidly, need help!
Mar  3 10:47:55 tjener squid[20366]: Squid Parent: child process 20369
exited due to signal 6

cache.log: Squid Cache (Version 2.7.STABLE3): 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
Memory usage for squid via mallinfo():
   total space in arena:    2116 KB
   Ordinary blocks:         2081 KB      4 blks
   Small blocks:               0 KB      0 blks
   Holding blocks:           428 KB      2 blks
   Free Small blocks:          0 KB
   Free Ordinary blocks:      34 KB
   Total in use:            2509 KB 99%
   Total free:                34 KB 1%


There is enough space on booth /var and /var/spool/squid.


I have had this before when the socket was blocked by a running
dansguardian.
Have you modified anything related to squid? Tried to set up some filter
or additional proxy?
This could also be a wrong IP / interface configuration.

Try to turn on debug/verbose logging, the above doesn't really say anything.


You where right. I forgot about a smal change in squidguard configuration


I can browse the web with iceweasel but apt-get can't connect to webcache


Do 'unset http_proxy', then apt-get won't try to use webcache.


Regards,
Reply to: