[6.1-5] Weird LXC behaviour : systemd doesn't start any service

T

technics

New Member
Jan 22, 2020
7
1
3
26
Hi everyone, first post here sorry if i miss some rules,

I played with LXC before but i just tried it in proxmox this weeks. All the CT i used are on Debian Buster and are setup via the proxmox webui. I got a strange behaviour on every LXC container i try to run :

- I create an unprivilege container
- I update/upgrade it and install some tools, let's say an ssh server
- I reboot the container
- On reboot, every services are waiting except networking.service, which is running
- At some point (like if i wait 5 minutes), systemctl list-jobs just says "no jobs running"

I don't get it, and i tried some solution i found online like adding lxc.mount.auto: sys to /etc/pve/lxc/<id>.conf or nesting=1 but none of that works.

I don't really know which logs are relevant in that case but feel free to guide me if it ever happen to you.

systemd --version : systemd 241

UPDATE : Ok so if i wait more than that everything goes back to normal, the services start and it works. Is it possible that networking.service takes a lot of time to start, locking other services ?

I'm tempted to mark it as solved but something still wrong here
 
Last edited:
technics said:
Hi everyone, first post here sorry if i miss some rules,

I played with LXC before but i just tried it in proxmox this weeks. All the CT i used are on Debian Buster and are setup via the proxmox webui. I got a strange behaviour on every LXC container i try to run :

- I create an unprivilege container
- I update/upgrade it and install some tools, let's say an ssh server
- I reboot the container
- On reboot, every services are waiting except networking.service, which is running
- At some point (like if i wait 5 minutes), systemctl list-jobs just says "no jobs running"

I don't get it, and i tried some solution i found online like adding lxc.mount.auto: sys to /etc/pve/lxc/<id>.conf or nesting=1 but none of that works.

I don't really know which logs are relevant in that case but feel free to guide me if it ever happen to you.

systemd --version : systemd 241

UPDATE : Ok so if i wait more than that everything goes back to normal, the services start and it works. Is it possible that networking.service takes a lot of time to start, locking other services ?

I'm tempted to mark it as solved but something still wrong here
Click to expand...
Hi,
yes systemd allows to wait for other services to start before others.
Maybe debugging with systemd-analyze blame https://www.freedesktop.org/software/systemd/man/systemd-analyze.html
gives info on what service is blocking. journalctl -r might also give hints.
 
  • Like
Reactions: technics
Chris said:
Hi,
yes systemd allows to wait for other services to start before others.
Maybe debugging with systemd-analyze blame https://www.freedesktop.org/software/systemd/man/systemd-analyze.html
gives info on what service is blocking. journalctl -r might also give hints.
Click to expand...

Thanks a lot @Chris !

Indeed, systemd-analyze blame return 5min 31ms networking.service and i think other services are waiting for it. I'll read the doc and learn how to configure other services to start before networking.service, if possible.
Do you think it's a normal behaviour ? Or it shouldn't be so long for it to start ?
 
technics said:
Thanks a lot @Chris !

Indeed, systemd-analyze blame return 5min 31ms networking.service and i think other services are waiting for it. I'll read the doc and learn how to configure other services to start before networking.service, if possible.
Do you think it's a normal behaviour ? Or it shouldn't be so long for it to start ?
Click to expand...
You should not configure other services to start before their dependency is ready, that makes no sense and will lead to more issues. You should instead try to find out why this service is taking so long. Check journalctl -u networking.service for errors and logs.
Maybe it is waiting for an IP via DHCP and can not reach the DHCP server? Just a guess...
 
Chris said:
You should not configure other services to start before their dependency is ready, that makes no sense and will lead to more issues. You should instead try to find out why this service is taking so long. Check journalctl -u networking.service for errors and logs.
Maybe it is waiting for an IP via DHCP and can not reach the DHCP server? Just a guess...
Click to expand...

Yep, you seems right :

Code: 
-- Logs begin at Wed 2020-01-22 09:32:42 UTC, end at Wed 2020-01-22 12:45:01 UTC. --
Jan 22 09:32:43 OnlyOffice systemd[1]: Starting Raise network interfaces...
Jan 22 09:32:44 OnlyOffice dhclient[92]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:44 OnlyOffice ifup[75]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:44 OnlyOffice ifup[75]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:44 OnlyOffice ifup[75]: All rights reserved.
Jan 22 09:32:44 OnlyOffice ifup[75]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:44 OnlyOffice dhclient[92]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:44 OnlyOffice dhclient[92]: All rights reserved.
Jan 22 09:32:44 OnlyOffice dhclient[92]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:44 OnlyOffice dhclient[92]:
Jan 22 09:32:44 OnlyOffice dhclient[92]: Listening on LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice ifup[75]: Listening on LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice ifup[75]: Sending on   LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice ifup[75]: Sending on   Socket/fallback
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jan 22 09:32:44 OnlyOffice dhclient[92]: Sending on   LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice dhclient[92]: Sending on   Socket/fallback
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPOFFER of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPOFFER of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPREQUEST for 192.168.0.45 on eth0 to 255.255.255.255 port 67
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPREQUEST for 192.168.0.45 on eth0 to 255.255.255.255 port 67
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPACK of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPACK of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:45 OnlyOffice dhclient[92]: bound to 192.168.0.45 -- renewal in 17537 seconds.
Jan 22 09:32:45 OnlyOffice ifup[75]: bound to 192.168.0.45 -- renewal in 17537 seconds.
Jan 22 09:32:46 OnlyOffice dhclient[172]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice ifup[75]: All rights reserved.
Jan 22 09:32:46 OnlyOffice ifup[75]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice dhclient[172]: All rights reserved.
Jan 22 09:32:46 OnlyOffice dhclient[172]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]:
Jan 22 09:32:46 OnlyOffice dhclient[172]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: PRC: Soliciting for leases (INIT).
Jan 22 09:32:46 OnlyOffice dhclient[172]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Forming Solicit, 0 ms elapsed.
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:46 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Forming Solicit, 1030 ms elapsed.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:47 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Forming Solicit, 3050 ms elapsed.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:49 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Forming Solicit, 6910 ms elapsed.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 7580ms.
Jan 22 09:32:46 OnlyOffice dhclient[172]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice ifup[75]: All rights reserved.
Jan 22 09:32:46 OnlyOffice ifup[75]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice dhclient[172]: All rights reserved.
Jan 22 09:32:46 OnlyOffice dhclient[172]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]:
Jan 22 09:32:46 OnlyOffice dhclient[172]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: PRC: Soliciting for leases (INIT).
Jan 22 09:32:46 OnlyOffice dhclient[172]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Forming Solicit, 0 ms elapsed.
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:46 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Forming Solicit, 1030 ms elapsed.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:47 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Forming Solicit, 3050 ms elapsed.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:49 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Forming Solicit, 6910 ms elapsed.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 7580ms.

Still, ip a gives the right ip address even if networking did not start, and i can ping the CT. I guess the problem could be solve by assigning a static ip address instead of doing it via dhcp ?

Thanks a lot for your time !
 
It's seems like DHCP was the problem here, as @Chris said. After a certain period of time, the container completely lost any internet connection. That's a strange behaviour and i'm not qualified enough to investigate this, unfortunately...

I solved this problem by assigning a static ip to the containers, it seems to work fine for now.
 
technics said:
I solved this problem by assigning a static ip to the containers, it seems to work fine for now.
Click to expand...
i'd also make sure the static addresses you assigned aren't in the DHCP range, to avoid having the same issue later on. maybe leave some ip block unavailable for DHCP
 
technics said:
Yep, you seems right :

