Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: AIX subsystem stops partially
Top Forums Shell Programming and Scripting AIX subsystem stops partially Post 303044567 by Tankz on Wednesday 26th of February 2020 04:04:55 PM
Old 02-26-2020
AIX subsystem stops partially
I have a shell script and I decided to create AIX service with subsystem.
. Here how the subsystem is defined:

Code:
    mkssys -s mytest -p "/home/tester/testServices/bin/test/script.sh" -a "start" -u 206 -R -Q -d -S -n 9 -f 15

Now the `script.sh` is the following script:
Code:
```
#!/bin/bash
 
 
PRINT_SCRIPT=/home/tester/testServices/Screen.sh
LOG_FILE="/home/tester/testServices/bin/test/log.txt"
 
 
   echo "Begin script" >> "$LOG_FILE"
 
 
 
 trap sigquit 9 15
 sigquit()
 {
 #   set -x
   
      echo "Stop case" >> "$LOG_FILE"
PID=`ps -ef | grep screen.sh | grep -v grep | awk '{print $2}'`
        kill -9 $PID
     exit 0
 }
 
 
 
case "$1" in
 
  start)
        echo "Starting screen.sh" >> "$LOG_FILE"
        $PRINT_SCRIPT
 
        ;;
  stop)
        echo "Stopping screen.sh" >> "$LOG_FILE"
        PID=`ps -ef | grep screen.sh | grep -v grep | awk '{print $2}'`
        kill -9 $PID
        ;;
  *)
        echo "USAGE " >> "$LOG_FILE"
 
        echo "Usage:  {start|stop}" >&2
        exit 1
        ;;
esac
exit 0
```


I have made the subsystem to be used under the user with ID=206, and i have added in /etc/sudoers permissions to start/stop the service .Interestingly when I start it via `sudo startsrc -s mytest` , the subsystem goes to active status (via lssrc -a) and the start) clause gets called and i see indeed a logging in the file, however when i stop the subsystem via `sudo stopsrc -s mytest` the subsystem goes from active to inoperative ,However I don't see any logging in the file and the underlying script $PRINT_SCRIPT keeps running .Now my theory is that it doesn't even get called since even "Begin script" is not logged into the file on stop.


Interestingly when i make the same service but change the user from 206 to 0 (aka root) and start and stop it as a root everything works perfect.Why under the user with ID=206 it doesn't log anything?And is this the correct way a shell script to understand from the AIX SRC that it has to stop, if not what is the practice to make a service understand that it has to stop , as you can see I have checked if "stop" arguments is passed and also tried with signals in the sigquit() but it doesn't work under non-root user.Also under root user, on stop it doesn't log anything but the script stops working.
Last edited by Tankz; 02-26-2020 at 05:14 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NFS client subsystem hang up on boot

Hi, I have a Unix box running HP-UX 10.20 and it suddenly won't boot. Every time it goes down the boot checklist, it hangs on "NFS client subsystem" and just continues to say busy/wait. I have read something about the /etc/auto_master but don't quite understand what has to happen to fix it. ... (4 Replies)
Discussion started by: Asheley Ryan
4 Replies

2. UNIX for Advanced & Expert Users

subsystem failure

aix 4.3 I get the following error from the errpt log BD797922 0306170008 P H enclosure0 SUBSYSTEM FAILURE I'm not clear on this kind of error. It never happened to me. What do this errors mean, and how do I clear or solve them? Any help is appreciated. (2 Replies)
Discussion started by: andwhat
2 Replies

3. AIX

Subsystem Component Failure

Hello All, Does some one have any idea about the subsystem component failure. Errpt command throws below errors for my server :- # errpt IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION B9735AF4 0304222408 P H hdisk5 SUBSYSTEM COMPONENT FAILURE B9735AF4 0304222408 P H... (1 Reply)
Discussion started by: Shrek
1 Replies

4. AIX

Generating a Subsystem

Hello, I'm trying to generate a subsystem which supports startsrc, stopsrc and refresh I want to specify special arguments in case of stopsrc and refresh for example: startsrc: /bin/testscript start stopsrc: /bin/testscript stop refresh: /bin/testscript restart which should be... (0 Replies)
Discussion started by: funksen
0 Replies

5. AIX

AIX 5.3 ML10 new install, rsh only partially working

Two boxes we just reloaded to use as a two node HACMP cluster to insure our software is compatible. Install disks we received at our library on 5/2009 AIX 5.3-ML10 For sake of argument names ibmaix1 and ibmaix2 On both: ibmaix1# oslevel -r 5300-10 .rhosts files with 600 permissions... (0 Replies)
Discussion started by: DrKillPatient
0 Replies

6. Ubuntu

Getting Subsystem ID/Vendor

Hey Guys ... How I can look up Subsystem ID of the WIFI card under Ubuntu... I did try lspci but its outputting only Vendor and Dev no subsys ... I need same data as below ( Windows ) PCI\VEN_168C&DEV_001C&SUBSYS_04281468&REV_01\4&1BF192B7&0&0020 thank you happy new year ! (2 Replies)
Discussion started by: NDxiak
2 Replies

7. UNIX for Dummies Questions & Answers

SFTP subsystem requests

Hi there, what is the meaning of this line: SFTP subsystem requests: 5 Time(s) in: /var/mail/root??? Tks in advance, GB (0 Replies)
Discussion started by: Giordano Bruno
0 Replies

8. AIX

sftp : have to specify subsystem from client side

I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies

9. HP-UX

[HP UNIX B.10.20] NFS Client SubSystem fail

Recently moved a HP Unix B.10.20 system from US to Thailand, and everything is work well in US but after we changed: 1. set_parms ip_address (change the IP to TH range) 2. set_parms addl_netwrk (change the Subnet, Gateway, Domain name, DNS Svr Name, and DNS IP) 3. vi /etc/hosts (to commented... (4 Replies)
Discussion started by: beta911
4 Replies

10. AIX

AIX 7.1 booting stops at C1922000 C19220FF

Hi, we have the p6 server running AIX 7.1 it suddenly stops working. I tried to re-cycle power but it keeps stopping at C19220FF. Activate the service processor pinhole reset switch but still stops at the same code. Error logs: 1. 501A1181 2016-06-08 22:06:20 'Service Process'... (1 Reply)
Discussion started by: lilyn
1 Replies

LEARN ABOUT V7

dh_systemd_start

DH_SYSTEMD_START(1)						     Debhelper						       DH_SYSTEMD_START(1)

NAME

       dh_systemd_start - start/stop/restart systemd unit files

SYNOPSIS

       dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]

DESCRIPTION

       dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
       sysv init script is available.

       As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
       which case it will only be restarted after the upgrade).  This logic is not used when there is a corresponding SysV init script because
       invoke-rc.d performs the stop/start/restart in that case.

OPTIONS

       --restart-after-upgrade
	   Do not stop the unit file until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop service on upgrade.

       --no-start
	   Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
	   corresponding init script).

NOTES

       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
       Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.

       Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
       in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.

SEE ALSO

       debhelper(7)

AUTHORS

       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						       DH_SYSTEMD_START(1)
All times are GMT -4. The time now is 07:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy