[opensuse-support] Upgrade apache2-mod_php7 halts zypper on TW
Hi, For some time now when upgrading TW (which I do regularly using zypper dup --no-allow-vendor-change) when it comes to apache2-mod_php7, zypper halts. That is, it ends with the 100% installed message, and than it stops. I have to "kill -9" it to free the terminal, and have to start zypper anew. Anyone any idea whit might cause that? cheers, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
11.01.2020 14:21, Jogchum Reitsma пишет:
Hi,
For some time now when upgrading TW (which I do regularly using zypper dup --no-allow-vendor-change) when it comes to apache2-mod_php7, zypper halts. That is, it ends with the 100% installed message, and than it stops. I have to "kill -9" it to free the terminal, and have to start zypper anew.
Anyone any idea whit might cause that?
Some script that runs as part of package installation/removal. Has nothing to do with zypper. Check what processes are running at this moment, check scripts that are part of package (rpm -q --scripts). -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 11-01-2020 om 12:21 schreef Jogchum Reitsma:
Hi,
For some time now when upgrading TW (which I do regularly using zypper dup --no-allow-vendor-change) when it comes to apache2-mod_php7, zypper halts. That is, it ends with the 100% installed message, and than it stops. I have to "kill -9" it to free the terminal, and have to start zypper anew.
Anyone any idea whit might cause that?
cheers, Jogchum
<Sent it PM by accedent> It has been a while since I got the opportunity to run these commands, but now the installation of apache2 stalls zypper again. ps -ef | grep apache: root 13713 7641 0 15:31 pts/1 00:00:00 rpm --root / --dbpath /var/lib/rpm -U --percent --noglob --force --nodeps -- /var/cache/zypp/packages/http-download.opensuse.org-4503a06a/x86_64/apache2-mod_wsgi-python3-4.6.8-2.2.x86_64.rpm root 13720 13717 0 15:31 pts/1 00:00:00 vi /etc/sysconfig/apache2# rpm -q --scripts apache2-mod_wsgi-python3: postinstall scriptlet (using /bin/sh): if ! /usr/sbin/a2enmod -q wsgi; then /usr/sbin/a2enmod wsgi fi postuninstall scriptlet (using /bin/sh): if [ "$1" = "0" ]; then if a2enmod -q wsgi; then /usr/sbin/a2enmod -d wsgi fi fi postinstall scriptlet (using /bin/sh): if ! /usr/sbin/a2enmod -q wsgi; then /usr/sbin/a2enmod wsgi fi postuninstall scriptlet (using /bin/sh): if [ "$1" = "0" ]; then if a2enmod -q wsgi; then /usr/sbin/a2enmod -d wsgi fi fi If I run " /usr/sbin/a2enmod -q wsgi" by hand, it stalls too, and if I kill it, the meaagage on the terminal is "/etc/sysconfig/apache2: regel 200: 31751 Geëlimineerd (eliminated in Dutch) The file /etc/sysconfig/apache2# contains on line 200 the line "vi /etc/sysconfig/apache2#" a self-referral. If I kill the "rpm --root <...>" line, on the terminal that runs the zypper dup the message is Installation of apache2-mod_wsgi-python3-4.6.8-2.2.x86_64 fialed: Error: Subprocess failed. Error: RPM filed: Vim: Warning: Output is not to a terminal zypper halts again on apache2-mod_php7-7.4.3-1.2.x86_64.rpm, and here also it is apparently the command "vi /etc/sysconfig/apache2#:" where the process halts. If I kill the several vi-processes from the postinstall script, zypper answers with /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@bin: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@boot: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@dev: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@etc: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@home: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@lib: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@lib64: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@mnt: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@opt: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@proc: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@root: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@run: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@sbin: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@selinux: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@srv: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@sys: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@tmp: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@usr: No such file or directory /usr/sbin/a2enmod: line 65: /etc/sysconfig/apache2@var: No such file or directory Any idea what to do to update apache2?
On 3/19/20 3:01 AM, Jogchum Reitsma wrote:
Op 11-01-2020 om 12:21 schreef Jogchum Reitsma:
Hi,
Any idea what to do to update apache2?
Filing a bug report is probably a good starting point this shouldn't be how any package works. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Op 19-03-2020 om 00:54 schreef Simon Lees:
On 3/19/20 3:01 AM, Jogchum Reitsma wrote:
Op 11-01-2020 om 12:21 schreef Jogchum Reitsma:
Hi, Any idea what to do to update apache2?
Filing a bug report is probably a good starting point this shouldn't be how any package works.
Entered https://bugzilla.opensuse.org/show_bug.cgi?id=1167266 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 20-03-2020 om 18:10 schreef Jogchum Reitsma:
Op 19-03-2020 om 00:54 schreef Simon Lees:
On 3/19/20 3:01 AM, Jogchum Reitsma wrote:
Op 11-01-2020 om 12:21 schreef Jogchum Reitsma:
Hi, Any idea what to do to update apache2?
Filing a bug report is probably a good starting point this shouldn't be how any package works.
Entered https://bugzilla.opensuse.org/show_bug.cgi?id=1167266
More than three weeks have past since I entered the bug, and nothing has happened since - no comments so far, and the bug is not assigned to someone, AFAICS. Anything I can do to draw some some attention to this? If not, I think I'll uninstall the Apache stack (if that works), and re-install it. But if that is successful, I probably can't reproduce the error anymore, and be of no help in determinating what caused the bug. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hello, Am Sonntag, 12. April 2020, 10:17:41 CEST schrieb Jogchum Reitsma:
Op 20-03-2020 om 18:10 schreef Jogchum Reitsma:
Entered https://bugzilla.opensuse.org/show_bug.cgi?id=1167266
More than three weeks have past since I entered the bug, and nothing has happened since - no comments so far, and the bug is not assigned to someone, AFAICS.
Anything I can do to draw some some attention to this?
I just assigned the bugreport to Petr (one of the Apache and PHP maintainers).
If not, I think I'll uninstall the Apache stack (if that works), and re-install it. But if that is successful, I probably can't reproduce the error anymore, and be of no help in determinating what caused the bug.
Looking at your report again, I noticed an important detail: /etc/sysconfig/apache2# contains itself a line "vi /etc/sysconfig/apache2#" I think that explains your problem ;-) The files in /etc/sysconfig/ often (not always) get sourced[1] [2] in scripts. If such a file contains a command, it will get executed, and in your case there's a command that starts vi - and vi runs until someone types :wq or q! ;-) (hint: rpm won't do that ;-) I'd recommend: Make a backup of /etc/sysconfig/apache, then edit /etc/sysconfig/apache and remove the "vi /etc/sysconfig/apache#" line. I'd be surprised if that line was added by a package update - it's more likely that you accidently typed it while you already had the file open ;-) Regards, Christian Boltz [1] "soucing" a script is the equivalent to #include in C - it will run as part of the script where it gets sourced. [2] not all sysconfig files get sourced - there's also the option to use them as EnvironmentFile=/etc/sysconfig/whatever in a *.service file. In this case, only variable assignments get honored, and everything else (hopefully) gets ignored - but for sure not executed. -- We really shouldn't expect that applications are compatible with python3. After all, it was only released a little more than a decade ago. [Arjen de Korte in opensuse-factory] -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 12-04-2020 om 13:38 schreef Christian Boltz:
Hello,
Op 20-03-2020 om 18:10 schreef Jogchum Reitsma:
Entered https://bugzilla.opensuse.org/show_bug.cgi?id=1167266 More than three weeks have past since I entered the bug, and nothing has happened since - no comments so far, and the bug is not assigned to someone, AFAICS.
Anything I can do to draw some some attention to this? I just assigned the bugreport to Petr (one of the Apache and PHP
Am Sonntag, 12. April 2020, 10:17:41 CEST schrieb Jogchum Reitsma: maintainers).
If not, I think I'll uninstall the Apache stack (if that works), and re-install it. But if that is successful, I probably can't reproduce the error anymore, and be of no help in determinating what caused the bug. Looking at your report again, I noticed an important detail:
/etc/sysconfig/apache2# contains itself a line "vi /etc/sysconfig/apache2#"
I think that explains your problem ;-)
The files in /etc/sysconfig/ often (not always) get sourced[1] [2] in scripts. If such a file contains a command, it will get executed, and in your case there's a command that starts vi - and vi runs until someone types :wq or q! ;-) (hint: rpm won't do that ;-)
I'd recommend: Make a backup of /etc/sysconfig/apache, then edit /etc/sysconfig/apache and remove the "vi /etc/sysconfig/apache#" line.
I'd be surprised if that line was added by a package update - it's more likely that you accidently typed it while you already had the file open ;-)
Regards,
Christian Boltz
[1] "soucing" a script is the equivalent to #include in C - it will run as part of the script where it gets sourced.
[2] not all sysconfig files get sourced - there's also the option to use them as EnvironmentFile=/etc/sysconfig/whatever in a *.service file. In this case, only variable assignments get honored, and everything else (hopefully) gets ignored - but for sure not executed.
Thanks, that was without a doubt indeed the problem - I followed your advice, and in the last TW-snapshot the apache parts were installed without problems. Though I can't remember ever having touched this /etc/sysconfig/apache by hand, I can understand you reasoning. In case you're right, my apologies for the inconvenience. I suppose I can close the bug? AFAICS apache doesn't start yet, systemctl start apache2 returns without console messages, but systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled) Active: reloading (reload) (Result: exit-code) since Mon 2020-04-13 17:14:29 CEST; 5s ago Process: 66224 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=254) Main PID: 66224 (code=exited, status=254) Status: "Reading configuration..." Tasks: 0 Memory: 5.3M CGroup: /system.slice/apache2.service apr 13 17:14:29 linux-mkay systemd[1]: Starting The Apache Webserver... apr 13 17:14:29 linux-mkay systemd[1]: Started The Apache Webserver. apr 13 17:14:29 linux-mkay systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a and ps -ef | grep apache returns only the grep command itself, so apache isn't running. I'll have to look into that further; it's another problem whatsoever. Thanks again, cheers, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hello, Am Montag, 13. April 2020, 18:26:40 CEST schrieb Jogchum Reitsma:
Op 12-04-2020 om 13:38 schreef Christian Boltz:
Am Sonntag, 12. April 2020, 10:17:41 CEST schrieb Jogchum Reitsma:
Op 20-03-2020 om 18:10 schreef Jogchum Reitsma:
Entered https://bugzilla.opensuse.org/show_bug.cgi?id=1167266
Looking at your report again, I noticed an important detail: /etc/sysconfig/apache2# contains itself a line "vi /etc/sysconfig/apache2#"
I think that explains your problem ;-)
I'd recommend: Make a backup of /etc/sysconfig/apache, then edit /etc/sysconfig/apache and remove the "vi /etc/sysconfig/apache#" line.
I'd be surprised if that line was added by a package update - it's more likely that you accidently typed it while you already had the file open ;-)
Thanks, that was without a doubt indeed the problem - I followed your advice, and in the last TW-snapshot the apache parts were installed without problems.
:-)
Though I can't remember ever having touched this /etc/sysconfig/apache by hand, I can understand you reasoning. In case you're right, my apologies for the inconvenience.
No worries, it was an interesting problem ;-)
I suppose I can close the bug?
Yes ;-)
AFAICS apache doesn't start yet, systemctl start apache2 returns without console messages, but
systemctl status apache2 ● apache2.service - The Apache Webserver
apr 13 17:14:29 linux-mkay systemd[1]: Starting The Apache Webserver... apr 13 17:14:29 linux-mkay systemd[1]: Started The Apache Webserver. apr 13 17:14:29 linux-mkay systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a
Check /var/log/apache/error_log - with some luck, it has a more helpful error message. Just to be sure, also check the result of grep '^[^#]' /etc/sysconfig/apache2 It should only show lines like APACHE_...="..." Regards, Christian Boltz --
Guter Controller z.B. Adaptec Der Satz enthält einen Widerspruch. [> Peter Sikorski GTL und Martin Schröder in opensuse-de]
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 13-04-2020 om 23:39 schreef Christian Boltz:
Hello,
<snip>
AFAICS apache doesn't start yet, systemctl start apache2 returns without console messages, but
systemctl status apache2 ● apache2.service - The Apache Webserver apr 13 17:14:29 linux-mkay systemd[1]: Starting The Apache Webserver... apr 13 17:14:29 linux-mkay systemd[1]: Started The Apache Webserver. apr 13 17:14:29 linux-mkay systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a Check /var/log/apache/error_log - with some luck, it has a more helpful error message.
Just to be sure, also check the result of grep '^[^#]' /etc/sysconfig/apache2 It should only show lines like APACHE_...="..."
Regards,
Christian Boltz
I started a separate thread for this, since to me it seems unrelated to the problem in this thread. regards, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Christian Boltz -
Jogchum Reitsma -
Simon Lees