Sponsored Content
Full Discussion: Systemd cant start my script
Top Forums UNIX for Advanced & Expert Users Systemd cant start my script Post 303036924 by kvaikla on Wednesday 17th of July 2019 12:46:24 PM
Old 07-17-2019
Systemd cant start my script

Hi,
systemd cant start my script, but it work, at command prompt.
Code and execute at command prompt
Code:
#cat collector.sh
#!/bin/bash
case $1 in
        start)
        /home/postgres/scripts/pgwatch2/pgwatch2.sh
        /home/postgres/scripts/pgwatch2/pgwatch2_UI.sh
        ;;
        stop)
        kill -9 `cat  /home/postgres/scripts/pgwatch2/pgwatch2_UI.PID`; rm -f /home/postgres/scripts/pgwatch2/pgwatch2_UI.PID
        kill -9 `cat /home/postgres/scripts/pgwatch2/pgwatch2.PID` ; rm -f /home/postgres/scripts/pgwatch2/pgwatch2.PID
        ;;
        *)
        echo "Usage:  collector.sh start|stop"
        exit 1
esac


#  ./collector.sh start; sleep 3; for PID in `cat *.PID`; do ps -fp $PID;  done;
UID         PID   PPID  C STIME TTY          TIME CMD
postgres 120535      1  2 19:30 pts/1    00:00:00 /opt/app/pgwatch2/pgwatch2-master/pgwatch2/pgwatch2
UID         PID   PPID  C STIME TTY          TIME CMD
postgres 120537      1 21 19:30 pts/1    00:00:00 /bin/python3.6 /opt/app/pgwatch2/pgwatch2-master/webpy/web.py

#cat /home/postgres/scripts/pgwatch2/pgwatch2.sh
#!/bin/bash
. $HOME/.pgprofile_pgwatch2
/opt/app/pgwatch2/pgwatch2-master/pgwatch2/pgwatch2 >> /home/postgres/scripts/pgwatch2/pgwatch2.log 2>&1 &
echo $! > /home/postgres/scripts/pgwatch2/pgwatch2.PID

#cat /home/postgres/scripts/pgwatch2/pgwatch2_UI.sh
#!/bin/bash
. $HOME/.pgprofile_pgwatch2
/bin/python3.6 /opt/app/pgwatch2/pgwatch2-master/webpy/web.py >> /home/postgres/scripts/pgwatch2/pgwatch2_UI.log 2>&1  &
echo $! > /home/postgres/scripts/pgwatch2/pgwatch2_UI.PID

systemd service and start output
Code:
#cat collector.service
[Unit]
Description=Pgwatch2 Gathering Daemon

[Service]
User=postgres
Group=postgres
Type=notify
ExecStart=/home/postgres/scripts/pgwatch2/collector.sh start
[Install]
WantedBy=multi-user.target


