Restarting a systemd.service with a dependency job failed.

Hello.
Let's say I have foo.service containing that:
[Unit]
Description=Is executed only if bar.service success
Requires=bar.service
After=bar.service
[Service]
Type=simple
TimeoutSec=6
Restart=on-failure
ExecStart=/usr/bin/touch /tmp/test
And i have bar.service containing that:
[Unit]
Description=Test in foo.tld is reachable
[Service]
Type=oneshot
ExecStart=/usr/bin/ping -c1 foo.tld
[Install]
WantedBy=multi-user.target
If the ping fails in bar.service, then I'll get that when I try to start foo.service: « A dependency job for foo.service failed. See 'journalctl -xn' for details. »
How can I make foo.service check every n seconds if its dependency jobs are fullfilled/successfull instead of just failing and stopping like it currently does ?
I'm searching for a "Restart" option that would apply if the dependency check fails. I'm not sure if this is possible.
Thank you in advance for your answers.

Maybe you're looking for RequiresOverrideable? From the man page of systemd.unit
RequiresOverridable=
Similar to Requires=. Dependencies listed in RequiresOverridable= which cannot be fulfilled or fail to start are ignored if the startup was explicitly requested by the user. If the start-up was
pulled in indirectly by some dependency or automatic start-up of units that is not requested by the user, this dependency must be fulfilled and otherwise the transaction fails. Hence, this option
may be used to configure dependencies that are normally honored unless the user explicitly starts up the unit, in which case whether they failed or not is irrelevant.

Similar Messages

[SOLVED]Correct way to restart a systemd service on resume from susp?

I have offlineimap setup to run as a daemon. It doesn't correctly resume operations after a resume from suspend to RAM without being restarted. The 'Conflicts=' line in the service file makes sure it is stopped when the machine suspends, but I can't figure out how to get it restarted again. Here is the service file:
[Unit]
Description=Start offlineimap as a daemon
Requires=network.target
Conflicts=suspend.target
After=network.target
[Service]
User=%i
EnvironmentFile=/home/%i/.gnupg/gpg-agent-info
ExecStart=/usr/bin/offlineimap
KillSignal=SIGUSR2
Restart=always
RestartSec=15
[Install]
WantedBy=multi-user.target
I found an email thread here that seemed to imply that I could add sleep.target to 'WantedBy=' and sleep.target to 'After=' to get service to startup again after resume, but that didn't seem to work.
Any ideas? Thanks!
Scott
Last edited by firecat53 (2014-07-01 16:40:20)

tomk wrote:
firecat53 wrote:It doesn't correctly resume operations after a resume from suspend to RAM without being restarted.
Is this just something you have observed on your own system, or is it a known bug?
Something I noticed and figured it was just due to frequently switching networks with VPN on/off again. After a quick search, I discovered the 'socktimeout' option, which I'm testing now to see if that solves the problem. It appears (although I _just_ found this, that it is a known bug. Some have had luck with setting socktimeout, others haven't. I'll post back if I see a difference or not.
Thanks for the nudge
Scott

Systemd problem with dbus, b43 and wirelles problem

HI,
My problem starts with broadcom-wl broken.
Now I replaced broadcom-wl by b43, and still I have problem.
My first is:
Sep 7 15:15:55 localhost dbus[368]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Sep 7 15:15:55 localhost dbus[368]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Sep 7 15:08:55 localhost pulseaudio[1227]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Sep 7 15:13:16 localhost dhcpcd[3868]: dhcpcd not running
Sep 7 15:13:18 localhost dhcpcd[3873]: eth0: sendmsg: Cannot assign requested address
Sep 7 15:15:42 localhost [ 5.101733] systemd[1]: Socket service syslog.service not loaded, refusing.
Sep 7 15:15:55 localhost pulseaudio[1047]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Sep 7 15:15:57 localhost dhcpcd[1061]: dhcpcd not running
Sep 7 15:15:57 localhost dhcpcd[1069]: dhcpcd not running
Sep 7 15:15:59 localhost dhcpcd[1074]: eth0: sendmsg: Cannot assign requested address
Sep 7 15:48:52 localhost dhcpcd[3194]: wlan0: up_interface: Operation not possible due to RF-kill
Sep 7 15:49:22 localhost dhcpcd[3194]: timed out
Sep 7 15:49:48 localhost dhcpcd[3245]: wlan0: up_interface: Operation not possible due to RF-kill
Sep 7 15:50:18 localhost dhcpcd[3245]: timed out
Sep 7 15:56:40 localhost dhcpcd[3677]: wlan0: up_interface: Operation not possible due to RF-kill
Sep 7 15:57:10 localhost dhcpcd[3677]: timed out
And something with b43:
# dmesg | grep b43
[ 5.101353] systemd[1]: Cannot add dependency job for unit b43.service, ignoring: Unit b43.service failed to load: No such file or directory. See system logs and 'systemctl status b43.service' for details.
[ 8.433686] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[ 8.561643] Registered led device: b43-phy0::tx
[ 8.561664] Registered led device: b43-phy0::rx
[ 8.561682] Registered led device: b43-phy0::radio
[ 1875.669071] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1875.931945] b43-phy0: Radio hardware status changed to DISABLED
Now I can't use any wirelles connection and my system looks broken.
Can anybody help?

I had this same issue. Unfortunately, I never found a solution.
Personally, I just switched to Wicd. It seems more reliable and higher-level than NetworkManager. That is, it uses the wireless_tools stuff which is pretty reliable, instead of it's own little library.

How do I restart the SNMP agents with the original command line options?

I'm creating an application that changes the SNMP trap target configuration files and then restarts the SNMP agent. I'm currently working with the mibiisa agent. I want to make sure that I restart the service with the new trap targets but with the original command line options. How can I restart the mibiisa service with the same command line options that it originally loaded with?

It is not "Network Time" that is the problem, but actually "SystemStarter." SystemStarter is an interim kludge to enable the work or the old StartupItems until they can be converted to LaunchDaemons or LaunchAgents controlled by launchd. Launcd calls SystemStarter to launch all the unconverted StartupItems. ntpd is now under the control of launchd directly.
Launchctl is the command to load and unload the plist files, but I don't think it has a mechanism to restart a daemon.
There are start and stop commands in launchctl, but the man page indicates that they are for debugging purposes.
I also imagine you could just kill the ntp daemon and let it restart with new settings. It is most likely set to "keepAlive" so that it will automatically restart.

Remote Restart of Services (with dependencies)

Hello all,
i've a short question about restarting a service on a remote machine with powerhell.
I've tried the following:
get-service -computername ServerXY -name ServiceXY | Set-Service -Status stopped
And it works like a charm. But some services have dependencies. For example DFSR:
PS C:\Windows\system32> get-service -ComputerName ServerXY -name dfsr | Set-Service -Status Stopped
Set-Service : Cannot stop service 'DFS Replication (dfsr)' because it is dependent on other services.
At line:1 char:51
+ get-service -ComputerName ServerXY -name dfsr | Set-Service -Status Stopped
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.ServiceProcess.ServiceController:ServiceController) [Set-Servi
ce], ServiceCommandException
+ FullyQualifiedErrorId : ServiceIsDependentOnNoForce,Microsoft.PowerShell.Commands.SetServiceCommand
Is there a possiblity to restart services with dependencies remote, too?
Regards, Heyko

Instead of Set-Service, use the Stop-Service cmdlet with the -Force parameter in order to stop services that have dependencies. If you want to restart the service, as you've mentioned, then pipe you Get-Service command to the Restart-Service cmdlet. This
cmdlet will also take the -Force parameter, allowing services to restart even when there are dependent services.
Update: Added info about the Restart-Service cmdlet.

Getting sasc-ng to work properly with systemd service files [SOLVED]

This thread is intended for getting the following AUR packages to work with each other with systemd service scripts:
https://aur.archlinux.org/packages/open-sasc-ng-dkms/
https://aur.archlinux.org/packages/open-sasc-ng/
https://aur.archlinux.org/packages/oscam-svn/ (this is a related package as it must properly execute prior to sasc-ng)
So my server is now on a fresh Arch install with systemd. All is well (& very fast) except I cannot get sasc-ng to function with systemd service init files. Prior to systemd the system worked fine with the rc initscripts & was very stable with the following setup:
rc.local
/etc/rc.d/oscam start
sleep 15
/etc/rc.d/sasc-ng start
sleep 4
/etc/rc.d/mythbackend start
/etc/conf.d/sasc-ng.conf
SASCNG_ARGS="-j 0:3 -j 1:4 -j 2:5" -b 16M --sid-allpid --sid-nocache --cam-budget"
DVBLOOPBACK_ARGS="num_adapters=3"
LOGDIR="/home/mythtv/logs/"
CAMDIR="/etc/camdir"
/etc/camdir/cardclient.conf
camd35:localhost:15050:1/0000/0000:mythtv:mythtv
I'll leave out the oscam stuff as that loads fine and doesn't appear to be a part of the problem
I've tried this with the systemd service file that comes with the open-sasc-ng-dkms package and when it was not sucessful I tried a bunch of variants including using "Type=simple" ect. "Type=Forked" seems to be only option that actually tries to start the processes. I also "hardcoded" the service files for the 2 sasc-ng components to find a few issues with the EnvironmentFile variables. The log variable has been removed for now as this seems to cause a fatal error but the rest of the variables load fine now. I also tested spliting up the DVB loopback module from the sasc-ng binary but this also gives similar results as the following script stands now. Running them manually with systemctl start commands doesn't make a difference but that is not surprising. The service file I'm fiddling with now which I feel has the best potential become working is:
sasc-ng.service
[Unit]
Description=Sasc-ng
After=oscam.service
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/sasc-ng
ExecStartPre=/sbin/modprobe dvbloopback $DVBLOOPBACK_ARGS
TimeoutSec=2
ExecStart=/usr/sbin/sasc-ng -D $SASCNG_ARGS --cam-dir=$CAMDIR
TimeoutSec=4
[Install]
WantedBy=multi-user.target
Mythbackend always runs fine (even without DTV via sasc-ng) with the following mythbackend.service:
[Unit]
Description=MythTV_backend
After=sasc-ng.service
[Service]
Type=simple
Environment=MYTHCONFDIR=/etc/conf.d/mythbackend
Environment=HOME=/usr/share/mythtv
User=mythtv
ExecStart=/usr/bin/mythbackend --logpath /var/log/mythtv
[Install]
WantedBy=multi-user.target
oscam.service taken mostly from AUR package also seems fine. I added the TimeoutSec=15 to give time for oscam to load the SC and client protocol before moving on or else sasc-ng fails
Unit]
Description=An Open Source Conditional Access Module software
After=network.target
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/oscam
ExecStart=/usr/bin/oscam $OSCAM_ARGS
TimeoutSec=15
[Install]
WantedBy=multi-user.target
Below is the output of the systemctl status commands. Despite the noise in the sasc-ng binary status, it is the loopback module that is " inactive (dead)" and there are no virtual DVB devices being created:
[mythtv@server ~]$ sudo systemctl status oscam.service
oscam.service - An Open Source Conditional Access Module software
Loaded: loaded (/usr/lib/systemd/system/oscam.service; enabled)
Active: active (running) since Tue, 2012-11-27 21:10:17 CET; 1min 7s ago
Process: 338 ExecStart=/usr/bin/oscam $OSCAM_ARGS (code=exited, status=0/SUCCESS)
Main PID: 377 (oscam)
CGroup: name=systemd:/system/oscam.service
├ 377 /usr/bin/oscam -b -c /etc/oscam
└ 378 /usr/bin/oscam -b -c /etc/oscam
Nov 27 21:10:17 server systemd[1]: Started An Open Source Conditional Acces...e.
[mythtv@server ~]$ sudo systemctl status loopback.service
loopback.service - Sasc-ng DVB Loopback Module
Loaded: loaded (/etc/systemd/system/loopback.service; enabled)
Active: inactive (dead) since Tue, 2012-11-27 21:10:28 CET; 1min 27s ago
Process: 907 ExecStart=/sbin/modprobe dvbloopback num_adapters=3 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/loopback.service
Nov 27 21:10:28 server systemd[1]: Started Sasc-ng DVB Loopback Module.
[mythtv@server ~]$ sudo systemctl status sasc-ng.service
sasc-ng.service - Sasc-ng
Loaded: loaded (/etc/systemd/system/sasc-ng.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-27 21:10:47 CET; 1min 45s ago
Process: 913 ExecStart=/usr/sbin/sasc-ng -D -j 0:3 -j 1:4 -j 2:5" -b 16M --sid-allpid --sid-nocache --cam-budget --cam-dir=/etc/camdir -l /home/mythtv/logs/sasc-ng.log (code=exited, status=0/SUCCESS)
Main PID: 921 (code=exited, status=255)
CGroup: name=systemd:/system/sasc-ng.service
Nov 27 21:10:39 server sasc-ng[921]: [921] [general.error] failed open /etc...ry
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc...ry
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc...ry
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.info] loading cardclien...nf
Nov 27 21:10:42 server sasc-ng[921]: [1062] Netwatcher thread started (pid=...6)
Nov 27 21:10:42 server sasc-ng[921]: [921] [general.error] no keys loaded f...m!
Nov 27 21:10:46 server sasc-ng[921]: [1098] SC housekeeper thread started (...2)
Nov 27 21:10:47 server sasc-ng[921]: [1062] Netwatcher thread ended (pid=92...6)
Nov 27 21:10:47 server systemd[1]: sasc-ng.service: main process exited, co.../a
Nov 27 21:10:47 server systemd[1]: Unit sasc-ng.service entered failed state
[mythtv@server ~]$ sudo systemctl status sasc-ng.service
sasc-ng.service - Sasc-ng
Loaded: loaded (/etc/systemd/system/sasc-ng.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-27 21:10:47 CET; 2min 9s ago
Process: 913 ExecStart=/usr/sbin/sasc-ng -D -j 0:3 -j 1:4 -j 2:5" -b 16M --sid-allpid --sid-nocache --cam-budget --cam-dir=/etc/camdir -l /home/mythtv/logs/sasc-ng.log (code=exited, status=0/SUCCESS)
Main PID: 921 (code=exited, status=255)
CGroup: name=systemd:/system/sasc-ng.service
Nov 27 21:10:39 server sasc-ng[921]: [921] [general.error] failed open /etc/camdir/smartcard.conf: No such file or directory
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc/camdir/cardslot.conf: No such file or directory
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc/camdir/SoftCam.Key: No such file or directory
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.info] loading cardclient config from /etc/camdir/cardclient.conf
Nov 27 21:10:42 server sasc-ng[921]: [1062] Netwatcher thread started (pid=921, tid=140074379712256)
Nov 27 21:10:42 server sasc-ng[921]: [921] [general.error] no keys loaded for softcam!
Nov 27 21:10:46 server sasc-ng[921]: [1098] SC housekeeper thread started (pid=921, tid=140074371319552)
Nov 27 21:10:47 server sasc-ng[921]: [1062] Netwatcher thread ended (pid=921, tid=140074379712256)
Nov 27 21:10:47 server systemd[1]: sasc-ng.service: main process exited, code=exited, status=255/n/a
Nov 27 21:10:47 server systemd[1]: Unit sasc-ng.service entered failed state
[mythtv@server ~]$
Any ideas?
Last edited by wdirksen (2012-12-10 19:54:43)

After some head scratching it seems to be all good now. Considering there have been no replies to this I've come to wonder if I might be the only one with this issue. I could get it working somewhat using service files but never ideal, ex. sasc-ng only using a few of the entitlements from oscam because it started too quick etc. Anyway this might help a few and I'm hoping the linux savvy who find what I'm writing here painfully newbie like or flawed will reply and educate me a bit if what's provided here needs some sharpening up:
1) Systemd was confusing the sasc-ng binary shorthand arguments with Linux init arguments and a few were misinterpreted if they were not nested into the environment specifiers. So the -l (log) was causing problems and -b (buffer) wasn't loading. To be safe I'm using only the sasc-ng longhand specifiers from now on (two "--" and more verbose) so that they can never be confused even if safely nested in an environment parameter. That means that /etc/conf.d/sasc-ng will also need to be changed to reflect this. I also decided to simplify the LOGFILE parameter to include the whole argument syntax.
2) Oscam.service needs to be initiated with oneshot and RemainAfterExit=yes to make sure the delay (15 seconds in my config) gets counted out before sasc-ng initiates.
[EDIT 12/12/2012: Initially I had a second TimeoutSec=2 after ExecStart in sasc-ng.service but this had no function. Turns out that it almost always does work without this delay but not always with my setup. Adding TimeoutSec=2 to mythbackend.service prior to ExecStart command does function and makes things init more consistant]
sasc-ng.service
[Unit]
Description=Sasc-ng
After=oscam.service
[Service]
Type=simple
EnvironmentFile=/etc/conf.d/sasc-ng
ExecStartPre=/sbin/modprobe dvbloopback $DVBLOOPBACK_ARGS
TimeoutSec=2
ExecStart=/usr/sbin/sasc-ng $SASCNG_ARGS --cam-dir $CAMDIR --log $LOGFILE
[Install]
WantedBy=multi-user.target
/etc/conf.d/sasc-ng
SASCNG_ARGS="--join 0:3 --join 1:4 --join 2:5 --buffer 16M --sid-allpid --sid-nocache --cam-budget"
DVBLOOPBACK_ARGS="num_adapters=3"
LOGFILE="/home/mythtv/logs/sasc-ng.log"
CAMDIR="/etc/camdir"
oscam.service
[Unit]
Description=An Open Source Conditional Access Module software
After=network.target
[Service]
Type=oneshot
EnvironmentFile=/etc/conf.d/oscam
ExecStart=/usr/bin/oscam $OSCAM_ARGS
TimeoutSec=15
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
mythbackend.service
[Unit]
Description=MythTV_backend
After=sasc-ng.service
[Service]
Type=simple
TimeoutSec=2
Environment=MYTHCONFDIR=/etc/conf.d/mythbackend
Environment=HOME=/usr/share/mythtv
User=mythtv
ExecStart=/usr/bin/mythbackend --logpath /var/log/mythtv
[Install]
WantedBy=multi-user.target
I will make the related changes to the open-sasc-ng AUR package which I currently maintain
Last edited by wdirksen (2012-12-23 14:40:43)

Systemd - help with creating a service file

Hi, I am trying to make a service file to execute "devmon --no-mount --exec-on-audio abcde". Basicly I want abcde to run when an audio cd is inserted into a headless computer. I have tried some udev rules but had no luck with that.
I then found udevil and devmon, and it seems to do exectly what I want.
So Ive made a systemd service file and put it in to /usr/lib/systemd/system
here is it:
/usr/lib/systemd/system/abcde-auto.service
[Unit]
Description=Virtual Distributed Ethernet
[Service]
Type=simple
ExecStart=/usr/bin/devmon --no-mount --exec-on-audio abcde
[Install]
WantedBy=multi-user.target
I have started this with
systemctl start abcde-auto.service
and I see that a devmon process has started with the same arguments I gave in the service file, so all is good.
But now, I am not too sure about the "Type" in the service file, devmon starts abcde, but:
systemctl stop abcde-auto.service
does not stop abcde, only devmon.
Is there a way to setup the service file so that abcde will end as well as devmon?
*Edit
Ive read this http://www.freedesktop.org/software/sys … rvice.html but Im still not too sure. Dont really know what most of it means.
Last edited by jrussell (2012-10-20 18:09:23)

