What the heck is wrong with cron?
*/1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
in /etc/cron.d doesn't get executed at all (ran from console works of course!). But the SAME file in /tmp runs flawlessly:
*/1 * * * * nobody /usr/bin/php /tmp/cron.php
It's CentOS7 on VPS with no SELinux.
I've noticed similiar behavior before (on bare metal server with SELinux).
On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
What the heck is wrong with cron?
*/1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
in /etc/cron.d doesn't get executed at all (ran from console works of course!). But the SAME file in /tmp runs flawlessly:
Just to be clear:
[root@kohrin cron.d]# sudo -u nobody /usr/bin/php /var/www/html/osticket/api/cron.php
Works as expected.
Why bother with */1? Wouldn't that be the same as just *? On Apr 22, 2016 5:48 PM, "Marcin Trendota" moonwolf.rh@gmail.com wrote:
On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
What the heck is wrong with cron?
*/1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
in /etc/cron.d doesn't get executed at all (ran from console works of course!). But the SAME file in /tmp runs flawlessly:
Just to be clear:
[root@kohrin cron.d]# sudo -u nobody /usr/bin/php /var/www/html/osticket/api/cron.php
Works as expected.
-- Over And Out MoonWolf _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Fri, Apr 22, 2016 at 05:58:39PM -0400, Steven Ford wrote:
Why bother with */1? Wouldn't that be the same as just *? On Apr 22, 2016 5:48 PM, "Marcin Trendota" moonwolf.rh@gmail.com wrote:
I had the same question. Plus, the man page says "'/<number>' specifies skips of the number's value through the range." That could be interpreted to be skip each minute.
On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
What the heck is wrong with cron?
*/1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
in /etc/cron.d doesn't get executed at all (ran from console works of course!). But the SAME file in /tmp runs flawlessly:
Just to be clear:
[root@kohrin cron.d]# sudo -u nobody /usr/bin/php /var/www/html/osticket/api/cron.php
Works as expected.
-- Over And Out MoonWolf _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
End of included message <<<
Anything interesting in the logs?
sudo journalctl -xf _SYSTEMD_UNIT=crond.service
On Saturday 23 of April 2016 10:08:54 AM Kahlil Hodgson wrote:
Anything interesting in the logs?
sudo journalctl -xf _SYSTEMD_UNIT=crond.service
Don't know.
[root@kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service -- Logs begin at śro 2015-12-02 22:34:16 CET. -- kwi 22 23:11:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:13:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:15:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:17:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:18:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:23:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:28:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:30:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:32:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:34:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron)
On 23 April 2016 at 10:25, Marcin Trendota moonwolf.rh@gmail.com wrote:
Anything interesting in the logs?
sudo journalctl -xf _SYSTEMD_UNIT=crond.service
Don't know.
[root@kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service
...
(/etc/cron.d/osticket-cron) kwi 22 23:28:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:30:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:32:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:34:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron)
That shows cron triggering your script once every 2 minutes, which makes _maybe_ makes sense with '*/1'.
So nothing wrong with you cron line, so its probably something in your environment.
If your script is failing, I would normally expect it to output some error messages. Cron will email this to root by default. Maybe check /var/spool/mail/root? Or set MAILTO="youremail address" at the top of your cron script.
Seemed strange is all. Can the nobody user read down into /var/www/html/osticket/api? If it works in tmp, maybe permissions are the issue. On Apr 22, 2016 7:57 PM, "Marcin Trendota" moonwolf.rh@gmail.com wrote:
On Friday 22 of April 2016 5:58:39 PM Steven Ford wrote:
Why bother with */1? Wouldn't that be the same as just *?
That's for debugging. It'll be */5 for production purposes.
Anyway. It still doesn't work. Why?
-- Over And Out MoonWolf _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 4/22/2016 5:27 PM, Marcin Trendota wrote:
On Friday 22 of April 2016 8:10:04 PM Steven Ford wrote:
Seemed strange is all. Can the nobody user read down into /var/www/html/osticket/api? If it works in tmp, maybe permissions are the issue.
As i said. sudo works as a charm. Cron rebels...
remember that cron doesnt run any user profile or login scripts, so it starts with no environment variables set. fully specify any paths in the commands run by cron..
After many hours of struggling with it, i did "crontab -u nobody -e" and put the same line in private nobody's crontab. Looks like it's working. Don't know why and how.
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
Sincerely Andy
While this is a developer edition only
i delete rm -rf $HOME/.mozilla
this be can be done better but now flash looks ok to
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.616 Status: Aktiviert Shockwave Flash 11.2 r202
On 04/26/2016 12:03 AM, Andreas Benzler wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
As far as I can tell Adobe stopped supporting flash on Linux and a deprecated vulnerable version is all that is available.
I would highly advice against using the flash plugin. Unfortunately advertising networks do not adequately vet flash based advertisements resulting in malware being distributed via flash on common websites we all visit, including news sites.
Usually the malware targets Windows but there is some that targets Linux and will encrypt files on your system asking a ransom for the decryption key.
Just say no to flash.
That's not what you asked, but that's what I advise.
On 2016-04-26, Alice Wonder alice@domblogger.net wrote:
On 04/26/2016 12:03 AM, Andreas Benzler wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
As far as I can tell Adobe stopped supporting flash on Linux and a deprecated vulnerable version is all that is available.
No, flash is still supported by Adobe on linux. Only security updates, though. No new features. The last update was on 8 April.
I would highly advice against using the flash plugin. Unfortunately advertising networks do not adequately vet flash based advertisements resulting in malware being distributed via flash on common websites we all visit, including news sites.
Usually the malware targets Windows but there is some that targets Linux and will encrypt files on your system asking a ransom for the decryption key.
Just say no to flash.
I agree with that sentiment. Sometimes, however, there are circumstances in which you just can't say no.
That's not what you asked, but that's what I advise.
In case anyone else has this problem, the issue seems to be that firefox retains stale information about the plugin status. You can force a refresh as follows:
1. Exit firefox 2. Uninstall flash-plugin 3. Start firefox, and exit again 4. Install flash-plugin
Date: Tuesday, April 26, 2016 09:26:11 +0000 From: Liam O'Toole liam.p.otoole@gmail.com
On 2016-04-26, Alice Wonder alice@domblogger.net wrote:
On 04/26/2016 12:03 AM, Andreas Benzler wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
In case anyone else has this problem, the issue seems to be that firefox retains stale information about the plugin status. You can force a refresh as follows:
- Exit firefox
- Uninstall flash-plugin
- Start firefox, and exit again
- Install flash-plugin
My flash install is showing 616 both in the binary and as reported from "about:plugins".
When I've had reason to look at this the past things were always in sync. My standard approach is to make certain that all instances of my FF version that uses flash are closed before I install from the adobe repo. I've never had to uninstall/reinstall the plugin.
I agree with generally trying to avoid flash (and cookies and javascript) so have different FF versions and instances that I use based on what is needed and what I'm willing to allow a site to use.
Hello Andreas,
On Tue, 26 Apr 2016 09:03:12 +0200 Andreas Benzler andreas@benzlerweb.de wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
On my 3 CentOS 6.5 systems here (all up-to-date), only one shows '577' whereas 616 is installed and the 577 binary has gone. Strange, I still didn't get how to "fix" this, even if doesn't sound overcritical to me.
Regards,
Do as allready commited:
close firefox uninstall fash start firefox close firefox install flash hopefully this works for you.
config is inside $HOME/.mozzilla
Am Dienstag, den 26.04.2016, 13:54 +0200 schrieb wwp:
Hello Andreas,
On Tue, 26 Apr 2016 09:03:12 +0200 Andreas Benzler andreas@benzlerweb.de wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
On my 3 CentOS 6.5 systems here (all up-to-date), only one shows '577' whereas 616 is installed and the 577 binary has gone. Strange, I still didn't get how to "fix" this, even if doesn't sound overcritical to me.
Regards,
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hello Andreas,
On Tue, 26 Apr 2016 15:18:15 +0200 Andreas Benzler andreas@benzlerweb.de wrote:
Do as allready commited:
close firefox uninstall fash start firefox close firefox install flash hopefully this works for you.
config is inside $HOME/.mozzilla
It simply worked, thanks!
Regards,
Am Dienstag, den 26.04.2016, 13:54 +0200 schrieb wwp:
Hello Andreas,
On Tue, 26 Apr 2016 09:03:12 +0200 Andreas Benzler andreas@benzlerweb.de wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
On my 3 CentOS 6.5 systems here (all up-to-date), only one shows '577' whereas 616 is installed and the 577 binary has gone. Strange, I still didn't get how to "fix" this, even if doesn't sound overcritical to me.
Regards,
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Tue, 26 Apr 2016 13:54, wwp wrote:
Hello Andreas,
On Tue, 26 Apr 2016 09:03:12 +0200 Andreas Benzler wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
On my 3 CentOS 6.5 systems here (all up-to-date), only one shows '577' whereas 616 is installed and the 577 binary has gone. Strange, I still didn't get how to "fix" this, even if doesn't sound overcritical to me.
Cause is the file "pluginreg.dat" in the Firefox profile folder. It stores the version info, but upon updates of the flashplayer, some times it will not get updated. Two ways to 'cure' that:
a) Uninstall flash, (Re-)start Firefox, close Firefox, install new version, start Firefox. (Due to the 'absence' of flash, the 'pluginreg.dat' gets removed, and afterwards it will get recreated with the new info)
b) Close firefox, remove 'pluginreg.dat', update flashplayer, start firefox
- Yamaban
On Tue, Apr 26, 2016 at 07:04:41PM +0200, Yamaban wrote:
On Tue, 26 Apr 2016 13:54, wwp wrote:
Hello Andreas,
On Tue, 26 Apr 2016 09:03:12 +0200 Andreas Benzler wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
On my 3 CentOS 6.5 systems here (all up-to-date), only one shows '577' whereas 616 is installed and the 577 binary has gone. Strange, I still didn't get how to "fix" this, even if doesn't sound overcritical to me.
Cause is the file "pluginreg.dat" in the Firefox profile folder. It stores the version info, but upon updates of the flashplayer, some times it will not get updated. Two ways to 'cure' that:
a) Uninstall flash, (Re-)start Firefox, close Firefox, install new version, start Firefox. (Due to the 'absence' of flash, the 'pluginreg.dat' gets removed, and afterwards it will get recreated with the new info)
b) Close firefox, remove 'pluginreg.dat', update flashplayer, start firefox
What always works for me, figured out after MUCH head-banging is: c) exit firefox, do yum install for the new package, restart firefox. no need to delete anything.
On Tue, 2016-04-26 at 19:04 +0200, Yamaban wrote:
On Tue, 26 Apr 2016 13:54, wwp wrote:
Hello Andreas,
On Tue, 26 Apr 2016 09:03:12 +0200 Andreas Benzler wrote:
Hello every one I installed the official flash plugin from adobe
About Plugins tells me:
Datei: libflashplayer.so Pfad: /usr/lib64/flash-plugin/libflashplayer.so Version: 11.2.202.577 Status: Aktiviert (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202But it is:
strings /usr/lib64/mozilla/plugins/libflashplayer.so | grep 616 FlashPlayer_11_2_202_616_FlashPlayer LNX 11,2,202,616 11.2.202.616 drm/%s/%s/%s/11.2.202.616%s
Any ideas?
<snip>
b) Close firefox, remove 'pluginreg.dat', update flashplayer, start firefox
This is what I've done for years when issues arise. Before doing so however,
cp -a pluginreg.dat pluginregdat.dat.YYMMDD
Just in case something is scrogged.
- Yamaban
<snip>
Bill
-
Alice Wonder -
Andreas Benzler -
Bill Maltby (C4B) -
Fred Smith -
John R Pierce -
Jon LaBadie -
Kahlil Hodgson -
Liam O'Toole -
Marcin Trendota -
Richard -
Steven Ford -
wwp -
Yamaban