24 Posts
0
4455
OMSA 9.4 dependencies in Fedora 32; Job for instsvcdrv.service failed because the control process exited with error code.
I know Fedora is not officially supported for OMSA but I've gotten it to work before. I've been able to manually run dnf localinstall on most of the RPMs
Here's where I'm at:
systemctl start instsvcdrv.service
Job for instsvcdrv.service failed because the control process exited with error code.
See "systemctl status instsvcdrv.service" and "journalctl -xe" for details.
systemd[1]: instsvcdrv.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The unit instsvcdrv.service has entered the 'failed' state with result 'exit-code'.
Aug 13 11:44:32 mandelbrot.dsm.fordham.edu systemd[1]: Failed to start Systems Management Device Drivers.
-- Subject: A start job for unit instsvcdrv.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- A start job for unit instsvcdrv.service has finished with a failure.
-- The job identifier is 23260 and the job result is failed.
Here are some dependency errors for Tomcat:
dnf localinstall srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64.rpm
Last metadata expiration check: 0:08:49 ago on Thu 13 Aug 2020 11:27:34 AM EDT.
Error:
Problem: conflicting requests
- nothing provides libdsupt.so.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
- nothing provides libomacs.so.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
- nothing provides libwsman_client.so.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
But one of the library's is there:
dnf install https://rpmfind.net/linux/fedora/linux/releases/32/Everything/x86_64/os/Packages/l/libwsman1-2.6.8-12.fc32.x86_64.rpm
Last metadata expiration check: 0:20:53 ago on Thu 13 Aug 2020 11:27:34 AM EDT.
libwsman1-2.6.8-12.fc32.x86_64.rpm 209 kB/s | 139 kB 00:00
Package libwsman1-2.6.8-12.fc32.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
What else can I try?
MassGroupText
24 Posts
0
September 18th, 2020 07:00
Success! I got it working on Fedora 32. I can't say for sure which step here ultimately got it working but I'll do my best to recall what I did.
-rwxrwSrwx 1 root root 64799781 Dec 24 2019 srvadmin-cm-9.4.0-20.02.00.x86_64.rpm
-rwxrwSrwx 1 root root 1061528 Dec 24 2019 srvadmin-deng-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 137356 Dec 24 2019 srvadmin-deng-snmp-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 1220064 Dec 24 2019 srvadmin-hapi-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 1892932 Dec 24 2019 srvadmin-idracadm7-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 4207024 Dec 24 2019 srvadmin-isvc-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 381840 Dec 24 2019 srvadmin-isvc-snmp-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 2885108 Dec 24 2019 srvadmin-itunnelprovider-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 39856124 Dec 24 2019 srvadmin-jre-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 273664 Dec 24 2019 srvadmin-marvellib-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 29660 Dec 24 2019 srvadmin-nvme-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 1055624 Dec 24 2019 srvadmin-omacore-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 4500504 Dec 24 2019 srvadmin-omacs-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 152576 Dec 24 2019 srvadmin-omaksmig-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 2441636 Dec 24 2019 srvadmin-omcommon-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 40160 Dec 24 2019 srvadmin-omilcore-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 2195872 Dec 24 2019 srvadmin-ominst-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 7496 Dec 24 2019 srvadmin-oslog-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 100320 Dec 24 2019 srvadmin-realssd-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 704500 Dec 24 2019 srvadmin-smcommon-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 7711516 Dec 24 2019 srvadmin-smweb-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 8077400 Dec 24 2019 srvadmin-storage-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 274932 Dec 24 2019 srvadmin-storage-cli-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 207960 Dec 24 2019 srvadmin-storage-snmp-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 517968 Dec 24 2019 srvadmin-storelib-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 53496 Dec 24 2019 srvadmin-storelib-sysfs-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 65452 Dec 24 2019 srvadmin-sysfsutils-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 19514812 Dec 24 2019 srvadmin-tomcat-9.4.0-3787.15943.el8.x86_64.rpm
-rwxrwSrwx 1 root root 64964 Dec 24 2019 srvadmin-xmlsup-9.4.0-3787.15943.el8.x86_64.rpm
libxml2
syscfg
net-snmp
dnf install https://rpmfind.net/linux/fedora/linux/releases/32/Everything/x86_64/os/Packages/l/libwsman1-2.6.8-12.fc32.x86_64.rpm
instsvcdrv: enabled
dsm_sa_datamgrd: enabled
dsm_sa_eventmgrd: enabled
dsm_sa_snmpd: enabled
dsm_om_connsvc: enabled
lrwxrwxrwx 1 root root 13 Dec 24 2019 /opt/dell/srvadmin/lib64/libdsupt.so -> libdsupt.so.1
lrwxrwxrwx 1 root root 21 Dec 24 2019 /opt/dell/srvadmin/lib64/libdsupt.so.1 -> libdsupt.so.1.100.147
-rw-r--r-- 1 root root 11160960 Dec 24 2019 /opt/dell/srvadmin/lib64/libdsupt.so.1.100.147
lrwxrwxrwx 1 root root 13 Dec 24 2019 /opt/dell/srvadmin/lib64/libomacs.so -> libomacs.so.1
lrwxrwxrwx 1 root root 21 Dec 24 2019 /opt/dell/srvadmin/lib64/libomacs.so.1 -> libomacs.so.1.100.147
-rw-r--r-- 1 root root 2521032 Dec 24 2019 /opt/dell/srvadmin/lib64/libomacs.so.1.100.147
This is the 2nd Fedora server I was able to get OMSA running. It took a few minutes after starting the service but as long you use https://127.0.0.1:1311 you should be able to avoid any firewalld issues.
OMSA working on Fedora 32
I was never able to get instsvcdrv.service to start correctly but that doesn't appear to hinder OMSA from starting as you can see from my screenshot. Hope this helps someone. @DellCaresPro @Dell -Charles R @DELL-Chris H
MassGroupText
24 Posts
0
August 13th, 2020 13:00
Well I tried to point out that I find one of them and the script still does not find it:
dnf install https://rpmfind.net/linux/fedora/linux/releases/32/Everything/x86_64/os/Packages/l/libwsman1-2.6.8-1...
Last metadata expiration check: 0:20:53 ago on Thu 13 Aug 2020 11:27:34 AM EDT.
libwsman1-2.6.8-12.fc32.x86_64.rpm 209 kB/s | 139 kB 00:00
Package libwsman1-2.6.8-12.fc32.x86_64 is already installed.
I can't find where these come from:
nothing provides libdsupt.so.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
- nothing provides libomacs.so.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
In /opt/dell/srvadmin/var/log/openmanage/dsm_om_connsvcdIO.log I see this:
13-Aug-2020 10:06:05.026 INFO [Thread-4] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["https-jsse-nio-1311"]
13-Aug-2020 10:06:05.095 INFO [Thread-4] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/opt/dell/srvadmin/lib64/openmanage/apache-tomcat/lib/catalina.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
13-Aug-2020 10:06:05.212 INFO [Thread-4] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["https-jsse-nio-1311"]
[Aug 13 10:06:05 2020] (143585) ModuleDetach: waiting for StartServer thread to finish...
[Aug 13 10:06:05 2020] (143585) ModuleDetach: exit
[Aug 13 10:06:05 2020] (143585) RunServer:worker process EXIT status(0)
[Aug 13 10:06:05 2020] (143585) RunServer exit with status(0)
[Aug 13 10:06:05 2020] (143584) RunServer:daemon process EXIT status(0)
/opt/dell/srvadmin/var/log/isvcdd.log has:
modprobe: FATAL: Module dell_rbu not found in directory /lib/modules/5.7.14-200.fc32.x86_64
MassGroupText
24 Posts
0
August 13th, 2020 13:00
BIOS & iDRAC version
yes and that has nothing to do with this.
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
0
August 13th, 2020 13:00
MassGroupText,
As you said it isn't supported so we will be limited on details.
From the log you provided, seen below,
Problem: conflicting requests
- nothing provides https://dell.to/31ODzDV.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
- nothing provides https://dell.to/2XX4goX.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
- nothing provides libwsman_client.so.1()(64bit) needed by srvadmin-tomcat-9.4.0-3787.15943.el7.x86_64
it appears that the Web Server isn't installed and is missing packages, which those dependencies will need to be installed. What I would suggest is to try using Yum to install the dependencies
Let me know what you see.
DELL-Charles R
Moderator
Moderator
•
3.7K Posts
0
August 13th, 2020 13:00
Hello MassGroupText,
I'll log your update for your case owner Chris has left for the day.
Could you see if your BIOS and DRAC firmware are at the latest version?
MassGroupText
24 Posts
0
August 16th, 2020 18:00
Reconstruction Completed8 drives now showing in the RAID10
OK looks like reconstruction finally completed. @Dell -Charles R @DELL-Chris H how do I get the OS (Fedora) to see the increased available disk space?
Also how can I get OMSA working?
Gparted not showing new disk space
DELL-Erman O
Moderator
Moderator
•
2.5K Posts
0
August 17th, 2020 00:00
Hello,
You can review these articles for how to run OMSA on Linux system? https://dell.to/31W8HS5 https://dell.to/34dCuYW But I'm not sure about Fedora(unsupported OS) I don't familiar this OS but Can you try to add new disk method please? https://dell.to/3kYSKDt
MassGroupText
24 Posts
0
August 20th, 2020 13:00
Can't start the service, keep getting these errors:
/opt/dell/srvadmin/sbin/srvadmin-services.sh start
Job for instsvcdrv.service failed because the control process exited with error code.
See "systemctl status instsvcdrv.service" and "journalctl -xe" for details.
systemctl status instsvcdrv.service --no-pager -l
● instsvcdrv.service - Systems Management Device Drivers
Loaded: loaded (/etc/systemd/system/instsvcdrv.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-08-20 16:30:24 EDT; 35s ago
Process: 1505970 ExecStart=/usr/libexec/instsvcdrv-helper start (code=exited, status=155)
CPU: 162ms
Aug 20 16:30:24 myserver systemd[1]: Starting Systems Management Device Drivers...
Aug 20 16:30:24 myserver systemd[1]: instsvcdrv.service: Control process exited, code=exited, status=155/n/a
Aug 20 16:30:24 myserver systemd[1]: instsvcdrv.service: Failed with result 'exit-code'.
Aug 20 16:30:24 myserver systemd[1]: Failed to start Systems Management Device Drivers.
[root@mandelbrot ~]# journalctl -xe
Aug 20 16:30:20 myserver sshd[1505867]: pam_unix(sshd:session): session opened for user root by (uid=0)
Aug 20 16:30:24 myserver systemd[1]: Starting Systems Management Device Drivers...
instsvcdrv.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit instsvcdrv.service has entered the 'failed' state with result 'exit-code'.
Aug 20 16:30:24 myserver systemd[1]: Failed to start Systems Management Device Drivers.
MassGroupText
24 Posts
0
August 20th, 2020 14:00
Already tried that:
ln -s /opt/dell/srvadmin/sbin/racadm-wrapper-idrac7 /bin/racadm
ln: failed to create symbolic link '/bin/racadm': File exists
I do have it working on another Fedora 32 system.
Dell-DylanJ
4 Operator
4 Operator
•
2.9K Posts
0
August 20th, 2020 14:00
With this being an unsupported OS, we can't promise it'll ever work, but looking into the error, I did find something worth looking at and trying. OMSA 9.3 had a similar problem listed as a known issue with a published workaround. I'd definitely give this a look, seems like they resolved it with a permission adjustment and a soft link. It was written with Ubuntu in mind, though, so there is going to some difference.
https://dell.to/3l3nDqe
The fix they list is as follows:
Let us know if this makes any progress.
MassGroupText
24 Posts
0
September 17th, 2020 11:00