I use type 'oneshot' and add an ExecStop= to start and stop scripts.
Like here is the unit file I use to start and stop arno-iptables-firewall
[Unit]
Description=Arno iptables firewall
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/arno-iptables-firewall start
ExecStop=/usr/sbin/arno-iptables-firewall stop
[Install]
WantedBy=multi-user.target

How to make a systemd service for a bash script with pipes?

I haven't been able to make a successful systemd service from this script.
The script itself works (in terminal and xdg autostart), but systemd doesn't run anything after the first pipe (neither sed nor spd-say execute).
Here's my service:
[Unit]
Description=Speak kernel and userspace messages
[Service]
Type=simple
ExecStart=/usr/local/sbin/dmesg-speak
[Install]
WantedBy=multi-user.target
Systemd says the script starts successfully, but only dmesg is started; it's output is not piped through sed or spd-say.
I've also tried Type=forking without much success.
Is there something I can do other than switching to sysv-init?
Do I need IgnoreSIGPIPE=false?
Last edited by quequotion (2015-02-12 17:07:21)

fsckd wrote:The linked script appears to lack a hashbang. No hashbang = arbitrary interpretor.
Yeah, that should probably be there. Since last post I've employed /usr/bin/bash in the service and added a hasbang, but sdp-say still does not run as a systemd service.
I didn't test either option individually; the key seems to be finding an audio output accessible before user login. I am not certain:
ccoffey wrote:If a pulseaudio session exists at all
I am curious to try this:
ccoffey wrote:run pulseaudio and dbus via XVFB.
Setting DISPLAY as root would then allow you play audio.
Still, it seems to me that ALSA would be available at some stage during boot, as is speech-dispatcher (for working with speakup!). If espeak were configured to play audio for root to ALSA, there would be a sound outlet for it (espeak can be used in pipeline mode without speech-dispatcher if need be), and pulseaudio would be probably be OK with that whenever it got around to starting (audio passed through alsa gets piped through, regardless of its source right?).
I have tried the script with espeak instead of spd-say without success.
Last edited by quequotion (2015-02-26 03:06:24)

[SOLVED] Help with systemd .service script

