[MacPorts] #47976: Snow Leopard buildbot builder is offline since May 18
MacPorts
noreply at macports.org
Fri Jun 5 16:29:23 PDT 2015
#47976: Snow Leopard buildbot builder is offline since May 18
----------------------------+---------------------
Reporter: ryandesign@… | Owner: admin@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: server/hosting | Version:
Keywords: | Port:
----------------------------+---------------------
This was originally reported to the Mac OS Forge admin email address, but
some emails between Keith and myself may be getting lost, so I want to
report the issue here where we can hopefully track and resolve it
successfully.
-----
`Mon May 18 02:04:51 PDT 2015`: [https://build.macports.org/builders
/buildports-snowleopard-x86_64/builds/35778 Ports build 35778] (trying to
rebuild dmapd after r136473) failed with an exception because the builder
went offline.
`Mon May 18 16:53:38 PDT 2015`: The builder has not been attempting any
builds since the exception was noted. I
[https://lists.macosforge.org/mailman/private/macports-
mgr/2015-May/005895.html reported this to Mac OS Forge].
`Mon May 18 21:10:20 PDT 2015`: Keith restarted the server, after which
the builder resumed trying to do builds.
[https://build.macports.org/builders/buildports-snowleopard-
x86_64/builds/35779 Ports build 35779] failed because it
[https://build.macports.org/builders/buildports-snowleopard-
x86_64/builds/35779/steps/write%20portlist%20file/logs/stdio could not
write the portlist] because the SQLite registry database was corrupted.
All subsequent builds to date have failed for the same reason.
`Tue May 19 09:30:46 PDT 2015`:
[https://lists.macosforge.org/mailman/private/macports-
mgr/2015-May/005896.html Keith responded] that the server had been
displaying a dialog box asking to be restarted, and that he had restarted
it.
-----
`Tue May 19 17:14:44 PDT 2015`: [https://lists.macosforge.org/pipermail
/macports-dev/2015-May/030566.html Ben Gilbert reported the problem] on
macports-dev.
`Tue May 19 20:16:54 PDT 2015`: [https://lists.macosforge.org/pipermail
/macports-dev/2015-May/030567.html I responded to Ben] letting him know
the above, Cc'ing Mac OS Forge. I wondered if the server had run out of
disk space. I wondered if running a `port` command with `sudo`—such as
`sudo port installed`—would repair the SQLite database corruption; I asked
Keith to try it. I asked Keith to clarify the restart dialog box he had
seen.
`Thu May 21 14:53:36 PDT 2015`: [https://lists.macosforge.org/pipermail
/macports-dev/2015-May/030578.html I reminded Mac OS Forge], forwarding my
message from May 19. I added that SQLite can repair some corruption if it
has write access to the database, which it would with `sudo` but that
generating the port list happens without `sudo`.
-----
`Sat May 23 13:32:55 PDT 2015`: [https://lists.macosforge.org/pipermail
/macports-dev/2015-May/030594.html Dave Evans reported the problem] on
macports-dev.
`Sat May 23 15:58:24 PDT 2015`:
[https://lists.macosforge.org/mailman/private/macports-
mgr/2015-May/005913.html I reminded Mac OS Forge], forwarding my message
from May 21.
-----
`Wed May 27 23:03:22 PDT 2015`:
[https://lists.macosforge.org/mailman/private/macports-
mgr/2015-May/005919.html I reminded Mac OS Forge] in a new email.
`Thu May 28 13:56:04 PDT 2015`:
[https://lists.macosforge.org/mailman/private/macports-
mgr/2015-May/005922.html Keith asked if there was still a problem] after
restarting the server.
`Thu May 28 14:31:28 PDT 2015`:
[https://lists.macosforge.org/mailman/private/macports-
mgr/2015-May/005923.html I said yes, a problem still exists], forwarding
my message from May 23.
-----
At this time I still want to know:
* What was the nature of the dialog box the server was displaying about
needing a restart? Was it a kernel panic or some other situation?
* Did the server run out of disk space? If so, can we get 5-10GB
additional disk space?
* Does running `sudo port installed` fix the problem? If not, we need to
come up with another solution.
* Were my forwarded and Cc'd emails to Mac OS Forge perhaps not
delivered, or discarded by a spam filter? If so, can we fix this so that
communication to Mac OS Forge can occur unimpeded?
Thanks.
--
Ticket URL: <https://trac.macports.org/ticket/47976>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list