glassfish
  1. glassfish
  2. GLASSFISH-16310

Can't access Glassfish update url or ping pkg.glassfish.org on FreeBSD 8.2 x64

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: None
    • Component/s: update_center
    • Labels:
      None
    • Environment:

      FreeBSD 8.2 x64 (reproducible)

      Description

      This is a reproducible problem on x64 FreeBSD 8.2. Tested on different installs.

      – ping on FreeBSD 8.2 x64 -------------------------
      command: ping pkg.glassfish.org
      output: PING pkg.glassfish.org (192.9.164.62): 56 data bytes
      (stops there and keeps stuck)
      -----------------------------------------------

      – fetch on FreeBSD 8.2 x64 -------------------------
      command: fetch http://pkg.glassfish.org/v3/stable/catalog/0
      output:
      fetch: http://pkg.glassfish.org/v3/stable/catalog/0: Not Found
      -----------------------------------------------

      – curl on FreeBSD 8.2 x64 -------------------------
      curl -v http://pkg.glassfish.org/v3/stable/catalog/0

      • About to connect() to pkg.glassfish.org port 80 (#0)
      • Trying 192.9.164.62... connected
      • Connected to pkg.glassfish.org (192.9.164.62) port 80 (#0)
        > GET /v3/stable/catalog/0 HTTP/1.1
        > User-Agent: curl/7.21.3 (amd64-portbld-freebsd8.2) libcurl/7.21.3 OpenSSL/0.9.8q zlib/1.2.3
        > Host: pkg.glassfish.org
        > Accept: /
        >
        < HTTP/1.1 404 Not Found
        < Date: Sun, 03 Apr 2011 21:00:19 GMT
        < Server: Apache/2.2.6 (Unix)
        < Content-Length: 217
        < Content-Type: text/html; charset=iso-8859-1
        <
        <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
        <html><head>
        <title>404 Not Found</title>
        </head><body>
        <h1>Not Found</h1>
        <p>The requested URL /v3/stable/catalog/0 was not found on this server.</p>
        </body></html>
      • Connection #0 to host pkg.glassfish.org left intact
      • Closing connection #0

      – same curl command executed on another machine (Mac OS X) –
      curl -v http://pkg.glassfish.org/v3/stable/catalog/0

      • About to connect() to pkg.glassfish.org port 80 (#0)
      • Trying 192.9.164.62... connected
      • Connected to pkg.glassfish.org (192.9.164.62) port 80 (#0)
        > GET /v3/stable/catalog/0 HTTP/1.1
        > User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
        > Host: pkg.glassfish.org
        > Accept: /
        >
        < HTTP/1.1 200 OK
        < Date: Sun, 03 Apr 2011 21:03:04 GMT
        < Server: CherryPy/3.1.1
        < Content-Length: 21298
        < Last-Modified: 2011-02-28T08:40:29.460219
        < X-Catalog-Type: full
        < Content-Type: text/plain;charset=utf-8
        <
        S Last-Modified: 2011-02-28T08:40:29.460219
        S prefix: CRSV
        S npkgs: 412
        V pkg:/glassfish-verifier@3.0,0-74.1:20091202T094934Z
        V pkg:/glassfish-verifier@3.0,0-74.2:20091203T061648Z
        ...
        ...

      I'm also getting a 404 error when trying to open the update URL in a web-browser on FreeBSD.

      This is the only URL I know which doesn't work on FreeBSD (when it works on other OSs).

      It might as well be a FreeBSD bug...
      possible bugs:

      I'm filing this bug because I'm not 100% sure this is a FreeBSD bug. Maybe it's just a problem with the server configuration as this is the only URL/server I know that doesn't work when it should. Feel free to close this bug when you think this is a FreeBSD bug.

      The problem is that it's impossible to check for, download and install updates on FreeBSD using update center, updatetool or pkg due to this issue.

        Activity

        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Well, the cause is very simple: Update Center currently does not support FreeBSD platform which means that we don't have pkg and updatetool clients which would work on FreeBSD and we also do not have FreeBSD content repository set up on our update server. You are not able to access the URL since pkg.glassfish.org server performs redirection to correct repository URL based on client OS. In case of FreeBSD, there is no corresponding repository.

        I am marking this issue as improvement since the fix requires porting Update Center to additional platform. I'll check if there is corresponding improvement request already filed in updatecenter2 project and file one if necessary.

        In the meantime, I suppose we could change redirection logic to redirect FreeBSD requests to another platform repository, maybe Linux, but even in that case you could only be able to use Update Center implementation in GlassFish Admin console which uses Java API. That would help if you want to install additional components, but unfortunately won't help with updates since the only way to apply updates at this point is through standalone clients, i.e. pkg and updatetool.

        Show
        Snjezana Sevo-Zenzerovic added a comment - Well, the cause is very simple: Update Center currently does not support FreeBSD platform which means that we don't have pkg and updatetool clients which would work on FreeBSD and we also do not have FreeBSD content repository set up on our update server. You are not able to access the URL since pkg.glassfish.org server performs redirection to correct repository URL based on client OS. In case of FreeBSD, there is no corresponding repository. I am marking this issue as improvement since the fix requires porting Update Center to additional platform. I'll check if there is corresponding improvement request already filed in updatecenter2 project and file one if necessary. In the meantime, I suppose we could change redirection logic to redirect FreeBSD requests to another platform repository, maybe Linux, but even in that case you could only be able to use Update Center implementation in GlassFish Admin console which uses Java API. That would help if you want to install additional components, but unfortunately won't help with updates since the only way to apply updates at this point is through standalone clients, i.e. pkg and updatetool.
        Hide
        ref added a comment -

        I didn't expect the answer to be that "simple".

        I don't quite understand why pkg and updatetool wouldn't work on FreeBSD but to be honest I don't know how these two tools work at all. I just thought that they were java tools which simply update the installed files etc. If it would work this way there shouldn't be a difference between Linux, Mac OS and FreeBSD. But again, I don't know anything about these tools or how they work.

        I tried moving the whole glassfish folder to a Mac OS powered system, updated glassfish via updatetool/pkg and moved the files back to my FreeBSD system after updating. This worked. I don't understand how pkg and updatetool can't be platfrom independent or why a Mac OS/Linux installer wouldn't work on FreeBSD. What do these tools do that makes them not work properly on FreeBSD? (I don't expect you to answer this one but would be happy to get an explanation)

        In the meantime I can use 'asupgrade' to install major updates (from 3.0.1 to 3.1 for example) which should work or simple copy the whole glassfish folder to another OS to update glassfish.

        Thanks for you quick reply.

        Show
        ref added a comment - I didn't expect the answer to be that "simple". I don't quite understand why pkg and updatetool wouldn't work on FreeBSD but to be honest I don't know how these two tools work at all. I just thought that they were java tools which simply update the installed files etc. If it would work this way there shouldn't be a difference between Linux, Mac OS and FreeBSD. But again, I don't know anything about these tools or how they work. I tried moving the whole glassfish folder to a Mac OS powered system, updated glassfish via updatetool/pkg and moved the files back to my FreeBSD system after updating. This worked. I don't understand how pkg and updatetool can't be platfrom independent or why a Mac OS/Linux installer wouldn't work on FreeBSD. What do these tools do that makes them not work properly on FreeBSD? (I don't expect you to answer this one but would be happy to get an explanation) In the meantime I can use 'asupgrade' to install major updates (from 3.0.1 to 3.1 for example) which should work or simple copy the whole glassfish folder to another OS to update glassfish. Thanks for you quick reply.
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        I can answer at least part of your question...

        pkg and updatetool clients are not Java based but python based and they include minimized private copy of python runtime for each supported platform. So, supporting these tools on FreeBSD requires some porting and packaging effort in updatecenter2 project. Project does deliver Java API for basic UC functions, but at this point feature gap between Java based API and full fledged pkg/updatetool clients is still significant enough that Java API cannot be used for GlassFish updates.

        As for GlassFish installer, things should be simpler since installer framework is for the most part Java based, but I believe that it would be necessary to extend current platform bindings to recognize FreeBSD platform and install relevant content.

        Show
        Snjezana Sevo-Zenzerovic added a comment - I can answer at least part of your question... pkg and updatetool clients are not Java based but python based and they include minimized private copy of python runtime for each supported platform. So, supporting these tools on FreeBSD requires some porting and packaging effort in updatecenter2 project. Project does deliver Java API for basic UC functions, but at this point feature gap between Java based API and full fledged pkg/updatetool clients is still significant enough that Java API cannot be used for GlassFish updates. As for GlassFish installer, things should be simpler since installer framework is for the most part Java based, but I believe that it would be necessary to extend current platform bindings to recognize FreeBSD platform and install relevant content.

          People

          • Assignee:
            Snjezana Sevo-Zenzerovic
            Reporter:
            ref
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: