Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jrtaylor

Pages: [1] 2
1
Manually deleting entries does not solve the problem. File /etc/netplan/netplan.yaml is created from information stored somewhere else and that is where it needs to be removed.

2
Where is this info stored so that I can remove the virtual interfaces???

3
Yes it is in /etc/netplan/netplan.yaml but I think it is also in the mysql db as I tried to add another interface and assign one of the old virt interfaces to it and it says it was a duplicate. Resaving the interfaces does not help either. If you added a gateway manually it also gets stuck.

Code: [Select]
cat /etc/netplan/netplan.yaml
network:
  version: 2
  renderer: NetworkManager
  ethernets:
    eth0:
      dhcp4: false
      dhcp6: false
      addresses:
        - x.x.x.x/29
      nameservers:
        search:
            - "xxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
      routes:
        - to: 'default'
          via: x.x.x.x
          metric: 1
          on-link: true
        - to: 10.254.254.0/24
          via: 192.168.183.243
    eth1:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.183.254/24
      nameservers:
        search:
            - "xxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth2:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.42.254/24
      nameservers:
        search:
            - "xxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth3:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.153.254/24
      nameservers:
        search:
            - "xxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth4:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.155.254/24
      nameservers:
        search:
            - "xxxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth5:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.55.254/24
      nameservers:
        search:
            - "xxxxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth6:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.156.254/24
      nameservers:
        search:
            - "xxxxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth0.eth01:
      dhcp4: false
      dhcp6: false
      match:
        name: eth0.eth01
      set-name: eth0.eth01
      addresses:
        - 10.1.10.254/24
#            label: "eth0:eth01"
    eth0.eth02:
      dhcp4: false
      dhcp6: false
      match:
        name: eth0.eth02
      set-name: eth0.eth02
      addresses:
        - 10.1.10.1/24
#            label: "eth0:eth02"
    eth1.eth11:
      dhcp4: false
      dhcp6: false
      match:
        name: eth1.eth11
      set-name: eth1.eth11
      addresses:
        - 192.168.183.1/24
#            label: "eth1:eth11"

ls -al /etc/netplan/netplan.yaml
-rw-r----- 1 root root 2244 May 16 10:42 /etc/netplan/netplan.yaml


4
From the change log.

Remove vifaces form and mark the feature as deprecated

Problem is the interfaces are not deleted and are left broken! Make sure to delete them before upgrading.

5
I upgraded a server from 7.0 to 8.0 that was using Virtual Interfaces. After upgrade the Virtual Interfaces that were set are gone but the web ui still thinks the IP's are assigned. Is 8 supposed to have the Virtual Interface option?

6
One big thing that I want to note here is that the IDS/IPS system seems to block some of the upgrade. After turning it off almost ALL my problems went away!!! The only thing I still see are these messages.

Code: [Select]
Apr  7 22:31:25 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  7 22:31:26 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  7 22:31:26 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  7 22:31:27 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  7 22:31:28 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  7 22:31:31 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.


7
Still trying to upgrade a system that was installed 6.0 and upgraded to 6.2.x with no problems. I cloned the system and have attempted to upgrade to 7. After a bit I reboot and get stuff like this in the logs.

Code: [Select]
Apr  1 15:32:10 mx1 systemd[1]: Reloading.
Apr  1 15:32:10 mx1 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
Apr  1 15:32:10 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  1 15:32:10 mx1 systemd[1]: /lib/systemd/system/dovecot.service:19: PIDFile= references a path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the unit file accordingly.
Apr  1 15:32:20 mx1 systemd[1]: Reloading.
Apr  1 15:32:20 mx1 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
Apr  1 15:32:20 mx1 systemd[1]: named.service: Wants dependency dropin /etc/systemd/system/named.service.wants/fix-744304.conf is not a symlink, ignoring.
Apr  1 15:32:20 mx1 systemd[1]: /lib/systemd/system/dovecot.service:19: PIDFile= references a path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the unit file accordingly.


8
Hi,
I have two machines with zentyal 6.2 and I have the offer on the web gui to upgrade to zentyal 7.0, however the process gets stuck on preparing. On both machines I have zentyal core 6.2.3, on web gui there is 6.2.8 suggestion (it redirects to doc page), but I cannot update it even via command line.
Any idea?
Thank you

