[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-03-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Mark Thomas changed: What|Removed |Added CC||yift...@moogsoft.com --- Comment #33 fro

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Mark Thomas changed: What|Removed |Added CC||harvinder_ru...@hotmail.com --- Comment

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #31 from Christopher Schultz --- (In reply to Mark Thomas from comment #26) (for the record) > Assuming the above is correct I think we have two options: > > 1. Revert the "&" -> "&&" change. systemd users (and possibly others) w

Re: [Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/13/19 06:46, bugzi...@apache.org wrote: > https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 > > --- Comment #26 from Mark Thomas --- Got it. > > With the single & the pid of the process that is put in the > background is not the pid

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #29 from Mark Thomas --- (In reply to Konstantin Kolinko from comment #28) > My preference is to revert and to start planning a new patch from there. +1 We can re-open bug 53930 and discuss options there. Calling touch on a named

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #28 from Konstantin Kolinko --- (In reply to Rainer Jung from comment #27) > Excellent analysis! > > I *think* the "&" at the end of the line is only useful, if a pipe command > is actually being used. So one could put it into the

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #27 from Rainer Jung --- Excellent analysis! I *think* the "&" at the end of the line is only useful, if a pipe command is actually being used. So one could put it into the construction of the string variable to which we pipe, just

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #26 from Mark Thomas --- Got it. With the single & the pid of the process that is put in the background is not the pid of the Tomcat process. If I specify $CATALINA_PID and then configure systemd to use the same file with PIDFILE e

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #24 from Mark Thomas --- (In reply to Rainer Jung from comment #22) > Do we actually understand, what would be wrong with the line > > 2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $catalina_out_command "&" > > (single escaped

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #25 from Mark Thomas --- (In reply to Mark Thomas from comment #24) > bash: syntax error near unexpected token `}' I think this is just incorrect escaping of the command and could be a red herring. -- You are receiving this mail

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #23 from Thomas Opfer --- (In reply to Rainer Jung from comment #22) > Do we actually understand, what would be wrong with the line > > 2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $catalina_out_command "&" > > (single escape

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #22 from Rainer Jung --- Do we actually understand, what would be wrong with the line 2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $catalina_out_command "&" (single escaped ampersand)? As far as I understand from this ticket

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #21 from Thomas Opfer --- > If I am understanding this correctly that would mean: > > - reverting r1848046 and r1850829 for 9.0.x > - reverting r1848048 and r1850830 for 8.5.x > - reverting r1848049 and r1850831 for 7.0.x That sho

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #20 from Mark Thomas --- (In reply to Konstantin Kolinko from comment #19) > An idea: use a named pipe (a FIFO special file) to solve the original bug > 53930. If I am understanding this correctly that would mean: - reverting r184

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #19 from Konstantin Kolinko --- An idea: use a named pipe (a FIFO special file) to solve the original bug 53930. 1. mkfifo command is documented in POSIX. It is a standard feature. http://pubs.opengroup.org/onlinepubs/9699919799/u

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #18 from Konstantin Kolinko --- For a reference: POSIX-2018 documentation on Shell Command Language: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html The $! parameter is defined in section "2.5.2 Special Pa

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #17 from Konstantin Kolinko --- Another report of this issue on the users@ list. https://markmail.org/message/x4rzdpsjzoi2pbdd Quoting: --- I'm observing this on RHEL 6 and 7. RHEL6$ /bin/sh --version GNU bash, version 4.1.2(1)-r

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #16 from Mark Thomas --- Sigh. Sorry for the hassle. Sticking with catalina.sh from 9.0.14 is the way to go if you are seeing issues. We should be able to get this fixed for the next release. I don't know yet what that fix will loo

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #15 from Thomas Opfer --- (In reply to norad from comment #14) This is the same problem I observed. > Now I'm using the old catalina.sh from v9.0.14 that works fine, but I'm > considering whether it is better to modify my script i

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Thomas Opfer changed: What|Removed |Added CC||ubuntu...@thomasopfer.de -- You are re

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #14 from no...@email.it --- This fix seems to break the shell script /etc/init.d/tomcat I use to manage Tomcat as a service with systemd (generated from init.d): https://git.io/fhQv4 Output follows: $ sudo service tomcat start Job

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 no...@email.it changed: What|Removed |Added CC||no...@email.it -- You are receiving t

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 ubuntu...@thomasopfer.de changed: What|Removed |Added Resolution|FIXED |--- Status|RESOL

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Mark Thomas changed: What|Removed |Added CC||patrik@gmx.net --- Comment #11 from

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #10 from Mark Thomas --- The issue isn't obvious but is observable on Ubuntu. I agree that "\&" -> to "\&\&" is the correct fix. I'll get that implemented and back-ported. -- You are receiving this mail because: You are the assig

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #9 from Igal Sapir --- I can not reproduce the issue on Ubuntu 18.04 with Java 1.8.0_192 Tomcat shuts down immediately when calling shutdown.sh -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #8 from Patrik S. --- Yes, BZ-63063 is exactly the same issue opened for tomcat 8.5 branch. In tomcat 9.0 the catalina.sh contains at the same line 479 and 489 that faulty code: 2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $c

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #7 from Igal Sapir --- Possibly related to BZ-63063 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubs

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #6 from Igal Sapir --- (In reply to Christopher Schultz from comment #5) > On the users' mailing list, I asked Steve to try the catalina.sh from 9.0.13 > on his 9.0.14 install, but there has been no reply for a few days. He wrote t

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #5 from Christopher Schultz --- On the users' mailing list, I asked Steve to try the catalina.sh from 9.0.13 on his 9.0.14 install, but there has been no reply for a few days. -- You are receiving this mail because: You are the as

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #4 from Igal Sapir --- I will look into this issue if no one else has already started -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #3 from Igal Sapir --- (In reply to Steve Demy from comment #2) > Tomcat 9.0.14 runs as expected using a transplanted 9.0.13 catalina.sh. It > starts, stops and restarts using systemd (systemctl start|stop|restart > tomcat). So

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 jpho...@korem.com changed: What|Removed |Added CC||jpho...@korem.com -- You are recei

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Steve Demy changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED

[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS

2019-01-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 Christopher Schultz changed: What|Removed |Added Resolution|--- |INVALID Status|NEW