• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

cron jobs not functioning after migration

K

kselphelp

Guest
first off, i'm not sure if this is the right forum, i'm fairly confused by what i'm seeing here, so apologies ahead of time.

i have recently gotten a new server with plesk 8.0.1, which i use via windows xp. i know next to nothing about linux/unix, i navigate all of my actions via the windows xp/plesk interface, so again, i'm somewhat confused by these forums, as there is no area for plesk 8 for windows.

in any case, i utilized the migration manager to bring everything from the old server (which had plesk 7.5 reloaded). after several failed attempts, it finally seemed to happen successfully. or so i thought.

it was recently brought to my attention that all of my cron jobs (created via plesk, not ssh or whatever) are not functioning. they all show up under the domain, but they don't work anymore. due to the nature of that particular domain's website, this is creating havoc for the users. perhaps this is a known issue?

the tasks are fairly elementary in nature, they are all like this:
mv ./httpsdocs/<directory>/<filename> ./httpsdocs/<directory>/<filename2>

i don't know if the path has been changed or what, i have no idea how to determine such, nor do i have any idea how to telnet, etc, and i need this resolved in a more expeditious fashion than tech support is apparently able to provide.

i'm begging here.

thanks in advance
 
Sounds like your cron daemon is not running.

If you have SSH access to your box, then enter the following at the command line:

ps aux | grep cron

You should get a response back something like:
root 32691 0.0 0.0 2472 908 ? Ss Nov20 0:00 crond

If you do not see this response then start the crond daemon by entering: /etc/rc.d/init.d/crond start
 
that did it, thanks. now if i could just figure out how get rid of the two failed attempts at migration which decided to store themselves somewhere on the server anyway, i'd be cool.
 
Look for /usr/local/psa/PMM

The temp migration files should be stored somewhere in this area. I do not remember the exact path
 
ls /usr/local/psa/PMM
PleskX.tar.signed archives mb2md.pl scout.pl var
agents log4cpp.properties plesk.dtd tmp

ls /tmp
____build_installing.log
____build_problems.log
horde-3.1.2.log
imp-4.1.1.log
keyupdate.php
kronolith-2.1.1.log
mnemo-2.1.log
php5-configurator.log
psa-autoresponder-1GT8IZ
psa-autoresponder-1SyvpJ
psa-autoresponder-2irv26
psa-autoresponder-2w2vj6
psa-autoresponder-3dtHBu
psa-autoresponder-3g3zUG
psa-autoresponder-3jkDFp
psa-autoresponder-48n717
psa-autoresponder-5JTLU4
psa-autoresponder-5KlXGS
psa-autoresponder-69zdnJ
psa-autoresponder-6Y54gY
psa-autoresponder-76BloN
psa-autoresponder-7DHkfI
psa-autoresponder-7XfHOF
psa-autoresponder-8HHl9J
psa-autoresponder-8rFUq9
psa-autoresponder-9En9y9
psa-autoresponder-9Pdznj
psa-autoresponder-AVDhTV
psa-autoresponder-DDxckH
psa-autoresponder-DZTKj3
psa-autoresponder-DxOYkj
psa-autoresponder-E7wWIL
psa-autoresponder-EJbvhX
psa-autoresponder-Ea2wzu
psa-autoresponder-EltfB9
psa-autoresponder-EpMI7B
psa-autoresponder-GqNf36
psa-autoresponder-IPqhGc
psa-autoresponder-IUVxV3
psa-autoresponder-KJ6mLo
psa-autoresponder-KXikQw
psa-autoresponder-N3nNCO
psa-autoresponder-PJFvgT
psa-autoresponder-PnZczT
psa-autoresponder-RFnqli
psa-autoresponder-RHiv4W
psa-autoresponder-SgSCEq
psa-autoresponder-T3mTxv
psa-autoresponder-TBghMM
psa-autoresponder-TMlLue
psa-autoresponder-TwMkrv
psa-autoresponder-W7I3x1
psa-autoresponder-Xs1Rkt
psa-autoresponder-Y89q0s
psa-autoresponder-YsZHos
psa-autoresponder-YvlAw9
psa-autoresponder-ZGs4CV
psa-autoresponder-ZSjWu1
psa-autoresponder-ZrYg9n
psa-autoresponder-baQ4F4
psa-autoresponder-bigFmW
psa-autoresponder-c4XFrD
psa-autoresponder-cqmrMe
psa-autoresponder-dTeMV1
psa-autoresponder-dZIh4P
psa-autoresponder-dlyKWO
psa-autoresponder-eUDskP
psa-autoresponder-fisBNi
psa-autoresponder-fsh0iA
psa-autoresponder-h4My5D
psa-autoresponder-jxDCxa
psa-autoresponder-mzuxlR
psa-autoresponder-nydD0p
psa-autoresponder-o9S6hp
psa-autoresponder-oRYl9w
psa-autoresponder-pQnXXd
psa-autoresponder-puGdZ0
psa-autoresponder-qyBukO
psa-autoresponder-sTfYOz
psa-autoresponder-tOB3UM
psa-autoresponder-taKH5M
psa-autoresponder-tah5Yb
psa-autoresponder-uRCzCW
psa-autoresponder-vqe92d
psa-autoresponder-wtBjEi
psa-autoresponder-xCTu1P
psa-autoresponder-zxRu9F
psa-courier-imap-3.0.8-fc4.build80060613.20.log
psa-hotfix80060618.11.log
psa-qmail.log
psa_8.0.1_FedoraCore_4_build80060613.20_installing.log
psa_8.0.1_FedoraCore_4_build80060613.20_pam_install.log
psa_8.0.1_FedoraCore_4_build80060613.20_pam_problem.log
psa_8.0.1_FedoraCore_4_build80060613.20_problems.log
psa_8.0.1_FedoraCore_4_build80060713.16_installing.log
psa_8.0.1_FedoraCore_4_build80060713.16_problems.log
psa_8.0.1_FedoraCore_4_build80060727.19_installing.log
psa_8.0.1_FedoraCore_4_build80060727.19_problems.log
turba-2.1.1.log

don't know how to delete/remove any of this though
 
these are not the temp migration files. I will look again at where they should be stored....
 
Back
Top