damionmeier Absent Member.
Absent Member.
1404 views

gwia not starting libwv_core.so missing

Hi,

we have installed a testing system and migrated a GW 8 to GW 2014 system.

POA and MTA are fine.

However, the GWIA is not starting. When trying to start it manually, we get the error message:

./gwia: error while loading shared libraries: libwv_core.so: cannot open shared object file: No such file or directory

On a previous testing system we did not have this problem.

Where could we get the shared libraries?

Thanks for any help.

dm
Labels (1)
0 Likes
10 Replies
Micro Focus Expert
Micro Focus Expert

Re: gwia not starting libwv_core.so missing

Hi dm,

To start the agents manually you need to export the library path. Here's the command to do so:

export LD_LIBRARY_PATH=/opt/novell/groupwise/agents/lib

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
damionmeier Absent Member.
Absent Member.

Re: gwia not starting libwv_core.so missing

Hi Laura,

thanks for your quick answer.

I had exported the Library path ( found this in another thread here ), but it did not help.

Also, when i check in /opt/novell/groupwise/agents/lib the libwv_core.so file is not there. Also nowhere else on the system.

Unfortunately i do not have another functioning gw 2014 server to copy the files over, so I was hoping I can download from somewhere.

dm
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: gwia not starting libwv_core.so missing

Hi dm,

I would recommend running the install script again.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
damionmeier Absent Member.
Absent Member.

Re: gwia not starting libwv_core.so missing

Hi,

I did. 🙂

It tells me that everything necessary is already installed.

I then tried to install the openmotif-2.3.1-3.15.1.x86_64 RPM seperately, because it seems the libwv_core.so is part of that package. However, it also tells me everything is already installed

dm
0 Likes
Knowledge Partner
Knowledge Partner

Re: gwia not starting libwv_core.so missing

rpm options of --replacepkgs --force needed to push them through
alternatively an rpm browser might allow for file extract, but I haven't found one of those yet.
___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
damionmeier Absent Member.
Absent Member.

Re: gwia not starting libwv_core.so missing

Ok, I quickly installed a second groupwise server. Used the same SLES installation media and the same GW installation package.

I compared the /opt/novell/groupwise/agents/lib folders on both and realized that on the second groupwise server there were 132 more files in this directory than in the first.

Copied them over.

GWIA is starting.

But how can that be? Same installation package !!!! Same procedures used.
0 Likes
snielson1 Absent Member.
Absent Member.

Re: gwia not starting libwv_core.so missing

I'd be curious if the gw-oracle-outside-in rpm was installed on the server, which is where that file comes from. You can find that RPM in the GroupWise installer ../server/linux/x86_64/gw-oracle-outside-in-8.5.3-4.x86_64.rpm

Shane Nielson Kind of alright at doing stuff with the computer thing
0 Likes
damionmeier Absent Member.
Absent Member.

Re: gwia not starting libwv_core.so missing

on both servers, old and new, gw-oracle-outside-in-8.5.2-3 is installed.

both were installed from the same groupwise installation package using the install.sh script

one had about 350 files in the /opt/novell/groupwise/agents/lib directory, the other around 130

This is the reason why I sometimes wonder whether it was really a good idea to be in IT. 🙂


dm
Knowledge Partner
Knowledge Partner

Re: gwia not starting libwv_core.so missing

In article <damionmeier.87zjoo@no-mx.forums.microfocus.com>, Damionmeier
wrote:
> This is the reason why I sometimes wonder whether it was really a good
> idea to be in IT. 🙂


Well it can reduce costs of hair cuts by us pulling them out 😉

likely that one rpm didn't install properly and didn't error out
properly along the way. That is why a forced rewrite of just that rpm
likely would have put all those files where they are supposed to be.
You picked another way to do the same basic thing(more steps, but ones
you know already), so you are good to go now and thank you for posting
your success so that we can all learn from the experience.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
kev1nw
New Member.

Re: gwia not starting libwv_core.so missing

Be careful with this, if you intend to upgrade to Groupwise 18!

GW18 installs different versions of libcurl.so and libssl.so than we had on our OES 2015 SP1 servers.
With LD_LIBRARY_PATH set to the Groupwise versions, "yast online_update" will give you a segmentation fault.

We had this problem on our servers, after upgrading to GW18, and ended up raising a SR.

Regards
Kevin

On 13/11/2017 12:04, laurabuckley wrote:
>


> export LD_LIBRARY_PATH=/opt/novell/groupwise/agents/lib
>
> Cheers,
>



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.