Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Anonymous_User Absent Member.
Absent Member.
1685 views

Ifolder 3 on OES1 stopped working - no obvious reason. Where do Istart?

OES/Linux SP1 iFolder 3.

Noticed that iFolder3 clients were unable to login and/or sync.
No apparent reason, no changes made at either server or client.

Restarted the server on general principles. No effect.

Attempts to connect to iFolder3 Administration via iMangler 2.5 give this
result when trying to authenticate. Where/What do I look at to try and
figure
this out?


AxisFault faultCode: {http://xml.apache.org/axis/}HTTP faultSubcode:
faultString: (500)Internal Server Error faultActor: faultNode: faultDetail:
{}:return code: 500 <html> <title>Error 500</title><body
bgcolor="white"><h1><font color="red">Server error in '/simias10'
application</font></h1><hr> <h2><font color="maroon"><i>The request timed
out.</i></font></h2> <b>Description: </b>Error processing request. <p>
<b>Error Message: </b>HTTP 500. The request timed out. <p> <hr> </body>
</html> <!-- System.Web.HttpException: The request timed out. -->
{http://xml.apache.org/axis/}HttpErrorCode:500 (500)Internal Server Error at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:732
) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:
32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at
org.apache.axis.client.Call.invokeEngine(Call.java:2765) at
org.apache.axis.client.Call.invoke(Call.java:2748) at
org.apache.axis.client.Call.invoke(Call.java:2424) at
org.apache.axis.client.Call.invoke(Call.java:2347) at
org.apache.axis.client.Call.invoke(Call.java:1804) at
com.novell.ifolder.web.IFolderEnterpriseSoapStub.getSystem(IFolderEnterprise
SoapStub.java:679) at
com.novell.ifolder.plugins.ConnectTask.connectToHost(ConnectTask.java:115)
at com.novell.ifolder.plugins.ConnectTask.connected(ConnectTask.java:210) at
com.novell.ifolder.plugins.SelectiFolderTask.execute(SelectiFolderTask.java:
46) at com.novell.emframe.dev.Task.execute(Task.java:461) at
com.novell.nps.gadgetManager.BaseGadgetInstance.processRequest(BaseGadgetIns
tance.java:842) at
com.novell.nps.gadgetManager.BaseGadgetInstance.handleAction(BaseGadgetInsta
nce.java:2349) at
com.novell.nps.gadgetManager.GadgetManager.processInstanceRequest(GadgetMana
ger.java:1558) at
com.novell.nps.gadgetManager.GadgetManager.processServiceRequest(GadgetManag
er.java:1015) at
com.novell.nps.PortalServlet.handleFrameService(PortalServlet.java:503) at
com.novell.nps.PortalServlet.processRequest(PortalServlet.java:376) at
com.novell.nps.PortalServlet.doPost(PortalServlet.java:276) at
com.novell.nps.PortalServlet.doGet(PortalServlet.java:259) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:696) at
com.novell.emframe.fw.servlet.AuthenticatorServlet.service(AuthenticatorServ
let.java:248) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:809) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:200) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:146) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:209) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:144) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596) at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
..java:504) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:594) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133
) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596) at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:118) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:594) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116
) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:594) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:127) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152) at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300) at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374) at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:683) at java.lang.Thread.run(Thread.java:534)

TIA


--

Geoff Roberts
Computer Systems Manager
Saint Mark's College
Port Pirie, South Australia
geoffrobxATstmarksxdotppxdotcatholicxdoteduxdotaux
Remove the x's

Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Ifolder 3 on OES1 stopped working - no obvious reason. Where doIstart?

>>> On Tuesday, 12 February 2008 at 11:26 pm, in message
<47B1B8CB.A099.0007.0@stmarksx.ppx.catholicx.edux.aux>, Geoff
Roberts<geoffrobx@stmarksx.ppx.catholicx.edux.aux> wrote:
> OES/Linux SP1 iFolder 3.
>
> Noticed that iFolder3 clients were unable to login and/or sync.
> No apparent reason, no changes made at either server or client.
>
> Restarted the server on general principles. No effect.
>
> Attempts to connect to iFolder3 Administration via iMangler 2.5 give
> this result when trying to authenticate.


(screen full of meaningless java omitted)

Ok. This was apparently due to internally generated certificates
*expiring*.
How nice. It automatically breaks every couple of years apparently.
Fabulous concept.

I had a cert related issue on the NW65SP7 Groupwise box (Webaccess giving a
503) that caused me
to regenerate the certificate there (once I figured out why - much TID
search to figure it out)

I did not connect this to the ifolder3 issue right away as they are not on
the same server, obviously and the GW box is not the LDAP authenticator used
by the ifolder3 box.

TID 3388233 was somewhat useful, however it would have been more helpful
if:

1) Instead of saying the Simias.log is located in the the 'Simias Data Store
Location' it could
name the (default) location so I didn't have to do another search to find
it.

2) The GREP command produces no result on OES1/iFolder3.2.

/var/lib/wwwrun/.local/share/simias/Simias.config seems to exist so not sure
why.

In fact, Simias.config doesn't seem to exist anywhere on the server. OES2
maybe?
The TID says iFolder 3.x which should mean it was good for all versions of
iFolder3?

I found the names I needed in a file called simias-server-bootstrap.config
which is in \opt\novell\ifolder3\etc

Using this a a refererence and after importing the certificates from each
of the NW servers after they were rebooted, (Though it said the new certs
were 'not current',
whatever that means, as they had not before/not after times that were valid)
it imported them.
It was then possible to run the shell script and reconfigure ifolder3
without deleting the data.

TID 3248305 was somewhat useful, however the one certificate certmgr
displayed was not expired,
(at least not til 2015 which is sensible) however when I told it to fetch
via LDAP from each of
the NW servers it bought up an expired cert from all except the GW box I had
already sorted, so I
didn't add them.
So I went on with regenerating certs using pkidiag and rebooted them. After
that, certmgr added
them to the address store, however the -list command still only lists the
one (unexpired) cert it
always had, so the reason is not really obvious when you look at the list as
it would lead you to
believe all was well with the certificate(s).

A meaningful error message (like say, 'expired certificate') would be nice,
instead of a
screenful of meaningless to non programmers Java spaghetti from imangler
when it didn't let
me log in to ifolder3 admin.

An even better idea would be if internally generated certs never expired.

Frankly, a self issued cert should be good forever more, why does it have
to have an expiry date? And if it does, why isn't it 2050? It has taken
an
hour or two of wading through TIDs just to find out what the heck happened,
then regenerating
the certificates (didn't know I ever needed to) restarting servers, then
wading through more TIDS
and doing a reconfigure of ifolder3 to get it working again without loss of
data.
In short this nonsense cost me a day and I really didn't have the time for
it.

The mono cert seemed valid til 2015 but some other certs from the NW servers
seem
to be good for 2 or 3 years only, no idea why.

I really didn't have time to go through all this crap to fix something
because
it broke itself for no good reason. Can something be done so I don't have
to
go through this gymkhana in future? Or will this happen whenever certs
expire?
If I regenerate certs pre expiry, will the same result occur?

Oh, and I can't seem to install the ifolder3 plugin into imanager 2.7 on the
nw boxes.
I d/l ifolder3start.npm from novell and try to add it to the list, but it
never appears
in the NPMs available to install list. No error is produced, it just seems
to ignore it.
Some sensible reason? I am forced to use imanager 2.5 on the OES1/Linux
server to handle
it.

TIA






--

Geoff Roberts
Computer Systems Manager
Saint Mark's College
Port Pirie, South Australia
geoffrobxATstmarksxdotppxdotcatholicxdoteduxdotaux
Remove the x's

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.