[Bug 815163] New: Memcached server does not start after upgrading to latest updates
https://bugzilla.novell.com/show_bug.cgi?id=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c0 Summary: Memcached server does not start after upgrading to latest updates Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vaibhavkaushal123@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 First of all, this is my first bug report. So if I have selected a wrong section, excuse me for that. Second - I have reported x86-64 because I used that version. I guess this problem might be with other archs as well. Here is the long description of the bug: I upgraded to 12.3 and then switched on Tumbleweed. Apper told me last night to upgrade and I did. However today morning, when i launched my localhost (Apache) and tried to access my project, PHP told me that it could not connect to Memcache server. Investigated a little, the server was not running. Tried to enable it from YaST, used the service command and tried to run the startup script manually (in /etc/init.d) but nothing worked. Reproducible: Always Steps to Reproduce: 1. Start OpenSUSE 2. Go to YaST, Services management. 3. Try to launch Memcached server. Actual Results: The result is reported to be success but does not work. Expected Results: The memcached server should have started. [Continued from the input given in "DETAILS" section of this very report} Finally I thought to have a look inside the startup scripts and I found this in /etc/init.d/memcached: Code: startproc -u $MEMCACHED_USER -g $MEMCACHED_GROUP $MEMCACHED_BIN -d $MEMCACHED_PARAMS Then I opened the /etc/sysconfig/memcached file (mentioned in /etc/init.d/memcached as the MEMCACHED_CONFIG file, so thought to open to get the MEMCACHED_PARAMS value) and found this line: Code: MEMCACHED_PARAMS="-d -l 127.0.0.1" If you notice, the -d parameter is getting repeated twice. When I removed the extra -d from the /etc/sysconfig/memcached file, things went fine. Please make sure that the next update fixes the files. The rest is working okay. Regards, Vaibhav -- 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mrueckert@suse.com |ovo.novell.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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c1 Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert@suse.com AssignedTo|mrueckert@suse.com |crrodriguez@opensuse.org --- Comment #1 from Marcus Rückert <mrueckert@suse.com> 2013-04-22 08:32:20 UTC --- memcach+ 5220 0.0 0.0 317080 872 ? Ssl 10:26 0:00 /usr/sbin/memcached -d -d -l 127.0.0.1 i doubt the extra "-d" is your problem. export SYSTEMD_NO_WRAP=1 and it works for me. the problem is the systemd unit that someone added. that seems to trip over the "-d" in the params options. Christian you introduced the memcached.service 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c2 --- Comment #2 from Cristian Rodríguez <crrodriguez@opensuse.org> 2013-04-22 12:58:51 CLT --- zypper in memcached Updating /etc/sysconfig/memcached... ➜ ~ systemctl start memcached ➜ ~ systemctl status memcached memcached.service - memcached daemon Loaded: loaded (/usr/lib/systemd/system/memcached.service; disabled) Active: active (running) since lun 2013-04-22 13:51:37 CLST; 5s ago Main PID: 11599 (memcached) CGroup: name=systemd:/system/memcached.service └─11599 /usr/sbin/memcached -l 127.0.0.1 --> MEMCACHED_PARAMS="-d -l 127.0.0.1" that 's wrong, you upgraded from a previous version and /etc/sysconfig/memcached did not got updated. MEMCACHED_PARAMS now defaults to "-l 127.0.0.1" as it should.. You must not use "-d", that would require a different time of systemd unit, one of type forking.. -- 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c3 --- Comment #3 from Vaibhav Kaushal <vaibhavkaushal123@gmail.com> 2013-04-22 17:55:20 UTC --- I can understand that I need to make the changes and that -d should not be there. However, the point is - whoever made the update patch should have checked. No, I am not whiling like a little baby. I too am an OSS contributor to a PHP framework project and I know that it is not always possible, still this is an 'OS' so... I hope you understand. Anyways, is there a chance that the files will be getting updated in any upcoming patch? (I have made changes anyways, so I am off the worry shelf; just asking). -- 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c4 --- Comment #4 from Cristian Rodríguez <crrodriguez@opensuse.org> 2013-04-22 14:29:12 CLT --- (In reply to comment #3)
I can understand that I need to make the changes and that -d should not be there. However, the point is - whoever made the update patch should have checked.
I did check it, in fact the files for a new install will work just fine.. but this sysconfig stuff does not have a programatic way to merge user changes in a particular sysconfig variable without removing all user modifications to that variable and creating it again from the start.
Anyways, is there a chance that the files will be getting updated in any upcoming patch? (I have made changes anyways, so I am off the worry shelf; just asking).
See above, this stuff is absolutely retarded and should have been obsoleted long time ago by the particular daemon own 's configuration 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c5 --- Comment #5 from Cristian Rodríguez <crrodriguez@opensuse.org> 2013-04-22 14:32:08 CLT --- (In reply to comment #3)
I can understand that I need to make the changes and that -d should not be there. However, the point is - whoever made the update patch should have checked.
did it create an memcached*rpmnew file in /etc/sysconfig/ on upgrade ? -- 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c6 --- Comment #6 from Vaibhav Kaushal <vaibhavkaushal123@gmail.com> 2013-04-22 18:49:19 UTC --- No it did not. -- 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=815163 https://bugzilla.novell.com/show_bug.cgi?id=815163#c7 --- Comment #7 from Cristian Rodríguez <crrodriguez@opensuse.org> 2013-04-22 14:53:41 CLT --- (In reply to comment #6)
No it did not.
Which illustrates my point.. -- 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