2015-01-31 0:53 GMT+01:00 Christian Demsar <vixsomnis@fastmail.com>:
So I just installed clamav but when I'm trying to start it with:
'sudo systemctl start clamd.service'
I get: Job for clamd.service failed. See "systemctl status clamd.service" and "journalctl -xe" for details.
'systemctl status clamd.service' clamd.service - clamav daemon Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since p 2015-01-30 21:14:04 CET; 10s ago Process: 9693 ExecStart=/usr/bin/clamd (code=exited, status=1/FAILURE)
It tells you to look in the logs. Did you do that?! Without wanting to be condescending: I don't think you should be using archlinux if you are not capable of looking through logs and searching google (I found the package for your "error" through a fast google search....)
Indeed. I find the solution at: https://wiki.manjaro.org/index.php?title=Clamav
Okay, so in regards to ClamAV, I encountered no errors [1] starting clamd with the service file in the clamav package [2].
You should check your service file at "/usr/lib/systemd/system/clamd.service" and make sure it matches the one I uploaded to pastebin.
I have the same /usr/lib/systemd/system/clamd.service file as you.
If you can link a paste of your log at "/var/log/clamav/clamd.log", that would help.
http://pastebin.com/RC9ZzYMs This log was I get before solve the clamav problem.
Your journalctl log can be captured using:
journalctl -xe | tail -n 500 | tee journal.log ^^^ ^^^ Takes last 500 lines. Saves and prints output.
Make sure to check these 500 lines that get printed to your terminal for anything sensitive, like passwords. NetworkManager doesn't show passwords in the log, but it does show network SSIDs and connection protocols, and other bits of information. There's probably more in there than you would guess (there is in mine).
I did check these 500 lines and don't find anything sensitive, like passwords. Only find the lines bellow and don't know whether are these lines all right: jan 30 21:19:09 csparch org.a11y.atspi.Registry[4719]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. jan 30 21:19:09 csparch org.a11y.Bus[4553]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. jan 30 21:19:16 csparch systemd[4450]: Stopping Default. -- Subject: Unit UNIT has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
I had some kernel panic problems I couldn't diagnose with a much-used MSI P67 motherboard. I'm pretty sure it was a motherboard issue, since I'm using the same power supply, most of the same RAM, and the same storage (different motherboard and CPU) and I haven't encountered any more. If you decide to do a fresh install and you still get kernel panics, I'd guess it's hardware related. Like a broken SATA port or a loose connection.
Well, my motherboard is Asus P5N-E SLI. I observe that that I can't use my DVD writer; it can't read neither any CD nor DVD. I must to disassemble this DVD writer and assemble my old IDE CD writer to can reach the broken system when had kernel panic. -- Regards from Pal