Crontab error: no crontab For [user]

Question

I'm seeing an error every time I do the command below. Why?

$crontab -l
no crontab for server

where server is the user account.

This issue comes about because the script in crontab doesn't work, so I've tried to break down the problem. This is what I have put in using crontab -e:

crontab -e
@reboot /usr/bin/teamspeak3-server_linux-amd64/ts3server_minimal_runscript.sh

I press ctrl + o and save it, reboot and find the script doesn't boot (even though the script itself does work if I double click it from the GUI). If I do a crontab -l after the reboot, I find I get the same error as above. Even before the reboot, if I try and open the crontab -e just after I saved this command inside of the file, the line of code isn't there.

This may help: https://superuser.com/questions/359580/error-adding-cronjobs-in-mac-os-x-lion My problem was resolved. — Daebarkee, Apr 28 '17 at 19:09

score 36 · Answer 1 · answered Jun 28 '15 at 13:05

36

That's probably because this user does not have a crontab, yet. You can create a crontab for this user by calling:

crontab -e

answered Jun 28 '15 at 13:05

binfalse

5,528
4
27
28

Ok I will update my question with some more info about my problem. Please, I beg you so much to help me fix it. – john smith Jun 28 '15 at 15:21
Ok I have updated my question to be more specific to the problem I'm facing. See if you can help. I'm really struggling here. – john smith Jun 28 '15 at 15:28
mac users see: https://superuser.com/a/540693/928461 – stevec Nov 02 '20 at 21:54
Thank you, I thought I could just go into the terminal and write a command and it will get automatically added to the crontab without having the need to create it. Your answer helped put things into perspective. – Talha Imam Mar 04 '22 at 16:45

score 8 · Answer 2 · edited Mar 27 '23 at 16:33

8

If you get the message "No crontab for username" type the following:

sudo crontab -u username -e

You will be asked to select an editor from a menu. Then a default file will open.

Save the file without naming it.

To check that the file was successfully created type:

crontab -l

edited Mar 27 '23 at 16:33

Stephen Kitt

434,908

answered May 18 '19 at 16:39

John Wayland Bales

181

score 3 · Answer 3 · answered Jun 28 '15 at 15:14

3

The user server does not have any schedule job in crontab so crontab -l outputs that information, not an error. Normally, you can find a user's crontab file in directory /var/spool/cron/crontabs.

answered Jun 28 '15 at 15:14

unsung

41

The reason it doesn't is because I can't make a job in that file that it remembers. I've updated my post, please check it now. – john smith Jun 28 '15 at 16:37
After adding job to crontab, what is the result of crontab -l? @johnsmith – unsung Jun 29 '15 at 10:23
2

Hi I have fixed this now. It turns out the actual root cause of the problem was that I was using ctrl+z to close nano (sends process to background) rather than ctrl+x, so the cron job was not installing. – john smith Jun 30 '15 at 10:11

score 0 · Answer 4 · answered Oct 13 '20 at 18:39

For me this was a silly mistake, I was setting up a cron using sudo and then running the crontab -l without sudo, so I was setting up the cros on root a/c and checking on the user's account due to which it was not finding the crons which were set up.

When I ran sudo crontab -l it gave me all the crons which had been set up correctly.

score 0 · Answer 5 · answered Oct 19 '21 at 23:25

0

In my case (Oracle Linux) it was complaining about the absence of files under /tmp/ It turned out that the folder was removed earlier. After creating /tmp again - it works like a charm. I hope it'll help someone.

answered Oct 19 '21 at 23:25

Andriy Boyko

111
2

Sanket Wahane · Answer 6 · 2021-11-15T13:21:32.523

-1

Here's the syntax or example for given problem:

`root@tacktile-desktop:/home/tacktile/Downloads# (crontab -u root -l ; echo "*/2 * * * * /usr/sbin/logrotate /etc/logrotate.conf") | crontab -u root -`

root@tacktile-desktop:/home/tacktile/Downloads# crontab -l */5 * * * * /usr/sbin/logrotate /etc/logrotate.conf */5 * * * * //usr/bin/bash /usr/binaries/scripts/tomcatlogs.sh */5 * * * * /usr/bin/bash /usr/binaries/scripts/tomcatlogs.sh */5 * * * * /usr/sbin/logrotate /etc/logrotate.conf */2 * * * * /usr/sbin/logrotate /etc/logrotate.conf

edited Nov 15 '21 at 13:21

answered Nov 15 '21 at 13:19

Sanket Wahane

1

1

Welcome to the site, and thank you for your contribution. Please note that brevity is acceptable, but fuller explanations are better. You may want to add a note why you think this approach will solve the OPs problem. – AdminBee Nov 15 '21 at 13:21

score -3 · Answer 7 · answered Jun 25 '19 at 10:17

-3

Your crontab not run. You need to run your command on the root with 4 steps:

Step 1: crontab -e
Step 2: o (o in alphabet)
Step 3: Fill your command. Ex: */2 * * * * root /usr/local/auto/restart.sh >/dev/null 2>&1 
Step 4: Exit

ESC :wq Enter

Review your CMD –> crontab -l . It was saved here(/var/spool/cron)

Source: https://thuthuatcaidat.com/sua-loi-no-crontab-for-root/

answered Jun 25 '19 at 10:17

Oanh Mai

1

1

This actually doesn't answer the question since author ot the question already performed these steps – mrc02_kr Jun 25 '19 at 10:25

Crontab error: no crontab For [user]

7 Answers7

Linked