I am outraged that the community let this "payable" app fail without warning.
I too have just realized that owncloud isn't working right after I've converted the damn kvm machine to lxc and made everything work as it should (openvpn, nfs mounts, lvm mounts,..).
I've spent a few hours doing the conversion and then went ahead checking if everything works.
Well everything works except for the Owncloud app.
Reading about how it auto-updated to oblivion, I've even tried to revive the damn thing. After disabling an extra app, I've set "maintenance" to off.. guess what? All my users are gone. Only admin remains.

What?????!!!??!?!?!?

Tell me... who was the boss that let this happen? This is not the way upgrades were supposed to go.
I mean.. you didn't auto-replace zarafa with kopano. I guess there's a good reason not to do that.

What do I do now? I have all the files on the filesystem, so I'm ok. I'll just take the files and documents to a safer place.

Nick Howitt wrote:

Hi Patrick, since the upgrade process is still manual, I do not see Kopano automatically replacing Zarafa, and the document also indicates you'd need to purchase Kopano first.

No doubt this is the case nowdays. But Zarafa will become obsolete at one time. I would like to know if there is a plan to replace it with Kopano. AFAIK there's Kopano Community release available at kopano.io .

Kopano Basic is still not a substitute for Zarafa Community in ClearOS 7 Home subscription. Can we expect this to happen anytime soon?

An important update - if anyone hits this kind of a problem.

What's been going on on my system was the systemd restarted clamd service due to timeouts. This went on for some time until systemd gave up and failed the service. After some time most other services that depend on clamd failed permanently aswell (in effect if I got clamd working, other services still did not run).

There's a way to tell systemd to timeout after a specific amount of seconds.
I've added a line:
"TimeoutStartSec=600"
to the clamd.service unit file inside /usr/lib/systemd/system/clamd.service

Now the problem is solved for me.

An important update - if anyone hits this kind of a problem.

What's been going on on my system was the systemd restarted clamd service due to timeouts. This went on for some time until systemd gave up and failed the service. After some time most other services that depend on clamd failed permanently aswell (in effect if I got clamd working, other services still did not run).

There's a way to tell systemd to timeout after a specific amount of seconds.
I've added a line:
"TimeoutStartSec=600"
to the clamd.service unit file inside /usr/lib/systemd/system/clamd.service

Now the problem is solved for me.

Hi, Tony.

Thanks for the tip. I will look into the systemd's framework to see what process is hogging the system and try to solve it there. I sure hope systemd is at such a stage in its development to offer some parameters for delayed service startups. Though that kinda beats its whole "run-everything-at-once" phylosophy. I might just be experiencing some expected side-effects which I have not seen before.
I would just hate it going back to the "slackware"-like solutions, putting stuff inside rc.local. I'll give systemd a fighting chance this time .
As far as the hw goes, It runs good enough once things settle down. I'm in no hurry to go shopping yet.

Hi. Replying to my own issue.
I've seen no apparent reason why clamd would work outside of systemd. However I have noticed that after I reboot Clearos server, its average load hits 10+. Observing things further, I've seen that systemd keeps restarting the service - I see clamd proces changing pid.
My best guess is that the machine is just too busy starting all the services it has to restart clamd several times. I see a lot of cpu usage goes to clamscan after boot. This goes on for a few minutes then settles - afterwards the clamd service starts and everything works.

It seems I will need to replace my hardware sometime soon.

Problem with clamav

This morning I've got an error from proxy server saying "Error: could not perform virus scan".
Doing some research I have found that there's been an upgrade of the "clearsdn-antimalware-6.1-20170209.1025.noarch" and "clearsdn-antispam-6.1-20170209.1025.noarch" packages. To my knowledge this was the only change made on the system from last night.
There are errors reported by dansguardian-av service - it cannot connect to /var/run/clamav/clamd.sock - indeed, no such file exists. No clamd.pid there either.
Trying to stop/start clamd.service using systemctl I got an error saying: "Job for clamd.service failed because a timeout was exceeded. See "systemctl status clamd.service" and "journalctl -xe" for details."
The service itself was in "activating" state - a clamd process was running. Since it failed to start, I've decided to run "systemctl stop clamd" and run it manually. Running "clamd restart" made it work again. I've tried restarting the server, tried to make the service run with systemd again and again with no luck.
Now, I run it manually, but I have to start it on my own if I restart the server.
There is no usefull info in the clamd.log file.
Can anyone help?

I've written to support - having a "home-edition Essentials" subscripton.
The answer I got was somewhat surprising. As if something is wrong with my configuration. Right.
I know a thing or two about linux, so I have managed to install the owncloud using yum.

So here is the solution for those, who experience the problem described in this thread:
as root run:
# yum install owncloud --nogpgcheck -y
# yum install app-owncloud

- the second command is without the "--nogpgcheck" parameter - it is not needed. As a matter of fact - it shoud never be needed.

If your menu is not updated. go to marketplace and find the "Owncloud for Home" - you can click "Configure" there. The menu will whow owncloud item later on.

@Ben, is this the new norm?

I've written to support - having a "home-edition Essentials" subscripton.
The answer I got was somewhat surprising. As if something is wrong with my configuration. Right.
I know a thing or two about linux, so I have managed to install the owncloud using yum.

So here is the solution for those, who experience the problem described in this thread:
as root run:
# yum install owncloud --nogpgcheck -y
# yum install app-owncloud

- the second command is without the "--nogpgcheck" parameter - it is not needed. As a matter of fact - it shoud never be needed.

If your menu is not updated. go to marketplace and find the "Owncloud for Home" - you can click "Configure" there. The menu will whow owncloud item later on.

@Ben, is this the new norm?