Serious loading problem

[erdsiger]

Hi,

I have a serious problem. Today when I wanted to look at my site, it loaded the content, but hasn't finished the loading, it just loaded something but couldn't imagine what. I surprised when saw the server statistics (look at the first attached image). After that I managed to find out, that the server was always trying to load the cron-image.php file (second attached image, I removed the IP addresses column and some other lines which were from an other site). I was trying to solve the problem, but the only solution was to rename the cron-image.php. After this, everything worked normally.

I have two questions. What causes this problem and what's the solution? Because I had to rename the cron-image.php file, what functions doesn't work now?

If it is necessary, I can give you more information or statistics. Thanks in advance!

[boccio]

cron-image.php triggers cron jobs for Vivvo, such as newsfeed importer and newsletter. I have no idea why would this make such spikes on CPU usage, please give us access to your logs/server so we can analyze it.

[Saboteur]

boccio, just got same problem like erdsiger. Create ticket CEM-35506-526 whith more detailed information. Also rename the cron-image.php

[erdsiger]

I sent you, boccio a PM, but haven't got any response.

[Simon]

I have the same problem here too

[utvara]

Here is a quick fix for cron-image issue. This will be included in upcoming 4.0.3 release. Apply this only if you are experiencing high server load on cron image file.

Slobodan Utvic,
Vivvo CMS lead developer

[qwadrat]

I just uploaded "cron_image_patch.zip" (the contained cron-image.php). Problem is not solved yet. CPU usage: 100% :confused:

Update
---
Just deleted "cron_image.php" (mydomain.tld/cron_image.php) and everything works fine.

I guess that's not the way it should be :confused:

[Alex]

Are you using 4.0.3 version?

[qwadrat]

Hello Alex,

the Backend tells me "You are currently running Vivvo CMS v4.0.2 build 2379.".

... an update is the solution for the problem?

[shketuljko]

Please update your script to 4.0.3 first and tell us do you have problem with CPU then.