kevs-oc

Shut down the service, moved the existing /usr/local/bin/rportd file and /var/lib/rport folder to my home folder. I exploded the contents of the backup file the update script made and restored...

/usr/local/bin/rportd-0.6.0 --version returned "version 0.6.0" (I renamed the file to keep it as a reference) ldd rportd-0.6.0 linux-vdso.so.1 (0x00007ffca4545000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f29dd56b000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f29dd548000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6...

I rolled back to 0.5.0 and my old clients can connect however when I try to add a new client, it also gets the bad handshake error. Systemctl status shows...

And I take it back about the OS. I'm actually running on Ubuntu 20.04.3. Sorry about that. One more thing I noticed on the server side. When rportd starts, it...

The new client is on the same network as an old client that is able to connect. This is lab network I am testing these new devices on and there...

After upgrading none of the existing clients could connect. The clients were a mix of 0.5.0 and 0.6.0.

Before I try the upgrade again I would like to get back to where I was. I booted up some older devices that I had on the shelf that had...

I compared the rport.conf files from the working and non-working devices and found the server urls to be different. The newly installed clients are trying to reach my server using...

@otto404-114 I did that and was able to connect but got the client id in use error. The new conf file that comes down has a new param called use_system_id...

I double-checked my backup file and it does not contain a backup of the rportd.conf file. According to the upgrade script: `# Create a backup FOLDERS="/usr/local/bin/rportd /var/lib/rport /var/log/rport" throw_info "Creating...