Having a problem with at and batch queue execution. Help pls?

English Applications
#1

I am having an issue with using at with opensuse and I don’t understand why it does not seem to be working. In my crontab I have a command (sun.sh) that runs once per day. It runs fine and produces the following batch jobs:
jjh@linux:~/sunschedule> atq
33 Sat Apr 23 06:30:00 2016 a jjh —à corresponds to the sun is up
34 Sat Apr 23 20:10:00 2016 a jjh —à corresponds to the sun down script
The problem is, neither script gets executed. This worked fine in debian/Ubuntu. Protections for the script files are all 777. I do not get any errors…
I can execute sun.sh from my user CL and it works, generates the batch jobs, but the associated scripts are never executed. So what could be the problem and how can I track it down???

In my crontab I have:
PATH=/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin
#export PATH

run dusk-dawn calculation at 12:00 AM for LR light B4 to be run on Sun, T, Th (0,2,4)

0 0 * * * /home/jjh/sunschedule/sun.sh > /home/jjh/sunschedule/sunsched_output.txt

And sun.sh is:
sun=($(heyu show dawndusk)) # a function to get the dusk and dawn times via a program ‘heyu’

Get 2nd index

dawn=${sun[2]}

Get 6th index

dusk=${sun[6]}
echo "Sunrise is at "$dawn
echo "Sunset is at "$dusk

Actions to take:

at $dawn -f /home/jjh/sunschedule/sunup2.sh
at $dusk -f /home/jjh/sunschedule/sundown_b4.sh

sunup2.sh is:
echo “sun is up”

sundown_b4.sh is:
echo “sun down”
heyu on LivingRoomLight
The problem is sunup2.sh and sundown_b4.sh never get executed.

Any help is appreciated.
Thanks
J

#2

Is the at daemon running ? (systemctl status atd.service)

If yes, do you see any error messages in the system logs?

Hendrik

#3

Hmmmm well, if I interpret the information below correctly…apparently it is not running???..why wouldn’t it be? and how do I start it everytime I boot the machine?

jjh@linux:~> which at
/usr/bin/at
jjh@linux:~> which atd
which: no atd in (/home/jjh/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/lib/mit/bin)
jjh@linux:~> systemctl status atd.service
atd.service - Deferred execution scheduler
Loaded: loaded (/usr/lib/systemd/system/atd.service; disabled)
Active: inactive (dead)

Well now I really am confused…after doing the following, it looks to be running? …very confusing…
jjh@linux:~> pgrep -l atd
13587 atd
jjh@linux:~> echo echo hello world | at now
warning: commands will be executed using /bin/sh
job 35 at Sat Apr 23 15:12:00 2016
jjh@linux:~> ps aux | grep atd
jjh 12467 0.0 0.0 4396 1476 pts/3 S+ 15:13 0:00 grep --color=auto atd
at 13587 0.0 0.0 3048 592 ? Ss Apr20 0:00 atd
jjh@linux:~> whereis atd
atd: /usr/sbin/atd /usr/share/man/man8/atd.8.gz

Hopefully someone can clue me in on what is really going on…

#4

If you were using an old version of Debian, you would still have been using sysVinit.
Practically all current version of Linux distros including Debian have been adopting a different subsystem called systemd, which for various reasons performs better, manages subsystems better and is more efficient/performs better.

One of the features of systemd is that a distro can migrate gradually, and the older sysVinit init system is fully supported during transition and development. Not all older init files and commands are replaced immediately, and in these cases (likely includes your scenario), systemd simply creates Unit files which initially are little more than shells for the older files, commands and processes.

This becomes relevant because I suspect that you invoked/started your “at” command the old way which is still supported, but by doing so the systemd “shell” isn’t aware of what you’ve done. This is how you’re getting conflicting information. You can open the Unit file (which isn’t anything more than a configuration file) to verify that its contents simply invokes the command you likely ran directly plus any other options which may be relevant.

To find the name of the Unit file you should look at, inspect what is displayed when you run the “status” command. It should also include a snippet of relevant log data if the service couldn’t start, so I recommend you stop your atd manually and use the systemctl command for better info.

systemctl status atd.service

HTH,
TSU

#5

Ahhhhh, well that is begining to clear things up, but I still dont understand the situation enough to make progress. It was an older version of Debian (v6) but Ubuntu was a bit newer (Ubuntu server 10.1 LTS) If I interpreted your suggestions correctly, I logged in as my normal user, then su/root, and did the following, with no apparent success (at still is not running…) Additional suggestions appreciated…

