Got this error message when trying to start the MGS_VeyronHost_x64_Bandit service manually.
Confirm the Parchment, Game Service, and MGS_VeyronProxy service are running.
Environment info: Axiom GTP93, APP1 - 10.247.173.148
Related
For my service, I have:
#cat my.service
[Unit]
Description=My Service
After=dbus.service
Requires=dbus.service
...
Some time i see that my service fails to get dbus connection
(dbus_bus_get_private() fails without any error msg).
one possibility i think is that dbus is not fully initialized.
From above service file config, i understand when i start my service,
dbus service is started 1st and then my service.
but i am not sure if my service start step is delayed until dbus is
fully up , initialized and running and ready to accept conections.
is there a way to specify this in my service file.
For ex, for systemd-networkd,service, i see it specify like :
#On kdbus systems we pull in the busname explicitly, because it
#carries policy that allows the daemon to acquire its name.
Wants=org.freedesktop.network1.busname
After=org.freedesktop.network1.busname
Can i use same (specifying After/Wants on a dbus name) ?
Appreciate your help on this.
Thanks
Is there some way to trigger an event (e.g. running a script to push some logs to S3) when an EC2 instance is stopped/terminated?
I have looked into triggering the script using a service in /usr/lib/systemd/system but I haven't had any luck with that yet. I have heard that networking capabilities on the instance can be shutdown before a service is triggered and if true, that could be why the script is not executing correctly.
So the answer is not really AWS specific, but it is working for me now (tested on EC2 instance stopping and terminating).
I've created a system.d service file:
/usr/lib/systemd/system/my_shutdown.service
[Unit]
Description=my_shutdown Service
Before=shutdown.target reboot.target halt.target
Requires=network-online.target network.target
[Service]
KillMode=none
ExecStart=/bin/true
ExecStop=/path/to/my_script.sh
RemainAfterExit=yes
Type=oneshot
[Install]
WantedBy=multi-user.target
Added this service to multi-user.target:
systemctl enable my_shutdown.service
Alternatively you can manually create the symlink:
ln -s /usr/lib/systemd/system/my_shutdown.service /etc/systemd/system/multi-user.target.wants/my_shutdown.service
Started the service and tested by stopping/terminating the instance.
systemctl start my_shutdown.service
My understanding:
Description: a description of our service.
Before: we want our service to stop before these targets are started.
Requires: our service requires that network capabilities are available. These targets must not be stopped before our service starts/stops.
KillMode: none; do not kill our process.
ExecStart: /bin/true; a command that does nothing but returns a success. Run when are service is started.
ExecStop: the script to run. Run when are service is being stopped.
RemainAfterExit: consider our service active even when all its processes exited.
Type: oneshot; it is expected that the process has to exit before systemd starts follow-up units.
WantedBy: the target we want to add our service to.
References:
https://www.freedesktop.org/software/systemd/man/systemd.service.html
https://www.freedesktop.org/software/systemd/man/systemd.kill.html#
https://www.freedesktop.org/software/systemd/man/systemd.special.html
https://www.freedesktop.org/software/systemd/man/systemd.target.html
You can trigger events, such as pushing logs to S3 on specific events, with CloudWatch... Learn more here: https://aws.amazon.com/cloudwatch/
I have a service resource but I can't get chef to start it, instead chef just spits out an error message:
SystemCallError: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service.
I'm not sure what to do to fix this and I can't find anything on this error (could be I'm not looking in the right place).
The service is distributed as a gem that's installed.
The service itself is a Sinatra app that uses the win32-service gem to start it as a service
The platform is windows server (I know but I have no choice, I have to use windows server)
The code in the chef recipe for this service is:
service service_name do
init_command ("#{%x(gem env gemdir).strip.gsub('/','\\')}\\gems\\#{service_name}-#{installing_version}")
start_command "rake service:start"
stop_command "rake service:stop"
reload_command "rake service:reload"
restart_command "rake service:restart"
supports start: true, restart: true, reload: true
action [:enable,:start]
end
The issue is not with Chef, but with your service itself. Typically when I'm in this situation, I will login manually and attempt to start the service. Sometimes that will give you additional information. Also, take a look at the log files for your app and see if you can figure out why it's not starting.
Ultimately, Chef just calls your init and start commands, but it can't do much if those commands fail.
When I create a new windows service on a machine, I have to run the EXE, which runs under my account, before I can actually start the service with its "real" credentials.
I'm using the sc commands to create, config, and start the service:
sc create "Presto Self Updating Service Host" binPath= "C:\Program Files (x86)\Presto\Presto Self Updating Service Host\SelfUpdatingServiceHost.exe"
sc config "Presto Self Updating Service Host" obj= "serviceAccount" password= "pw" start= auto
sc start "Presto Self Updating Service Host"
The service won't start until I go into the service properties and enter the password manually. That causes the service account to get "logon as a service rights." I've given up on trying to automate that. So, after I do that part, I start the service and I get an error message:
There is nothing in the event log about a failure. So what I do is run the EXE myself. That works. Then I close the EXE and start the service (with the serviceAccount user) and then it works. Any idea why it running it as me first would finally cause it to work as the other user?
While working on configuring the Shibbolet SP, I had to stop and start the shibd service many times after reconfiguring the shibboleth2.xml file.
first it worked ok, but then I couldn't start it again!
when running this command on cmd C:\>net start shibd_default, I got the following:
The Shibboleth 2 Daemon <Default> service is starting.
The Shibboleth 2 Daemon <Default> service could not be started.
The service did not report an error.
and when attempting to run it from Control Panel > Services > Administrative Tools , I got this error
The Shibboleth 2 Daemon <Default> service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
I've re-installed the Shibboleth SP to overcome this problem, but still getting this error!
Can anyone help me figure this out?
Thanks
Please check your log files at C:\opt\shibboleth-sp\var\log\shibboleth for errors.
IF there is a XML configuration error, the service won't load properly.
I Got an error similar to the one below:
ERROR Shibboleth.Config : error while loading resource (C:/opt/shibboleth-sp/etc/shibboleth/shibboleth2.xml): XML error(s) during parsing, check log for specifics
2013-05-13 10:59:13 FATAL Shibboleth.Config : caught exception while loading configuration: XML error(s) during parsing, check log for specifics