Failed to start raise network interfaces debian 10 как исправить

#1 Post by Lamios » 2017-12-10 00:06

Lamios

Posts: 37
Joined: 2017-12-09 23:26

[Solved] Failed to start raise network interfaces

#1

Post

by Lamios » 2017-12-10 00:06

Hello,

when I start Debian I get an error message saying the following:

Code: Select all

[Failed] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.

systemctl status networking.service gives me the following:

Code: Select all

● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: en
   Active: failed (Result: exit-code) since Sat 2017-12-09 12:49:24 GMT; 11h ago
     Docs: man:interfaces(5)
 Main PID: 2043 (code=exited, status=1/FAILURE)
lines 1-5/5 (END)

ifconfig -a lists the following devices:
— enp0s25
— lo
— vpn0
— wlp2s0

The network had been configured automatically with DHCP during the installation…

I am still able to connect to the internet, also if I sometimes have to reboot, because I get the massage that the connection had been deactivated.

The system (Debian 9 with KDE) is newly installed and the problem existed from beginning. The results from google and forum searches did not fit to my error message (at least as far as I can asses it as a Linux beginner).

Thank you for your help!
Lamios

P.S.: I hope the post is complete for the beginning. I am not sure in the moment, which additional output is going to be needed.

Last edited by Lamios on 2017-12-11 15:48, edited 1 time in total.

Lamios

Posts: 37
Joined: 2017-12-09 23:26

Re: Failed to start raise network interfaces

#4

Post

by Lamios » 2017-12-10 11:40

Thank you for the very fast reply!

systemctl cat networking.service:

Code: Select all

# /lib/systemd/system/networking.service
[Unit]
Description=Raise network interfaces
Documentation=man:interfaces(5)
DefaultDependencies=no
Wants=network.target
After=local-fs.target network-pre.target apparmor.service systemd-sysctl.service syst
Before=network.target shutdown.target network-online.target
Conflicts=shutdown.target

[Install]
WantedBy=multi-user.target
WantedBy=network-online.target

[Service]
Type=oneshot
EnvironmentFile=-/etc/default/networking
ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --re
ExecStart=/sbin/ifup -a --read-environment
ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
RemainAfterExit=true
TimeoutStartSec=5min
lines 1-22/22 (END)

journalctl -u networking.service:

Code: Select all

-- Logs begin at Sun 2017-12-10 12:00:15 GMT, end at Sun 2017-12-10 12:07:46 GMT. --
Dec 10 12:00:16 PP systemd[1]: Starting Raise network interfaces...
Dec 10 12:00:16 PP ifup[334]: /etc/network/if-pre-up.d/firewall_renamed: 2: /etc/netw
Dec 10 12:00:16 PP ifup[334]: run-parts: /etc/network/if-pre-up.d/firewall_renamed ex
Dec 10 12:00:16 PP ifup[334]: ifup: pre-up script failed
Dec 10 12:00:16 PP systemd[1]: networking.service: Main process exited, code=exited, 
Dec 10 12:00:16 PP systemd[1]: Failed to start Raise network interfaces.
Dec 10 12:00:16 PP systemd[1]: networking.service: Unit entered failed state.
Dec 10 12:00:16 PP systemd[1]: networking.service: Failed with result 'exit-code'.
Dec 10 12:00:17 PP systemd[1]: Starting Raise network interfaces...
Dec 10 12:00:17 PP ifup[594]: /etc/network/if-pre-up.d/firewall_renamed: 2: /etc/netw
Dec 10 12:00:17 PP ifup[594]: run-parts: /etc/network/if-pre-up.d/firewall_renamed ex
Dec 10 12:00:17 PP ifup[594]: ifup: pre-up script failed
Dec 10 12:00:17 PP systemd[1]: networking.service: Main process exited, code=exited, 
Dec 10 12:00:17 PP systemd[1]: Failed to start Raise network interfaces.
Dec 10 12:00:17 PP systemd[1]: networking.service: Unit entered failed state.
Dec 10 12:00:17 PP systemd[1]: networking.service: Failed with result 'exit-code'.
lines 1-17/17 (END)

The loopback network interface contain the following:

