I once had a functioning cron job. Then it stopped working. Now, after the cron attempts to run, I get an error reading, "Unable to set uids."
My current cron is:
<songxxxx@xxxxxx> wget -O /dev/null "https://songxxxxxxxxxxld.com/xxxxx/index.php?option=com_community&task=cron" >/dev/null 2>&1
This worked previously.
I tried your suggestions of updating JomSocial (I'm now using 4.3.4). I also checked my AWS credentials. Nothing there has changed. If I manually run the cron, it will process. Videos are still able to be uploaded. However, there is no automatic processing of activity AND some activity never shows up in my Activity area within JomSocial.
Can you help?
Hi,
I tried run cron job manually, and still get the issue like this,
0 - S3::putObject(): [SignatureDoesNotMatch] The request signature we calculated does not match the signature you provided. Check your key and signing method.
which this is coming from amazon S3
if you have issue on cron configuration
<songxxxx@xxxxxx> wget -O /dev/null "
songxxxxxxxxxxld.com/xxxxx/index.php?opt..._community&task=cron
" >/dev/null 2>&1
I suggest you use 3rd party cron job services like easycron.com
thank you!
Thank you for the feedback. Can you tell me why I would be getting an issue with Amazon S3? Have you seen anything like this before? Would creating new credentials be a possible fix? Is there something else I should try on the Amazon end?
Also, if I use a third-party option to run a cron... will Amazon S3 still work? Seems I need to cure the Amazon issue for things to work. Also, I would like to try to add a forum to the JomSocial site and it appears I will need a working site (working cron) for a forum to work.
Laurie
Hi,
I am not sure it related with Amazon S3 or from our code itself, but please you try new credentials and let me know how it goes..
the 3rd party cron job is not related with amazon s3 itself, this is different issue, so to avoid the confusing with cron job code, you can use 3rd party cron services like easycron.com, it will be easier, you just need to put the URL address and set the time :)
thank you
UPDATE: After changing Amazon credentials I can now run a manual cron from Mail Queue as I wrote, below. However, over on my e-mail where I receive an email each time the cron runs, I am getting this message:
/usr/local/cpanel/bin/jailshell: dev/null: No such file or directory
Do you have anything to cure this?
Dimas wrote: Hi,
I am not sure it related with Amazon S3 or from our code itself, but please you try new credentials and let me know how it goes..
the 3rd party cron job is not related with amazon s3 itself, this is different issue, so to avoid the confusing with cron job code, you can use 3rd party cron services like easycron.com, it will be easier, you just need to put the URL address and set the time :)
thank you
Hi Laurie,
Seems you are still using cron from your cPanel right ? please you change the code to be like this
lynx -source "https://songxxxxxxxxxxld.com/xxxxx/index.php?option=com_community&task=cron" > /dev/null
Not certain why you had this problem. Did you go to the correct directory? I don't have the site in the root directory.
I will test the credentials I left you and see if I made an error.
In the meantime, I've given up on Cpanel and gone to cron-job.org for the cron.
Dimas wrote: Hi Laurie,
Seems you are still using cron from your cPanel right ? please you change the code to be like thislynx -source "https://songxxxxxxxxxxld.com/xxxxx/index.php?option=com_community&task=cron" > /dev/null
I always have problem to connect your backend, and always get this, so hard for me to inspect the issue further
thank you!
This was my error. I gave you a bad password. Sorry.
I will make sure to provide more accurate information in the future.
For now, the cron issue is solved. Thanks!
Laurie wrote: Not certain why you had this problem. Did you go to the correct directory? I don't have the site in the root directory.
I will test the credentials I left you and see if I made an error.
In the meantime, I've given up on Cpanel and gone to cron-job.org for the cron.
Dimas wrote: Hi Laurie,
Seems you are still using cron from your cPanel right ? please you change the code to be like thislynx -source "https://songxxxxxxxxxxld.com/xxxxx/index.php?option=com_community&task=cron" > /dev/null
I always have problem to connect your backend, and always get this, so hard for me to inspect the issue further
thank you!
Glad to know that, you can open this ticket again if this issue still happens, and in the future please make sure the password is correct :)