Anonymous_User Absent Member.
Absent Member.
2517 views

Storage Manager 5 for OES 2018 is now available

We've put a version of Storage Manager 5 for OES 2018 into the patch
channel: http://download.novell.com/Download?buildid=GqIaxK3XPv4~

Please note that there are a few caveats related to installation of this
version on OES 2018, and that you'll want to carefully read the
installation instructions. If you have any issues, please let us know
immediately. Thank you for your patience!

-- NFMS Support Team
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Storage Manager 5 for OES 2018 is now available

On 28/02/2018 6:46 AM, NFMS Support Team wrote:
> We've put a version of Storage Manager 5 for OES 2018 into the patch
> channel: http://download.novell.com/Download?buildid=GqIaxK3XPv4~
>
> Please note that there are a few caveats related to installation of this
> version on OES 2018, and that you'll want to carefully read the
> installation instructions. If you have any issues, please let us know
> immediately. Thank you for your patience!
>
> -- NFMS Support Team


Thanks for the update. Unfortunately, I'm still having issues getting
the event monitor working on OES 2018. The engine and the agent work
fine, but the event monitor won't start.

I think I've done everything correctly. I installed with nodeps and I've
turned off fips as per the doco and restarted the server (noting that
the example seemed to be wrong, I used ndsconfig set
n4u.server.fips_tls=1 rather than ndsconfig set n4u.server.fips=1 which
gave an error about incorrect property.)

When I try to start nsmeventd it fails. The information is:

● nsmeventd.service - LSB: NSM Event Monitor
Loaded: loaded (/etc/init.d/nsmeventd; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2018-03-03 19:43:41
AEDT; 28s ago
Docs: man:systemd-sysv-generator(8)
Process: 3631 ExecStart=/etc/init.d/nsmeventd start (code=exited,
status=7)

Mar 03 19:43:41 storage-mgr systemd[1]: Starting LSB: NSM Event Monitor...
Mar 03 19:43:41 storage-mgr nsmeventd[3631]: Starting NSM Event Monitor
Mar 03 19:43:41 storage-mgr startproc[3640]: startproc: exit status of
parent of /opt/novell/storagemanager/event/bin/nsmeventd: 127
Mar 03 19:43:41 storage-mgr nsmeventd[3631]: ..failed
Mar 03 19:43:41 storage-mgr systemd[1]: nsmeventd.service: Control
process exited, code=exited status=7
Mar 03 19:43:41 storage-mgr systemd[1]: Failed to start LSB: NSM Event
Monitor.
Mar 03 19:43:41 storage-mgr systemd[1]: nsmeventd.service: Unit entered
failed state.
Mar 03 19:43:41 storage-mgr systemd[1]: nsmeventd.service: Failed with
result 'exit-code'.

There is nothing in /var/opt/novell/storagemanager/event

/var/log/messages showed nothing more than the stuff above.

Any thoughts?

Regards
Robert
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Storage Manager 5 for OES 2018 is now available

On 3/3/2018 3:46 AM, Robert Shera wrote:
> On 28/02/2018 6:46 AM, NFMS Support Team wrote:
>> We've put a version of Storage Manager 5 for OES 2018 into the patch
>> channel: http://download.novell.com/Download?buildid=GqIaxK3XPv4~
>>
>> Please note that there are a few caveats related to installation of
>> this version on OES 2018, and that you'll want to carefully read the
>> installation instructions. If you have any issues, please let us know
>> immediately. Thank you for your patience!
>>
>> -- NFMS Support Team

>
> Thanks for the update. Unfortunately, I'm still having issues getting
> the event monitor working on OES 2018. The engine and the agent work
> fine, but the event monitor won't start.
>
> I think I've done everything correctly. I installed with nodeps and I've
> turned off fips as per the doco and restarted the server (noting that
> the example seemed to be wrong, I used ndsconfig set
> n4u.server.fips_tls=1 rather than ndsconfig set n4u.server.fips=1 which
> gave an error about incorrect property.)
>
> When I try to start nsmeventd it fails. The information is:
>
> ● nsmeventd.service - LSB: NSM Event Monitor
>    Loaded: loaded (/etc/init.d/nsmeventd; bad; vendor preset: disabled)
>    Active: failed (Result: exit-code) since Sat 2018-03-03 19:43:41
> AEDT; 28s ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 3631 ExecStart=/etc/init.d/nsmeventd start (code=exited,
> status=7)
>
> Mar 03 19:43:41 storage-mgr systemd[1]: Starting LSB: NSM Event Monitor...
> Mar 03 19:43:41 storage-mgr nsmeventd[3631]: Starting NSM Event Monitor
> Mar 03 19:43:41 storage-mgr startproc[3640]: startproc:  exit status of
> parent of /opt/novell/storagemanager/event/bin/nsmeventd: 127
> Mar 03 19:43:41 storage-mgr nsmeventd[3631]: ..failed
> Mar 03 19:43:41 storage-mgr systemd[1]: nsmeventd.service: Control
> process exited, code=exited status=7
> Mar 03 19:43:41 storage-mgr systemd[1]: Failed to start LSB: NSM Event
> Monitor.
> Mar 03 19:43:41 storage-mgr systemd[1]: nsmeventd.service: Unit entered
> failed state.
> Mar 03 19:43:41 storage-mgr systemd[1]: nsmeventd.service: Failed with
> result 'exit-code'.
>
> There is nothing in /var/opt/novell/storagemanager/event
>
> /var/log/messages showed nothing more than the stuff above.
>
> Any thoughts?
>
> Regards
> Robert


Robert,

Would you mind reaching out to us at storagemanager@novell.com so we can
look at your logs, etc. directly? Thanks.

-- NFMS Support Team
0 Likes
rshera Absent Member.
Absent Member.

Re: Storage Manager 5 for OES 2018 is now available

Thanks - shall do
Robert
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.