getting 404 for adminui link after upgrade

book

Article ID: 192544

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER

Issue/Introduction

 

We're running an AdminUI and when we try to access it with a browser,
it gives return code 404 and looking at the files system, it seems
that the deployment of the AdminUI has failed :

  [[email protected] deployments]$ ll
  total 28
  drwxrwxr-x 4 smuser smuser 48 Jun 1 12:22 castylesr5.1.1.ear
  -rw-rw-r-- 1 smuser smuser 18 Jun 1 14:08 castylesr5.1.1.ear.deployed
  drwxrwxr-x 16 smuser smuser 4096 Jun 1 12:26 iam_siteminder.ear
  -rw-rw-r-- 1 smuser smuser 5948 Jun 1 14:08 iam_siteminder.ear.failed
  -rw-rw-r-- 1 smuser smuser 8869 Nov 20 2014 README.txt

How can we fix this ?

 

Cause

 

The file tomahawk-1.1.5.jar seems to be corrupted, which prevents the
deployment of the AdminUI application to continue and finalize
correctly :

  2020-06-02 09:13:29,739 INFO [org.jboss.as] (MSC service thread 1-3)
  JBAS015899: WildFly 8.2.0.Final "Tweek" starting

  [...]

  2020-06-02 09:13:31,097 INFO
  [org.jboss.as.server.deployment.scanner]
  (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed
  deployment iam_siteminder.ear

  2020-06-02 09:13:31,259 INFO
  [org.jboss.as.server.deployment.scanner]
  (DeploymentScanner-threads - 1) JBAS015003: Found castylesr5.1.1.ear
  in deployment directory. To trigger deployment create a file called
  castylesr5.1.1.ear.dodeploy

  2020-06-02 09:13:31,259 INFO
  [org.jboss.as.server.deployment.scanner]
  (DeploymentScanner-threads - 1) JBAS015003: Found iam_siteminder.ear
  in deployment directory. To trigger deployment create a file called
  iam_siteminder.ear.dodeploy

  2020-06-02 09:14:01,982 INFO [org.jboss.as.server.deployment] (MSC
  service thread 1-4) JBAS015876: Starting deployment of
  "iam_siteminder.ear" (runtime-name: "iam_siteminder.ear")

  [...]

  2020-06-02 09:17:03,666 ERROR [org.jboss.msc.service.fail] (MSC
  service thread 1-1) MSC000001: Failed to start service
  jboss.undertow.deployment.default-server.default-host./iam/siteminder:
  org.jboss.msc.service.StartException in service
  jboss.undertow.deployment.default-server.default-host./iam/siteminder:
  Failed to start service

   at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_212]
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_212]
   at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_212]

  Caused by: com.sun.jersey.core.spi.scanning.ScannerException: IO
  error scanning jar /WEB-INF/lib/tomahawk-1.1.5.jar

  Caused by: java.util.zip.ZipException: invalid entry CRC (expected
  0x980b62b9 but got 0x2b77b52d)

  2020-06-02 09:17:03,697 ERROR
  [org.jboss.as.controller.management-operation] (Controller Boot
  Thread) JBAS014613: Operation ("deploy") failed - address:
  ([("deployment" => "iam_siteminder.ear")]) - failure description: {

      "JBAS014671: Failed services" =>
      {"jboss.undertow.deployment.default-server.default-host./iam/siteminder"
      => "org.jboss.msc.service.StartException in service
      jboss.undertow.deployment.default-server.default-host./iam/siteminder:
      Failed to start service

      Caused by: com.sun.jersey.core.spi.scanning.ScannerException: IO
      error scanning jar /WEB-INF/lib/tomahawk-1.1.5.jar

      Caused by: java.util.zip.ZipException: invalid entry CRC
      (expected 0x980b62b9 but got 0x2b77b52d)"},

If you look at the cksum on the tomahawk file, it reports different
than the out of the box one :

  # find . -name "tomahawk-1.1.5.jar" -exec cksum {} \;

  490916480 2941159
  ./standalone/deployments/iam_siteminder.ear/user_console.war/WEB-INF/lib/tomahawk-1.1.5.jar

  490916480 2941159
  ./standalone/tmp/vfs/deployment/deployment4ee096348af7cfda/tomahawk-1.1.5.jar-e284a704dc68b15d/tomahawk-1.1.5.jar

On AdminUI 12.8SP3 on linux, you should find those 2, and the
following check sums, which means that you don't run the correct
tomahawk libraries :

    1453478146 2941159
  ./standalone/deployments/iam_siteminder.ear/user_console.war/WEB-INF/lib/tomahawk-1.1.5.jar

    1453478146 2941159
  ./standalone/tmp/vfs/deployment/deployment8d1b871270902591/tomahawk-1.1.5.jar-2430e1995b11b91d/tomahawk-1.1.5.jar

 

Environment

 

AdminUI 12.8SP3 on RedHat 7;

 

Resolution

 

Install again the AdminUI in order to get all the libraries correctly
installed.