linux:/home/jjh # systemctl status atd
atd.service - Deferred execution scheduler
Loaded: loaded (/usr/lib/systemd/system/atd.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-04-23 15:41:21 EDT; 6h ago
Main PID: 13994 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
linux:/home/jjh # systemctl stop atd
linux:/home/jjh # systemctl status atd
atd.service - Deferred execution scheduler
Loaded: loaded (/usr/lib/systemd/system/atd.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-04-23 15:41:21 EDT; 6h ago
Main PID: 13994 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
linux:/home/jjh # systemctl start atd
linux:/home/jjh # systemctl status atd
atd.service - Deferred execution scheduler
Loaded: loaded (/usr/lib/systemd/system/atd.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-04-23 22:09:47 EDT; 5s ago
Process: 5433 ExecStart=/usr/sbin/atd -f (code=exited, status=1/FAILURE)
Main PID: 5433 (code=exited, status=1/FAILURE)
linux:/home/jjh #

It appears to try and load but, failed? Oh, the syslogs are different in OpenSuse that what I am used to in slack/debian/ubuntu…there is no file ‘message.log’ so what file is system events/errors written to???
Thanks
J

#6

Use (as root) either

journalctl -b -u atd

or

journalctl -b | grep atd

to find out, what these FAILURE messages mean.

Hendrik

#7

Empty??
linux:/home/jjh # journalctl -b -u atd
– Logs begin at Fri 2016-01-15 17:05:48 EST, end at Sun 2016-04-24 09:23:08 EDT. –
linux:/home/jjh # journalctl -b | grep atd
linux:/home/jjh #

In addition, I went into the CL version of Yast and looked at ‘Services’…at is marked as ‘Enabled’ and marked as 'Inactive" So is this the base problem? How does one make it ‘Active’?
Thanks for your help
J

#8

“enabled” means “start at system boot”, “active” means running, “inactive” obviously not running. It is strange, that you don’t see anything in the logs.
Does

journalctl -b

show any output?

Otherwise try to start atd manually as root in a console window:

atd -d -f

to see if any errors show up.

Hendrik

#9

Thank you very much for getting back to me…Below is the response to your suggestions. Before I get into that, a lot of errors are caused by hylafax (fax server) I set up a script to email me a fax before I had configured a mail server - actually, a send only mail server called msmtp. So the system keeps trying to resend mail, and I cant figure out how to stop it. I tried stopping the fax server but something else in the system seems to have inherited the send mail job and I can’t figure out who or how to stop it…Perhaps you can suggest something?
Now, back to the original issue…here is the output:
Apr 24 17:25:47 linux.site postfix/smtp[9105]: connect to alt4.gmail-smtp-in.l.google.com[173.194.65.27]:25: Connection timed out
Apr 24 17:25:47 linux.site postfix/smtp[9106]: connect to alt4.gmail-smtp-in.l.google.com[173.194.65.27]:25: Connection timed out
Apr 24 17:25:47 linux.site postfix/smtp[9107]: connect to alt4.gmail-smtp-in.l.google.com[173.194.65.27]:25: Connection timed out
Apr 24 17:25:47 linux.site postfix/smtp[9105]: 9CE4731DDE: to=<jjhudak@gmail.com>, relay=none, delay=363345, delays=363195/0.06/150/0, dsn=4.4.1, status=de
Apr 24 17:25:47 linux.site postfix/smtp[9109]: connect to alt4.gmail-smtp-in.l.google.com[173.194.65.27]:25: Connection timed out
Apr 24 17:25:47 linux.site postfix/smtp[9108]: connect to alt4.gmail-smtp-in.l.google.com[173.194.65.27]:25: Connection timed out
Apr 24 17:25:47 linux.site postfix/smtp[9106]: 97514309AB: to=<jjhudak@gmail.com>, relay=none, delay=401145, delays=400995/0.08/150/0, dsn=4.4.1, status=de
Apr 24 17:25:47 linux.site postfix/smtp[9107]: C3DA1302F0: to=<jjhudak@gmail.com>, relay=none, delay=413745, delays=413595/0.09/150/0, dsn=4.4.1, status=de
Apr 24 17:25:47 linux.site postfix/smtp[9109]: 5847931067: to=<jjhudak@gmail.com>, relay=none, delay=388545, delays=388394/0.12/150/0, dsn=4.4.1, status=de
Apr 24 17:25:47 linux.site postfix/smtp[9108]: 80D702FC33: to=<jjhudak@gmail.com>, relay=none, delay=426346, delays=426195/0.11/150/0, dsn=4.4.1, status=de
Apr 24 17:25:47 linux.site postfix/error[9247]: E424B31722: to=<jjhudak@gmail.com>, relay=none, delay=375945, delays=375795/150/0/0.01, dsn=4.4.1, status=d
Apr 24 17:25:47 linux.site sshd[9244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:25:49 linux.site sshd[9241]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:25:50 linux.site sshd[9248]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:25:51 linux.site sshd[9241]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:25:52 linux.site sshd[9249]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:25:54 linux.site sshd[9241]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:25:55 linux.site sshd[9241]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:26:03 linux.site sshd[9252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:04 linux.site sshd[9250]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:05 linux.site sshd[9262]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:05 linux.site FaxGetty[9263]: Unknown speaker volume “on”; using “quiet”
Apr 24 17:26:05 linux.site FaxGetty[9263]: OPEN /dev/ttyACM0 HylaFAX ™ Version 5.5.5
Apr 24 17:26:05 linux.site FaxGetty[9263]: /dev/ttyACM0: Can not open modem (No such file or directory)
Apr 24 17:26:07 linux.site sshd[9250]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:08 linux.site sshd[9264]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:10 linux.site sshd[9250]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:10 linux.site sshd[9250]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:26:13 linux.site sshd[9267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:15 linux.site sshd[9265]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:16 linux.site sshd[9268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:18 linux.site sshd[9265]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:19 linux.site sshd[9269]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:21 linux.site sshd[9265]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:21 linux.site sshd[9265]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:26:24 linux.site sshd[9272]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:26 linux.site sshd[9270]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:27 linux.site sshd[9273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:29 linux.site sshd[9270]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:29 linux.site sshd[9274]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:32 linux.site sshd[9270]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:32 linux.site sshd[9270]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:26:34 linux.site sshd[9277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:35 linux.site FaxGetty[9263]: /dev/ttyACM0: Can not open modem (No such file or directory)
Apr 24 17:26:36 linux.site sshd[9275]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:37 linux.site sshd[9278]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:39 linux.site sshd[9275]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:40 linux.site sshd[9279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:42 linux.site sshd[9275]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:42 linux.site sshd[9275]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:26:46 linux.site sshd[9282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:47 linux.site sshd[9280]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:48 linux.site sshd[9283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:50 linux.site sshd[9280]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:51 linux.site sshd[9284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:53 linux.site sshd[9280]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:53 linux.site sshd[9280]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:26:56 linux.site sshd[9296]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:26:58 linux.site sshd[9285]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:26:59 linux.site sshd[9297]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:01 linux.site sshd[9285]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:02 linux.site sshd[9298]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:04 linux.site sshd[9285]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:04 linux.site sshd[9285]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:27:05 linux.site FaxGetty[9263]: /dev/ttyACM0: Can not open modem (No such file or directory)
Apr 24 17:27:05 linux.site FaxGetty[9263]: Unable to setup modem on /dev/ttyACM0; giving up after 2 attempts
Apr 24 17:27:05 linux.site FaxGetty[9263]: CLOSE /dev/ttyACM0
Apr 24 17:27:05 linux.site FaxQueuer[16048]: MODEM /dev/ttyACM0 appears to be wedged
Apr 24 17:27:05 linux.site FaxQueuer[16048]: MODEM WEDGED: bin/wedged ‘ttyACM0’ ‘/dev/ttyACM0’
Apr 24 17:27:08 linux.site sshd[9319]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:10 linux.site sshd[9300]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:11 linux.site sshd[9320]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:13 linux.site sshd[9300]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:14 linux.site sshd[9321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:16 linux.site sshd[9300]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:16 linux.site sshd[9300]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:27:25 linux.site sshd[9324]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:27 linux.site sshd[9322]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:28 linux.site sshd[9325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:29 linux.site sshd[9322]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:30 linux.site sshd[9326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:32 linux.site sshd[9322]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:32 linux.site sshd[9322]: Received disconnect from 183.3.202.196: 11: [preauth]
Apr 24 17:27:35 linux.site sshd[9329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:36 linux.site FaxGetty[9330]: Unknown speaker volume “on”; using “quiet”
Apr 24 17:27:36 linux.site FaxGetty[9330]: OPEN /dev/ttyACM0 HylaFAX ™ Version 5.5.5
Apr 24 17:27:36 linux.site FaxGetty[9330]: /dev/ttyACM0: Can not open modem (No such file or directory)
Apr 24 17:27:37 linux.site sshd[9327]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:38 linux.site sshd[9331]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:39 linux.site sshd[9327]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:40 linux.site sshd[9332]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.3.202.196 user=root
Apr 24 17:27:42 linux.site sshd[9327]: error: PAM: Authentication failure for root from 183.3.202.196
Apr 24 17:27:43 linux.site sshd[9327]: Received disconnect from 183.3.202.196: 11: [preauth]
lines 4155-4179/4179 (END)

linux:/home/jjh # atd -d -f
Another atd already running with pid 13587
linux:/home/jjh #

I have NO clue why there is an authentication failure…to my knowledge, no one is logging in…I did log in from work, kept my ssh connection open, and left…and over the weekend the machines are rebooted, so to my knowledge, the ssh session via putty would die, and would not restart when the machine is rebooted, so, I have no idea why that is happening…
thanks for your help
J

#10

wow, according to IP lookup 183.3.202.196 is China Telecom Guangdong --guess my machine is being attacked…sigh
|SP:
|
|China Telecom Guangdong|
|Host Name:|183.3.202.196|
|Organization:|China Telecom Guangdong|
|Country: |China (CN) https://forums.opensuse.org/image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAALCAIAAAD5gJpuAAAABGdBTUEAAK/INwWK6QAAASRJREFUKM9dkTFKQ2EQhCfJi2IRsBJTpBAEL6BH8BjmEJZaeB0LkZjCxlJBvICewEJFEBMTszO7a/G/Fx7CFsOyM/ux23kBAgigCwDYPsb7HdA0BQBQS1cB7F6cD04wu4z Xmwe farzyaCKaUkQ0qy6OfptApgMM7ezutg7J9nHgtuHHr/gPMbJpnGpIVZktVopAIyv8qY c t y87A0 ZvzGNYZZchVldpIAKQHz5x6mQ2jpStc/lA5f3jFZ2mgWZxRBArLywLp ELc4mlmSSJRVNfEi1IV0pgeYLfV8zaYUn1tnFQEZtKC0pWwD/pyWsN0AqiEGGWT3RcKdZiClPdwCVgKB6w2GSXXmKdXxz/pDgHu7pLqDz2HpkW6j17GiqAv4AOq5zMGmEpvUAAAAASUVORK5CYII=|
|Region/State:|30 Guangdong|
|City:|Guangzhou|

#11

No signs of atd in this part of the log, but

shows, that it is running. Did you “grep” or filter the log output for atd?

You should stop the running atd and start the one at the console. Then wait until a job should get executed.

And sorry, but I’m no expert for mailing and fax servers. You should open new threads for these issues.

Hendrik

#12

I stopped the running at process…but it said that one was not running…I then started the process manually, said it could not start (again said it was Loaded, Inactive, used the CL version of Yast and it said same thing). At this point, I got the feeling the OS was very confused. I rebooted the system, and lo and behold…

linux:/home/jjh/sunschedule # atd -d -f
Another atd already running with pid 766
linux:/home/jjh/sunschedule # ps -lax|grep atd
4 25 766 1 20 0 3048 1748 pause Ss ? 0:00 /usr/sbin/atd -f
0 0 4461 3636 20 0 4400 1528 pipe_w S+ pts/1 0:00 grep --color=auto atd
linux:/home/jjh/sunschedule # pgrep -l atd
766 atd
linux:/home/jjh/sunschedule # systemctl status atd.service
atd.service - Deferred execution scheduler
Loaded: loaded (/usr/lib/systemd/system/atd.service; enabled)
Active: active (running) since Mon 2016-04-25 14:12:51 EDT; 41min ago
Main PID: 766 (atd)
CGroup: /system.slice/atd.service
└─766 /usr/sbin/atd -f

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

OK, so it is now running but I have no clue how it got into such a state. I’ll see if it executes the scripts…they are in the queue:
sh sun.sh
Sunrise is at 06:28
Sunset is at 20:13
warning: commands will be executed using /bin/sh
job 39 at Mon Apr 25 20:13:00 2016
warning: commands will be executed using /bin/sh
job 40 at Mon Apr 25 20:13:00 2016

I guess this case can be closed, but unfortunately I have no clue what resolved it (well yea, rebooting appears to have fixed it) or what caused it…

So how do I see the system error log again?
Thanks to all who helped me get some insight into this problem
J