Mageia 2 Impressive. Dansguardian broken.

[koosjr]

I got on the Mageia 1 train shorty after initial release and is still using it on my main computer.

Apart from some teething problems - the most important one that my printer was not working properly - i enjoyed using it was pretty stable.

I installed Mageia 2 this morning without any revisionf of the Beta versions, and I must say, the improvement is impressive! It installed very easy, unlike Mageia 1 that struggled with the boot loader and in general it seems like it is faster in most aspects. From what I have seen so far, it looks very promising and worth it migrate my main box soon.

It installed my HP 6500A in seconds and on Mageia 1 the ADF scanner does not work. On Mageia 2 it works nice!

I have not tested all the rest, but again, it looks like it did get better. Keep up the good work.

However, Dansguardian is broken for some reason and one cannot restart it in the system services module of the control panel. This is a must for the kids computer.

[doktor5000]

Actually as far as i know the services currently can't be controlled properly via the control center, this is bit of a fallout from the migration to systemd, as that whole GUI would have needed to be rewritten. You can do it in a terminal via service dansguardian restart and you can also create a desktop shortcut for that one, which is probably a bit more convenient.

[koosjr]

Thanks doc. Unfortunately it does not work, and this is the output I get after doing systemctl --failed:

UNIT LOAD ACTIVE SUB JOB DESCRIPTION
dansguardian.service loaded failed failed LSB: Starts the dansguardian daemon
icapd.service loaded failed failed LSB: Starts the c-icap daemon
lm_sensors.service loaded failed failed Initialize hardware monitoring sensors

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.

3 units listed. Pass --all to see inactive units, too.

[doktor5000]

So please report it as a bug: https://wiki.mageia.org/en/How_to_report_a_bug_properly
As you mentioned systemctl --failed, can you please post the full output of

Code: Select all

service dansguardian restart

?

As a shot into the blue, this could just be an easy problem like missing LSB headers, maybe you want to take a look at https://wiki.mageia.org/en/Initscripts_ ... SB_headers

[koosjr]

Thanks Doc!

This problem sort of made me investigate alternatives, and I decided to give OpenDNS a try. Seems like it is also a good alternative, although I do think Dansguardian is better due to considerable more customizing possible.

Also, seems like Webmin is broken too. It does not come up in the System Services list where one can start it.

[koosjr]

Bug Reported.

[isadora]

Koosjr can you please give a link to your bug-report, thank you!!!

[koosjr]

https://bugs.mageia.org/show_bug.cgi?id=6313

https://bugs.mageia.org/show_bug.cgi?id=6314

[kalagani]

Hello,
for information, I had got same pb: dansguardian do not running with Mageia2 while running with Mageia1.
So I read the link to the bug 6313 and make below
_uninstall the dansguardian-2.10.1.1-6.mga1 package
_run the urpme --auto-orphans like suggested
_add repository to update_testing
_install the new dansguardian-2.10.1.1-6.1.mga2
_restart PC
and now dansguardian is running with Mageia2!

[doktor5000]

_run the urpme --auto-orphans like suggested

FWIW, this should not be suggested, and breaks things much too often if used without knowledge what it really does,
and apart from that is is not needed to get anything running or fixed.

Please mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks

[kalagani]

Hello doktor5000,
my post is just for information about solution found from reading bug 6313!
While this bug not closed and rpm not delivered from normal repository,
I think, it is early to prefix the topic SOLVED...