You have to upgrade to 6.2.8 before attempting to upgrade to 7.0. Make sure you have a backup or snapshot before attempting an upgrade.

9
I tried that command and all I get is :

[0;32m - Checking the zentyal-core version...
 Your system is up to date

It does nothing clicking the button.
The documentation on this is very sparse.
Is there a reference to how to get from 6.2.4 to 6.2.8?

You need to upgrade your 6.2.x to 6.2.8 by using the web interface or command line.

web interface
Software Management--> Zentyal Components--> Update tab
Software Management--> System Updates

command line (this will update both zentyal and system at the same time)
apt update
apt upgrade

10
Removed failed source. Not sure where it came from. The upgrade still failed. I cannot upload the log file. This looks like the problem.

This seems to provide zentyal-ips.

Code: [Select]
apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]                                                               
Get:3 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]                                                                                   
Hit:4 http://packages.zentyal.org/zentyal 7.0 InRelease                                                                                                     
Get:5 http://ppa.launchpad.net/oisf/suricata-stable/ubuntu focal InRelease [17.5 kB]                           
Get:6 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]                     
Err:5 http://ppa.launchpad.net/oisf/suricata-stable/ubuntu focal InRelease                                                                                                                               
  Connection timed out [IP: 91.189.95.85 80]
Fetched 324 kB in 30s (10.6 kB/s)   
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://ppa.launchpad.net/oisf/suricata-stable/ubuntu/dists/focal/InRelease  Connection timed out [IP: 91.189.95.85 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

11
Hangs during upgrade.

Code: [Select]
*** Preparing for upgrade to Zentyal 7.0...
+ echo

+ prepareZentyalRepositories
+ wget -qO - keys.zentyal.org/zentyal-7.0-packages.asc
+ sudo apt-key add -
OK
+ '[' -f /etc/apt/sources.list.d/zentyal-archive.list ']'
+ '[' -f /var/lib/zentyal/.commercial-edition ']'
+ sed -ri '/zentyal(.)6.2/d' /etc/apt/sources.list
+ echo 'deb http://packages.zentyal.org/zentyal 7.0 main extra'
+ grep -qR http://ppa.launchpad.net/oisf/suricata-stable/ubuntu /etc/apt/sources.list /etc/apt/sources.list~ /etc/apt/sources.list.d
+ echo 'deb http://ppa.launchpad.net/oisf/suricata-stable/ubuntu focal main'
+ apt-key adv --keyserver keyserver.ubuntu.com --recv-keys D7F87B2966EB736F
Executing: /tmp/apt-key-gpghome.LfsjAz87zp/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys D7F87B2966EB736F

12
Just upgraded from 6.2.8 to 7.0 and the webadmin would not start because of the ssl problem. Ran these and the problem went away.

sudo rm -rf /var/lib/zentyal/conf/ssl
sudo /usr/share/zentyal/create-certificate /var/lib/zentyal/conf/ssl `hostname --fqdn`
sudo systemctl start zentyal.webadmin-nginx.service

Problem not fixed.

Ugdate:

I did have to roll back the upgrade. Lots of stuff did not update and the upgrade had a key error. I have seen this before with other 18.x to 20 upgrades.

13
wget http://archive.ubuntu.com/ubuntu/pool/main/a/apt/libapt-pkg5.0_1.2.29_amd64.deb
sudo dpkg --install --force-downgrade libapt-pkg5.0_1.2.29_amd64.deb

14
Go to Software Management -> Zentyal Components and update from there.

15
Installation and Upgrades / Re: Stuck Upgrading from 5.1.3 to 6.0
« on: December 05, 2018, 07:29:13 pm »
I had something like this happen when upgrading from 5.0 to 6.01. Do a "ps -ef" or "ps -aux" and find the stuck process. In my case zentyal-core package would not finish running "dpkg --configure -a" so I kill the last process in the chain and the upgrade started to finish. I did have to do this several times to get it to finish. After it said the upgrade was done I rebooted the server and ran "sudo dpkg --configure -a" to make sure all the zentyal packages finished.

Pages: [1] 2