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