[Bug 736715] New: OBS Web Interface Error when $multiaction_notify_support = 0
https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c0 Summary: OBS Web Interface Error when $multiaction_notify_support = 0 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: mrueckert@suse.com ReportedBy: andrzej.lisowski@ericsson.com QAContact: adrian@suse.com Found By: --- Blocker: --- Created an attachment (id=467380) --> (http://bugzilla.novell.com/attachment.cgi?id=467380) Screenshot with OBS Web Interface Error in jpg format User-Agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 Private instance of OBS is being prepared. The OBS software has been downloaded as virtual appliance from openSUSE and is running on VMWare ESXi 4.0 host. During the work on the integration of this private Open Build Service instance with Hermes http://en.opensuse.org/openSUSE:Hermes the parameter $multiaction_notify_support = 0 has been enabled in the /usr/lib/obs/server/BSConfig.pm file. Unfortunately after enabling this parameter and restarting the private OBS instance the web interface for OBS became dysfunctional and was continuously responding with the following notification on all attempt to access the OBS. ========================================= OBS Web Interface Error: Error Details: Errorcode: unknown Message: <?xml version="1.0" encoding="UTF-8"?> <status code="unknown"> <summary>uncaught exception: Failed to establish connect ======================================================= The screenshot with the reported error message has been attached to this report. After commenting out the parameter $multiaction_notify_support = 0 back and restarting the private OBS instance again the OBS comes back to normal. The issue is 100% reproducible. Identical behavior has been observed with Google Chrome, Internet Explorer and Mozilla Firefox and both Linux and Windows client machines. The following OBS packages have been installed on the host where the issue occures: obs-private-server:~ # rpm -qa | grep obs obs-service-verify_file-0.1-4.1.noarch obs-service-download_src_package-0.1-3.1.noarch obs-signd-2.1.2-1.1.x86_64 obs-service-set_version-0.1-5.1.noarch obs-service-download_url-0.1-12.1.noarch obs-worker-2.1.11-4.7.noarch obs-server-2.1.11-4.7.x86_64 obs-productconverter-2.1.11-4.7.x86_64 obs-utils-2.1.11-4.7.x86_64 obs-api-2.1.11-4.7.x86_64 obs-source_service-2.1.11-4.7.x86_64 obs-common-2.1.0-1.1.x86_64 obs-service-recompress-0.1-8.1.noarch obs-service-extract_file-0.1-6.1.noarch obs-service-tar_scm-0.2.1-16.1.noarch obs-private-server:~ # rpm -qa | grep osc osc-0.132.6-61.3.noarch Reproducible: Always Steps to Reproduce: 1. Enable the parameter $multiaction_notify_support = 0 in the /usr/lib/obs/server/BSConfig.pm file 2. Restart the OBS instance 3. Access the OBS web interface using the web browser Actual Results: The following error message is reported in the OBS web interface: OBS Web Interface Error: Error Details: Errorcode: unknown Message: <?xml version="1.0" encoding="UTF-8"?> <status code="unknown"> <summary>uncaught exception: Failed to establish connect Expected Results: The OBS should work normally after enabling the parameter $multiaction_notify_support = 0 in the /usr/lib/obs/server/BSConfig.pm file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mrueckert@suse.com |adrian@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert@suse.com Component|OBS Request |backend Version|unspecified |backend AssignedTo|adrian@suse.com |mls@suse.com Product|openSUSE.org |openSUSE Build Service -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c1 Michael Schröder <mls@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mls@suse.com |adrian@suse.com --- Comment #1 from Michael Schröder <mls@suse.com> 2011-12-14 11:02:28 UTC --- Hmm, "$multiaction_notify_support = 0" is the default, so I don't see how this can be the source of your problem. Do you see anything suspicious in the logfiles? Are all build service processes running? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c2 --- Comment #2 from Andrzej Lisowski <andrzej.lisowski@ericsson.com> 2011-12-14 11:39:22 UTC --- Actually I have found something in the log files: :::::::::::::: dispatcher.log :::::::::::::: syntax error at BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//bs_dispatch line 46. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_dispatch line 46. :::::::::::::: publisher.log :::::::::::::: syntax error at /usr/lib/obs/server//BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//bs_publish line 38. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_publish line 38. :::::::::::::: rep_server.log :::::::::::::: syntax error at BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//bs_repserver line 48. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_repserver line 48. :::::::::::::: scheduler_i586.log :::::::::::::: syntax error at BSConfig.pm line 58, near "our " Compilation failed in require at ./bs_sched line 39. BEGIN failed--compilation aborted at ./bs_sched line 39. :::::::::::::: scheduler_x86_64.log :::::::::::::: syntax error at BSConfig.pm line 58, near "our " Compilation failed in require at ./bs_sched line 39. BEGIN failed--compilation aborted at ./bs_sched line 39. :::::::::::::: signer.log :::::::::::::: syntax error at /usr/lib/obs/server//BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//bs_signer line 39. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_signer line 39. :::::::::::::: src_server.log :::::::::::::: syntax error at /usr/lib/obs/server//BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//bs_srcserver line 40. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_srcserver line 40. :::::::::::::: src_service.log :::::::::::::: syntax error at /usr/lib/obs/server//BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//BSStdServer.pm line 34. BEGIN failed--compilation aborted at /usr/lib/obs/server//BSStdServer.pm line 34. Compilation failed in require at /usr/lib/obs/server//bs_service line 41. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_service line 41. :::::::::::::: warden.log :::::::::::::: syntax error at /usr/lib/obs/server//BSConfig.pm line 58, near "our " Compilation failed in require at /usr/lib/obs/server//bs_warden line 37. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_warden line 37. So after looking closely another time at the template I have found the root for this problem :-) Have a look at line 65 of the template for the BSConfig.pm file: http://gitorious.org/opensuse/build-service/blobs/899b861726f688927c57cd9f7f... You'll fine the following line there: #our $multiaction_notify_support = 0 But it should be: #our $multiaction_notify_support = 0; When I was removing the # sign I should add as well ; sign at the end of the line so it would look like that our $multiaction_notify_support = 0; Once I have added the sign ; at the end of the line the system works fine again. I guess that it would be good to add the ; sign at the end of the line also in the template file for BSConfig.pm so the new users for OBS would not fall into this trap again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736715 https://bugzilla.novell.com/show_bug.cgi?id=736715#c3 Adrian Schröter <adrian@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #3 from Adrian Schröter <adrian@suse.com> 2011-12-14 12:25:25 UTC --- Sorry, but we do not ship OBS 2.1 with Hermes. If you need support on getting such an instance running, I recommend that you ask consulting (eg. B1 Systems) for creating such a setup. Of course we can take patches if you debug the issue yourself, but we can't put effort in installation support here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com