Code: 
-- Logs begin at Wed 2020-01-22 09:32:42 UTC, end at Wed 2020-01-22 12:45:01 UTC. --
Jan 22 09:32:43 OnlyOffice systemd[1]: Starting Raise network interfaces...
Jan 22 09:32:44 OnlyOffice dhclient[92]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:44 OnlyOffice ifup[75]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:44 OnlyOffice ifup[75]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:44 OnlyOffice ifup[75]: All rights reserved.
Jan 22 09:32:44 OnlyOffice ifup[75]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:44 OnlyOffice dhclient[92]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:44 OnlyOffice dhclient[92]: All rights reserved.
Jan 22 09:32:44 OnlyOffice dhclient[92]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:44 OnlyOffice dhclient[92]:
Jan 22 09:32:44 OnlyOffice dhclient[92]: Listening on LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice ifup[75]: Listening on LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice ifup[75]: Sending on   LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice ifup[75]: Sending on   Socket/fallback
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jan 22 09:32:44 OnlyOffice dhclient[92]: Sending on   LPF/eth0/5e:f9:2f:9b:e8:83
Jan 22 09:32:44 OnlyOffice dhclient[92]: Sending on   Socket/fallback
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPOFFER of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPOFFER of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPREQUEST for 192.168.0.45 on eth0 to 255.255.255.255 port 67
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPREQUEST for 192.168.0.45 on eth0 to 255.255.255.255 port 67
Jan 22 09:32:44 OnlyOffice dhclient[92]: DHCPACK of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:44 OnlyOffice ifup[75]: DHCPACK of 192.168.0.45 from 192.168.0.254
Jan 22 09:32:45 OnlyOffice dhclient[92]: bound to 192.168.0.45 -- renewal in 17537 seconds.
Jan 22 09:32:45 OnlyOffice ifup[75]: bound to 192.168.0.45 -- renewal in 17537 seconds.
Jan 22 09:32:46 OnlyOffice dhclient[172]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice ifup[75]: All rights reserved.
Jan 22 09:32:46 OnlyOffice ifup[75]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice dhclient[172]: All rights reserved.
Jan 22 09:32:46 OnlyOffice dhclient[172]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]:
Jan 22 09:32:46 OnlyOffice dhclient[172]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: PRC: Soliciting for leases (INIT).
Jan 22 09:32:46 OnlyOffice dhclient[172]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Forming Solicit, 0 ms elapsed.
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:46 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Forming Solicit, 1030 ms elapsed.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:47 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Forming Solicit, 3050 ms elapsed.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:49 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Forming Solicit, 6910 ms elapsed.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 7580ms.
Jan 22 09:32:46 OnlyOffice dhclient[172]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Internet Systems Consortium DHCP Client 4.4.1
Jan 22 09:32:46 OnlyOffice ifup[75]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice ifup[75]: All rights reserved.
Jan 22 09:32:46 OnlyOffice ifup[75]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]: Copyright 2004-2018 Internet Systems Consortium.
Jan 22 09:32:46 OnlyOffice dhclient[172]: All rights reserved.
Jan 22 09:32:46 OnlyOffice dhclient[172]: For info, please visit https://www.isc.org/software/dhcp/
Jan 22 09:32:46 OnlyOffice dhclient[172]:
Jan 22 09:32:46 OnlyOffice dhclient[172]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Listening on Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: PRC: Soliciting for leases (INIT).
Jan 22 09:32:46 OnlyOffice dhclient[172]: Sending on   Socket/eth0
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Forming Solicit, 0 ms elapsed.
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:46 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:46 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 1030ms.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Forming Solicit, 1030 ms elapsed.
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:47 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:47 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 2020ms.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Forming Solicit, 3050 ms elapsed.
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:49 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:49 OnlyOffice dhclient[172]: XMT: Solicit on eth0, interval 3860ms.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Forming Solicit, 6910 ms elapsed.
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  X-- IA_NA 2f:9b:e8:83
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request renew in  +3600
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT:  | X-- Request rebind in +5400
Jan 22 09:32:53 OnlyOffice ifup[75]: XMT: Solicit on eth0, interval 7580ms.

Still, ip a gives the right ip address even if networking did not start, and i can ping the CT. I guess the problem could be solve by assigning a static ip address instead of doing it via dhcp ?

Thanks a lot for your time !
Click to expand...
From the previous output it seems that your container requested an IPv6 address via DHCP. So maybe your DHCP server only provides IPv4? This could mean simply setting IPv4 to DHCP and IPv6 to static could solve the problem.
 
Chris said:
From the previous output it seems that your container requested an IPv6 address via DHCP. So maybe your DHCP server only provides IPv4? This could mean simply setting IPv4 to DHCP and IPv6 to static could solve the problem.
Click to expand...

Exactly, i hadn't enable what my ISP call "DHCPv6", i did it and everything works just fine. This was kind of a stupid problem, but now i know.

Last question : if i enable "static" in the ipv6 container config and leave the box blank, will it ask for an ipv6 or not ?

Thanks a lot for all your knowledge, i learnt a lot about networking and container this week !
 
technics said:
Exactly, i hadn't enable what my ISP call "DHCPv6", i did it and everything works just fine. This was kind of a stupid problem, but now i know.

Last question : if i enable "static" in the ipv6 container config and leave the box blank, will it ask for an ipv6 or not ?

Thanks a lot for all your knowledge, i learnt a lot about networking and container this week !
Click to expand...
With static and leaving the field blank you will simply not set a ipv6 address. Then you will not get an ipv6 address via DHCP.
Glad it works!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back