We build. You grow.

Get best community software here

Start a social network, a fan-site, an education project with oxwall - free opensource community software

email notifications about a new private message are not sent | Forum

ross Team
ross Feb 15 '16
Provide me your cron command? is it wget?
tammy harris
tammy harris Feb 15 '16
i have try wget curl and direct all the same 
curl seams give less trouble 
ross Team
ross Feb 15 '16
you need to try local again and see if that overloads your cron


Login to your server via SSH

- Run cd [path-to-your-Oxwall-homedir]/ow_cron command to enter the Cron folder

- Run pwd command

- You will see the path to the Cron folder (e. g. /home/yoursite/public_html/ow_cron)

- Run which php command

- You will see the path to PHP (e. g. /usr/local/bin/php)

Put two paths you got into one: path to PHP/path to Cron folder: For example:

/usr/local/bin/php /home/site/public_html/ow_cron/run.php

Use this command in Add New Cron Job section in cPanel.

Note: contact your hosting company if you have troubles with connecting via SSH.

tammy harris
tammy harris Feb 15 '16
cron is set to direct just need wait on get server mails
tammy harris
tammy harris Feb 15 '16
Time: Mon Feb 15 22:17:50 2016 

+1100 PID: 8588 (Parent PID:8586) 

Account: mine

 Uptime: 108 seconds

/home/virtfs/mine/usr/local/bin/php  

Command Line (often faked in exploits):

 /usr/local/bin/php /home/mine/public_html/ow_cron/run.php 

 Network connections by the process (if any):

 tcp: 208.67.20.49:56193 -> 195.20.205.9:80

The Forum post is edited by tammy harris Feb 15 '16
tammy harris
tammy harris Feb 15 '16
i can see another problem there
use direct
208.67.20.49:56193 -> 195.20.205.9:80

its connect unsecured not ssl port 80
and is use main server ip not dedicated ip 

 
in use curl 208.67.20.50:48866 -> 208.67.20.50:443

is connect ssl port  443
and is use dedicated ip 

The Forum post is edited by tammy harris Feb 15 '16
ross Team
ross Feb 15 '16
Ok, now disable all your plugins one by one, we need to find out which one takes so much time for the cron run 
ross Team
ross Feb 15 '16
one request per topic
tammy harris
tammy harris Feb 15 '16

and thats from spam killer plugin plugin

ip 195.20.205.9   is  stop forum spam 

maybe the url rewrites is stuffing with that as well being none ssl 



ross Team
ross Feb 15 '16
It has nothing to do with this, disable plugins one by one check your cron process ID time
tammy harris
tammy harris Feb 15 '16



ross there no way in hell i am going to disable one plugin a day just to see whats the problem
it would take me a month
the simple fact is that its stupid to have everything on one cron 
no other script does it 
and would take oxwall 2 minutes to fix 

and all this bullcrap is a huge waste of time 

5 pages now in that time you could of fixed the cron to 2 runs 30 times now 

but like everything else here you have to argue for week and months on problems 
and when finally get the problem across and is marked to be fixed it never does get fixed 

  
tammy harris
tammy harris Feb 15 '16
every one else would say opps yes that is a stuff up only one cron is stupid we will fix it now 

and they fix it 
not mark it to be fixed and have a product developer who picks what will be fixed and what wont be fixed

no lets not fix the cron let waste our time on make something new that only half works and makes another 10 problems that we wont bother to fix   
tammy harris
tammy harris Feb 15 '16
oxwall is a company here to make money from there plugins and so is skaffer

you cant make money on something that dont work
you cant make money on something that you dont fix anything
you cant make money on something that crashes on every update
you cant make money on something that over 80% of plugins do not work or not as they should 
you cant make money on something that is so hard to get support 
you cant make money on something that is so dam hard to report problems 
tammy harris
tammy harris Feb 15 '16
Time: Tue Feb 16 00:09:03 2016 +1100

Account: mine

Resource: Virtual Memory SizeExceeded: 928 > 500 (MB)

Executable: /home/virtfs/mine/usr/local/bin/php

Command Line: /usr/local/bin/php /home/mine/public_html/ow_cron/run.php

PID: 25339 (Parent PID:25338)

Killed: No


now we are back to cron use almost 1 gb ram 

The Forum post is edited by tammy harris Feb 15 '16
tammy harris
tammy harris Feb 15 '16
theres heaps of port 465 so thats try send mail taking 65 seconds 
thats 65 seconds for cron to remove  mails from db to mail server
so its not just 3rd party plugins is base plugins

ONE CRON CAN NOT DO EVERYTHING 
The Forum post is edited by tammy harris Feb 15 '16
tammy harris
tammy harris Feb 15 '16
search the net on cron jobs overlapping causeing problems

Each cron job is executed independent of any other jobs you may have specified. This means that your long-lived script will not impede other jobs from being executed at the specified time.

If any of your scripts are still executing at their next scheduled cron interval, then another, concurrent, instance of your script will be executed.

This can have unforeseen consequences depending on what your script does. I would recommend reading the Wikipedia article on File Locking, specifically the section on Lock files. A lock file is a simple mechanism to signal that a resource — in your case the someScript3.sh script — is currently 'locked' (i.e. in use) and should not be executed again until the lock file is removed.

tammy harris
tammy harris Feb 15 '16
point is cron should not run overlapping 

cron should not be one run 

really there should be 3 
1 mails
2 ow base plugins
3 3rd party plugins 
tammy harris
tammy harris Feb 15 '16
i have set my cron run every 2 minutes this should get my mails flowing 
as theres no way this will ever be fixed 
tammy harris
tammy harris Feb 15 '16
cron set to 2 minutes so they do not overlap and stuff each other up and mail is flowing again 

so no more bullcrap the problem is not cron




tammy harris
tammy harris Feb 15 '16
each on of them is 100 mails sent 
Pages: « 1 2 3 4 5 6 »