# systemctl start collector.service
# systemctl status collector
- collector.service - Pgwatch2 Gathering Daemon
   Loaded: loaded (/etc/systemd/system/collector.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Wed 2019-07-17 19:28:09 EEST; 6s ago
  Process: 120324 ExecStart=/home/postgres/scripts/pgwatch2/collector.sh start (code=exited, status=          0/SUCCESS)
 Main PID: 120324 (code=exited, status=0/SUCCESS)

Jul 17 19:28:09 pgwatch2db.estpak.ee systemd[1]: Starting Pgwatch2 Gathering Daemon...
Jul 17 19:28:09 pgwatch2db.estpak.ee systemd[1]: Started Pgwatch2 Gathering Daemon.

# journalctl -f -u collector

...
Jul 17 19:28:09 pgwatch2db.estpak.ee systemd[1]: Starting Pgwatch2 Gathering Daemon...
Jul 17 19:28:09 pgwatch2db.estpak.ee systemd[1]: Started Pgwatch2 Gathering Daemon.

Why systemd does not like my code?
thnx
br
Kaido
 

9 More Discussions You Might Find Interesting

1. What is on Your Mind?

Linux systemd - Is it really required?

I was testing Fedora 16 mostly to check the new features. One thing that caught my eye as a systems admin is the systemd which is incorporated in Fedora for quite a while now. From the first look of it, this appears more close to Solaris's SMF. With parallelization capabilities, advanced... (0 Replies)
Discussion started by: admin_xor
0 Replies

2. UNIX for Advanced & Expert Users

Systemd

I am writing a program that must determine certain things about services. How can I, or my program, determine which services are started automatically when a given target becomes active. It is my impression that just looking in the target's .wants directory is inadequate because of other... (2 Replies)
Discussion started by: Brandon9000
2 Replies

3. Linux

Systemd hibernation is killing me

I'm on Arch and I have a strange issue with systemctl hibernate command. It hibernates and resumes just fine (I have TuxOnIce), but in the last stage of resume, it completely shuts down my laptop screen, so I cannot see anything even though I know the system resumed just fined and the desktop is... (1 Reply)
Discussion started by: lockheed
1 Replies

4. UNIX for Advanced & Expert Users

Systemd

Hallo I don't know where to put my question so I put it here. I want that systemd let run a script but only on shutdown or reboot and before the system umount the mounted devices. I look on google but only a little information is found and not working Until no, I don't find an solution for... (1 Reply)
Discussion started by: thailand
1 Replies

5. SuSE

Starting mgetty with systemd?

Hello All, OS: openSUSE 13.1 (Bottle) (armv7hl) uname -a: Linux linux.site 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/Linux So this is my first attempt at starting a service at boot with systemd. I've done this with inittab in the past, but I'm having... (0 Replies)
Discussion started by: mrm5102
0 Replies

6. Red Hat

Stdin during rhel 7 bootup (systemd)

Hi All, I had a startup script (rc3.d/S01getinput) which will accept user inputs during the boot up in console. Basically it will prompt for input. It was working fine in RHEL6. Now I have migrated to RHEL 7 and script gets executed as part of the boot up process. But it does not... (1 Reply)
Discussion started by: kalpeer
1 Replies

7. Linux

CentOS7 systemd-timer

hi moring everyone, i has used systemd-timer running the task, i set every 5 second execute 1 times,but the systemd-timer don't by that also random times execute. what's reason. testest.timer configure ------------------------------------------------------------------------ ... (2 Replies)
Discussion started by: shean
2 Replies

8. Shell Programming and Scripting

Have troubles with bash script: xubuntu systemd.link onboard

Hey there. I'm new in write bash scripts in fact this is my first one so please be patient ;). Also english is not my native language but i hope you understand me anyway. I installed xubuntu on my mothers laptop and every time a new version update gets installed the keyboard doesn't work... (9 Replies)
Discussion started by: Apop85
9 Replies

9. UNIX for Beginners Questions & Answers

I can not understand the command from the systemd?

journalctl --since "tomorrow" By idea to show magazines from tomorrow. As it is illogical. Tell me what is the essence of the team with the key tomorrow? Code tags please (1 Reply)
Discussion started by: alekseev
1 Replies
SYSTEMD-NOTIFY(1)                                                 systemd-notify                                                 SYSTEMD-NOTIFY(1)

NAME
systemd-notify - Notify service manager about start-up completion and other daemon status changes SYNOPSIS
systemd-notify [OPTIONS...] [VARIABLE=VALUE...] DESCRIPTION
systemd-notify may be called by daemon scripts to notify the init system about status changes. It can be used to send arbitrary information, encoded in an environment-block-like list of strings. Most importantly, it can be used for start-up completion notification. This is mostly just a wrapper around sd_notify() and makes this functionality available to shell scripts. For details see sd_notify(3). The command line may carry a list of environment variables to send as part of the status update. Note that systemd will refuse reception of status updates from this command unless NotifyAccess= is set for the service unit this command is called from. Note that sd_notify() notifications may be attributed to units correctly only if either the sending process is still around at the time PID 1 processes the message, or if the sending process is explicitly runtime-tracked by the service manager. The latter is the case if the service manager originally forked off the process, i.e. on all processes that match NotifyAccess=main or NotifyAccess=exec. Conversely, if an auxiliary process of the unit sends an sd_notify() message and immediately exits, the service manager might not be able to properly attribute the message to the unit, and thus will ignore it, even if NotifyAccess=all is set for it. systemd-notify will first attempt to invoke sd_notify() pretending to have the PID of the invoking process. This will only succeed when invoked with sufficient privileges. On failure, it will then fall back to invoking it under its own PID. This behaviour is useful in order that when the tool is invoked from a shell script the shell process -- and not the systemd-notify process -- appears as sender of the message, which in turn is helpful if the shell process is the main process of a service, due to the limitations of NotifyAccess=all described above. OPTIONS
The following options are understood: --ready Inform the init system about service start-up completion. This is equivalent to systemd-notify READY=1. For details about the semantics of this option see sd_notify(3). --pid= Inform the init system about the main PID of the daemon. Takes a PID as argument. If the argument is omitted, the PID of the process that invoked systemd-notify is used. This is equivalent to systemd-notify MAINPID=$PID. For details about the semantics of this option see sd_notify(3). --uid=USER Set the user ID to send the notification from. Takes a UNIX user name or numeric UID. When specified the notification message will be sent with the specified UID as sender, in place of the user the command was invoked as. This option requires sufficient privileges in order to be able manipulate the user identity of the process. --status= Send a free-form status string for the daemon to the init systemd. This option takes the status string as argument. This is equivalent to systemd-notify STATUS=.... For details about the semantics of this option see sd_notify(3). --booted Returns 0 if the system was booted up with systemd, non-zero otherwise. If this option is passed, no message is sent. This option is hence unrelated to the other options. For details about the semantics of this option, see sd_booted(3). An alternate way to check for this state is to call systemctl(1) with the is-system-running command. It will return "offline" if the system was not booted with systemd. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. EXAMPLE
Example 1. Start-up Notification and Status Updates A simple shell daemon that sends start-up notifications after having set up its communication channel. During runtime it sends further status updates to the init system: #!/bin/bash mkfifo /tmp/waldo systemd-notify --ready --status="Waiting for data..." while : ; do read a < /tmp/waldo systemd-notify --status="Processing $a" # Do something with $a ... systemd-notify --status="Waiting for data..." done SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), sd_notify(3), sd_booted(3) systemd 237 SYSTEMD-NOTIFY(1)
All times are GMT -4. The time now is 04:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy