#!/bin/bash #============================================================================== # Copyright and license info is available in the LICENSE file included with # the Server Deployment Package (SDP), and also available online: # https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE #------------------------------------------------------------------------------ # P4Web base init script # Do nothing unless $SDP_INSTANCE is defined. export SDP_INSTANCE="${1:-Unset}" export OS_INIT_MECHANISM="${OS_INIT_MECHANISM:-Unset}" declare -i StartDelay="${SDP_START_DELAY:-2}" declare -i UseSystemd=0 declare MustUseSystemdMsg= # p4web must run as root if the listen port is 1024 or less, e.g. to run on port 80. declare -i RunAsRoot=0 declare Log= if [[ $SDP_INSTANCE == Unset ]]; then echo -e "\\nError: The SDP_INSTANCE is not defined.\\n" exit 1 fi export P4WEBBIN="/p4/${SDP_INSTANCE:-1}/bin/p4web_${SDP_INSTANCE:-1}" export P4WEBLOG="/p4/${SDP_INSTANCE:-1}/logs/p4web.log" Log="/p4/${SDP_INSTANCE:-1}/logs/p4web.init.log" # Load SDP controlled shell environment. # shellcheck disable=SC1091 source /p4/common/bin/p4_vars "$SDP_INSTANCE" || { echo -e "\\nError: Failed to load SDP environment for instance $SDP_INSTANCE.\\n" exit 1 } # Added support for optional P4WEB_USER setting. If set, P4USER will be set # to this user before starting the p4web service. This is recommended, as it # prevents p4web from possibly logging out the primary super user that # operates checkpoints. If defined, the user should also be added to # SDP_AUTOMATION_USERS defined in the Instance Vars file, i.e. the p4_N.vars # file in /p4/common/config. This change is done in a way to avoid disrupting # existing installations. To use the feature, do something like this, # replacing N with the SDP instance name: # # source /p4/common/bin/p4_vars N # echo P4WEB_USER=p4web >> /p4/common/site/config/$P4SERVER.vars.local [[ -n "${P4WEB_USER:-}" ]] && export P4USER="$P4WEB_USER" export P4WEBPORT=${P4WEBPORT:-8080} export P4WEBPORTNUM=${P4WEBPORT##*:} if [[ "$P4WEBPORTNUM" =~ ^[0-9]+$ ]]; then if [[ "$P4WEBPORTNUM" -le 1024 ]]; then export P4WEBARGS="-B -p $P4PORT -w $P4WEBPORT -U $OSUSER -L $P4WEBLOG" RunAsRoot=1 else export P4WEBARGS="-B -p $P4PORT -w $P4WEBPORT -L $P4WEBLOG" fi else echo -e "\\nError: The P4WEBPORTNUM value [$P4WEBPORTNUM] derived from P4WEBPORT [$P4WEBPORT] must be purely numeric.\\n" exit 1 fi # shellcheck disable=SC1091 source "$P4CBIN/ps_functions.sh" || { echo -e "\\nError: Failed to load SDP ps_functions.sh lib.\\n" exit 1 } # Determine if systemd is configured for this instance. if [[ -n "$(command -v systemctl)" ]]; then ServiceName="${P4WEBBIN##*/}" if [[ -n "$(systemctl is-enabled "$ServiceName" 2>/dev/null)" ]]; then UseSystemd=1 MustUseSystemdMsg="\\nError: It appears an attempt was made to start or stop the $ServiceName\\nservice without using systemd. When a systemd unit file is configured, only the\\nsystemd init mechanism can be used to start and stop the service, so that\\nsystemd maintains a more reliable indication of the status of the service. Run\\nas root or as $OSUSER with sudo. For example:\\n\\n\\tsudo systemctl start $ServiceName\\n\\tsudo systemctl stop $ServiceName\\n\\tsystemctl status $ServiceName\\n\\nNote that the 'status' check does not require sudo.\\n\\nThe systemd unit file is:\\n\\n<<<<<<<<\\n$(sudo systemctl cat "$ServiceName")\\n>>>>>>>\\n\\nIf you used 'systemctl' and still got this message, then please check if OS_INIT_MECHANISM is defined\\nin the above file." fi fi if [[ $(id -u) -eq 0 ]]; then if [[ "$RunAsRoot" -eq 0 ]]; then exec su - "$OSUSER" -c "$0 $*" fi elif [[ $(id -u -n) != "$OSUSER" ]]; then if [[ "$RunAsRoot" -eq 1 ]]; then echo -e "\\nError: Running as $(id -u -n), but $0 can only be run as root because the port number is $P4WEBPORTNUM (less than 1024 requires root).\\n" exit 1 else echo -e "\\nError: Running as $(id -u -n), but $0 can only be run as root or $OSUSER.\\n" exit 1 fi else if [[ "$RunAsRoot" -eq 1 ]]; then echo -e "\\nError: Running as $(id -u -n), but $0 can only be run as root because the port number is $P4WEBPORTNUM (less than 1024 requires root).\\n" exit 1 fi fi # See how we were called. case "${2:-usage}" in start) if [[ "$UseSystemd" -eq 1 && "$OS_INIT_MECHANISM" != "systemd" ]]; then echo -e "$MustUseSystemdMsg" exit 1 fi # Delay start $StartDelay seconds, for enhanced start reliability after reboot. sleep "$StartDelay" if [[ "$UseSystemd" -eq 1 ]]; then echo -e "$(date +'%Y-%m-%d-%H%M%S'): Starting $P4WEBBIN with:\\n\\t$P4WEBBIN $P4WEBARGS" # shellcheck disable=SC2086 $P4WEBBIN $P4WEBARGS >> "$Log" 2>&1 else echo -e "$(date +'%Y-%m-%d-%H%M%S'): Starting $P4WEBBIN with:\\n\\t$P4WEBBIN $P4WEBARGS &" >> "$Log" 2>&1 # shellcheck disable=SC2086 $P4WEBBIN $P4WEBARGS >> "$Log" 2>&1 & fi ;; status) p4web_pids=$(get_pids "$P4WEBBIN") if [[ -n "$p4web_pids" ]]; then echo "${P4WEBBIN} is running as pids: $p4web_pids." exit 0 else echo "${P4WEBBIN} is NOT running." exit 1 fi ;; stop) p4web_pids=$(get_pids "$P4WEBBIN") if [[ -n "$p4web_pids" ]]; then while [[ -n "$p4web_pids" ]]; do echo "Shutting down ${P4WEBBIN} pids: $p4web_pids." echo "Shutting down ${P4WEBBIN} pids: $p4web_pids." >> "$Log" 2>&1 # shellcheck disable=SC2086 kill $p4web_pids 2>&1 | $GREP -v -i "No such" sleep 1 p4web_pids=$(get_pids "$P4WEBBIN") done echo "${P4WEBBIN} stopped." exit 0 else echo "${P4WEBBIN} was NOT running." exit 1 fi ;; restart) $0 "$SDP_INSTANCE" stop $0 "$SDP_INSTANCE" start ;; *) echo -e "\\nUsage: $0 SDP_INSTANCE {start|stop|status|restart}\\n" exit 1 ;; esac exit 0
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 29969 | C. Thomas Tyler | Refined docs for P4WEB_USER setting.. | ||
#3 | 29967 | C. Thomas Tyler |
Added support for optional P4WEB_USER setting. If set, P4USER will be set to this user before starting the p4web service. This is recommended, as it prevents p4web from possibly logging out the primary super user that operates checkpoints. If defined, the user should also be added to SDP_AUTOMATION_USERS defined in the Instance Vars file, i.e. the p4_N.vars file in /p4/common/config. This change is done in a way to avoid disrupting existing installations. To use the feature, do something like this, replacing N with the SDP instance name: echo P4WEB_USER=p4web >> /p4/common/site/config/$P4HOME.local #review-29968 |
||
#2 | 29725 | C. Thomas Tyler |
Moved p4web init script template to Unsupported to clarify it is not supported. Modernized p4web_base to work with systemd. #review-29726 |
||
#1 | 26652 | Robert Cowham |
This is Tom's change: Introduced new 'Unsupported' directory to clarify that some files in the SDP are not officially supported. These files are samples for illustration, to provide examples, or are deprecated but not yet ready for removal from the package. The Maintenance and many SDP triggers have been moved under here, along with other SDP scripts and triggers. Added comments to p4_vars indicating that it should not be edited directly. Added reference to an optional site_global_vars file that, if it exists, will be sourced to provide global user settings without needing to edit p4_vars. As an exception to the refactoring, the totalusers.py Maintenance script will be moved to indicate that it is supported. Removed settings to support long-sunset P4Web from supported structure. Structure under new .../Unsupported folder is: Samples/bin Sample scripts. Samples/triggers Sample trigger scripts. Samples/triggers/tests Sample trigger script tests. Samples/broker Sample broker filter scripts. Deprecated/triggers Deprecated triggers. To Do in a subsequent change: Make corresponding doc changes. |
||
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/p4web_base | |||||
#10 | 23040 | C. Thomas Tyler |
Enhancements to p4d_base: * Added $LOGS/p4d_init.log to track calls to init. * Increased verbosity somewhat, though the 'p4d -xvu' output still goes only to the p4d_init.log, with an error message referencing that log in event of error. * Replaced old preflight log with standard LOGFILE for all tracking. * Fixed issue starting server due to LOGFILE not being defined; not documented as a bug since it is a fix to unreleased behavior in the last change in the dev branch. * Enhanced to automatically replace '-d' with '--daemonsafe' if p4d 2017.1+ * Enhanced to call p4login rather than duplicating logic in p4login. No rotation is provided for p4d_init.log; it is continuously appended and is expected to grow only a few M per year with typical usage (the bigger the server, the less the growth). Enhancements to all *_base scripts: * Enhanced so default behvaior, with no args, is to show a usage message (rather than doing 'status'). |
||
#9 | 20559 | C. Thomas Tyler |
Fixed recent regression with 'restart' option in init scripts; they now need to pass in the SDP_INSTANCE parameter. Also corrected usage messages. |
||
#8 | 20491 | C. Thomas Tyler |
Fixed an environment insulation bug in init scripts. More testing (and thinking) revealed that the only way to truly provide a guarantee of insulation from user-set defaults in ~perforce/.bashrc (etc.) is to pass SDP_INSTANCE as a parameter to the *_base scripts, so that the instance name is explicitly passed into the su/exec call (when run as root). This change also includes minor cleanup in init scripts and *_base scripts. |
||
#7 | 20448 | C. Thomas Tyler |
Fixed env bug seen when running init scripts as root. Updated *_base scripts and *_init script templates to a new standard. Goals: 1. Init scripts that use corresponding *_base scripts are minimized so that do nothing more than set SDP_INSTANCE and then call the corresponding *_base script. 2. The 'su' commands always pass $* instead of $1, deferring all processing to the *_base script. 3. The shell environment is now guaranteeds to have the same results regardless of whether it is called as 'root' or as the defined OSUSER. 4. The p4_vars file is always sourced exactly once. Two calls to 'source p4_vars' appear in some cases, one immediatley before the su/exec call, and another after the after the 'su/exec'. Only one or the other is sourced. 5. All init scripts have a reasonably consistent usage message. 6. All init scripts accept a 'status' argument. This change fixes a bug where 'p4broker_N_init status' run as the 'perforce' user would report many pids unrelated to Perforce if run as root, e.g. doing 'service p4broker_N_init status'. This also eliminates a potential issue where the 'perforce' user might source a p4_vars with a default instance in ~/.profile or ~/.bashrc, thus invalidating the instance specified when the user ran the init script as root. |
||
#6 | 20429 | C. Thomas Tyler |
Updated p4web_base and p4ftpd_base with a check that they are running as root, with error if not (as those init scripts must be run as root; they can't run as perforce). |
||
#5 | 16029 | C. Thomas Tyler |
Routine merge to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#4 | 15778 | C. Thomas Tyler | Routine Merge Down to dev from main. | ||
#3 | 13906 | C. Thomas Tyler |
Normalized P4INSTANCE to SDP_INSTANCE to get Unix/Windows implementations in sync. Reasons: 1. Things that interact with SDP in both Unix and Windows environments shoudn't have to account for this obscure SDP difference between Unix and Windows. (I came across this doing CBD work). 2. The Windows and Unix scripts have different variable names for defining the same concept, the SDP instance. Unix uses P4INSTANCE, while Windows uses SDP_INSTANCE. 3. This instance tag, a data set identifier, is an SDP concept. I prefer the SDP_INSTANCE name over P4INSTANCE, so I prpose to normalize to SDP_INSTANCE. 4. The P4INSTANCE name makes it look like a setting that might be recognized by the p4d itself, which it is not. (There are other such things such as P4SERVER that could perhaps be renamed as a separate task; but I'm not sure we want to totally disallow the P4 prefix for variable names. It looks too right to be wrong in same cases, like P4BIN and P4DBIN. That's a discussion for another day, outside the scope of this task). Meanwhile: * Fixed a bug in the Windows 2013.3 upgrade script that was referencing undefined P4INSTANCE, as the Windows environment defined only SDP_INSTANCE. * Had P4INSTANCE been removed completely, this change would likely cause trouble for users doing updates for existing SDP installations. So, though it involves slight technical debt, I opted to keep a redundant definition of P4INSTANCE in p4_vars.template, with comments indicating SDP_INSTANCE should be used in favor of P4INSTANCE, with a warning that P4INSTANCE may go away in a future release. This should avoid unnecessary upgrade pain. * In mkdirs.sh, the varialbe name was INSTANCE rather than SDP_INSTANCE. I changed that as well. That required manual change rather than sub/replace to avoid corrupting other similar varialbe names (e.g. MASTERINSTANCE). This is a trivial change technically (a substitute/replace, plus tweaks in p4_vars.template), but impacts many files. |
||
#2 | 12169 | Russell C. Jackson (Rusty) |
Updated copyright date to 2015 Updated shell scripts to require an instance parameter to eliminate the need for calling p4master_run. Python and Perl still need it since you have to set the environment for them to run in. Incorporated comments from reviewers. Left the . instead of source as that seems more common in the field and has the same functionality. |
||
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | ||
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4web_base | |||||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |