ChrisH Posted November 16, 2009 Posted November 16, 2009 I am getting a lot of slow downs on the filter and when I look at the log I get this: Any ideas?
mounters Posted November 16, 2009 Posted November 16, 2009 Have you tried optimizing the database? Go to information » settings » database backup and click on Optimize database, this will take a while and can effect system performance whilst it's running.
ChrisH Posted November 16, 2009 Author Posted November 16, 2009 (edited) Thanks for the suggestion, it sounds like a good one but on that page it tells me it cant connect to the DB so at least I sort of know what the problem is. I still seems to have internet access though... Edited November 16, 2009 by ChrisH
mounters Posted November 16, 2009 Posted November 16, 2009 I'd get onto support then, I had an odd problem with the database recently and they got me sorted.
tom_newton Posted November 16, 2009 Posted November 16, 2009 Definitely a database issue - which should mean your logs just back up to flat file until the DB connection is restored, and you get reporting back. Web filtering will not be compromised - the two systems (filtering, reporting) are designed with a hard gap between them so one would have a tricky time taking out the other Advice is to call support and to get them to mash your DB back into shape.
ChrisH Posted November 16, 2009 Author Posted November 16, 2009 Looks like my support has lapsed so I am going to reinstall to a new box. Will I get run into problems at the license stage if I try this?
tom_newton Posted November 16, 2009 Posted November 16, 2009 Chris: No problem - your licence will allow this just fine. 1
ChrisH Posted November 17, 2009 Author Posted November 17, 2009 Ok I have reinstalled and got rid of the database error. But I am getting this message spammed all the time now which I don't remember it being normal. Nov 17 09:53:40 s_sys@Cache dansguardian[3711] Connection handler caught an exception: St9exception Nov 17 10:03:15 s_sys@Cache dansguardian[7119] Connection handler caught an exception: St9exception Nov 17 10:03:15 s_sys@Cache dansguardian[3696] Connection handler caught an exception: St9exception Nov 17 10:03:15 s_sys@Cache dansguardian[5463] Connection handler caught an exception: St9exception Nov 17 10:03:15 s_sys@Cache dansguardian[5465] Connection handler caught an exception: St9exception Nov 17 10:03:17 s_sys@Cache dansguardian[5471] Connection handler caught an exception: St9exception Nov 17 10:03:18 s_sys@Cache dansguardian[5472] Connection handler caught an exception: Can't read from socket: Success Nov 17 10:03:18 s_sys@Cache dansguardian[5763] Connection handler caught an exception: St9exception I did cheat slightly and use the replication feature to get all the settings over so I may have brought part of the old problem over. Anyone get anything like this is their real time system log? 1
rob_f Posted November 17, 2009 Posted November 17, 2009 I believe this error occurs when clients start sending data but for some reason it isn't getting returned to them, for example if they disconnect or there are network issues inbetween. I may be wrong however It isn't necessarily indicative of a problem with the SmoothWall system itself, do you have any pattern or frequency of occurrence of the error? Thx
tom_newton Posted November 19, 2009 Posted November 19, 2009 AFAIK, this "error" is a result of some of the new code in FP3 - it is just slightly more verbose than it uised to be and may be safely ignored as long as your system appears normal otherwise. 3
ChrisH Posted November 19, 2009 Author Posted November 19, 2009 Ok that's good. I have managed to get it up and running as needed. The only trouble I did have is when I did a fresh install on the old hardware, then restored the config from the temp one I had no web interface. I had to go into the setup at the console and had to set the default interface.
robk Posted November 19, 2009 Posted November 19, 2009 Well that saves a call to support! We had exactly the same occur on our UTM after the FP3 upgrade, only performace dropped off after a few days with the db load. After several hours on the phone to support we ended up wiping the database and starting again, now seeing the second set of errors mentioned in the OP`s thread. Performance seems to have picked up though.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now