I see an odd issue with Data Protector 24.4 on SLES 15 SP6 (x86_64):
A backup showed IPC connection errors, so I inspected the client that had been booted after a kernel update yesterday:
× omni.socket - DATA-PROTECTOR-INET
Loaded: loaded (/usr/lib/systemd/system/omni.socket; disabled; preset: disabled)
Active: failed (Result: resources)
Listen: 172.20.2.24:5565 (Stream)
Accepted: 0; Connected: 0;
CPU: 1ms
Jan 23 17:32:23 localhost (sd-listen)[796]: omni.socket: Failed to create listening socket (172.20.2.24:5565): Cannot assign requested address
Jan 23 17:32:23 localhost systemd[1]: omni.socket: Failed to receive listening socket (172.20.2.24:5565): Input/output error
Jan 23 17:32:23 localhost systemd[1]: omni.socket: Failed to listen on sockets: Input/output error
Jan 23 17:32:23 localhost systemd[1]: omni.socket: Failed with result 'resources'.
Jan 23 17:32:23 localhost systemd[1]: Failed to listen on DATA-PROTECTOR-INET.
When I tried to inspect the omni.service unit, I could not find it. When I tried to find out whether this had been delivered by RPm or not, it even gets more strange:
I found a /usr/lib/systemd/system/omni.socket, but that is not part of any RPM (says "rpm -qf /usr/lib/systemd/system/omni.socket").
So I removed all the RPMs and re-installed the client.
The client installation log claimed that every component installed sucessfully (!), but the client could not be imported.
When checking the client after that, I see that there still is no omni.servcie unit, and no process is listening on the omni socket 5565/tcp.
Here are the essential logs from that installation:
Jan 24 08:07:52 pc [RPM][9533]: Transaction ID 67933c48 started
Jan 24 08:07:55 pc [RPM][9533]: install OB2-CORE-24.4-1.x86_64: success
Jan 24 08:07:55 pc [RPM][9533]: install OB2-CORE-24.4-1.x86_64: success
Jan 24 08:07:55 pc [RPM][9533]: Transaction ID 67933c48 finished: 0
Jan 24 08:09:01 pc [RPM][10111]: Transaction ID 67933c8d started
Jan 24 08:09:08 pc [RPM][10111]: install OB2-TS-CORE-24.4-1.x86_64: success
Jan 24 08:09:08 pc [RPM][10111]: install OB2-TS-CORE-24.4-1.x86_64: success
Jan 24 08:09:08 pc [RPM][10111]: Transaction ID 67933c8d finished: 0
Jan 24 08:09:12 pc [RPM][10626]: Transaction ID 67933c98 started
Jan 24 08:09:13 pc [RPM][10626]: install OB2-CMNUTILS-24.4-1.x86_64: success
Jan 24 08:09:13 pc [RPM][10626]: install OB2-CMNUTILS-24.4-1.x86_64: success
Jan 24 08:09:13 pc [RPM][10626]: Transaction ID 67933c98 finished: 0
Jan 24 08:09:17 pc [RPM][10916]: Transaction ID 67933c9d started
Jan 24 08:09:18 pc [RPM][10916]: install OB2-DA-24.4-1.x86_64: success
Jan 24 08:09:18 pc [RPM][10916]: install OB2-DA-24.4-1.x86_64: success
Jan 24 08:09:18 pc [RPM][10916]: Transaction ID 67933c9d finished: 0
Jan 24 08:09:23 pc [RPM][11244]: Transaction ID 67933ca3 started
Jan 24 08:09:26 pc [RPM][11244]: install OB2-AUTODR-24.4-1.x86_64: success
Jan 24 08:09:26 pc [RPM][11244]: install OB2-AUTODR-24.4-1.x86_64: success
Jan 24 08:09:26 pc [RPM][11244]: Transaction ID 67933ca3 finished: 0
Note that every install is logged as successful twice, and the delays between package installs is significant (4-5 seconds). I could not see any kind of error message.
I also checked the package installation scripts using "rpm -q --scripts $(rpm -qa OB2\*)", but could not find where the socket file comes from.