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
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c1
Klaus Kämpf kkaempf@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO CC| |kkaempf@novell.com, | |schubi@novell.com Found By|--- |Development Info Provider| |jreidinger@novell.com Target Milestone|--- |Future 11.3
--- Comment #1 from Klaus Kämpf kkaempf@novell.com 2009-12-01 14:42:45 UTC --- Oops, looks like we cannot handle updates of the running webyast.
This might be tricky anyways.
Can you log in again ?
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c2
Josef Reidinger jreidinger@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |jsuchome@novell.com Info Provider|jreidinger@novell.com |
--- Comment #2 from Josef Reidinger jreidinger@novell.com 2009-12-01 14:45:40 UTC --- jsuchome also repoduce it. It is related to lighttpd update.
And what is worse, that now I cannot communicate with appliance even if I manually restart services.
So no page shown anymore.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c3
Jiří Suchomel jsuchome@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical
--- Comment #3 from Jiří Suchomel jsuchome@novell.com 2009-12-01 14:52:46 UTC --- I cannot log in. I'm using VirtualBox with NAT and with next attempt, I cannot connect to port 54984
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c4
--- Comment #4 from Josef Reidinger jreidinger@novell.com 2009-12-01 14:54:01 UTC --- I use bridged network. I try restart network, yastw* and lighttpd service and nothing help.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c5
--- Comment #5 from Josef Reidinger jreidinger@novell.com 2009-12-01 15:02:45 UTC --- If I restart target machine, then it starts working.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c6
Klaus Kämpf kkaempf@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kkaempf@novell.com |jreidinger@novell.com
--- Comment #6 from Klaus Kämpf kkaempf@novell.com 2009-12-01 15:03:24 UTC --- Josef, I assign this to you for further investigation.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c7
Jiří Suchomel jsuchome@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P1 - Urgent CC| |mvidner@novell.com
--- Comment #7 from Jiří Suchomel jsuchome@novell.com 2009-12-01 15:08:34 UTC --- Martin suggested that SDK patches (like this one) should be already installed.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c8
Josef Reidinger jreidinger@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mrueckert@novell.com
--- Comment #8 from Josef Reidinger jreidinger@novell.com 2009-12-01 15:10:00 UTC --- OK, I see that patch is successfully installed. If I try ruby update, it works. So problem is in lighttpd update.
Darix - as lighttpd maintainer do you have idea what is going wrong during update? Maybe some service restart missing.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c9
Marcus Rückert mrueckert@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert@novell.com
--- Comment #9 from Marcus Rückert mrueckert@novell.com 2009-12-01 15:18:30 UTC --- is the lighttpd running?
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c10
--- Comment #10 from Josef Reidinger jreidinger@novell.com 2009-12-01 15:34:01 UTC --- (In reply to comment #9)
is the lighttpd running?
Yes, webyast use lighttpd to its run.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Jiří Suchomel jsuchome@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Install update fail |Installing lighttpd patch | |crashes webyast
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 mrueckert@novell.com 2009-12-01 18:00:25 UTC --- any test machine which i can access?
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c13
--- Comment #13 from Martin Vidner mvidner@novell.com 2009-12-02 10:13:28 UTC --- After the update is installed, lighttpd is running with /etc/lighttpd/lighttpd.conf, and the two lighttpds for yastws and yastws are not running (BUT the init scripts think they do. a bug!)
/var/log/yastws/log/production.log shows /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:160:in `exit', probably a result of the RPM script restarting the server.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c14
--- Comment #14 from Stefan Schubert schubi@novell.com 2009-12-02 11:35:44 UTC --- Yes, I can confirm. After the update:
lighttpd 5535 1.8 8.1 61012 41656 ? S 12:00 0:28 /usr/bin/ruby /srv/www/yast/public/dispatch.fcgi lighttpd 8846 0.0 0.1 5560 896 ? S 12:22 0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c15
--- Comment #15 from Stefan Schubert schubi@novell.com 2009-12-02 11:49:05 UTC --- Before update of lighttpd we have had:
lighttpd 5532 0.0 0.5 6780 2748 ? S 12:00 0:00 /usr/sbin/lighttpd -f /srv/www/yast/config/lighttpd.conf lighttpd 5535 0.7 8.1 61012 41656 ? S 12:00 0:12 /usr/bin/ruby /srv/www/yast/public/dispatch.fcgi yastws 5557 0.0 0.3 6244 1664 ? S 12:00 0:00 /usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c16
--- Comment #16 from Jiří Suchomel jsuchome@novell.com 2009-12-02 11:54:49 UTC --- Setting DISABLE_RESTART_ON_UPDATE in /etc/sysconfig/services helps, I've just installed all updates with this and webyast looks healthy.
However, I do not know if we can do this, it will affect all services...
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c17
--- Comment #17 from Jiří Suchomel jsuchome@novell.com 2009-12-02 11:55:23 UTC --- (In reply to comment #16)
Setting DISABLE_RESTART_ON_UPDATE in /etc/sysconfig/services
I mean, Setting DISABLE_RESTART_ON_UPDATE to "yes"
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c18
--- Comment #18 from Stefan Schubert schubi@novell.com 2009-12-02 12:07:41 UTC --- So, i would suggest that this flag should be set in the appliance and the user should be informed in the release notes that we have set this.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c19
--- Comment #19 from Ludwig Nussel lnussel@novell.com 2009-12-02 12:17:20 UTC --- Well, that will also disable restarts other services, even those that handle it gracefully e.g. ssh. The lighttpd init scripts kills all instances of lighttpd as it doesn't pass a pidfile to killproc. IIRC killproc would only kill one instance if it had a pid file. So this problem could be solved by fixing the lighttpd init script.
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 mrueckert@novell.com 2009-12-02 13:16:07 UTC --- i can not rely on the pid file, as it is set in the config file and i dont really think parsing the config will work reliable.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c21
--- Comment #21 from Stefan Schubert schubi@novell.com 2009-12-02 13:45:29 UTC --- Darix, do you see another solution for this problem ? Otherwise I see the solution which we have made in comment#18 only.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c22
--- Comment #22 from Jiří Suchomel jsuchome@novell.com 2009-12-02 13:48:11 UTC --- .. or we can include current lighttpd patch in the appliance (comment 7) and hope that its next update will also somehow behave correctly on restart.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c23
--- Comment #23 from Stefan Schubert schubi@novell.com 2009-12-02 13:59:51 UTC --- comment#22 That would be at least useable for appliances. Sure.
BTW. we are setting the pid files in lighttpd.conf:
## ## store a pid file ## server.pid-file = state_dir + "/yastwc.pid"
## ## store a pid file ## server.pid-file = state_dir + "/yastws.pid"
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c24
Stefan Schubert schubi@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jreidinger@novell.com |mrueckert@novell.com
--- Comment #24 from Stefan Schubert schubi@novell.com 2009-12-02 14:18:07 UTC --- I think Darix as the package maintainer of lighttpd is the right person :-)
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 mrueckert@novell.com 2009-12-02 15:06:39 UTC --- to behave 100% correctly an lighttpd restart would also need to restart your lighty instances.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c26
--- Comment #26 from Martin Vidner mvidner@novell.com 2009-12-02 17:21:16 UTC --- (In reply to comment #25)
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 :-(
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c27
Klaus Kämpf kkaempf@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P2 - High Status|NEEDINFO |ASSIGNED Info Provider|mrueckert@novell.com | AssignedTo|mrueckert@novell.com |mvidner@novell.com
--- Comment #27 from Klaus Kämpf kkaempf@novell.com 2009-12-02 19:52:19 UTC --- After checking back with mrueckert (lighttpd maintainer) and mls (rpm maintainer), we settled now for "%triggerin" to restart yast{wc,ws} if lighttpd gets updated.
package checked into obs
Martin, please create a new image for testing
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c28
Stefan Schubert schubi@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mvidner@novell.com |mrueckert@novell.com
--- Comment #28 from Stefan Schubert schubi@novell.com 2009-12-03 08:46:16 UTC --- No, it does not work :-( I have tested with these packages and build 22. As I have Darix understood there is also a patch for lighttpd needed and there has been raised and additional problem with startproc. He has promised to write yesterday an Email to Werner concerning that stuff but I have not seen one :-(
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c29
Stefan Schubert schubi@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mvidner@novell.com
--- Comment #29 from Stefan Schubert schubi@novell.com 2009-12-03 09:17:08 UTC --- In order to go on we have decided to pick up Martin's proposal from comment #7 Martin, could you please add the latest version of lighttpd to our repos ?
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c30
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mvidner@novell.com |
--- Comment #30 from Martin Vidner mvidner@novell.com 2009-12-03 10:20:00 UTC --- 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.
Darix, we do need lighttpd fixed to work only on its own instance. This is a critical problem for WebYaST.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c31
--- Comment #31 from Martin Vidner mvidner@novell.com 2009-12-03 10:22:51 UTC --- (In reply to comment #30)
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.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c32
Klaus Kämpf kkaempf@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|WebYaST |Other QAContact|qa@suse.de |kkaempf@novell.com
--- Comment #32 from Klaus Kämpf kkaempf@novell.com 2009-12-03 10:33:04 UTC --- (In reply to comment #30)
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
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c33
--- Comment #33 from Martin Vidner mvidner@novell.com 2009-12-03 11:33:17 UTC --- (In reply to comment #32)
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.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c34
--- Comment #34 from Stefan Schubert schubi@novell.com 2009-12-03 11:39:52 UTC --- A simple restart or try-restart does not work:
webyast-demo:~ # ps aux|grep light lighttpd 5535 0.7 8.1 61012 41656 ? S 12:00 0:17 /usr/bin/ruby /srv/www/yast/public/dispatch.fcgi lighttpd 8902 0.3 0.1 5560 896 ? S 12:37 0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf root 8911 0.0 0.1 3264 792 pts/0 S+ 12:38 0:00 grep light webyast-demo:~ # rcyastws stop Shutting down yastws done webyast-demo:~ # cat /var/run/yastws.pid 5557 webyast-demo:~ # rcyastws status Checking for service yastws running webyast-demo:~ # ps aux|grep light lighttpd 5535 0.7 8.1 61012 41656 ? S 12:00 0:17 /usr/bin/ruby /srv/www/yast/public/dispatch.fcgi lighttpd 8902 0.0 0.1 5560 896 ? S 12:37 0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf root 8930 0.0 0.1 3264 788 pts/0 S+ 12:39 0:00 grep light webyast-demo:~ # webyast-demo:~ # webyast-demo:~ # rcyastws restart Shutting down yastws done Starting yastws done webyast-demo:~ # ps aux|grep light lighttpd 5535 0.7 8.1 61012 41656 ? S 12:00 0:17 /usr/bin/ruby /srv/www/yast/public/dispatch.fcgi lighttpd 8902 0.0 0.1 5560 896 ? S 12:37 0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf root 8956 0.0 0.1 3264 792 pts/0 S+ 12:39 0:00 grep light webyast-demo:~ # cat /var/run/yastws.pid 5557
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c35
--- Comment #35 from Stefan Schubert schubi@novell.com 2009-12-03 12:03:30 UTC --- Created an attachment (id=330735) --> (http://bugzilla.novell.com/attachment.cgi?id=330735) start script for WebYaST client
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c36
--- Comment #36 from Stefan Schubert schubi@novell.com 2009-12-03 12:04:26 UTC --- Created an attachment (id=330736) --> (http://bugzilla.novell.com/attachment.cgi?id=330736) start script for WebYaST service
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c37
Stefan Schubert schubi@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |werner@novell.com
--- Comment #37 from Stefan Schubert schubi@novell.com 2009-12-03 12:08:32 UTC --- I think we have collected enough data to ask Werner for help :-) Werner, please have a look to both init scripts and espl. to the comment#33. Perhaps we have made a general error here. Could you please check ? If you would like to see it "online" just call me.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Dr. Werner Fink werner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #330735|application/octet-stream |text/plain mime type| |
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Dr. Werner Fink werner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #330736|application/octet-stream |text/plain mime type| |
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c40
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |werner@novell.com
--- Comment #40 from Martin Vidner mvidner@novell.com 2009-12-03 14:23:02 UTC --- Werner, do I understand it right that checkproc -k does not need -i? And because -k means "imitate killproc", than killproc does not need -i either? I have just removed them from yastwS and it indeed left yastwC untouched.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c41
--- Comment #41 from Martin Vidner mvidner@novell.com 2009-12-03 14:29:58 UTC --- Created an attachment (id=330771) --> (http://bugzilla.novell.com/attachment.cgi?id=330771) rclighttpd.diff
Here's a proposed patch to /etc/init.d/lighttpd. As said earlier, figuring out PID_FILE properly is very hard, I'll think about it and what to do if it fails.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c42
--- Comment #42 from Martin Vidner mvidner@novell.com 2009-12-03 14:44:44 UTC --- But that does not really help. The whole concept of -p and -i works differently than we need, especially with startproc which (understandably) does not have a killproc-like option.
startproc, even with -p, does not start a process if it is already running. and because the generic lighttpd cannot know about the other packages that also use its executable (yastwc, yastws), it cannot use -i So, if webyast is running, "rclighttpd start" reports success falsely, and does not start it.
I think that startproc and friends are simply incompatible with a daemon that has multiple independent instances using a single executable.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c43
Dr. Werner Fink werner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |radmanic@novell.com, | |ro@novell.com Info Provider|werner@novell.com |
--- Comment #43 from Dr. Werner Fink werner@novell.com 2009-12-03 15:01:02 UTC --- The -p option works as LSB told us. And the option -i works e.g. see sendmail. The -k option for checkproc simply does:
-k This option makes checkproc work like killproc(8) which changes the operation mode, e.g. the exit status of the program will be that of killproc(8). Without this option, checkproc works like startproc (8) and finds all processes with an executable that matches the specified pathname, even if a given pid file (see option -p) isn't up-to-date. Nevertheless it uses its own exit status (see section EXIT CODES).
to implement an other option for using pid file only even if it is not valid anymore, that is not to scan the /proc file system in case of an broken pid file I have simply not the time.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c44
--- Comment #44 from Martin Vidner mvidner@novell.com 2009-12-03 15:32:07 UTC --- (In reply to comment #43)
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. """
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 werner@novell.com 2009-12-03 15:54:35 UTC --- AFACIR from comment #34 the pid file exists
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c46
--- Comment #46 from Stefan Schubert schubi@novell.com 2009-12-03 16:01:05 UTC --- I think that could be a workaround:
in the spec file of yast2-webservice:
#--------------------------------------------------------------- # restart yastws on lighttpd update (bnc#559534) %triggerin -- lighttpd
killproc -i /var/run/yastwc.pid /usr/sbin/lighttpd if test -f '/var/run/yastws.pid' rm /var/run/yastws.pid startproc -p /var/run/yastws.pid -i /var/run/yastwc.pid /usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf fi
in the spec file of yast2-webclient: #--------------------------------------------------------------- # restart yastwc on lighttpd update (bnc#559534) %triggerin -- lighttpd
killproc -i /var/run/yastws.pid /usr/sbin/lighttpd if test -f '/var/run/yastwc.pid' rm /var/run/yastwc.pid startproc -p /var/run/yastwc.pid -i /var/run/yastws.pid /usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf fi
The killproc kills all wrong started lighttpd deamons. The test -f '/var/run/yastw?.pid' checks if the process has run before.
I have made these calls step by step after the lighttpd package has been installed and both services are running again. So I have the hope (if trigger works) we can use this workarounnd.
Any opinions ?
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c47
--- Comment #47 from Stefan Schubert schubi@novell.com 2009-12-03 16:05:53 UTC --- The disadvantage would be that all other lighttpd deamons (not yast-deamons) will be stopped. But at that moment they are already killed by the lighttpd update.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c48
--- Comment #48 from Martin Vidner mvidner@novell.com 2009-12-03 16:14:37 UTC --- (In reply to comment #45)
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.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c49
--- Comment #49 from Martin Vidner mvidner@novell.com 2009-12-03 16:31:40 UTC --- Re comment 46 and 47:
mvidner: [this is incorrect, you are] killing other lightys (vendor's payload?) schubi: at that moment there is no valid lightys available. At least we have no other fix. As I said it is just a "workaround" schubi: At least I like it more than patching "DISABLE_RESTART_ON_UPDATE" mvidner: IMHO the workaround is "don't update lighty" and the fix is patching webyast, lighty, and sysvinit (and physics) mvidner: I was hoping for a simple fix, but by now I don't see one schubi: sure. For the moment it fits. I believe that with my workaround we could "survive" also the next lighttpd updates without solving the real problem.
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 werner@novell.com 2009-12-03 17:05:16 UTC --- Try mbuild boole-werner-84 for a better version of startproc as in fact *one* line was missed to enable force in case of providing a pid file. And also make the manual page more clear how startproc works.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c51
--- Comment #51 from Martin Vidner mvidner@novell.com 2009-12-04 08:20:43 UTC --- Created an attachment (id=330994) --> (http://bugzilla.novell.com/attachment.cgi?id=330994) lighty-webyast-init-test
Werner thank you!
The sysvinit fix is working (together with the comment 41 fix for rclighttpd and fixes for yastw[cs] that I yet have to post). I am attaching a working version of the test suite.
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 werner@novell.com 2009-12-04 08:44:02 UTC --- I'm indebted to you as you're report has taken me to the missing line within startproc.c :)
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c53
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #330771|0 |1 is obsolete| |
--- Comment #53 from Martin Vidner mvidner@novell.com 2009-12-04 10:48:40 UTC --- Created an attachment (id=331020) --> (http://bugzilla.novell.com/attachment.cgi?id=331020) /tmp/rclighttpd.diff, with PID_FILE parsing
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c54
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #330994|0 |1 is obsolete| |
--- Comment #54 from Martin Vidner mvidner@novell.com 2009-12-04 14:12:13 UTC --- Created an attachment (id=331050) --> (http://bugzilla.novell.com/attachment.cgi?id=331050) lighty-webyast-init-test, complete and prettyfied
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c55
Dr. Werner Fink werner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maintenance@opensuse.org
--- Comment #55 from Dr. Werner Fink werner@novell.com 2009-12-04 14:17:11 UTC --- Submitted a fixed sysvinit package to factory *and* 11.2 IMHO this requires a SWAMID for an update not only for sysvinit :)
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c56
--- Comment #56 from Martin Vidner mvidner@novell.com 2009-12-04 14:20:18 UTC --- Thank you. Actually WebYaST needs the fix in SLE 11 GA. (Sorry not to mention it earlier, we only track WY bugs under 11.2)
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 werner@novell.com 2009-12-04 14:39:29 UTC --- OK I've submitted it also to SLES11-SP1
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 kkaempf@novell.com 2009-12-04 14:40:12 UTC --- Please open a separate bug report for the sysvinit issue !
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c59
--- Comment #59 from Martin Vidner mvidner@novell.com 2009-12-04 14:47:15 UTC --- Note that we need it for SLE 11 GA, before SP1.
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 werner@novell.com 2009-12-04 14:52:30 UTC --- done
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c61
--- Comment #61 from Martin Vidner mvidner@novell.com 2009-12-07 09:14:44 UTC --- Unfortunately, despite my wonderful test case, there's still a bug, where "rclighttpd restart" kills webyast.
Now it is killproc ignoring -p :
# pgrep -fl lighttpd 3631 /usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf # grep . /var/run/yastw[cs].pid /var/run/yastwc.pid:3203 /var/run/yastws.pid:3631 # cat /var/run/lighttpd.pid cat: /var/run/lighttpd.pid: není souborem ani adresářem # killproc -TERM -p /var/run/lighttpd.pid /usr/sbin/lighttpd # pgrep -fl lighttpd #
So killproc kills yastws, contrary to common sense and LSB ("If the -p pidfile option is specified and the named pidfile does not exist, the functions shall assume that the daemon is not running.")
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c62
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mrueckert@novell.com |werner@novell.com
--- Comment #62 from Martin Vidner mvidner@novell.com 2009-12-07 09:17:04 UTC --- Additionally, checkproc (and pidofproc) without -k ignore the pid file in a similar way. I could work around this by using -k (and rclighttpd does it), but the killproc problem needs a fix in sysvinit.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c63
--- Comment #63 from Martin Vidner mvidner@novell.com 2009-12-07 12:07:10 UTC --- Created an attachment (id=331340) --> (http://bugzilla.novell.com/attachment.cgi?id=331340) lighty-webyast-init-test, extended with today's bugs
And finally, startproc -p will not start the process IFF the pid file is stale and a process is already running with that executable.
Attaching an extended test script for c61-c63.
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 werner@novell.com 2009-12-07 13:19:37 UTC --- (In reply to comment #63)
How should startproc determine that the pid file is stale? It could be a crash of one of several processes of one binrary without having the pid file removed. This case is AFAICS from LSB specs not handled.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c65
--- Comment #65 from Martin Vidner mvidner@novell.com 2009-12-07 13:50:38 UTC ---
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.
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 werner@novell.com 2009-12-07 14:51:42 UTC --- The mbuild boole-werner-90 us running, please check out.
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 werner@novell.com 2009-12-07 15:02:12 UTC --- (In reply to comment #66)
Somehow libselinux-devel seems to be broken??
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c68
--- Comment #68 from Martin Vidner mvidner@novell.com 2009-12-07 16:14:52 UTC --- boole-werner-91 has passed all 73 assertions in 9 test cases. Thanks, Werner! Please submit to /work/src/done/SLES11 and SUSE:SLE-11:GA:Products:Test .
I will copy the built package to http://www.suse.de/~mvidner/webyast-lighty/ .
For WebYaST packages, Build0025 is fine already, I will rebuild the appliance with this sysvinit fix as 0.25.1 and call that GMC.
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c69
--- Comment #69 from Martin Vidner mvidner@novell.com 2009-12-08 07:32:42 UTC --- Darix, is lighttpd available for 11.2 already, in some devel project?
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 mrueckert@novell.com 2009-12-08 14:32:18 UTC --- the fixed lighty is in sle11. i didnt submit one for 11.2
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c74
Swamp Workflow Management swamp@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:sle11:29465
--- Comment #74 from Swamp Workflow Management swamp@suse.com 2009-12-17 15:04:47 UTC --- Update released for: sysvinit, sysvinit-debuginfo, sysvinit-debugsource Products: SLE-DEBUGINFO 11 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11 (i386, x86_64) SLE-SERVER 11 (i386, ia64, ppc64, s390x, x86_64)
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c75
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jkrupa@novell.com AssignedTo|werner@novell.com |mrueckert@novell.com
--- Comment #75 from Martin Vidner mvidner@novell.com 2010-01-25 15:49:40 UTC --- lighty is still hanging in /work/src/done/SLE11/lighttpd while it is needed for WebYaST which is officially launched tomorrow :-((
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c76
Marcus Meissner meissner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ast@novell.com
--- Comment #76 from Marcus Meissner meissner@novell.com 2010-01-25 15:54:06 UTC --- a nice. "is in sle11" was associatged with "in sle11 GA", not with "submitted for update".
New SWAMPINFO required
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c77
Swamp Workflow Management swamp@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11:29465 |maint:released:sle11:29465 | |maint:running:30469
--- Comment #77 from Swamp Workflow Management swamp@suse.com 2010-01-25 16:36:33 UTC --- The SWAMPID for this issue is 30469. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/30469)
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c79
Klaus Kämpf kkaempf@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent Target Milestone|Future 11.3 |Final
--- Comment #79 from Klaus Kämpf kkaempf@novell.com 2010-01-25 18:29:36 UTC --- Raising prio because of bnc#562236
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c80
Swamp Workflow Management swamp@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11:29465 |maint:released:sle11:29465 |maint:running:30469 |maint:running:30469 | |maint:released:sle11:30475
--- Comment #80 from Swamp Workflow Management swamp@suse.com 2010-01-29 23:08:55 UTC --- Update released for: lighttpd, lighttpd-debuginfo, lighttpd-debugsource, lighttpd-mod_cml, lighttpd-mod_magnet, lighttpd-mod_mysql_vhost, lighttpd-mod_rrdtool, lighttpd-mod_trigger_b4_dl, lighttpd-mod_webdav Products: SLE-DEBUGINFO 11 (i386, ia64, ppc64, s390x, x86_64) SLE-SDK 11 (i386, ia64, ppc64, s390x, x86_64)
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c81
Dirk Mueller dmueller@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED
--- Comment #81 from Dirk Mueller dmueller@novell.com 2010-01-30 14:48:39 CET --- update released
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c82
Marcus Rückert mrueckert@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@novell.com
--- Comment #82 from Marcus Rückert mrueckert@novell.com 2010-02-01 20:14:13 UTC --- *** Bug 545338 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=545338
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c
Swamp Workflow Management swamp@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11:29465 |maint:released:sle11:29465 |maint:running:30469 |maint:released:sle11:30475 |maint:released:sle11:30475 |
http://bugzilla.novell.com/show_bug.cgi?id=559534
http://bugzilla.novell.com/show_bug.cgi?id=559534#c83
Swamp Workflow Management swamp@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11:29465 |maint:released:sle11:29465 |maint:released:sle11:30475 |maint:released:sle11:30475 | |maint:released:11.1:34862 | |maint:released:11.2:34862 | |maint:released:11.3:34862
--- Comment #83 from Swamp Workflow Management swamp@suse.com 2010-08-10 07:25:04 UTC --- Update released for: sysvinit, sysvinit-debuginfo, sysvinit-debugsource, sysvinit-tools, sysvinit-tools-debuginfo Products: openSUSE 11.1 (debug, i586, ppc, x86_64) openSUSE 11.2 (debug, i586, x86_64) openSUSE 11.3 (debug, i586, x86_64)
http://bugzilla.novell.com/show_bug.cgi?id=559534 http://bugzilla.novell.com/show_bug.cgi?id=559534#c84
--- Comment #84 from Bernhard Wiedemann bwiedemann@suse.com --- This is an autogenerated message for OBS integration: This bug (559534) was mentioned in https://build.opensuse.org/request/show/38504 Factory / lighttpd
-
bugzilla_noreply＠novell.com