Softaculous

Topic : Ubuntu 22.04

Posted By: wnic on February 9, 2023, 10:05 am

We have a new Ubuntu 22 Virtualizor server.
Ubuntu is new to us.
The command service virtnetwork restart results
that viifbr0 no longer works and is no longer visible.

Only
service virtnetwork stop
service virtnetwork start
brings viifbr0 back online.

When the server is rebooted, viifbr0 is not present.
All VPS are down and can not be started.

Again, only the following commands help

service virtnetwork stop
service virtnetwork start

and the manual start of the VPS.

Where is the fault and how can we fix this problem?
Why is service virtnetwork restart not working ?
Thank you.

Posted By: jevingala on February 9, 2023, 12:58 pm | Post: 1

Hi,

When the server is rebooted, viifbr0 is not present.
>> It should start automatically.

May I know what error do you see when you use : service virtnetwork status

Or you can create permanent bridge to avoid this issue :

https://www.virtualizor.com/docs/admin/kvm-bridge/#managing-bridge-on-ubuntu-18-04

-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/

Posted By: wnic on February 9, 2023, 1:21 pm | Post: 2

/etc/netplan# service virtnetwork restart
/etc/netplan# service virtnetwork status
● virtnetwork.service - Virtualizor Network Service
Loaded: loaded (/etc/systemd/system/virtnetwork.service; enabled; vendor preset: enabled)
Active: active (exited) since Thu 2023-02-09 14:02:52 CET; 3s ago
Process: 42957 ExecStart=/etc/init.d/virtnetwork start (code=exited, status=0/SUCCESS)
CPU: 35ms

Feb 09 14:02:51 servername systemd[1]: Starting Virtualizor Network Service...
Feb 09 14:02:52 servername virtnetwork[42958]: Error: No ip address found.
Feb 09 14:02:52 servername systemd[1]: Started Virtualizor Network Service.
The ip is not found !

/etc/netplan# service virtnetwork stop
/etc/netplan# service virtnetwork start
/etc/netplan# service virtnetwork status
● virtnetwork.service - Virtualizor Network Service Loaded: loaded (/etc/systemd/system/virtnetwork.service; enabled; vendor preset: enabled)
Active: active (exited) since Thu 2023-02-09 14:04:16 CET; 2s ago
Process: 43085 ExecStart=/etc/init.d/virtnetwork start (code=exited, status=0/SUCCESS)
CPU: 217ms

Feb 09 14:03:44 servername systemd[1]: Starting Virtualizor Network Service...
Feb 09 14:03:44 servername virtnetwork[43086]: Bringing up viifbr0 - OK
Feb 09 14:03:54 servername virtnetwork[43086]: Waiting for 10 seconds...1...2...3...4...5...6...7...8...9...10
Feb 09 14:04:13 servername virtnetwork[43086]: Checking network connectivity through ping to 4.2.2.1
Feb 09 14:04:16 servername virtnetwork[43086]: Internet connectivity check successful viifbr0 - OK
Feb 09 14:04:16 servername systemd[1]: Started Virtualizor Network Service.

The ip is found and is working fine !

Posted By: jevingala on February 9, 2023, 2:04 pm | Post: 3

Hi,

No need to run virtnetwork restart command after rebooting the server.

Can you share what status does it shows on rebooting the server ?

-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/

Posted By: wnic on February 9, 2023, 2:28 pm | Post: 4

Server rebooting. IP not found problem persists:
# service virtnetwork status
● virtnetwork.service - Virtualizor Network Service Loaded: loaded (/etc/systemd/system/virtnetwork.service; enabled; vendor p>
Active: active (exited) since Thu 2023-02-09 15:21:27 CET; 2min 26s ago
Process: 1644 ExecStart=/etc/init.d/virtnetwork start (code=exited, status=>
CPU: 35ms
Feb 09 15:21:27 servername systemd[1]: Starting Virtualizor Network S>
Feb 09 15:21:27 servername virtnetwork[1645]: Error: No ip address fo>
Feb 09 15:21:27 servername systemd[1]: Started Virtualizor Network Se>
lines 1-9/9 (END)...skipping...
● virtnetwork.service - Virtualizor Network Service
Loaded: loaded (/etc/systemd/system/virtnetwork.service; enabled; vendor preset: enabled)
Active: active (exited) since Thu 2023-02-09 15:21:27 CET; 2min 26s ago
Process: 1644 ExecStart=/etc/init.d/virtnetwork start (code=exited, status=0/SUCCESS)
CPU: 35ms

Feb 09 15:21:27 servername systemd[1]: Starting Virtualizor Network Service...
Feb 09 15:21:27 servername virtnetwork[1645]: Error: No ip address found.
Feb 09 15:21:27 servername systemd[1]: Started Virtualizor Network Service.

Posted By: wnic on February 10, 2023, 9:45 am | Post: 5

It seems to be an IPv6 problem. IPv6 remains registered on eno1 which is wrong.

Therefore a permanent bridge is necessary.

The error message

Feb 09 21:42:35 hostname virtnetwork[971]: Error: No ip address found.

exists but does not matter anymore.

Posted By: wnic on February 10, 2023, 10:01 am | Post: 6

The next problem is:
** (generate:54521): WARNING **: 10:43:02.788: `gateway4` has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.

You should update your bridge documentation.

Posted By: jevingala on February 10, 2023, 12:18 pm | Post: 7

Hi,

I will ask my team to check and handle ipv6 for virtnetwork service too.

Regarding ' No IP Address found ' error, if you can open a ticket so that we can check virtnetwork issue :

https://softaculous.deskuss.com/open.php?topicId=2

For Gateway4, we will check and update the documentation.

-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/