Outage of All Servers - Update

PLANNED OUTAGE OVER
------------------------------------

The planned outage is over. We have a new service now. Another type of even higher level "cloud storage" service.

We now have vmain, mapping just about all the drives from everywhere, on folders. These are nicely arranged, and have their permissions nicely set according to what needs to be to keep people out, who don't belong. They are mapped there, and then reshared, via samba. So, you can map one drive, which maps them all. The reason we needed to do this, is mainly because of the NAS. It would only be something like 25 drive, if it weren't for that. With that, it's now around 50 drives (without actually counting). So you are getting a 50 in one savings!

--- Dennis Earl Smiley ---

Outage of All Servers

PLANNED OUTAGE
---------------------------

Until further notice, you will probably find ALL the servers out, and not working. As part of working on vmain's SMB consolidation service, we needed to back up all servers. This will mean there is an outage on all servers.


--- Dennis Earl Smiley ---

Outage of App Servers

We are just now posting here, but this was a planned outage. We are trying to add an SMB consolidation service on vmain. This requires some outages here and there. The first, outage, was the App servers. They are currently still down.

--- Dennis Earl Smiley ---

Outage of App Servers

The outage of app servers has been resolved. All the app servers now work. We re-imaged the servers on main2, and all is good. Hopefully, this won't happen again for awhile.

--- Dennis Earl Smiley ---

Services

Various services were modified. Please check out the new "Changes and Revisions" page, for more details. Or see our ad, here, for less technical information: http://smileynet001.ddns.net:81/~smileynet_inet/ads/smileynet_website.htm

--- Dennis Earl Smiley ---

Outage - More Specific

OK. So there is an outage of ALL app servers on main2. Looks like after the automatic restart, now they need to be re-imaged again... I guess I'll do that within the next 3 days or so.

--- Dennis Earl Smiley ---

Outage of Some Servers

There is an outage of some of the App servers. The one we have caught so far, is vsuselinux. We will work on this, as time allows.

--- Dennis Earl Smiley ---

Temporary Outage Caused by Router Changes

You may have noticed, at any point yesterday, and this afternoon, that many of the network services were down. Actually, most of them were working still. It's just that you couldn't use them, because the routers were being worked on.

Airprint functionality needed to be enabled. Otherwise, the exact design was working perfect. The only way we could do this, and get this working okay, was to collapse the 192.168.2.0 subnet into 192.168.1.0. For now, the third subnet (and even 4th), are working with only minor changes. DNS still works as expected. The changes there are transperant.

We tested and came up with that as the solution. It also, no longer requires pre-registration of MACs in order to connect to the guest network. However, you will still need the password. Depending on what you are doing, you will also still need an AUP signed and on file.

--- Dennis Earl Smiley ---

Windows Updates

There were Windows Updates to install. The two servers rebooted themselves to install the Windows Updates. main1 rebooted fine. main2 didn't reboot all the way. We had to flip the power off and back on. Then we had to wait for it to boot. It booted fine after that.

The outage is now over with. Everything works okay. All the servers are working okay.

--- Dennis Earl Smiley ---

vweb Online Again

I made a post to "History of the Network". It is repeated here, for convienence, since it applies here too.

Since there was a GRUB 17 error, I knew that Linux wouldn't work, and that GRUB didn't work. I couldn't access the rescue system either, because of that error. So I knew I had to fix it offline.

I used the Sys-Resc CD, which I'm always using, to boot the machine. I could confirm that the filesystem was damaged. So I ran fsck, to check and fix errors on the filesystem.

I "should" have ran it with the "-a" switch, but I didn't. I had to say, "yes", to all the errors, since I didn't use that switch.

Then it worked and I could see files on the system again. Before trying it out, I backed up the system, as I don't want to lose the websites, if at all possible. If there was no changes since I created the system, I just would have re-installed the standard pattern, but there were changes. So now, I have a backup image of the system.

Then, I tried the system, and it was indeed fixed. So now the system is fixed, and the server works again. And we got a backup out of the system too!

vweb is functioning again, and everything is okay.

--- Dennis Earl Smiley ---

There. You see it. vweb is functioning again. All the servers are functioning again.

--- Dennis Earl Smiley ---

Service Reliability Information

I have noticed that services are not always "as" reliable as I'd like them to be at this point. Mostly the servers. Sometimes they go out and need to be fixed.

The fact that they are not always as reliable as I'd like, has to do with the fact that there are 5 VMs, running on one host at the same time. This machine has 2GB of RAM, and supposedly, Windows 10 uses 1GB of RAM. So it's very slow at times, and needs to be rebooted sometimes, by pushing the button.

I apologize that I can't make it more reliable right now, but unfortunately, that costs money ($), that I don't have.

The best thing if I could do anything in the world, would be to use an Anstle Box (https://antsle.com/). Unfortunately, this is still way out of the budget. What the next best thing to do would be, is to have 2-3 laptops instead of desktop machines, that would be running the servers. They could be Windows 10, like this is. But that's outside of my budget too.

The last option, is to at least upgrade the two desktop towers, which would be either servers of the same physical size, or just more desktops. The focus would be the RAM for now. However, that's outside of the realm of what my budget will allow too, so I just have these for now.

They work, but will require more maintenance for now. Sorry for the outages. Because of imaging, it won't be a lot of work to fix. The issue, however, is simply the data. I will "hope", that I haven't lost any data, but it may be the case that I lost some data. The servers don't have backups working right now yet.

Sorry for this inconvienience. I will have it up and running as soon as I have the manpower (me) to do it.

--- Dennis Earl Smiley ---

vweb - Outage

There is an outage on vweb right now. vweb is having hard disk failure, giving a GRUB 17 error. I will try to recover the data as soon as I can. If it's impossible to recover the data, I may have lost some websites, and need to redo them. But they will be redone, and everything will be fixed. This should be being worked on in the next few days, maybe starting today or tomorrow. Please be patient.

--- Dennis Earl Smiley ---

main1 Update

main1 has been rebooted. All of the servers now work. It had to be fixed some too.

--- Dennis Earl Smiley ---

main1

There is an outage of all the servers on main1. main1 is being rebooted right now.

--- Dennis Earl Smiley ---

App Servers

All the app servers are functioning again.

--- Dennis Earl Smiley ---