after a fresh opensuse 12.2 install atd daemon broken
at console command : atd 18:00
system answers : Can’t open /var/run/atd.pid to signal atd. No atd running?
please help
after a fresh opensuse 12.2 install atd daemon broken
at console command : atd 18:00
system answers : Can’t open /var/run/atd.pid to signal atd. No atd running?
please help
Hi
Shouldn’t that be;
atd
at 18:00
yes at
or batch
nobody has a solution ?
atd daemon is broken as described above on three opensuse 12.2 fresh installs whatever it is x86 or x86_64 !
please help
Make sure it is installed
check Yast-System run levels see if listed and marked to run.
“atd” is disabled by default.
open Yast, go to System Services, and enable it.
the command you enter to schedult is “at”, not “atd”.
see “man at”, or use konqueror to view “man:/at” - view the section 1 version.
yes atd is installed and turned on in sys runlevels however with a star like this yes*
checking with systemctl gives:
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/atd.service
atd is installed and turned on in sys runlevels however with a star like this yes*
checking with systemctl gives:
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/atd.service
systemctl restart atd.service
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; disabled)
Active: failed (Result: exit-code) since Fri, 05 Oct 2012 18:28:00 +0200; 4s ago
Process: 5015 ExecStart=/usr/sbin/atd -f (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/atd.service
i tried by removing the -f option but with no success.
Thanks for your help.
Copy /lib/systemd/system/atd.service into /etc/systemd/system/
Edit /etc/systemd/system/atd.service and remove “-f” option
Issue “systemctl daemon-reload”
Issue “systemctl restart atd.service”
Hi
Ok, if you open YaST -> /etc/sysconfig editor and add the following values;
ATD_BATCH_INTERVAL = 60
ATD_LOADAVG = 0.8
The above are the defaults, but needed for a modified atd.service which needs to modified like so;
vi /lib/systemd/system/atd.service
--- modify as follows ---
[Unit]
Description=Execution Queue Daemon
After=syslog.target
[Service]
Type=forking
EnvironmentFile=-/etc/sysconfig/atd
ExecStart=/usr/sbin/atd -b ${ATD_BATCH_INTERVAL} -l ${ATD_LOADAVG}
[Install]
WantedBy=multi-user.target
Now we need to reload and start;
systemctl --system daemon-reload
systemctl start atd.service
systemctl status atd.service
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; disabled)
Active: active (running) since Fri, 05 Oct 2012 12:14:52 -0500; 1s ago
Process: 20851 ExecStart=/usr/sbin/atd -b ${ATD_BATCH_INTERVAL} -l ${ATD_LOADAVG} (code=exited, status=0/SUCCESS)
Main PID: 20852 (atd)
CGroup: name=systemd:/system/atd.service
└ 20852 /usr/sbin/atd -b 60 -l 0.8
If this works for you, please confirm and will see if I can sort out a bug/update.
Hi
That’s not the correct way to fix the issue… all services reside in openSUSE in /lib/systemd/system/ ![]()
That is. /lib/systemd is for packagers (all files are unconditionally overwritten on update) and /etc/systemd is for administrator to customize or overwrite unit definitions. Having changed copy in /etc/systemd ensures it is not lost in case of update.
Of course if atd update that fixes this problem is available, one should remove unit from /etc/systemd to be sure to get default version again.
Thanks but that did not help arvidjaar ,
same message after reboot and submitting a new at job:
Can’t open /var/run/atd.pid to signal atd. No atd running?
something is wrong with file permissions ! but where ?
any suggestions ?
Hi thanks very much for your help ,
I have followed your instructions and modified the daemon setup as above
on two different machines
one with 64bits and one with 32bits
systemctl status atd.service
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; enabled)
Active: active (running) since Thu, 11 Oct 2012 00:04:12 +0200; 2s ago
Process: 3220 ExecStart=/usr/sbin/atd -b ${ATD_BATCH_INTERVAL} -l ${ATD_LOADAVG} (code=exited, status=0/SUCCESS)
Main PID: 3221 (atd)
CGroup: name=systemd:/system/atd.service
└ 3221 /usr/sbin/atd -b 60 -l 0.8
Things are now fine for me .
Hi thanks very much for your help ,
I have followed your instructions and modified the daemon setup as above
on two different machines
one with 64bits and one with 32bits
systemctl status atd.service
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; enabled)
Active: active (running) since Thu, 11 Oct 2012 00:04:12 +0200; 2s ago
Process: 3220 ExecStart=/usr/sbin/atd -b ${ATD_BATCH_INTERVAL} -l ${ATD_LOADAVG} (code=exited, status=0/SUCCESS)
Main PID: 3221 (atd)
CGroup: name=systemd:/system/atd.service
└ 3221 /usr/sbin/atd -b 60 -l 0.8
Things are now fine for me .
Hello,
I just installed the OpenSuse 12.2 and went into exactly this “atd” problem.
The patch as described in
and - the following was also needed -
and
helps.
“atd” is indeed broken in OpenSuse 12.2 DVD build.
Please supply a fix soon.
The described patch fixed the “atd” problem.
I finally got the solution:
After reading the atd man page, it says:
SYNOPSIS
atd -l load_avg] -b batch_interval] -d] -s]
I modified my atd.service file normaly under /lib/systemd/system to read:
ExecStart=/usr/sbin/atd -l 10 -b 60
Then I run:
systemctl --system daemon-reload
systemctl start atd.service
and:
systemctl status atd.service
Results:
atd.service - Execution Queue Daemon
Loaded: loaded (/etc/systemd/system/atd.service; enabled)
Active: active (exited) since Sat, 24 Nov 2012 16:58:15 -0500; 12min ago
Process: 16835 ExecStart=/usr/sbin/atd -l 10 -b 60 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/atd.service
└ 16836 /usr/sbin/atd -l 10 -b 60
Now I can run batch or at jobs.
On 2012-11-24 23:26, guszamso wrote:
> I modified my atd.service file normaly under /lib/systemd/system to
> read:
>
> ExecStart=/usr/sbin/atd -l 10 -b 60
Why? What was the reasoning you had to do that, please?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))