Topic: Dansguardian Startup Error

[sdpiowa]

I installed Dansguardian on our server today.  It was working until I started changing the config files, then it wouldn't start when I gave the restart command.  When the computer boots up and it tries to start it, it says [FAILED].

First of all, I was going off of the WIKI, so I don't think that I did anything wrong.  If there is no quick fix, how do I reinstall Dansguardian without reinstalling the operating system?

[chris burnat]

Moving to Contribution section where it is more appropriate.

[janet]

sdpiowa

.... Dansguardian .... was working until I started changing the config files

Well you need to tell us more than that, ie which config files, what changes did you make etc etc.

I'm guessing you have made a wrong change to one of the files and that is preventing dansguardian from starting.

..how do I reinstall Dansguardian without reinstalling the operating system?

To remove do:
rpm -e dansguardian smeserver-dansguardian
signal-event reboot
Note you will also need to revert db settings to default values as per wiki.

Then follow the wiki to reinstall and configure

I STRONGLY suggest you only change one config file at a time, making note of the changes you make, and test after each change.

[sdpiowa]

Let's see; I changed the following files:
dansguardian.conf
dansguardianf1.conf
bannedextensionlist
bannedsitelist
bannedurllist

I only un-commented settings on the following:
bannedextensionlist

I only changed the rest of the files based on what either the config file or the WIKI told me to do.


I didn't realize that I had to restart Dansguardian for changes to take effect, so that was part of my problem.  That's why I didn't try to restart it earlier.


ALSO: Is there a way to revert the config files back to the default settings?

[Stefano]

I didn't realize that I had to restart Dansguardian for changes to take effect, so that was part of my problem.  That's why I didn't try to restart it earlier.

just a question: did you check any log (at least /var/log/messages) to understand what's the problem?

Ciao
Stefano

[sdpiowa]

No, I didn't.  I'm still learning SME Server, so I didn't think to check that.

I've reinstalled Dansguardian, and it's working so far (but it isn't fully configured yet).

[Stefano]

No, I didn't.  I'm still learning SME Server, so I didn't think to check that.

ok.. in linux and every X* like O.S. almost everything is logged.. if something fails, you can be sure that you'll find the reason in a log file..

most of them are in /var/log directory; you should start to learn to check then (you can do also via server-manager) if you want to troubleshoot SME (or, generally speaking, linux)

I've reinstalled Dansguardian, and it's working so far (but it isn't fully configured yet).

this is windows's style approach to the problem.. here we are talking about a server O.S., not a toy

please, take the time to read the documentation and to read the wiki: you'll find some usefull info to start thinking as a sysad.

Ciao
Stefano

[sdpiowa]

I think I found the problem.  When I was "commenting" lines for blocked extensions before, I was doing:
#."FILETYPE"
instead of:
# ."FILETYPE"

I did it the second way this time and it is still working.

[Franco]

A space after your "#" won't make a difference, anything after the "#" won't.

[sdpiowa]

I just realized that I have the problem immediately after enabling a content scanner.  How can I enable one like Clamd?  The instant I enable it Dansguardian won't start.

[Stefano]

I just realized that I have the problem immediately after enabling a content scanner.  How can I enable one like Clamd?  The instant I enable it Dansguardian won't start.

are you following this howto?

Stefano