Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
On Do, 25.07.19 19:16, Debraj Manna (subharaj.ma...@gmail.com) wrote: > Thanks Mantas for replying. > > ExecStartPre=-/bin/su ubuntu -c "/home/ubuntu/build-target/ > kafka/kafka-systemd-prestart.sh" > ExecStart=/bin/su ubuntu -c "/home/ubuntu/build-target/ > kafka/kafka-systemd-health.sh" > ExecStopPost=-/bin/bash /home/ubuntu/build-target/ > kafka/kafka-systemd-poststop.sh > > If I specify User= then all the scripts will be executed with that user. > Can you let me know if I only need to execute > kafka-systemd-prestart.sh and kafka-systemd-health.sh > with let's say ubuntu user and kafka-systemd-poststop.sh with root user > what is the recommended way to do this? Use "ExecStartPre=+…" for running some ExecXYZ= lines with full privileges. See documentation for details. You may combine "+" and "-" if you like. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
On Do, 25.07.19 14:20, Mantas Mikulėnas (graw...@gmail.com) wrote: > Take a look at `journalctl -o verbose SYSLOG_IDENTIFIER=su _PID=38464`. > > I suspect the messages *are* in the journal, just not tagged with > UNIT=kafka.service anymore. In some distros, `su` is actually configured to > call pam_systemd and set up a new systemd-logind session – when this > happens, the process is moved out of kafka.service into a user session > scope, and its syslog messages are grouped accordingly. It shouldn't just be "some distros" btw, it hopefully should be all. Everything else would be a bug. > Consider replacing `su` with `runuser`, or indeed with systemd's [Service] > User= option. "runuser" creates a PAM session too. "setpriv" is the command to use. (Yes don't ask me why we have all three of su, runuser and setpriv being different but also the same...) Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
On Do, 25.07.19 15:55, Debraj Manna (subharaj.ma...@gmail.com) wrote: > I have unit file which looks like below. I am seeing some of the echo are > showing up in syslog but not in journalctl. Can someone let me know what is > going on? > systemd version 229 running on Ubuntu 16. > > ExecStartPre=-/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh" > ExecStart=/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh" If you use "su" this creates a new login session (and thus a scope unit) for your program, and thus any processes/logs will be associated with that login session scope unit, and not with the service unit you are writing here. Use "User=" to run services under specific user identities. Or at least use "setpriv" rather than "su" since the former just changes privs, but doesn't actually acquire a PAM session and everything. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
Am 25.07.19 um 15:46 schrieb Debraj Manna: > Thanks Mantas for replying. > > ExecStartPre=-/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh" > ExecStart=/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh" > ExecStopPost=-/bin/bash > /home/ubuntu/build-target/kafka/kafka-systemd-poststop.sh > > If I specify User= then all the scripts will be executed with that user. > Can you let me know if I only need to execute kafka-systemd-prestart.sh > and kafka-systemd-health.sh with let's sayubuntu user > and kafka-systemd-poststop.sh withroot user what is the recommended way > to do this? to split that mess into different services with proper dependencies ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
Thanks Mantas for replying. ExecStartPre=-/bin/su ubuntu -c "/home/ubuntu/build-target/ kafka/kafka-systemd-prestart.sh" ExecStart=/bin/su ubuntu -c "/home/ubuntu/build-target/ kafka/kafka-systemd-health.sh" ExecStopPost=-/bin/bash /home/ubuntu/build-target/ kafka/kafka-systemd-poststop.sh If I specify User= then all the scripts will be executed with that user. Can you let me know if I only need to execute kafka-systemd-prestart.sh and kafka-systemd-health.sh with let's say ubuntu user and kafka-systemd-poststop.sh with root user what is the recommended way to do this? On Thu, Jul 25, 2019 at 4:50 PM Mantas Mikulėnas wrote: > On Thu, Jul 25, 2019 at 1:26 PM Debraj Manna > wrote: > >> I have unit file which looks like below. I am seeing some of the echo are >> showing up in syslog but not in journalctl. Can someone let me know what is >> going on? >> systemd version 229 running on Ubuntu 16. >> >> [Unit] >> Description=Kafka Service >> >> [Service] >> Type=simple >> Environment=KAFKA_HOME=/home/ubuntu/deploy/kafka >> Environment=LIB_DIR=/var/lib/kafka >> Environment=LOG_DIR=/var/log/kafka >> Environment=TEMP_DIR=/home/ubuntu/tmp >> >> Environment=TOOLS_JAR=/home/ubuntu/build-target/common-utils/tools-0.001-SNAPSHOT.jar >> Environment=MIN_DATA_PARTITION_FREE_SPACE_PCT=10 >> Environment=MIN_DATA_PARTITION_FREE_SPACE_GB=10 >> Environment=DATA_PARTITION_NAME=/var >> >> ExecStartPre=-/bin/mkdir -p /var/log/kafka >> ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/log/kafka >> ExecStartPre=-/bin/mkdir -p /var/lib/kafka/kafka-logs >> ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/lib/kafka/kafka-logs >> ExecStartPre=-/bin/rm -f /var/log/kafka/kafka-logs/.lock >> ExecStartPre=-/bin/mkdir -p /home/ubuntu/tmp >> ExecStartPre=-/bin/chown -R ubuntu:ubuntu /home/ubuntu/tmp >> ExecStartPre=-/bin/chmod -R 775 /home/ubuntu/tmp >> ExecStartPre=-/bin/su ubuntu -c >> "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh" >> ExecStart=/bin/su ubuntu -c >> "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh" >> >> [...] > >> Doing sudo journalctl -u kafka.service looks like below >> >> Jul 25 07:41:39 platform2 systemd[1]: Started Kafka Service. >> Jul 25 07:41:39 platform2 su[39160]: Successful su for ubuntu by root >> Jul 25 07:41:39 platform2 su[39160]: + ??? root:ubuntu >> Jul 25 07:41:39 platform2 su[39160]: pam_unix(su:session): session opened >> for user ubuntu by (uid=0) >> Jul 25 07:41:40 platform2 bash[39192]: [Jul 25 2019 07:41:40-572] Exiting >> kafka... >> >> I am not seeing some of the echo from kafka-systemd-prestart.sh in journatl >> but I am seeing those logs in syslog >> >> Jul 25 10:17:03 platform2 su[38464]: WatchedEvent state:SyncConnected >> type:None path:null >> Jul 25 10:17:03 platform2 su[38464]: Node does not exist: /brokers/ids/2 >> Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-343] partition >> /var free% 9 required% 10 freegb 134 required 10 >> Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-344] Sufficient >> disk space is not available, sleeping for 60 seconds before exiting... >> >> > Take a look at `journalctl -o verbose SYSLOG_IDENTIFIER=su _PID=38464`. > > I suspect the messages *are* in the journal, just not tagged with > UNIT=kafka.service anymore. In some distros, `su` is actually configured to > call pam_systemd and set up a new systemd-logind session – when this > happens, the process is moved out of kafka.service into a user session > scope, and its syslog messages are grouped accordingly. > > Consider replacing `su` with `runuser`, or indeed with systemd's [Service] > User= option. > > -- > Mantas Mikulėnas > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
On Thu, Jul 25, 2019 at 1:26 PM Debraj Manna wrote: > I have unit file which looks like below. I am seeing some of the echo are > showing up in syslog but not in journalctl. Can someone let me know what is > going on? > systemd version 229 running on Ubuntu 16. > > [Unit] > Description=Kafka Service > > [Service] > Type=simple > Environment=KAFKA_HOME=/home/ubuntu/deploy/kafka > Environment=LIB_DIR=/var/lib/kafka > Environment=LOG_DIR=/var/log/kafka > Environment=TEMP_DIR=/home/ubuntu/tmp > > Environment=TOOLS_JAR=/home/ubuntu/build-target/common-utils/tools-0.001-SNAPSHOT.jar > Environment=MIN_DATA_PARTITION_FREE_SPACE_PCT=10 > Environment=MIN_DATA_PARTITION_FREE_SPACE_GB=10 > Environment=DATA_PARTITION_NAME=/var > > ExecStartPre=-/bin/mkdir -p /var/log/kafka > ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/log/kafka > ExecStartPre=-/bin/mkdir -p /var/lib/kafka/kafka-logs > ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/lib/kafka/kafka-logs > ExecStartPre=-/bin/rm -f /var/log/kafka/kafka-logs/.lock > ExecStartPre=-/bin/mkdir -p /home/ubuntu/tmp > ExecStartPre=-/bin/chown -R ubuntu:ubuntu /home/ubuntu/tmp > ExecStartPre=-/bin/chmod -R 775 /home/ubuntu/tmp > ExecStartPre=-/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh" > ExecStart=/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh" > > [...] > Doing sudo journalctl -u kafka.service looks like below > > Jul 25 07:41:39 platform2 systemd[1]: Started Kafka Service. > Jul 25 07:41:39 platform2 su[39160]: Successful su for ubuntu by root > Jul 25 07:41:39 platform2 su[39160]: + ??? root:ubuntu > Jul 25 07:41:39 platform2 su[39160]: pam_unix(su:session): session opened for > user ubuntu by (uid=0) > Jul 25 07:41:40 platform2 bash[39192]: [Jul 25 2019 07:41:40-572] Exiting > kafka... > > I am not seeing some of the echo from kafka-systemd-prestart.sh in journatl > but I am seeing those logs in syslog > > Jul 25 10:17:03 platform2 su[38464]: WatchedEvent state:SyncConnected > type:None path:null > Jul 25 10:17:03 platform2 su[38464]: Node does not exist: /brokers/ids/2 > Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-343] partition > /var free% 9 required% 10 freegb 134 required 10 > Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-344] Sufficient > disk space is not available, sleeping for 60 seconds before exiting... > > Take a look at `journalctl -o verbose SYSLOG_IDENTIFIER=su _PID=38464`. I suspect the messages *are* in the journal, just not tagged with UNIT=kafka.service anymore. In some distros, `su` is actually configured to call pam_systemd and set up a new systemd-logind session – when this happens, the process is moved out of kafka.service into a user session scope, and its syslog messages are grouped accordingly. Consider replacing `su` with `runuser`, or indeed with systemd's [Service] User= option. -- Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
Thanks Silvio for replying. I will check your suggestions.
But it appears this is some issue with systemd version 229 as mentioned in
https://unix.stackexchange.com/a/417632
On Thu, Jul 25, 2019 at 4:09 PM Silvio Knizek wrote:
> Am Donnerstag, den 25.07.2019, 15:55 +0530 schrieb Debraj Manna:
> > I have unit file which looks like below. I am seeing some of the echo
> > are
> > showing up in syslog but not in journalctl. Can someone let me know
> > what is
> > going on?
> > systemd version 229 running on Ubuntu 16.
> >
> > [Unit]
> > Description=Kafka Service
> >
> > [Service]
> > Type=simple
> > Environment=KAFKA_HOME=/home/ubuntu/deploy/kafka
> > Environment=LIB_DIR=/var/lib/kafka
> > Environment=LOG_DIR=/var/log/kafka
> > Environment=TEMP_DIR=/home/ubuntu/tmp
> > Environment=TOOLS_JAR=/home/ubuntu/build-target/common-utils/tools-
> > 0.001-SNAPSHOT.jar
> > Environment=MIN_DATA_PARTITION_FREE_SPACE_PCT=10
> > Environment=MIN_DATA_PARTITION_FREE_SPACE_GB=10
> > Environment=DATA_PARTITION_NAME=/var
> >
> > ExecStartPre=-/bin/mkdir -p /var/log/kafka
> > ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/log/kafka
> > ExecStartPre=-/bin/mkdir -p /var/lib/kafka/kafka-logs
> > ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/lib/kafka/kafka-logs
> > ExecStartPre=-/bin/rm -f /var/log/kafka/kafka-logs/.lock
> > ExecStartPre=-/bin/mkdir -p /home/ubuntu/tmp
> > ExecStartPre=-/bin/chown -R ubuntu:ubuntu /home/ubuntu/tmp
> > ExecStartPre=-/bin/chmod -R 775 /home/ubuntu/tmp
> > ExecStartPre=-/bin/su ubuntu -c
> > "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh"
> > ExecStart=/bin/su ubuntu -c
> > "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh"
> > ExecStopPost=-/bin/bash
> > /home/ubuntu/build-target/kafka/kafka-systemd-poststop.sh
> > RestartSec=2s
> > Restart=always
> > LimitNOFILE=65535
> > KillSignal=SIGTERM
> > SendSIGKILL=no
> > SuccessExitStatus=1 143
> >
> > [Install]
> > WantedBy=multi-user.target
> >
> > kafka-systemd-prestart.sh looks like below
> >
> > echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] Starting kafka..."
> > timeout --signal=sigkill 600s java -cp "$TOOLS_JAR"
> > com.vnera.tools.kafka.KafkaIndexValidator "$LIB_DIR/kafka-logs"
> > "$KAFKA_HOME/config/server.properties" true
> > broker_id=`sudo grep -F "broker.id"
> > $KAFKA_HOME/config/server.properties | awk -F '=' '{print $2}'`
> > zookeeper_list=`sudo grep -F "zookeeper.connect="
> > $KAFKA_HOME/config/server.properties | awk -F '=' '{print $2}'`
> > echo "attempting removal of broker id $broker_id"
> >
> > used_pct=`df ${DATA_PARTITION_NAME} --output=pcent | grep -v Use |
> > grep -o '[^ ]*[^ %]'`
> > free_pct=$(expr 100 - $used_pct)
> > free_gb=`df -h ${DATA_PARTITION_NAME} --output=avail --block-size G |
> > grep -v Avail | grep -o '[^ ]*[^ G]'`
> > echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] partition
> > ${DATA_PARTITION_NAME} free% $free_pct required%
> > ${MIN_DATA_PARTITION_FREE_SPACE_PCT} freegb ${free_gb} required
> > ${MIN_DATA_PARTITION_FREE_SPACE_GB}"
> >
> > # Some other code
> >
> > kafka-systemd-poststop.sh looks like below
> >
> > ---
> >
> > echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] Exiting kafka..."
> > cmd="ps -ef | grep -v grep | grep kafkaServer"
> >
> > # Some other code
> >
> > echo "completed exiting kafka"
> >
> > Doing sudo journalctl -u kafka.service looks like below
> >
> > Jul 25 07:41:39 platform2 systemd[1]: Started Kafka Service.
> > Jul 25 07:41:39 platform2 su[39160]: Successful su for ubuntu by root
> > Jul 25 07:41:39 platform2 su[39160]: + ??? root:ubuntu
> > Jul 25 07:41:39 platform2 su[39160]: pam_unix(su:session): session
> > opened for user ubuntu by (uid=0)
> > Jul 25 07:41:40 platform2 bash[39192]: [Jul 25 2019 07:41:40-572]
> > Exiting kafka...
> >
> > I am not seeing some of the echo from kafka-systemd-prestart.sh in
> > journatl but I am seeing those logs in syslog
> >
> > Jul 25 10:17:03 platform2 su[38464]: WatchedEvent state:SyncConnected
> > type:None path:null
> > Jul 25 10:17:03 platform2 su[38464]: Node does not exist:
> > /brokers/ids/2
> > Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-343]
> > partition /var free% 9 required% 10 freegb 134 required 10
> > Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-344]
> > Sufficient disk space is not available, sleeping for 60 seconds
> > before
> > exiting...
>
> Hi,
>
> first of all, take a look at man:tmpfiles.d to replace the whole
> mkdir/chmod ExecStartPre= stuff.
> Second, don't use »su« in .service. It breaks stuff by creating a new
> cgroup hierarchy because it's run through pam. Use User= instead.
> With both this changes your shell scripts shouldn't be necessary at all
> and than everything should land in the journal.
> Please don't re-invent the stuff systemd is already providing.
>
> BR
> Silvio
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
Am Donnerstag, den 25.07.2019, 15:55 +0530 schrieb Debraj Manna:
> I have unit file which looks like below. I am seeing some of the echo
> are
> showing up in syslog but not in journalctl. Can someone let me know
> what is
> going on?
> systemd version 229 running on Ubuntu 16.
>
> [Unit]
> Description=Kafka Service
>
> [Service]
> Type=simple
> Environment=KAFKA_HOME=/home/ubuntu/deploy/kafka
> Environment=LIB_DIR=/var/lib/kafka
> Environment=LOG_DIR=/var/log/kafka
> Environment=TEMP_DIR=/home/ubuntu/tmp
> Environment=TOOLS_JAR=/home/ubuntu/build-target/common-utils/tools-
> 0.001-SNAPSHOT.jar
> Environment=MIN_DATA_PARTITION_FREE_SPACE_PCT=10
> Environment=MIN_DATA_PARTITION_FREE_SPACE_GB=10
> Environment=DATA_PARTITION_NAME=/var
>
> ExecStartPre=-/bin/mkdir -p /var/log/kafka
> ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/log/kafka
> ExecStartPre=-/bin/mkdir -p /var/lib/kafka/kafka-logs
> ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/lib/kafka/kafka-logs
> ExecStartPre=-/bin/rm -f /var/log/kafka/kafka-logs/.lock
> ExecStartPre=-/bin/mkdir -p /home/ubuntu/tmp
> ExecStartPre=-/bin/chown -R ubuntu:ubuntu /home/ubuntu/tmp
> ExecStartPre=-/bin/chmod -R 775 /home/ubuntu/tmp
> ExecStartPre=-/bin/su ubuntu -c
> "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh"
> ExecStart=/bin/su ubuntu -c
> "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh"
> ExecStopPost=-/bin/bash
> /home/ubuntu/build-target/kafka/kafka-systemd-poststop.sh
> RestartSec=2s
> Restart=always
> LimitNOFILE=65535
> KillSignal=SIGTERM
> SendSIGKILL=no
> SuccessExitStatus=1 143
>
> [Install]
> WantedBy=multi-user.target
>
> kafka-systemd-prestart.sh looks like below
>
> echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] Starting kafka..."
> timeout --signal=sigkill 600s java -cp "$TOOLS_JAR"
> com.vnera.tools.kafka.KafkaIndexValidator "$LIB_DIR/kafka-logs"
> "$KAFKA_HOME/config/server.properties" true
> broker_id=`sudo grep -F "broker.id"
> $KAFKA_HOME/config/server.properties | awk -F '=' '{print $2}'`
> zookeeper_list=`sudo grep -F "zookeeper.connect="
> $KAFKA_HOME/config/server.properties | awk -F '=' '{print $2}'`
> echo "attempting removal of broker id $broker_id"
>
> used_pct=`df ${DATA_PARTITION_NAME} --output=pcent | grep -v Use |
> grep -o '[^ ]*[^ %]'`
> free_pct=$(expr 100 - $used_pct)
> free_gb=`df -h ${DATA_PARTITION_NAME} --output=avail --block-size G |
> grep -v Avail | grep -o '[^ ]*[^ G]'`
> echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] partition
> ${DATA_PARTITION_NAME} free% $free_pct required%
> ${MIN_DATA_PARTITION_FREE_SPACE_PCT} freegb ${free_gb} required
> ${MIN_DATA_PARTITION_FREE_SPACE_GB}"
>
> # Some other code
>
> kafka-systemd-poststop.sh looks like below
>
> ---
>
> echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] Exiting kafka..."
> cmd="ps -ef | grep -v grep | grep kafkaServer"
>
> # Some other code
>
> echo "completed exiting kafka"
>
> Doing sudo journalctl -u kafka.service looks like below
>
> Jul 25 07:41:39 platform2 systemd[1]: Started Kafka Service.
> Jul 25 07:41:39 platform2 su[39160]: Successful su for ubuntu by root
> Jul 25 07:41:39 platform2 su[39160]: + ??? root:ubuntu
> Jul 25 07:41:39 platform2 su[39160]: pam_unix(su:session): session
> opened for user ubuntu by (uid=0)
> Jul 25 07:41:40 platform2 bash[39192]: [Jul 25 2019 07:41:40-572]
> Exiting kafka...
>
> I am not seeing some of the echo from kafka-systemd-prestart.sh in
> journatl but I am seeing those logs in syslog
>
> Jul 25 10:17:03 platform2 su[38464]: WatchedEvent state:SyncConnected
> type:None path:null
> Jul 25 10:17:03 platform2 su[38464]: Node does not exist:
> /brokers/ids/2
> Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-343]
> partition /var free% 9 required% 10 freegb 134 required 10
> Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-344]
> Sufficient disk space is not available, sleeping for 60 seconds
> before
> exiting...
Hi,
first of all, take a look at man:tmpfiles.d to replace the whole
mkdir/chmod ExecStartPre= stuff.
Second, don't use »su« in .service. It breaks stuff by creating a new
cgroup hierarchy because it's run through pam. Use User= instead.
With both this changes your shell scripts shouldn't be necessary at all
and than everything should land in the journal.
Please don't re-invent the stuff systemd is already providing.
BR
Silvio
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog
I have unit file which looks like below. I am seeing some of the echo are
showing up in syslog but not in journalctl. Can someone let me know what is
going on?
systemd version 229 running on Ubuntu 16.
[Unit]
Description=Kafka Service
[Service]
Type=simple
Environment=KAFKA_HOME=/home/ubuntu/deploy/kafka
Environment=LIB_DIR=/var/lib/kafka
Environment=LOG_DIR=/var/log/kafka
Environment=TEMP_DIR=/home/ubuntu/tmp
Environment=TOOLS_JAR=/home/ubuntu/build-target/common-utils/tools-0.001-SNAPSHOT.jar
Environment=MIN_DATA_PARTITION_FREE_SPACE_PCT=10
Environment=MIN_DATA_PARTITION_FREE_SPACE_GB=10
Environment=DATA_PARTITION_NAME=/var
ExecStartPre=-/bin/mkdir -p /var/log/kafka
ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/log/kafka
ExecStartPre=-/bin/mkdir -p /var/lib/kafka/kafka-logs
ExecStartPre=-/bin/chown -R ubuntu:ubuntu /var/lib/kafka/kafka-logs
ExecStartPre=-/bin/rm -f /var/log/kafka/kafka-logs/.lock
ExecStartPre=-/bin/mkdir -p /home/ubuntu/tmp
ExecStartPre=-/bin/chown -R ubuntu:ubuntu /home/ubuntu/tmp
ExecStartPre=-/bin/chmod -R 775 /home/ubuntu/tmp
ExecStartPre=-/bin/su ubuntu -c
"/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh"
ExecStart=/bin/su ubuntu -c
"/home/ubuntu/build-target/kafka/kafka-systemd-health.sh"
ExecStopPost=-/bin/bash
/home/ubuntu/build-target/kafka/kafka-systemd-poststop.sh
RestartSec=2s
Restart=always
LimitNOFILE=65535
KillSignal=SIGTERM
SendSIGKILL=no
SuccessExitStatus=1 143
[Install]
WantedBy=multi-user.target
kafka-systemd-prestart.sh looks like below
echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] Starting kafka..."
timeout --signal=sigkill 600s java -cp "$TOOLS_JAR"
com.vnera.tools.kafka.KafkaIndexValidator "$LIB_DIR/kafka-logs"
"$KAFKA_HOME/config/server.properties" true
broker_id=`sudo grep -F "broker.id"
$KAFKA_HOME/config/server.properties | awk -F '=' '{print $2}'`
zookeeper_list=`sudo grep -F "zookeeper.connect="
$KAFKA_HOME/config/server.properties | awk -F '=' '{print $2}'`
echo "attempting removal of broker id $broker_id"
used_pct=`df ${DATA_PARTITION_NAME} --output=pcent | grep -v Use |
grep -o '[^ ]*[^ %]'`
free_pct=$(expr 100 - $used_pct)
free_gb=`df -h ${DATA_PARTITION_NAME} --output=avail --block-size G |
grep -v Avail | grep -o '[^ ]*[^ G]'`
echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] partition
${DATA_PARTITION_NAME} free% $free_pct required%
${MIN_DATA_PARTITION_FREE_SPACE_PCT} freegb ${free_gb} required
${MIN_DATA_PARTITION_FREE_SPACE_GB}"
# Some other code
kafka-systemd-poststop.sh looks like below
---
echo "[`date +"%h %d %Y %H:%M:%S-%3N"`] Exiting kafka..."
cmd="ps -ef | grep -v grep | grep kafkaServer"
# Some other code
echo "completed exiting kafka"
Doing sudo journalctl -u kafka.service looks like below
Jul 25 07:41:39 platform2 systemd[1]: Started Kafka Service.
Jul 25 07:41:39 platform2 su[39160]: Successful su for ubuntu by root
Jul 25 07:41:39 platform2 su[39160]: + ??? root:ubuntu
Jul 25 07:41:39 platform2 su[39160]: pam_unix(su:session): session
opened for user ubuntu by (uid=0)
Jul 25 07:41:40 platform2 bash[39192]: [Jul 25 2019 07:41:40-572]
Exiting kafka...
I am not seeing some of the echo from kafka-systemd-prestart.sh in
journatl but I am seeing those logs in syslog
Jul 25 10:17:03 platform2 su[38464]: WatchedEvent state:SyncConnected
type:None path:null
Jul 25 10:17:03 platform2 su[38464]: Node does not exist: /brokers/ids/2
Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-343]
partition /var free% 9 required% 10 freegb 134 required 10
Jul 25 10:17:03 platform2 su[38464]: [Jul 25 2019 10:17:03-344]
Sufficient disk space is not available, sleeping for 60 seconds before
exiting...
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
