I have approximately 125 emails from my Cron Daemon starting at 4:22 AM. All of them say this:
PHP Fatal error: Call to undefined function: iworx_check_restart() in /home/interworx/cron/iworx.php on line 84
They are coming in every 5 minutes, and I can’t think of any other cause besides an automatic update. Is anyone else experiencing this?
I have them, too (starting at 4:30 EST) … but coming from:
Cron <iworx@web1> cd /home/interworx/cron ; ./iworx.pex --fively
and saying:
Allowed memory size of 134217728 bytes exhausted (tried to allocate 0 bytes)
Unfortunately, the services aren’t responding on the box now, either. I can SSH in and reboot – but it’s not fixing the lack of httpd, nor the cron messages.
[root@web1 init.d]# ./httpd start
Flushing IPC Semaphores [ OK ]
Starting httpd: Syntax error on line 1 of /etc/httpd/conf.d/some.domain.com.conf:
/etc/httpd/conf.d/some.domain.conf:1: <VirtualHost> was not closed.
[FAILED]
The above some.domain.com.conf file in question has:
DocumentRoot /home/interworx/var/overage
Instead of their normal path. I assume (and wouldn’t be surprised that) this is the path to the “you’re over your bandwidth” default location (as they often go over their allocated amount) – but it’s never created this issue before.
This was indeed a new bug in 1.9.2, if you run yum update it’ll pull down the fix (auto update will apply it also).
Jimp - your problem is different from JayBaen, and I can’t reproduce that one here. You may want to open a support ticket if it isn’t resolved so we can check it out.
That’s correct, it should prevent this problem from happening again but you do need to manually add the
</VirtualHost> line to the end of any conf file that’s missing it.
I just got this error emailed to me. Its like the 3rd one, I think I deleted the others, but I only get one every once in a while, not slammed like others.
SUBJECT: Cron <iworx@server1> cd /home/interworx/cron ; ./iworx.pex --fively
/bin/bash: line 1: cd: /home/interworx/cron: Permission denied
/bin/bash: line 1: ./iworx.pex: No such file or directory
EDIT
I also got one right after that with the “–fifteenly” with the same error.
My guess is this was b/c of the small InterWorx update, especially b/c the time of these errors was during my “–daily” cron.
Is this permission error a new part of InterWorx with the latest upgrades? Or is this just a random non-eventful occurance?
I was going to ask if there was a way to shut down the --5’ly and --15’ly cron jobs while the --daily was running since the daily is very CPU intensive and was thinking that having the 5’ly and 15’ly overlapping the daily was the cause of my Apache not starting itself back up on the --daily httpd restart (I think my ticket is still in the system about that).
Also, this thread is about “iworx_check_restart()”. Is this a new function in the /cron/iworx.php file? And it is run every 5 mins?
I discovered another one of these today that crept up after some changes to a Siteworx account. I think this was the process I followed that created the error:
Siteworx account originally created in 1.8.x - no changes to options since creation.
It lived through the upgrades of 1.9.x and 2.0.x
Now, as a 2.0.x account, I enabled both CGI and Scriptworx for the account at the same time, and saved the changes.
After this point, the “fively” messages began pouring in, and httpd wouldn’t restart correctly (same as earlier issue in this thread).
I found the missing </VirutalHost> in that *.conf, inserted it and it solved the issue.
Just wanted to make sure if it’s a bug in upgrading any older Siteworx account within the 2.0 framework, you all know about it.
I know this has been a random bug for almost as long as I can remember. The last I’d heard they didn’t know for sure what caused it (other than the obvious). I was told to ignore it unless it became cronic. Any update on that?