cannot start http server becouse networkmanager

on my fresh installed 42.2 I would like to have http server working, go to yast, click on http server, and it says me that configuration cannot works becouse networkmanager.
I continue and at the end it gives me the error (impossibile adattare il servizio apache2) that translated should be is impossible adapt the service apache2
what can I do to have a working http server??
manythanks, ciao, pier :slight_smile:

Is this a desktop system? Have you considered changing from NetworkManager to wicked instead?

yes is a desktop system, during and just after the installation there was wicked, but network didn’t worked with wicked so I changed to networkmanager that in my laptop works fine, shall I have to try to use wicked??

Well, perhaps you didn’t configure wicked in the first place? To change back to wicked… YaST > System > Network Settings > Global Options, then select ‘Wicked service’. Under the ‘Overview’ tab you then edit the relevant network device to use DHCP or static (particular to your LAN). Whn finished reboot.

ok, I configured wicked and internet works, but yast>http server doesn’t gives any advice but gives the same error:
(impossibile adattare il servizio apache2) that translated should be is impossible adapt the service apache2

Not enough information to go on unfortunately. What is reported by the following?

sudo systemctl status apache2

Review the openSUSE guide…
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.apache2.html

root's password:
● apache2.service - The Apache Webserver
   Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since mar 2017-02-21 20:23:28 CET; 17min ago
  Process: 3873 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=1/FAILURE)
  Process: 3864 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE)
 Main PID: 3864 (code=exited, status=1/FAILURE)

feb 21 20:23:28 servercasa start_apache2[3873]: [Tue Feb 21 20:23:28.840711 2017] [so:warn...ng
feb 21 20:23:28 servercasa start_apache2[3873]: [Tue Feb 21 20:23:28.840718 2017] [so:warn...ng
feb 21 20:23:28 servercasa start_apache2[3873]: [Tue Feb 21 20:23:28.840726 2017] [so:warn...ng
feb 21 20:23:28 servercasa start_apache2[3873]: [Tue Feb 21 20:23:28.840733 2017] [so:warn...ng
feb 21 20:23:28 servercasa start_apache2[3873]: AH00526: Syntax error on line 153 of /etc/...f:
feb 21 20:23:28 servercasa start_apache2[3873]: Invalid command 'Order', perhaps misspelle...on
feb 21 20:23:28 servercasa systemd[1]: apache2.service: Control process exited, code=exit...s=1
feb 21 20:23:28 servercasa systemd[1]: Failed to start The Apache Webserver.
feb 21 20:23:28 servercasa systemd[1]: apache2.service: Unit entered failed state.
feb 21 20:23:28 servercasa systemd[1]: apache2.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
pla@servercasa:~> 


That error does not stem from NM or Wicked, it’s because your configuration files have Apache 2.2 rules in them, mainly the “Order” - you’ll need to add the access_compat module if you want to use it or fix them to use the new Apache 2.4 require directive.

sudo a2enmod access_compat

Restart Apache2.

Edit:
To understand how configuration between 2.2 and 2.4 changed; https://httpd.apache.org/docs/2.4/upgrading.html

manythanks, I will try.
…but, wicked hasn’t any icon in system tray taht advise that it is working and is connected??

Of course not. That is not something the end user should bother about (and there are no icons for revolving disks, running CPUs, memory banks, etc.). The network is simply available (if the system manager/administrator has configured correctly). This works also without any GUI running or even available. It works so since the 1970’s.

This icon is only there since users walk around with their system (laptops and the like) and want to connect to different networks. Thus part of the system manager’s task is downloaded upon the user, and the tool to do that is NetworkManager and the icon is the end-user’s GUI interface to it.

If you want an indicator on your bar, I suggest the one I use, knemo: openSUSE Software

Since this is a laptop,
And,
If this laptop is moved from one network to another(eg connecting to different wireless AP),

Then you should go back to using Network Manager because wicked remembers only one network configuration at a time.

Properly configured,
Whether you use NM or not should not matter for running an Apache web server…
But,
If you want to configure your Apache web server to start automatically on boot, then you also need to configure a suitable network connection to start on system boot as well.

You should consider whether your Apache web server is intended for others to use or just for your local machine use because it can make a big difference how best to deploy and configure.

TSU

yes, but network sometimes doesn’t works for many reasons, wicked or not, so, I think it is useful an indicator to know if network works or not :slight_smile:

As I said, same for other hardware you have no icons for.
But a not functioning network connection is easy to detect for the end-user and thus he can complain with the system manager (same person?). And the system manager will know (we may hope) how to find out (with ifcfg, route, check router, etc.) what is wrong.

You may look at it as a single user, maybe walk around system where the original techniques are for computer room, multi-user or server (HTTP, data base, etc.) systems.
You do not want eighty users having an icon telling the about the one or more network connections of such a system.

In any case, I am completely happy with the desktop systems here not cluttering the end-users desktop with again some needless icon.

ok guys lol!, now the “it works” appear, only with localhost but works, from the external it gives

Access forbidden!

You don't have permission to access the requested directory. There is either no index document or the directory is read-protected.

If you think this is a server error, please contact the webmaster.
Error 403

, I reinstalled apache2, so the original apache2 folder is virgin, run sudo a2enmod access_compat, as yast module gives always error I started manually with systemctl start apache2, enabled with systemctl enable apache2, the command systemctl status apache2 now gives this

servercasa:/home/pla # systemctl status apache2
● apache2.service - The Apache Webserver
   Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled)
   Active: active (running) since mer 2017-02-22 21:14:02 CET; 23min ago
 Main PID: 21654 (/usr/sbin/httpd)
   Status: "Total requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec"
   CGroup: /system.slice/apache2.service
           ├─21654 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...
           ├─21663 /usr/bin/mono /usr/lib/mono/xsp2/mod-mono-server2.exe --filename /tmp/mod...
           ├─21664 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...
           ├─21665 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...
           ├─21666 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...
           ├─21667 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...
           ├─21668 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...
           └─21676 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile...

feb 22 21:14:01 servercasa systemd[1]: Starting The Apache Webserver...
feb 22 21:14:02 servercasa systemd[1]: Started The Apache Webserver.
servercasa:/home/pla # 


hoping that at the rebbot it works, now I have to copy and translate my old config from 2.2 to 2.4
manythanks to all, :slight_smile: ciao, :slight_smile: pier

Glad to read of your success with this. Thanks to Miuku for pointing you in the right direction with respect to apache 2.2 and 2.4 version config differences. :slight_smile:

Yes, that is one to keep in mind. There were already other people having that problem when they thought they could simply take over all config files on an upgrade. :frowning:

:)yes, that was my hope :), I come from a working 13.2 where died the hard disk, so I tried to start from the last, …in the past it worked very good, with sftp server it worked very well, …I will try with samba later, manythanks again :slight_smile:

BTW, my advice would be to reserve some time in the future to adapt your configuration to the new defenitions. Then you can stop using the compatibility module and you are up-to-date again.