[Bug 559534] New: Install update fail
http://bugzilla.novell.com/show_bug.cgi?id=559534 http://bugzilla.novell.com/show_bug.cgi?id=559534#c0 Summary: Install update fail Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: WebYaST AssignedTo: kkaempf@novell.com ReportedBy: jreidinger@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- When I try to install update of lighttpd it crashed. output: end of file reached Show details... /usr/lib/ruby/1.8/net/protocol.rb:135:in `sysread' /usr/lib/ruby/1.8/net/protocol.rb:135:in `rbuf_fill' /usr/lib/ruby/1.8/timeout.rb:62:in `timeout' /usr/lib/ruby/1.8/timeout.rb:93:in `timeout' /usr/lib/ruby/1.8/net/protocol.rb:134:in `rbuf_fill' /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line' /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new' /usr/lib/ruby/1.8/net/http.rb:1050:in `request' /usr/lib/ruby/1.8/net/http.rb:1037:in `request' /usr/lib/ruby/1.8/net/http.rb:543:in `start' /usr/lib/ruby/1.8/net/http.rb:1035:in `request' /usr/lib/ruby/1.8/net/http.rb:845:in `post' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:171:in `send' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:171:in `request' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:171:in `request' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:156:in `post' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/base.rb:1075:in `create' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/base.rb:864:in `save_without_validation' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/validations.rb:259:in `save' /srv/www/yast/vendor/plugins/patch_updates/app/controllers/patch_updates_controller.rb:140:in `install' /srv/www/yast/vendor/plugins/patch_updates/app/controllers/patch_updates_controller.rb:130:in `each' /srv/www/yast/vendor/plugins/patch_updates/app/controllers/patch_updates_controller.rb:130:in `install' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:1331:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:1331:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/filters.rb:617:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/rescue.rb:160:in `perform_action_without_flash' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/flash.rb:146:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:532:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:532:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/filters.rb:606:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:391:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:386:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/routing/route_set.rb:437:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:87:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:121:in `_call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' /srv/www/yast/lib/yast/rack/static_overlay.rb:47:in `call' /srv/www/yast/lib/yast/rack/static_overlay.rb:47:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:29:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:9:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:28:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/params_parser.rb:15:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/session/cookie_store.rb:93:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/failsafe.rb:26:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:106:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/content_length.rb:13:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/handler/fastcgi.rb:56:in `serve' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:103:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:153:in `with_signal_handler' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:101:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:78:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:77:in `each' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:76:in `catch' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:51:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:23:in `process!' /srv/www/yast/public/dispatch.fcgi:24 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c1
Klaus Kämpf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c2
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c3
Jiří Suchomel
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c4
--- Comment #4 from Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c5
--- Comment #5 from Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c6
Klaus Kämpf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c7
Jiří Suchomel
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c8
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c9
Marcus Rückert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c10
--- Comment #10 from Josef Reidinger
is the lighttpd running?
Yes, webyast use lighttpd to its run. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Jiří Suchomel
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c11
--- Comment #11 from Marcus Rückert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c13
--- Comment #13 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c14
--- Comment #14 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c15
--- Comment #15 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c16
--- Comment #16 from Jiří Suchomel
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c17
--- Comment #17 from Jiří Suchomel
Setting DISABLE_RESTART_ON_UPDATE in /etc/sysconfig/services
I mean, Setting DISABLE_RESTART_ON_UPDATE to "yes" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c18
--- Comment #18 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c19
--- Comment #19 from Ludwig Nussel
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c20
--- Comment #20 from Marcus Rückert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c21
--- Comment #21 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c22
--- Comment #22 from Jiří Suchomel
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c23
--- Comment #23 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c24
Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c25
--- Comment #25 from Marcus Rückert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c26
--- Comment #26 from Martin Vidner
to behave 100% correctly an lighttpd restart would also need to restart your lighty instances.
True, but we can include our own logic for that. If only the init script was not so eager in killing all instances, but I see that the current config layout makes selective killing quite hard :-( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c27
Klaus Kämpf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c28
Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c29
Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c30
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c31
--- Comment #31 from Martin Vidner
The actual triggers use %restart_on_update and this macro uses the try-restart init script action. It restarts the service only if it is running. But lighty kills yastw[sc] and so they do not restart.
Actually there is a bug where rcyastw[sc] think they are running when in fact only the generic lighttpd is running. I will fork this report. That means try-restart should restart webyast in the end because the bugs should cancel out. But it doesn't I don't know why yet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c32
Klaus Kämpf
Jsrain has confirmed that the triggers did not help.
The actual triggers use %restart_on_update and this macro uses the try-restart init script action. It restarts the service only if it is running. But lighty kills yastw[sc] and so they do not restart.
The lets try calling "...yast{wc,ws} restart" directly !
Darix, we do need lighttpd fixed to work only on its own instance. This is a critical problem for WebYaST.
Adapting component now, this is no WebYaST bug -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c33
--- Comment #33 from Martin Vidner
The lets try calling "...yast{wc,ws} restart" directly !
That won't help, it turns out to be related to the status problem. See bug 560302. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c34
--- Comment #34 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c35
--- Comment #35 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c36
--- Comment #36 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c37
Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c40
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c41
--- Comment #41 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c42
--- Comment #42 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c43
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c44
--- Comment #44 from Martin Vidner
The -p option works as LSB told us.
Now that you mention it, no, it works wrong. Here I have yastwc and yastws running, and the generic lighttpd stopped. # pgrep -fl lighttpd 6884 /usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf 6911 /usr/sbin/lighttpd -f /srv/www/yast/config/lighttpd.conf # rm /var/run/lighttpd.pid Now, this should start the generic one, but it doesn't: # startproc -p /var/run/lighttpd.pid \ -e /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf # pgrep -fl lighttpd 6884 /usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf 6911 /usr/sbin/lighttpd -f /srv/www/yast/config/lighttpd.conf (I understand why our implementation doesn't. And it needs the ignore file because of that.) But LSB does specify that PID be obeyed: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generi... """The start_daemon, killproc and pidofproc functions shall use the following algorithm for determining the status and the process identifiers of the specified program. 1. [...] If the -p pidfile option is specified and the named pidfile does not exist, the functions shall assume that the daemon is not running. """ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c45
--- Comment #45 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c46
--- Comment #46 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c47
--- Comment #47 from Stefan Schubert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c48
--- Comment #48 from Martin Vidner
AFACIR from comment #34 the pid file exists
In comment 44, where I was demonstrating how start_daemon(*) does not conform to LSB, the PID file does not exist. But anyway, I can demonstrate the brokenness on comment 34 too. When running yastws start, the pid file exists, and contains a pid that does not exist. Yet afterwards the service is not started. man startproc: "startproc does not use the pid to search for a process but the full path of the corresponding program which is used to identify the executable" LSB: "Conforming implementations may use other mechanisms besides those based on pidfiles, unless the -p pidfile option has been used. Conforming applications should not rely on such mechanisms and should always use a pidfile." (*) I used startproc, but meanwhile I checked that start_daemon is broken too. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c49
--- Comment #49 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c50
--- Comment #50 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c51
--- Comment #51 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c52
--- Comment #52 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c53
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c54
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c55
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c56
--- Comment #56 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c57
--- Comment #57 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c58
--- Comment #58 from Klaus Kämpf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c59
--- Comment #59 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c60
--- Comment #60 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c61
--- Comment #61 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c62
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c63
--- Comment #63 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c64
--- Comment #64 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c65
--- Comment #65 from Martin Vidner
How should startproc determine that the pid file is stale?
A pid file is stale if the pid it contains is not present (or if it is referencing a process running a different binary, more about that in http://perfec.to/stalepid.html but that is not the case here).
It could be a crash of one of several processes of one binrary without having the pid file removed.
Yes, like in our case, where the single lighty binary is used for 3 separate services.
This case is AFAICS from LSB specs not handled.
In this case, I think it is handled, with the quote from comment 48: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generi... LSB: "Conforming implementations may use other mechanisms besides those based on pidfiles, unless the -p pidfile option has been used. Conforming applications should not rely on such mechanisms and should always use a pidfile." I interpret that as directing startproc to check the pid only and not look at other processes using that binary. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c66
--- Comment #66 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c67
--- Comment #67 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c68
--- Comment #68 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c69
--- Comment #69 from Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c70
--- Comment #70 from Marcus Rückert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c74
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c75
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c76
Marcus Meissner
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c77
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c79
Klaus Kämpf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c80
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c81
Dirk Mueller
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c82
Marcus Rückert
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c83
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c84
--- Comment #84 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com