Closed glassfishrobot closed 15 years ago
@glassfishrobot Commented tmueller said: As of Monday, June 29 @ 9:26 PT, this problem is not showing up again, at least for Solaris/x86.
The log files at http://javaweb.sfbay/java/re/glassfish/ips/apache_logs/glass-zn-pkg-colo2.sun.com show the 503 return codes. For example:
From access_log.2009-06-29-00_00_00: 84.14.231.14 - - [29/Jun/2009:00:58:10 -0700] "GET /v3/dev/mac/file/0/be86a8dd962083a273ca3800af37cf2cb63d6f8b HTTP/1.1" 503 323 "-" "pkg/449ee554fb1e (darwin i386; 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386; user)" "e95e9f92-fa66-4cd2-834e-fd3cef8e275f" "-"
From error_log.2009-06-29-00_00_00: [Mon Jun 29 00:58:10 2009] [error] (146)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:60002 failed
Note that the timestamps in these two log entries are at the same time. If you look through the access log, there is a 503 response at the same time as a Connection refused message in the error log.
So undoubtedly, these transient 503 responses are due to being unable to connect to the backend pkg.depotd process. We'll need to get access to the pkg.depotd logs to see why it refused the connection.
@glassfishrobot Commented janey said: According to Tom, this issue is a result of restarting the repos before restarting Apache server. Restarting the repos first causes the LB to not direct traffic to zones.
Also as Tom pointed out there is no need to restart the repos since it's causing transient failures.
Leave this bug open as we determine if restart is needed.
@glassfishrobot Commented janey said: reassign to myself
@glassfishrobot Commented bsnaresh said: It seems to happen even today. Has it yet been decided whether the server has to be still restarted?
@glassfishrobot Commented bsnaresh said: Increasing the priority since it re-appears every now and then. The pkg tool installation started failing back since yesterday.
@glassfishrobot Commented janey said: Thanks, Snjezana!
@glassfishrobot Commented @ssevozen said: Weekly repository restart is not happening anymore so marking as fixed.
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-8603
@glassfishrobot Commented Reported by bsnaresh
@glassfishrobot Commented Marked as fixed on Friday, September 18th 2009, 5:50:39 am
The pkg tool or update center installation process in a freshly downloaded GF v3 build aborts with the following reason:
bin/updatetool
The software needed for this command (updatetool) is not installed.
If you choose to install Update Tool, your system will be automatically configured to periodically check for software updates. If you would like to configure the tool to not check for updates, you can override the default behavior via the tool's Preferences facility.
When this tool interacts with package repositories, some system information such as your system's IP address and operating system type and version is sent to the repository server. For more information please see:
http://wiki.updatecenter.java.net/Wiki.jsp?page=UsageMetricsUC2
Once installation is complete you may re-run this command.
Would you like to install Update Tool now (y/n): y
Proxy: Using system proxy settings. Install image: /home/naresh/workspace/deleteme/glassfishv3 Installing pkg packages. Input/output error: Connection failed: 503: Service Temporarily Unavailable
Could not download application packages. This could be because:
the package server is down or otherwise inaccessible or it is generating invalid data. Please contact the provider of the package server.
I have seen this in Ubuntu and Solaris too. This is happening quiet frequently these days. I don't think this is an issue with GlassFish, but some issue with the "package server". (I have tried with a GlassFish bundle which worked without any issue 2 days back, but shows this problem today).
Environment
Operating System: All Platform: Linux
Affected Versions
[V3]