I think I probably see the error in ‘journalctl -u networking.service’. I tried to setup a firewall with iptables but than thought it might be easier to use a firewall tool (at least for the beginning). To prevent an interference between the firewall tool and the existing iptables rules I renamed ‘/etc/iptables.firewall.rules’, ‘/etc/network/if-pre-up.d/firewall’ and ‘/etc/network/if-pre-up.d/firewall.save’ with the addition «_renamed». Is it possible that the .save had not been created by me earlier and is now causing the problem? Or is it because all these files are only renamed and not deleted?

p.H

Section Moderator
Section Moderator
Posts: 3015
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 122 times

Re: Failed to start raise network interfaces

#5

Post

by p.H » 2017-12-10 12:11

The lines you posted are truncated.

Scripts in /etc/network/if-*.d/ are run by run-parts. By default run-parts executes all scripts with names containing only letters, digits, underscore and hyphen [A-Za-z0-9_-]. So /etc/network/if-pre-up.d/firewall is executed, but /etc/network/if-pre-up.d/firewall.save is not because its name contains a dot, not in the allowed character list.

Renaming /etc/network/if-pre-up.d/firewall by adding _renamed does not disable its execution by run-parts because all characters of the suffix are allowed. However if an instruction in the script uses an other file such as /etc/iptables.firewall.rules and you renamed that file without updating the script, then an error may arise. Check in /etc/network/if-pre-up.d/firewall_renamed.

Also note that just renaming the script and not disabling it does not prevent interference with another firewall script.

Lamios

Posts: 37
Joined: 2017-12-09 23:26

Re: Failed to start raise network interfaces

#7

Post

by Lamios » 2017-12-10 22:05

‘journalctl -u networking.service —no-pager’ geave me the following output:

Code: Select all

-- Logs begin at Sun 2017-12-10 22:41:52 GMT, end at Sun 2017-12-10 22:46:26 GMT. --
Dec 10 22:41:53 PP systemd[1]: Starting Raise network interfaces...
Dec 10 22:41:53 PP ifup[313]: /etc/network/if-pre-up.d/firewall_renamed: 2: /etc/network/if-pre-up.d/firewall_renamed: cannot open /etc/iptables.firewall.rules: No such file
Dec 10 22:41:53 PP ifup[313]: run-parts: /etc/network/if-pre-up.d/firewall_renamed exited with return code 2
Dec 10 22:41:53 PP ifup[313]: ifup: pre-up script failed
Dec 10 22:41:53 PP systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 22:41:53 PP systemd[1]: Failed to start Raise network interfaces.
Dec 10 22:41:53 PP systemd[1]: networking.service: Unit entered failed state.
Dec 10 22:41:53 PP systemd[1]: networking.service: Failed with result 'exit-code'.
Dec 10 22:42:18 PP systemd[1]: Starting Raise network interfaces...
Dec 10 22:42:18 PP ifup[1530]: /etc/network/if-pre-up.d/firewall_renamed: 2: /etc/network/if-pre-up.d/firewall_renamed: cannot open /etc/iptables.firewall.rules: No such file
Dec 10 22:42:18 PP ifup[1530]: run-parts: /etc/network/if-pre-up.d/firewall_renamed exited with return code 2
Dec 10 22:42:18 PP systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 22:42:18 PP ifup[1530]: ifup: pre-up script failed
Dec 10 22:42:18 PP systemd[1]: Failed to start Raise network interfaces.
Dec 10 22:42:18 PP systemd[1]: networking.service: Unit entered failed state.
Dec 10 22:42:18 PP systemd[1]: networking.service: Failed with result 'exit-code'.

I did not update the script in ‘/etc/network/if-pre-up.d/’, thus that should be the reason. How can I disable the script?
In ‘/etc/network/if-pre-up.d/’ is also file called firewall.save (or now firewall_renamed.save), which I assumed the system created it to run the firewall rules I created. Is that true or is it there for any other reason?

p.H

Section Moderator
Section Moderator
Posts: 3015
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 122 times

Re: Failed to start raise network interfaces

#8

Post

by p.H » 2017-12-11 12:19

Lamios wrote:How can I disable the script?

(Re)move it, or rename it with a period («.») in the new name so that run-parts ignores it.

Lamios wrote:In ‘/etc/network/if-pre-up.d/’ is also file called firewall.save (or now firewall_renamed.save), which I assumed the system created it to run the firewall rules I created. Is that true or is it there for any other reason?

«The system» does not create such files on its own. Maybe your text editor did as a backup when you modified the original «firewall» file ?
Anyway its filename contains a period, thus is ignored by run-parts and not executed.

Lamios

Posts: 37
Joined: 2017-12-09 23:26
Источник

On a fresh installation of Debian 9 Stretch on a desktop PC when booting the

...
Failed to start Raise network interfaces
...

error occurres. The (cable) LAN-connection works but the (USB) WiFi is not working properly (detecting the WiFi networks but failing to connect). Previously on the same harware Debian 8 Jessie was installed working fine without any errors.

Seems the issues are connected to the recent predictable network interface names changes. Found users A, B, C, D, and E had similar symptoms. However, they had upgraded Ubuntu systems (without a clean install). Aditionally the proposed solutions are suggesting disabling the assignment of fixed/predictable/unique names. I would prefer to keep the new naming scheme/standard, eventually to find and eliminate the reason why(?) it is not working properly.

Found also users F, and G with the same problem — without solution.

Would be very thankful for any hint. Also, I’m happy to answer your questions if you need more in depth details.

Further you find some detailed system output. 

$ sudo systemctl status networking.service 
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-09-04 17:21:42 IST; 1h 27min ago
     Docs: man:interfaces(5)
  Process: 534 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 444 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
 Main PID: 534 (code=exited, status=1/FAILURE)

Sep 04 17:21:42 XXX ifup[534]: than a configuration issue please read the section on submitting
Sep 04 17:21:42 XXX ifup[534]: bugs on either our web page at www.isc.org or in the README file
Sep 04 17:21:42 XXX ifup[534]: before submitting a bug.  These pages explain the proper
Sep 04 17:21:42 XXX ifup[534]: process and the information we find helpful for debugging..
Sep 04 17:21:42 XXX ifup[534]: exiting.
Sep 04 17:21:42 XXX ifup[534]: ifup: failed to bring up eth0
Sep 04 17:21:42 XXX systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Sep 04 17:21:42 XXX systemd[1]: Failed to start Raise network interfaces.
Sep 04 17:21:42 XXX systemd[1]: networking.service: Unit entered failed state.
Sep 04 17:21:42 XXX systemd[1]: networking.service: Failed with result 'exit-code'.


$ cat /etc/network/interfaces.d/setup
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

EDIT2start:

$ sudo ifconfig
[sudo] password for XXX: 
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.31  netmask 255.255.255.0  broadcast 192.168.178.255
        inet6 xxxx::xxx:xxxx:xxxx:xxxx  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 765  bytes 523923 (511.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 803  bytes 101736 (99.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 50  bytes 3720 (3.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 50  bytes 3720 (3.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlxf4f26d1b7521: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

EDIT2end.

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
3: wlxf4f26d1b7521: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

EDITstart:

$ lsusb
...
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
...

$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

EDITend.

EDIT3start:

$ sudo systemctl status networking.service
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2017-09-05 10:29:16 IST; 44min ago
     Docs: man:interfaces(5)
  Process: 565 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
  Process: 438 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
 Main PID: 565 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/networking.service

Sep 05 10:26:56 sdd9 systemd[1]: Starting Raise network interfaces...
Sep 05 10:26:56 sdd9 ifup[565]: ifup: waiting for lock on /run/network/ifstate.enp3s0
Sep 05 10:29:16 sdd9 systemd[1]: Started Raise network interfaces.

EDIT3end.

Источник
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr2 state DOWN group default qlen 1000
    link/ether 74:da:38:d8:98:fc brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:de brd ff:ff:ff:ff:ff:ff
4: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:df brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:de brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.101/24 brd 10.1.1.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::ae1f:6bff:fe91:ede/64 scope link
       valid_lft forever preferred_lft forever
6: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ac:1f:6b:91:0e:df brd ff:ff:ff:ff:ff:ff
    inet 10.1.3.101/24 brd 10.1.3.255 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 fe80::ae1f:6bff:fe91:edf/64 scope link
       valid_lft forever preferred_lft forever
7: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 74:da:38:d8:98:fc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::76da:38ff:fed8:98fc/64 scope link
       valid_lft forever preferred_lft forever
8: vmbr110: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 56:19:63:6e:92:f5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::888:80ff:fe90:1d48/64 scope link
       valid_lft forever preferred_lft forever
9: vmbr105: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:41:8d:12:f1:cc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::10ff:76ff:fef2:d381/64 scope link
       valid_lft forever preferred_lft forever
10: vmbr150: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 42:bd:54:df:d9:5c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d8ec:e1ff:fe43:9057/64 scope link
       valid_lft forever preferred_lft forever
11: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether be:ef:4e:38:39:8c brd ff:ff:ff:ff:ff:ff
12: tap100i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether d2:8d:6a:d4:0b:e5 brd ff:ff:ff:ff:ff:ff
13: tap100i2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr2 state UNKNOWN group default qlen 1000
    link/ether 62:4f:27:58:39:14 brd ff:ff:ff:ff:ff:ff
14: tap100i3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr105 state UNKNOWN group default qlen 1000
    link/ether 1e:41:8d:12:f1:cc brd ff:ff:ff:ff:ff:ff
15: tap100i4: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr110 state UNKNOWN group default qlen 1000
    link/ether 56:19:63:6e:92:f5 brd ff:ff:ff:ff:ff:ff
16: tap100i5: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr150 state UNKNOWN group default qlen 1000
    link/ether 42:bd:54:df:d9:5c brd ff:ff:ff:ff:ff:ff
19: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr110 state UNKNOWN group default qlen 1000
    link/ether 8a:8a:2a:58:01:f3 brd ff:ff:ff:ff:ff:ff
20: tap105i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr105 state UNKNOWN group default qlen 1000
    link/ether 5e:7e:17:7c:2b:1a brd ff:ff:ff:ff:ff:ff
21: tap105i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether fe:15:ec:57:81:98 brd ff:ff:ff:ff:ff:ff

Источник

I am setting a Ubuntu’s VM (16.04.1 LTS) and I get an error when I try to connect from WinSCP in my windows to the VMs. The error is: developmentHost does not exist.

The network/interfaces file is this one:

enter image description here

If I execute a ifconfig command I get this info:

enter image description here

On the other side, the Virtualbox configuration for both network adapters are:

Adapter 1

In the above picture I included the port redirection, because I want to connect with the VM withou editing the windows hosts file.

Adapter 2

Furthermore I get this error about interfaces when I reboot.

enter image description here

asked Jan 12, 2017 at 9:40

mrc's user avatar

I don’t know how to fix the failure but i can show you a shortcut to deal with this problem temporarily…

1-use this command to find out which interfaces are available in your system.
# ip link
example: lo , enp0s8

2-add following lines in /etc/network/interfaces

auto enp0s8
iface enp0s8 inet dhcp

3-restart your VM.
and it’s done.

answered Mar 15, 2017 at 11:17

Amir sina Haftlangi's user avatar

1

In Ubuntu 16.04 there perhaps is no ethX interface anymore. This version now comes with the so called Predictable Network Interface Names, where the name of the interfaces can be determined by: which tries to find fixed slot topology information in certain firmware interfaces and uses them to assign fixed names to interfaces which incorporate their physical location on the mainboard. (refer to: freedesktop.org). Hence you have to find out the correct interface names by using the command ip a which prints something like:

1: lo: ...
2: ensXX: ...
n: ...

before you can configure your /etc/network/interfaces

See also: askubuntu.com

answered Mar 21, 2018 at 21:44

My-Name-Is's user avatar

My-Name-IsMy-Name-Is

4,73410 gold badges44 silver badges82 bronze badges

You mentioned something about a VM, if the hardware address changes then you might have the same issue as if you changed physical hardware.

Get current identifier for the network card:

root@mybox:/home/root# ip -a

1: …

2: enp0df: …. (Your identifier will be different)

Update this information in:
/etc/network/interfaces

# The primary network interface

auto enp0df

iface enp0df inet dhcp

Restart network services:

/etc/init.d/networking restart

answered Oct 1, 2018 at 16:14

Jayson's user avatar

i think you should change network advanced option.
if you set option modo promisco to Permitir todo(permit all), it will work fine.

answered Feb 27, 2017 at 3:44

nyancat's user avatar

1

I had the same question,at last I found that I closed my windows service

VMware NAT Service and VMnetDHCP

just run them

answered Dec 18, 2018 at 6:41

yaoyue1019's user avatar

Источник

Понравилась статья? Поделить с друзьями:
  • Failed to start playback netsdk returns error
  • Failed to start openbsd secure shell server как исправить
  • Failed to start nginx high performance web server как исправить
  • Failed to start lenovo driver error code 2148204812
  • Failed to start ista please make sure your ista configuration is valid как исправить