Author Topic: [CWP Pro] Bug Cron Jobs Section not usable.  (Read 1794 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
[CWP Pro] Bug Cron Jobs Section not usable.
« on: December 28, 2022, 09:14:31 PM »
I'm currently using two CWP Pro licenses and have been a CWP Pro user for about 4 years, however I'm now encountering a bug with the CWP panel under cron jobs. I can edit them, press run or pause and they all say successful but in turn they actually do nothing, you cannot edit them or delete them either.

This just started randomly occurring as of today.

Any suggestions?

Code: [Select]
curl http://dl1.centos-webpanel.com/files/s_scripts/sinfo.sh|sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   899  100   899    0     0   3281      0 --:--:-- --:--:-- --:--:--  3269
===============================================
Kernel:
Linux 4.18.0-425.3.1.el8.x86_64 #1 SMP Tue Nov 8 14:08:25 EST                                                                                                                                                              2022 x86_64 x86_64 x86_64 GNU/Linux

CPU info:
model name      : Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz

Release:
AlmaLinux release 8.7 (Stone Smilodon)

Arch:
x86_64

Virtualization Type:
xen
xen-hvm

Memory:
              total        used        free      shared  buff/cache   available
Mem:           3710        1645         488         150        1576        1680
Swap:          6143           0        6143

MySQL info:
mysql  Ver 15.1 Distrib 10.4.27-MariaDB, for Linux (x86_64) using readline 5.1

Disk Info:
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.8G     0  1.8G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           1.9G  8.5M  1.9G   1% /run
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/xvda2      200G   33G  167G  17% /
/dev/xvda1      217M  142M   60M  71% /boot
tmpfs           372M     0  372M   0% /run/user/0


#
# /etc/fstab
# Created by anaconda on Thu Oct  3 03:40:36 2019
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/xvda2 / xfs rw,seclabel,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquo                                                                                                                                                             ta 0 0
UUID=6314bd4f-69f8-400f-acae-f4de99b3ecd1 /boot                   ext4    defaul                                                                                                                                                             ts        1 2
/swapfile swap swap defaults 0 0


Apache PHP info:
PHP 7.4.32 (cli) (built: Oct  6 2022 18:16:21) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies

Apache start script check:
grep: /etc/init.d/httpd: No such file or directory

CWP Admin check:
/usr/local/cwpsrv/htdocs/admin

CWP version:
0.9.8.1148
===============================================


Offline
*
Re: [CWP Pro] Bug Cron Jobs Section not usable.
« Reply #1 on: January 22, 2023, 12:07:17 PM »
The bug is still active.

The issue is that there's 2 cron files:

[file] /home/{username}/cron
[file] /var/spool/cron/{username}

CWP dashboard uses the user folder whereas the OS uses var/spool/cron

I have had to use the API and FTP to create my own fixes by FTP delete cron and recreate each time with API.

Cronjobs are critical and I'm surprised CWP has not sorted this still.
PLEASE REMOVE CAPTCHA.. IT'S ANCIENT AND A MASSIVE TIME WASTE BAD EXPERIENCE FOR USERS. THE MATH SOLUTION IS SUFFICIENT. OR HAVE IT ONCE AND REMEMBER IF I'M A HUMAN

Offline
*****
Re: [CWP Pro] Bug Cron Jobs Section not usable.
« Reply #2 on: January 22, 2023, 06:16:43 PM »
Cronjobs are critical and I'm surprised CWP has not sorted this still.
Well, I'm not too surprised. But I've learned to work around a lot. And at this point my 3 CWP servers are pretty stable so not a lot of ongoing action with configuration changes. And I do 1/2 the work in the terminal anyway because it's fine-grained configuration outside the scope of the CWP web interface.