Attempting to open the Runners page in Admin I get a 500. Following steps on this issue, issue the following commands to resolve:
gitlab-rails console
> ApplicationSetting.first.delete
> ApplicationSetting.first
=> nill
Articles, notes and random thoughts on Software Development and Technology
Attempting to open the Runners page in Admin I get a 500. Following steps on this issue, issue the following commands to resolve:
gitlab-rails console
> ApplicationSetting.first.delete
> ApplicationSetting.first
=> nill
I’m not sure how all these issues occurred at the same time (or at least close enough together to cause issues), but here’s the story:
My Unifi network Controller app is on my 2008 Mac Pro. It has 2 GPUs, the original ATI Radeon HD 2600 XT that supports the Mac boot screen, and a Nvidia 750ti that is a PC card and so doesn’t support the boot screen. The 750ti is my normal gpu, the 2600XT is connected to a smaller monitor that I only use to access the Mac boot screen to switch between Windows 10 and MacOS.
At some point the 2600 XT just stopped working, it doesn’t have any video output from either of the monitor connectors. I’ve pulled it out and reseated it, but it’s just dead. While I was booted in MacOS a couple of days ago I changed the default boot disk to Windows 10 (mistake #1) to access some files from Windows. At that point I started to realize I’d lost a way of getting back into MacOS without a way to get to the boot screen.
Fast forward a few days, I started up my DL380 rack server which I use on a different IP range to the IP range for the rest of the house. I can get to the HP ILO on 10.0.0.2, but I can’t access ESXi which is normally on 10.0.0.3. I can’t get to the Unifi Controller (because it’s on the MacOS disk that I can’t boot) to see what IP that port on the hub has, and running arp -a or using Angry IP scanner is not showing any new IPs getting allocated via DHCP.
My stack of network hubs is under my desk, so getting underneath my desk I realized I’d plugged the DL380 in to the PoE input port and not a network port. While adding another PC to the hub a few weeks back I had moved that port from my 10.x.x.x network back to 192.168.1.x. So now plugging the DL380 network into any other free port on another hub means ESXI still thinks it’s on 10.0.0.3, but I can’t reach it as there’s no route via the port it’s now plugged into.
I need to switch back one of the ports on my Unifi switch back to the 10.x.x.x network, but:
Next steps:
I had a need to install and setup a Windows 8 VM. I have an original install DVD, so attached a USB DVD to my HP DL380 server and was planning on setting up a VM installed from the DVD. Some time later waiting for the ESXi console to be available, it was not responding and wondered what was going on. Started up the Remote Console option from iLO and found that the server had booted from the DVD. Yeah, that’s not gonna work 🙂
As part of reorganizing of my home network and homelab setup, I’m moving everything running on my DL380 G7 server from 19.168.1.0/24 addresses to it’s own network under 10.0.0.0/24
I thought I knew what new ip and gateway settings I needed in ILO on my server, so I changed them through the web interface, only to find out the gateway was incorrect and now I could no longer access ILO remotely on my network.
Luckily from the power on System settings, you can access the ILO config if you connect a monitor and keyboard and press F8 when prompted (see detailed step by step and timings of each option here). The F8 to access ILO settings is only on the screen for about 2 seconds, so if you miss it you’ll get the System Settings menu like this:
If you get into this Setup Utility menu then you need to exit and try again.
The F8 prompt you’re looking for appears only for about 2 seconds before the HP RAID array info appear – if you see this then you’ve already missed it and you’ll need to reboot and try again:
This is the ILO menu you should see after pressing F8 when prompted:
I had previously changed the gateway so a router on my 192.168.1.0 network that was unreachable from there. Changed, now we’re ready to reboot:
Success, ILO is now accessible on 10.0.0.2!