Hi all, Just a heads-up that a router update early this morning screwed up a bunch of our virtual machines when their filesystems became inaccessible; and then on restarting, an old obsolete machine was substituted accidentally for our current Jenkins server, and the latter may have been lost completely. Don't ask how such a thing could happen. Anyway, it means we may not have a UVic Jenkins for a while (I'm leaving town for a conference tomorrow morning). The Oxford Jenkins, meanwhile, has run out of disk space. :-( This may mean that I end up doing something I was hoping to put off till the summer: writing the new Jenkins build script and testing it. But that's hard to do on a crappy old laptop that can't run VMs, so it'll have to wait till I get back next week. There's a chance Systems can salvage our Jenkins, though. Keep your fingers crossed. Cheers, Martin
Eeek! Sounds like an awful ordeal for you, Martin. I'll try not to ask. :-} Guess I'll bump getting local build of P5 working up a bit on my priority list. (But honestly, not likely to get to it until I get WWO fixed ...)
Just a heads-up that a router update early this morning screwed up a bunch of our virtual machines when their filesystems became inaccessible; and then on restarting, an old obsolete machine was substituted accidentally for our current Jenkins server, and the latter may have been lost completely. Don't ask how such a thing could happen.
Anyway, it means we may not have a UVic Jenkins for a while (I'm leaving town for a conference tomorrow morning). The Oxford Jenkins, meanwhile, has run out of disk space. :-(
This may mean that I end up doing something I was hoping to put off till the summer: writing the new Jenkins build script and testing it. But that's hard to do on a crappy old laptop that can't run VMs, so it'll have to wait till I get back next week.
There's a chance Systems can salvage our Jenkins, though. Keep your fingers crossed.
I knew that as soon as I warned everybody about this, a solution would emerge. It turns out that we did have the correct VM, but by a huge and horrible coincidence, the system updates I did when we first got it started up again included an update to Jenkins; and that update caused Jenkins to refuse to start with Java 1.6. As of today, it seems, 1.7 is required. Once it crossed my mind to check the Jenkins logs rather than the Apache logs and the system logs, I was able to see the problem and install Java 1.7 so Jinks would start. Not a good day so far. A trigger has also mysteriously stopped working on a MySQL database that has been trouble-free for months. Cheers, Martin On 15-05-05 12:39 PM, Syd Bauman wrote:
Eeek! Sounds like an awful ordeal for you, Martin. I'll try not to ask. :-}
Guess I'll bump getting local build of P5 working up a bit on my priority list. (But honestly, not likely to get to it until I get WWO fixed ...)
Just a heads-up that a router update early this morning screwed up a bunch of our virtual machines when their filesystems became inaccessible; and then on restarting, an old obsolete machine was substituted accidentally for our current Jenkins server, and the latter may have been lost completely. Don't ask how such a thing could happen.
Anyway, it means we may not have a UVic Jenkins for a while (I'm leaving town for a conference tomorrow morning). The Oxford Jenkins, meanwhile, has run out of disk space. :-(
This may mean that I end up doing something I was hoping to put off till the summer: writing the new Jenkins build script and testing it. But that's hard to do on a crappy old laptop that can't run VMs, so it'll have to wait till I get back next week.
There's a chance Systems can salvage our Jenkins, though. Keep your fingers crossed.
Meanwhile I've cleared some space on bits.nsms.ox.ac.uk:8080 and so the Oxford Jenkins appears to be working again. -James On 05/05/15 20:59, Martin Holmes wrote:
I knew that as soon as I warned everybody about this, a solution would emerge.
It turns out that we did have the correct VM, but by a huge and horrible coincidence, the system updates I did when we first got it started up again included an update to Jenkins; and that update caused Jenkins to refuse to start with Java 1.6. As of today, it seems, 1.7 is required. Once it crossed my mind to check the Jenkins logs rather than the Apache logs and the system logs, I was able to see the problem and install Java 1.7 so Jinks would start.
Not a good day so far. A trigger has also mysteriously stopped working on a MySQL database that has been trouble-free for months.
Cheers, Martin
On 15-05-05 12:39 PM, Syd Bauman wrote:
Eeek! Sounds like an awful ordeal for you, Martin. I'll try not to ask. :-}
Guess I'll bump getting local build of P5 working up a bit on my priority list. (But honestly, not likely to get to it until I get WWO fixed ...)
Just a heads-up that a router update early this morning screwed up a bunch of our virtual machines when their filesystems became inaccessible; and then on restarting, an old obsolete machine was substituted accidentally for our current Jenkins server, and the latter may have been lost completely. Don't ask how such a thing could happen.
Anyway, it means we may not have a UVic Jenkins for a while (I'm leaving town for a conference tomorrow morning). The Oxford Jenkins, meanwhile, has run out of disk space. :-(
This may mean that I end up doing something I was hoping to put off till the summer: writing the new Jenkins build script and testing it. But that's hard to do on a crappy old laptop that can't run VMs, so it'll have to wait till I get back next week.
There's a chance Systems can salvage our Jenkins, though. Keep your fingers crossed.
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
participants (3)
-
James Cummings -
Martin Holmes -
Syd Bauman