Re: How to configure a network bridge from script ?

2016-05-13 Thread Dan Williams 
On Fri, 2016-05-13 at 09:36 +0300, Alexander Todorov wrote:
> На 12.05.2016 в 15:32, Phil Sutter написа:
> > 
> > Hi,
> > 
> > On Thu, May 12, 2016 at 02:47:19PM +0300, Alexander Todorov wrote:
> > > 
> > > # cat /etc/sysconfig/network-scripts/ifcfg-enp1s0f0
> > > Generated by dracut initrd
> > The line above is supposed to be a comment.
> > 
> OK, fixed that then I got:
> 
> # systemctl status network.service
> ● network.service - LSB: Bring up/down networking
> Loaded: loaded (/etc/rc.d/init.d/network)
> Active: failed (Result: exit-code) since пт 2016-05-13 02:33:54
> EDT; 36s ago
>   Docs: man:systemd-sysv-generator(8)
>    Process: 2189 ExecStart=/etc/rc.d/init.d/network start
> (code=exited, 
> status=1/FAILURE)
> 
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Could
> not load 
> file '/etc/sysconfig/network-scripts/ifcfg-lo'
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]:
> [  OK  ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]:
> Bringing up 
> interface enp1s0f0:  [  OK  ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]:
> Bringing up 
> interface enp1s0f1:  Error: Connection activation f...tion.

This line indicates that the scripts are returning a NetworkManager
error, but that error is elided so we don't know what it is.  When
NetworkManager is running, the ifup script basically calls 'nmcli con
up '.  So to better figure this out, you can:

nmcli g log level debug
ifup enp1s0f0

and then grab 'journalctl -b -u NetworkManager' and lets see what's
going on.

Dan

> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]:
> [FAILED]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]:
> Bringing up 
> interface br0:  [  OK  ]
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]:
> network.service: 
> Control process exited, code=exited status=1
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: Failed to
> start LSB: 
> Bring up/down networking.
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]:
> network.service: 
> Unit entered failed state.
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]:
> network.service: 
> Failed with result 'exit-code'.
> Hint: Some lines were ellipsized, use -l to show in full.
> 
> 
> 
> And
> 
> # ip a s
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group 
> default qlen 1
>  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: enp1s0f0:  mtu 1500 qdisc mq
> state UP group 
> default qlen 1000
>  link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
>  inet 10.16.42.33/21 brd 10.16.47.255 scope global dynamic
> enp1s0f0
> valid_lft 77820sec preferred_lft 77820sec
>  inet6 2620:52:0:102f:200:1aff:fe1a:9470/64 scope global
> noprefixroute dynamic
> valid_lft 2591924sec preferred_lft 604724sec
>  inet6 fe80::200:1aff:fe1a:9470/64 scope link
> valid_lft forever preferred_lft forever
> 3: enp1s0f1:  mtu 1500 qdisc mq
> state DOWN 
> group default qlen 1000
>  link/ether 00:00:1a:1a:94:71 brd ff:ff:ff:ff:ff:ff
> 4: br0:  mtu 1500 qdisc noqueue
> state DOWN 
> group default qlen 1000
>  link/ether 42:61:9f:68:1d:85 brd ff:ff:ff:ff:ff:ff
> 
> 
> --
> Alex
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.
> org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: How to configure a network bridge from script ?

2016-05-13 Thread Phil Sutter 
On Fri, May 13, 2016 at 09:36:32AM +0300, Alexander Todorov wrote:
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Could not load 
> file '/etc/sysconfig/network-scripts/ifcfg-lo'
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [  OK  ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up 
> interface enp1s0f0:  [  OK  ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up 
> interface enp1s0f1:  Error: Connection activation f...tion.

This line is incomplete. Please provide full logs, otherwise nobody is
able to help you.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: How to configure a network bridge from script ?

2016-05-13 Thread James Hogarth 
On 13 May 2016 07:37, "Alexander Todorov"  wrote:
>
> На 12.05.2016 в 15:32, Phil Sutter написа:
>>
>> Hi,
>>
>> On Thu, May 12, 2016 at 02:47:19PM +0300, Alexander Todorov wrote:
>>>
>>> # cat /etc/sysconfig/network-scripts/ifcfg-enp1s0f0
>>> Generated by dracut initrd
>>
>>
>> The line above is supposed to be a comment.
>>
>
> OK, fixed that then I got:
>
> # systemctl status network.service
>
> ● network.service - LSB: Bring up/down networking
>Loaded: loaded (/etc/rc.d/init.d/network)
>Active: failed (Result: exit-code) since пт 2016-05-13 02:33:54 EDT;
36s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 2189 ExecStart=/etc/rc.d/init.d/network start (code=exited,
status=1/FAILURE)
>
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Could not
load file '/etc/sysconfig/network-scripts/ifcfg-lo'
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [  OK  ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing
up interface enp1s0f0:  [  OK  ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing
up interface enp1s0f1:  Error: Connection activation f...tion.
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [FAILED]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing
up interface br0:  [  OK  ]
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]:
network.service: Control process exited, code=exited status=1
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: Failed to
start LSB: Bring up/down networking.
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]:
network.service: Unit entered failed state.
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]:
network.service: Failed with result 'exit-code'.
> Hint: Some lines were ellipsized, use -l to show in full.
>
>
>
> And
>
>
> # ip a s
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
> 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: enp1s0f0:  mtu 1500 qdisc mq state UP
group default qlen 1000
> link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
> inet 10.16.42.33/21 brd 10.16.47.255 scope global dynamic enp1s0f0
>valid_lft 77820sec preferred_lft 77820sec
>
> inet6 2620:52:0:102f:200:1aff:fe1a:9470/64 scope global noprefixroute
dynamic
>valid_lft 2591924sec preferred_lft 604724sec
>
> inet6 fe80::200:1aff:fe1a:9470/64 scope link
>valid_lft forever preferred_lft forever
> 3: enp1s0f1:  mtu 1500 qdisc mq state
DOWN group default qlen 1000
> link/ether 00:00:1a:1a:94:71 brd ff:ff:ff:ff:ff:ff
> 4: br0:  mtu 1500 qdisc noqueue state
DOWN group default qlen 1000
> link/ether 42:61:9f:68:1d:85 brd ff:ff:ff:ff:ff:ff
>

Please note that you have mailed the development and test Fedora lists, not
the users list.

This looks like it would better apply there.

Is there a reason you aren't using NetworkManager in your systemctl
attempts above?

If scripting networking you may well find a cleaner solution utilising
nmcli:

https://www.hogarthuk.com/?q=node/8
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: How to configure a network bridge from script ?

2016-05-13 Thread Alexander Todorov 

На 12.05.2016 в 15:32, Phil Sutter написа:

Hi,

On Thu, May 12, 2016 at 02:47:19PM +0300, Alexander Todorov wrote:

# cat /etc/sysconfig/network-scripts/ifcfg-enp1s0f0
Generated by dracut initrd


The line above is supposed to be a comment.



OK, fixed that then I got:

# systemctl status network.service
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: failed (Result: exit-code) since пт 2016-05-13 02:33:54 EDT; 36s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2189 ExecStart=/etc/rc.d/init.d/network start (code=exited, 
status=1/FAILURE)


май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Could not load 
file '/etc/sysconfig/network-scripts/ifcfg-lo'

май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [  OK  ]
май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up 
interface enp1s0f0:  [  OK  ]
май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up 
interface enp1s0f1:  Error: Connection activation f...tion.

май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [FAILED]
май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up 
interface br0:  [  OK  ]
май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: 
Control process exited, code=exited status=1
май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: Failed to start LSB: 
Bring up/down networking.
май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: 
Unit entered failed state.
май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: 
Failed with result 'exit-code'.

Hint: Some lines were ellipsized, use -l to show in full.



And

# ip a s
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1

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: enp1s0f0:  mtu 1500 qdisc mq state UP group 
default qlen 1000

link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
inet 10.16.42.33/21 brd 10.16.47.255 scope global dynamic enp1s0f0
   valid_lft 77820sec preferred_lft 77820sec
inet6 2620:52:0:102f:200:1aff:fe1a:9470/64 scope global noprefixroute 
dynamic
   valid_lft 2591924sec preferred_lft 604724sec
inet6 fe80::200:1aff:fe1a:9470/64 scope link
   valid_lft forever preferred_lft forever
3: enp1s0f1:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000

link/ether 00:00:1a:1a:94:71 brd ff:ff:ff:ff:ff:ff
4: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000

link/ether 42:61:9f:68:1d:85 brd ff:ff:ff:ff:ff:ff


--
Alex
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: How to configure a network bridge from script ?

2016-05-12 Thread Phil Sutter 
Hi,

On Thu, May 12, 2016 at 02:47:19PM +0300, Alexander Todorov wrote:
> # cat /etc/sysconfig/network-scripts/ifcfg-enp1s0f0
> Generated by dracut initrd

The line above is supposed to be a comment.

[...]

> май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: [  OK  ]
> май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: Bringing up 
> interface enp1s0f0:  /etc/sysconfig/network-scripts/ifcfg-enp1s0f0: line 1: 
> Generated: command not found

Here you see how the network service complains about it.

I am not sure it is the culprit of your issue, but let's try with the
obvious things first. :)

Cheers, Phil
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

How to configure a network bridge from script ?

2016-05-12 Thread Alexander Todorov 

Hi guys,
I'm having trouble starting a network bridge from a script without restarting 
the server.


I am following this doc in order to configure a bridged network on a Fedora 23 
Server host:


https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Network_Bridging_Using_the_Command_Line_Interface.html#sec-Create_a_Network_Bridge


my config files look like this:

# cat /etc/sysconfig/network-scripts/ifcfg-br0
DEVICE=br0
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=dhcp
DELAY=0

# cat /etc/sysconfig/network-scripts/ifcfg-enp1s0f0
Generated by dracut initrd
NAME="enp1s0f0"
DEVICE="enp1s0f0"
ONBOOT=yes
NETBOOT=yes
UUID="58081eef-9d1f-48db-a565-65f45bd1c6e8"
IPV6INIT=yes
BOOTPROTO=none
TYPE=Ethernet
BRIDGE=br0


After that I do:

# systemctl restart network
Job for network.service failed because the control process exited with error 
code. See "systemctl status network.service" and "journalctl -xe" for details.


# systemctl status network -l
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: failed (Result: exit-code) since ср 2016-05-04 10:33:32 EDT; 2min 
43s ago

 Docs: man:systemd-sysv-generator(8)
  Process: 1412 ExecStart=/etc/rc.d/init.d/network start (code=exited, 
status=1/FAILURE)


май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: [  OK  ]
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: Bringing up 
interface enp1s0f0:  /etc/sysconfig/network-scripts/ifcfg-enp1s0f0: line 1: 
Generated: command not found

май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: [  OK  ]
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: Bringing up 
interface enp1s0f1:  Error: Connection activation failed: No suitable device 
found for this connection.

май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: [FAILED]
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com network[1412]: Bringing up 
interface br0:  [  OK  ]
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: 
Control process exited, code=exited status=1
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com systemd[1]: Failed to start LSB: 
Bring up/down networking.
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: 
Unit entered failed state.
май 04 10:33:32 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: 
Failed with result 'exit-code'.



After the failure the network config looks like this:


# ip a s
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1

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: enp1s0f0:  mtu 1500 qdisc mq state UP group 
default qlen 1000

link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
inet 10.16.42.33/21 brd 10.16.47.255 scope global dynamic enp1s0f0
   valid_lft 86204sec preferred_lft 86204sec
inet6 2620:52:0:102f:200:1aff:fe1a:9470/64 scope global noprefixroute 
dynamic
   valid_lft 2591805sec preferred_lft 604605sec
inet6 fe80::200:1aff:fe1a:9470/64 scope link
   valid_lft forever preferred_lft forever
3: enp1s0f1:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000

link/ether 00:00:1a:1a:94:71 brd ff:ff:ff:ff:ff:ff
4: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000

link/ether 16:db:ac:3b:24:d4 brd ff:ff:ff:ff:ff:ff
inet6 fe80::14db:acff:fe3b:24d4/64 scope link
   valid_lft forever preferred_lft forever


If I reboot the system the bridge appears to be up and running:

**after reboot**

# ip a s
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1

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: enp1s0f0:  mtu 1500 qdisc mq master br0 
state UP group default qlen 1000

link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
3: enp1s0f1:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000

link/ether 00:00:1a:1a:94:71 brd ff:ff:ff:ff:ff:ff
4: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000

link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
inet 10.16.42.33/21 brd 10.16.47.255 scope global dynamic br0
   valid_lft 86391sec preferred_lft 86391sec
inet6 2620:52:0:102f:200:1aff:fe1a:9470/64 scope global mngtmpaddr dynamic
   valid_lft 2591988sec preferred_lft 604788sec
inet6 fe80::b496:e5ff:fe89:49e3/64 scope link
   valid_lft forever preferred_lft forever



This is with systemd-222-14.fc23.x86_64