Hello,
I have been using ArchLinux (ARM version) on some “plug computers” for over a year and love it. Recently I forced myself to move to systemd by upgrading all my computers from scratch. I migrated all my applications and learned new ways of doing things but am having trouble with one last migration. I run a c++ communication program that monitors a TCP port for traffic. In the past I started this program (daemon) from an entry in rc.conf. I have read all I can about systemd’s new approach to starting daemons (https://wiki.archlinux.org/index.php/Systemd and https://wiki.archlinux.org/index.php/Systemd/Services)
So far I created what I thought is the correct systemd .service file listed below.
[Unit]
Description=EQBCS
After=network.target
[Service]
Type=simple
ExecStart=/home/public/EQBCS/eqbcs -p 12947 -d &> /dev/null
[Install]
WantedBy=multi-user.target
I put this file in /usr/lib/systemd/system/eqbcs.service. I then ran the following commands in the following order:
systemctl daemon-reload
systemctl enable eqbcs.service (created a link in /etc/systemd/system/multi-user.target.wants)
systemctl start eqbcs.service
Here is output from systemctl (status)
eqbcs.service loaded failed failed EQBCS
I thought this would start the service but no luck. I also thought maybe a reboot would work but no luck. I verified I can start the daemon manually if I run /home/public/EQBCS/eqbcs -p 12947 -d &> /dev/null from the command line.
I think I am close, but after several hours of looking at examples of .service files and other posts, I am at a loss. I am not one of those types who posts a question without taking the time to read the wealth of information on these boards, but I am truly out of ideas and can’t figure out what to do next. I sincerely could use some help/advice.
Last edited by calzon65 (2013-06-01 21:18:20)

Thank you for the suggestions, I believe I am getting closer to success. When I run systemctl start eqbcs.servcie it starts the service but the only way I can get out of systemctl is to ^c out.
Here is my current .service file:
[Unit]
Description=EQBCS
After=network.target
[Service]
ExecStart=/home/public/EQBCS/eqbcs -p 12947
Type=forking
[Install]
WantedBy=multi-user.target
Output from systemctl status eqbcs:
eqbcs.service - EQBCS
Loaded: loaded (/etc/systemd/system/eqbcs.service; enabled)
Active: failed (Result: timeout) since Sat 2013-06-01 12:48:43 PDT; 2min 11s ago
Process: 427 ExecStart=/home/public/EQBCS/eqbcs -p 12947 (code=killed, signal=TERM)
Main PID: 396 (code=killed, signal=KILL)
CGroup: name=systemd:/system/eqbcs.service
Jun 01 12:47:13 alarm systemd[1]: Starting EQBCS...
Jun 01 12:47:13 alarm eqbcs[427]: WARNING: Running as root NOT recommended.
Jun 01 12:47:13 alarm eqbcs[427]: EQ Box Chat Server 10.12.18
Jun 01 12:47:13 alarm eqbcs[427]: Waiting for connections on port: 12947...
Jun 01 12:48:43 alarm systemd[1]: eqbcs.service operation timed out. Terminating.
Jun 01 12:48:43 alarm systemd[1]: Failed to start EQBCS.
Jun 01 12:48:43 alarm systemd[1]: Unit eqbcs.service entered failed state.
Are there any other suggestions for settings in my .service file?

Systemd service to shutdown remote machines with ssh

Hi All,
I'm trying to shutdown two raspberryPis that are connected to my pc when I switch the pc off.
I've made a simple script that looks like
#!/bin/bash
ping -c 1 10.0.1.2
if [ $? -eq 0 ]
then
ssh [email protected] "/sbin/shutdown -hP now"
fi
ping -c 1 10.0.2.2
if [ $? -eq 0 ]
then
ssh [email protected] "/sbin/shutdown -hP now"
fi
and I would like to call it with systemd (of course there is password-less ssh and the script works fine when called).
However all the approaches I'm trying fails because the network is switched off before or while the script is executing.
Two possible systemd services follows:
[Unit]
Description=Shutdown Raspberries
Wants=network.target
Requires=network.target [email protected] [email protected]
Before=shutdown.target reboot.target halt.target
DefaultDependencies=no
[Service]
Type=oneshot
User=ansvi
ExecStart=/path/to/shutdown_rpis.sh
RemainAfterExit=yes
TimeoutSec=90
[Install]
WantedBy=shutdown.target reboot.target halt.target
[Unit]
Description=Shutdown Raspberries
Requires=network.target
[Service]
User=ansvi
ExecStart=/bin/true
ExecStop=/path/to/shutdown_rpis.sh
RemainAfterExit=true
[Install]
WantedBy=multi-user.target
Did someone have similar issues and maybe found a solution? Can you correct/suggest a better way to do this?
Thanks
Pietro
Last edited by pie86 (2015-05-07 13:31:02)

To handle power from XBMC polkit rule is needed. It is probably the same with mythtv.
polkit.addRule(function(action, subject) {
if (action.id.match("org.freedesktop.login1.") && subject.isInGroup("mythtv")) {
return polkit.Result.YES;
Save this as /etc/polkit-1/rules.d/10-mythtv.rules and add user to mythtv group.

Restart Orchestrator server service failed with error 1053

Hi,
I'm using Orchestrator 6.0. I always get an error 1053 after restart Orchestrator server service.
And no matter how many times I restart my OS, the Orchestrator server service cannot be started any longer.
Does anyone can help on this?
By the way, if I installed a vCenter server 6.0 and Orchestrator 6.0 on a same machine, Orchestrator would always get this error. But if I installed them on different machines, Orchestrator server service can running well sometimes. Is there any limitation when install vCenter server 6.0 and Orchestrator 6.0?
Thanks in advance.
Vicky

Is the orchestrator configurator service running? If so, log in to https://<orchestratorserver>:8283 and take a look on the configuration. If not, take a look to the logs of the vRO service and if you like, post em here.

Creating an IBus systemd service file

I currently start ibus-daemon with the following in my ~/.xprofile:
ibus-daemon --daemonize --xim
The thing is this does not display very nicely in the output of `systemctl status`; there're several ibus related processes listed, all in the same process Group ID. I figure if I write an ibus.service and manage it with systemctl, they would be grouped together in the output of `systemctl status`, correct?
In any case, I'm trying to write an IBus systemd service file. What I have so far:
[Unit]
Description=Intelligent Input Bus
Documentation=man:ibus-daemon(1)
[Service]
Type=dbus
BusName=org.freedesktop.IBus
ExecStart=/usr/bin/ibus-daemon --replace --xim --panel disable
ExecReload=/usr/bin/ibus restart
ExecStop=/usr/bin/ibus exit
[Install]
WantedBy=default.target
I put the above in file ~/.config/systemd/user/ibus.service and tried
% systemctl --user start ibus.service
For 90 seconds the command didn't return. In that time, ibus-daemon was in fact started, I used the command `ibus` to check that the Bus part was working normally. 90 seconds later systemd bailed out,
Job for ibus.service failed. See 'systemctl status ibus.service' and 'journalctl -xn' for details.
Nothing useful in the journal, really,
systemd[388]: Starting Intelligent Input Bus...
systemd[388]: ibus.service start operation timed out. Terminating.
systemd[388]: Failed to start Intelligent Input Bus.
systemd[388]: Unit ibus.service entered failed state.
What was not working during the 90 seconds was I couldn't actually use IBus to input anyting. I was able to switch engines with `ibus engine <foo>` but if then I started typing IBus was not used at all.
Compare the process tree between manually running ibus-daemon and using systemctl start,
ibus-daemon --replace --xim --panel disable
systemd,1,1
|-gnome-terminal-,485,440
| |-zsh,7299,7299
| | `-ibus-daemon,9732,9732 --replace --xim --panel disable
| | |-ibus-dconf,9736,9732
| | | |-{dconf worker},9743,9732
| | | |-{gdbus},9742,9732
| | | `-{gmain},9740,9732
| | |-{gdbus},9739,9732
| | `-{gmain},9733,9732
`-ibus-x11,9738,9732 --kill-daemon
|-{gdbus},9746,9732
`-{gmain},9745,9732
systemctl --user start ibus
systemd,1,1
`-systemd,388,388 --user
|-(sd-pam),390,388
`-ibus-daemon,9911,9911 --replace --xim --panel disable
|-ibus-dconf,9914,9911
| |-{dconf worker},9921,9911
| |-{gdbus},9919,9911
| `-{gmain},9917,9911
|-{gdbus},9920,9911
|-{gmain},9912,9911
`-{pool},9926,9911
I see two differences: 1) ibus-x11 is present only if ibus-daemon is run manually; 2) Note the {pool} process in the systemctl case.
UPDATE²
ibus-x11 will fail to start silently if the DISPLAY env is not set, which is the case in the systemd env. Damn. When I set Environment="DISPLAY=:0" ibus-x11 is started just fine.
So the question remaining here, is why Type=dbus does not work?
I also tried to comment use Type=simple without BusName= to the same result.
UPDATE
I forgot to systemctl daemon-reload!
With Type=simple ibus-daemon *is* started. BUT, ibus-x11, which is supposed to be started with the --xim option, is not started. I guess it's because it forks? I'll try something.
I do feel it should be Type=dbus though, and I also found a file, part of the gnome-settings-daemon package, /usr/share/dbus-1/services/org.freedesktop.IBus.service with the content:
[D-BUS Service]
Name=org.freedesktop.IBus
Exec=/usr/bin/ibus-daemon --replace --xim --panel disable
Any idea how to make systemd happy?
Last edited by lolilolicon (2014-07-31 14:10:37)

The first post is too long... Let me update the status with a new post.
The user service file currently looks like this:
# [email protected]
[Unit]
Description=Intelligent Input Bus
Documentation=man:ibus-daemon(1)
[Service]
Environment="DISPLAY=%I"
ExecStart=/usr/bin/ibus-daemon --replace --xim --panel disable
ExecReload=/usr/bin/ibus restart
ExecStop=/usr/bin/ibus exit
[Install]
WantedBy=default.target
And you can enable it for the current DISPLAY via
% systemctl --user enable "ibus@$DISPLAY.service"
DISPLAY must be set for the --xim option to work.
According to systemd.exec(5), "processes started by user systemd instances inherit all environment variables from the user systemd instance". But at the time the user systemd instance is started, the DISPLAY env is not set yet, so I'm using the %I place holder here.
Although there doesn't seem to be much benefit, I still wonder why Type=dbus doesn't work. Is systemd looking for the wrong bus?

Linked Server unable to Connect in SQL Server 2012 after Restarting SQL Server Service it works fine. Why?

I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
Service it leads to Some other process failures.
RehaanKhan. M

After all the Errors, When I am restarting the SQL Server its working correctly.
Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
The following are the Errors i got connecting to SQl Server.
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Error-2:
Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303) OLE DB provider
"Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412). The step failed.
After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
for to fix above error i have followed the instructions in the following link,
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
Thank you.
RehaanKhan. M

Troble configuring Hyperion Shared Services with SQL Server 2005

I recently installed SQL server (SQL SERVER 2005) in my machine and then am trying to install Hyperion (9.3.1) products. I started with Shared services. It was installed successfully. Problem is occuring when am trying to configure Shared service with SQL database using Hyperion Configuration utility (9.3.1)
The error which is popping up is
Unable to connect to the database for the product Hyperion Shared Services.
Things which I tried from my end
1. Made sure TCP IP Protocol was enabled in SQL server configuration server.
2. hypuser was created in SQl server.
3. hypdb was created in SQL server.
4. Was having dynamic IP address so install Loopback adapter to obtain Static IP address and port.
5. Port and IP address was correct.
Let me know where I am going wrong.
Any help will be greatly appreciated.

Finally got it fixed firewall settings needed to be change : This document helped me a lot to troubleshoot the issue
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
This problem may occur when SQL Server 2005 is not configured to accept incoming local and remote connections, which is disabled by default in SQL Server 2005 Express Edition, SQL Server 2005 Developer Edition and also SQL Server 2005 Enterprise Edition. To solve the connection forbidden problem, SQL Server 2005 needs to configure to allow incoming local and remote connections.
Firstly, ensure that SQL Server 2005 is configured properly to allow incoming connections on the instance of database server, else enable and turn on the local and remote connections setting.
Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
On the “Surface Area Configuration for Services and Connections” page, expand Database Engine tree, click Remote Connections.
Select Local and remote connections, or Local connections only which applicable only if there is no remote system tries to connect to the SQL Server, useful when you just trying to connect and authenticate with the server after installing.
Select the appropriate protocol to enable to local and/or remote connections environment. To ensure maximum compatibility, select Using both TCP/IP and named pipes.
Click Apply button when done.
Click OK button when prompted with the message saying that “Changes to Connection Settings will not take effect until you restart the Database Engine service.”
On the “Surface Area Configuration for Services and Connections” page, expand Database Engine, then click Service.
Click Stop button to stop the SQL Server service.
Wait until the MSSQLSERVER service stops, and then click Start button to restart the MSSQLSERVER service.
Secondly, SQL Server Browser service has to be enabled to allow for local and remote connections if SQL Server 2005 is running by using an instance name and users are not using a specific TCP/IP port number in the connection string.
Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
On the “Surface Area Configuration for Services and Connections” page, click SQL Server Browser.
Select Automatic as the Startup type to start SQL Server Browser service automatically every time system starts.
Click Apply button.
Click on Start button to start the service immediately.
Click OK button.
Finally, if remote computer needs to connect and access SQL Server, an exceptions in Windows Firewall included in Windows XP SP2 (Service Pack 2), Windows Server 2003 and Windows Vista needs to be created. If you’re using third-party firewall system, the exception rules also needed to be created to allow external remote connections to the SQL Server 2005 and SQL Server Browser Service to communicate through the firewall, else connections will be blocked. Consult the firewall manual for more details. Each instance of SQL Server 2005 must have its own exception, together with an exclusion for SQL Server Browser service.
SQL Server 2005 uses an instance ID as part of the path when you install its program files. To create an exception for each instance of SQL Server, you must identify the correct instance ID. To obtain an instance ID, follow these steps:
Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Configuration Manager.
In “SQL Server Configuration Manager”, click the SQL Server Browser service in the right pane, right-click the instance name in the main window, and then click Properties.
On the “SQL Server Browser Properties” page, click the Advanced tab, locate the instance ID in the property list.
Click OK button.
Then create an exception for SQL Server 2005 in Windows Firewall.
Click on Start button, the click on Run and type firewall.cpl, and then click OK. For Windows Vista, type firewall.cpl in Start Search box and press Enter key, then click on Allow a program through Windows Firewall link on left tasks pane.
In “Windows Firewall”, click the Exceptions tab, and then click Add Program.
In the “Add a Program” window, click Browse button.
Click the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program, click Open button. MSSQL.1 with is a placeholder for the instance ID that is obtained from previous procedure. Note that the path may be different depending on where SQL Server 2005 is installed.
Click OK button.
Repeat steps 1 through 5 for each instance of SQL Server 2005 that needs an exception.
For SQL Server Browser service, locate the C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program, and click Open button.
Click OK button.

OEM12c jobs fail with "Error attempting to invoke console command"

Hi gurus,
I'm wondering if someone could help me on this issue.
When I try to execute a job it remains in "Running" state for a long time periord and looking at the jobs details I can see something like this:
Execution: DB11G.WORLD
     DB11G.WORLD     Running     Aug 29, 2012 10:17:31 AM GMT+02:00          57.9 minutes
Step: DeployDriver     DB11G.WORLD     Scheduled
Doing drilldown in "Scheduled" hiperlynk the message displayed is that:
Error attempting to invoke console command, retrying
And this is the Tip offered by oem:
     TIP:      Management Service from which the job step was dispatched.
Everything seems to be working even the Management Service, but any job launched fail in the same way.
Environment:
Oem12c 12.1.0.1.0 with last patch
Oracle Linux 5.7
DB Oracle 11gr2
Any suggestion on this issue will be welcome.
Thanks,
Carlos.

Thanks Eric for your feedback.
It seems that the problem was related with target "Oracle Authorization Policy Manager" because this target was down and after restart OMS and check that this target was up again all pending jobs worked and finished.
However the job_queue_processes value was a good point to take into account so I increase this parameter just in case.
Thanks,
Carlos.
QUERY STATUS = SOLVED

Restarting a systemd.service with a dependency job failed.

Similar Messages

Maybe you are looking for