Upgrading OS (centos 6 =>7)

[rhassing]

Hello,

What would be the best way to do an operating system upgrade?

I thought it would be best to install a second instance and add it to the cluster, let it sync en tear down the first instance.

If I do so, I get a license warning and I'm violating the license.

Would it also be possible to install a new instance en move the vmdk file which contains /usr/local/nagioslogserver/elasticsearch/data and attach it to the new installed node and mount it?

Best regards,
Rob Hassing

[ssax]

I talked with jmanley on this and he said he's going to have someone reach out to you.

[ssax]

Do you have snapshots being taken of your data?

You could just follow this on a new system:

https://assets.nagios.com/downloads/nag ... Server.pdf

Do you have a custom VMDK layout or did you just deploy our OVA?

Did you change the ES data directory location?

I think technically if you install LS on a new VM, system backup the old, restore to the new, then stop the elasticsearch service on the new one, copy the data over (or mount up the vmdk and copy the data over, or mount just the data directory where it should be mounted), then startup the service and it should work.

I can lab it up and give it a try.

[rhassing]

I could try that as well.

I will make the snapshot.

The VMDK is ova deployed, with an extra disk for data (1.5TB)

The directory is not changed, but it's on an other volume (second disk, so other vmdk).

[ssax]

Awesome, I was hoping the data had it's own disk, I'm labbing this up and will send an update shortly.

[ssax]

What is the output of these commands on the current system:

Code: Select all

fdisk -l
df -Th
pvdisplay
vgdisplay
lvdisplay
mount

[rhassing]

Code: Select all

[root@localhost ~]# fdisk -l

Disk /dev/sda: 107.4 GB, 107374182400 bytes
4 heads, 32 sectors/track, 1638400 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004aeaf

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1     1638400   104857584   83  Linux

Disk /dev/sdb: 1649.3 GB, 1649267441664 bytes
255 heads, 63 sectors/track, 200512 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9c3a597f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      200513  1610612704+  83  Linux
[root@localhost ~]# df -Th
Filesystem     Type      Size  Used Avail Use% Mounted on
rootfs         rootfs     99G  4,0G   94G   5% /
devtmpfs       devtmpfs   12G  156K   12G   1% /dev
tmpfs          tmpfs      12G     0   12G   0% /dev/shm
/dev/sda1      ext4       99G  4,0G   94G   5% /
/dev/sdb1      ext4      1,5T  1,3T  166G  89% /usr/local/nagioslogserver/elasticsearch/data
[root@localhost ~]# pvdisplay
-bash: pvdisplay: command not found
[root@localhost ~]# mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=12070040k,nr_inodes=3017510,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
/dev/sda1 on / type ext4 (rw,noatime,barrier=1,data=ordered)
/proc/bus/usb on /proc/bus/usb type usbfs (rw,relatime)
/dev/sdb1 on /usr/local/nagioslogserver/elasticsearch/data type ext4 (rw,noatime,barrier=1,data=ordered)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
[root@localhost ~]# 

There no use of lvm

[rhassing]

The second node is added 10 hours ago.
Currently it's synchronizing data and 353GB out of 1.4TB is synchronized.

[ssax]

Ok, I would stick with that as it's a lot more complex to try to get everything synced back up manually.

[rhassing]

The new server is up and running, all data is synchronized.

I shut down the old server and changed the ip address on the new server, to take over functionality of the old server.

The logdata is collected, but I have 1 problem. Some of my logged data doesn't show in the dashboard. As if it doesn't exist. But the counters in the unique host overview are increasing. I've tested with tcpdump and I see the data coming in on the logserver.

Another issue is, I cannot write the configuration. When I click apply configuration I get the following error:
"The instance is likely offline, please check and try again"