SSDC Registry Status
Forum rules
All posts to this forum must abide by the posting rules. Continued posting to any VAMWorld forum constitutes acceptance of the rules.
All posts to this forum must abide by the posting rules. Continued posting to any VAMWorld forum constitutes acceptance of the rules.
Re: SSDC Registry Status
No good for SSDC . No log in ..
Even tried old user name and password .
Even tried old user name and password .
Re: SSDC Registry Status
The rehosted server died. It overheated and didn't restart because the keyboard wasn't found. It got inadvertently disconnected when I deinstalled the original server. PS2 connector -- that's how old the system is. I plugged the keyboard back in and restarted. Should run for now. But I will see if I can find a halfway suitable desktop box at Costco after my dental cleaning in a bit. We need something to get through the next weeks at least.
- ServerDown2.jpg (92.31 KiB) Viewed 1197 times
Re: SSDC Registry Status
Tried to log in just now. After a lengthy wait I got an "Unable To Connect" message.
When in doubt... don't.
-
LateDateMorganGuy
- Posts: 1024
- Joined: Tue Jun 05, 2018 2:11 am
Re: SSDC Registry Status
When I read between the lines of what John is saying, forget about using the Registry for a few weeks. His words also seem to imply that anything you input may be lost once the server issue is resolved. But maybe I am wrong about that.
Re: SSDC Registry Status
Here is the deal.
The registry server died and I could not recover it easily yet.
There was a backup of the code area on 27 Sept, before I left for the last Long Beach Show. Only things missing are the three months of uploaded images after that date and a few very minor bug fix code changes.
The database was current, as it is backed up at 1:05am daily and no activity occurred from that backup until the system failure.
I restored the code (takes over 6 hours) and the database (nearly instantly) onto some very old (Windows 95 days) hardware to get back up for a while. But it is not appropriate.
Went out this afternoon and bought a desktop system with suitable specs at Costco.
Removed the Windows SSD and installed a pair of 2TB SSDs. Will see if I can somehow integrate another pair. I do like to have the OS and the data on separate physical volumes. But it is not entirely necessary. The pair being used is set up as a mirror.
Installed the latest Ubuntu Server OS and a few extra packages.
I am network copying the code over to install. Again, that will require about 6 hours to complete.
When that is done, I will identify necessary packages the Registry uses and install them. Then configure the web server, firewall, etc.
The current limping along rehosted system (on coxe.net) will be stopped; the database backed up; and the database transferred to the new server. The address will be changed; physically install it in the data room (my old wine cellar); and bring it up.
I will see if I can recover the lost uploaded images from the original server disks. Probably not though because they were on a striped RAID.
Since this system (at the original site address) will not have had significant stress testing or burn-in before I leave for FUN, I will also leave the coxe.net one running. That is in case the new one fails for any reason. But the coxe.net server should be considered as for read-only. Any set changes, registrations, ... there after the new one comes up will not be retained. But people will be able to see the price guide, their inventories and sets, pops, etc. I know some will need that at the show.
All that said, I encourage everyone to download their inventories from the current running server as CSV (comma separated values) spreadsheets. It is always a good idea to maintain a local copy.
So, the hope is to have a running registry.ssdcvams.com server tonight or tomorrow.
The registry server died and I could not recover it easily yet.
There was a backup of the code area on 27 Sept, before I left for the last Long Beach Show. Only things missing are the three months of uploaded images after that date and a few very minor bug fix code changes.
The database was current, as it is backed up at 1:05am daily and no activity occurred from that backup until the system failure.
I restored the code (takes over 6 hours) and the database (nearly instantly) onto some very old (Windows 95 days) hardware to get back up for a while. But it is not appropriate.
Went out this afternoon and bought a desktop system with suitable specs at Costco.
Removed the Windows SSD and installed a pair of 2TB SSDs. Will see if I can somehow integrate another pair. I do like to have the OS and the data on separate physical volumes. But it is not entirely necessary. The pair being used is set up as a mirror.
Installed the latest Ubuntu Server OS and a few extra packages.
I am network copying the code over to install. Again, that will require about 6 hours to complete.
When that is done, I will identify necessary packages the Registry uses and install them. Then configure the web server, firewall, etc.
The current limping along rehosted system (on coxe.net) will be stopped; the database backed up; and the database transferred to the new server. The address will be changed; physically install it in the data room (my old wine cellar); and bring it up.
I will see if I can recover the lost uploaded images from the original server disks. Probably not though because they were on a striped RAID.
Since this system (at the original site address) will not have had significant stress testing or burn-in before I leave for FUN, I will also leave the coxe.net one running. That is in case the new one fails for any reason. But the coxe.net server should be considered as for read-only. Any set changes, registrations, ... there after the new one comes up will not be retained. But people will be able to see the price guide, their inventories and sets, pops, etc. I know some will need that at the show.
All that said, I encourage everyone to download their inventories from the current running server as CSV (comma separated values) spreadsheets. It is always a good idea to maintain a local copy.
So, the hope is to have a running registry.ssdcvams.com server tonight or tomorrow.
Re: SSDC Registry Status
All that said, I encourage everyone to download their inventories from the current running server as CSV (comma separated values) spreadsheets. It is always a good idea to maintain a local copy.
Will do John (if I can get into the site and call up my inventory). Thanks for the great advice – and for everything you have done!
Will do John (if I can get into the site and call up my inventory). Thanks for the great advice – and for everything you have done!
When in doubt... don't.
Re: SSDC Registry Status
Code is all installed. I believe I got all of the needed packages installed too.
The coxe.net server was stopped; the database backed up; and is enroute to the new server. Takes about 5 or 6 minutes.
Then set the static address; move it into the data center; and bring it back up. We would then be on the new server and with the original URL.
The coxe.net server was stopped; the database backed up; and is enroute to the new server. Takes about 5 or 6 minutes.
Then set the static address; move it into the data center; and bring it back up. We would then be on the new server and with the original URL.
Re: SSDC Registry Status
Everything is up and running on the new server except one thing. The latest mkpasswd that encrypts your password to see if it matches has changed. The worst case would be everyone would need new passwords. The older mkpasswd did short encryptions with 2-character salts, the old UNIX /etc/passwd thing. Looking for a deprecated one that will run on this server.
For now, I brought the temporary one back up.
For now, I brought the temporary one back up.
Re: SSDC Registry Status
I was able to fix the password encryption. The database connection is apparently the final problem to solve.
So I set the real registry server to respond now to the original URL but it will hand it over to the temporary server. The temporary server now has a red warning bar on the login page warning that registrations and set changes will not be saved.
Everyone can still go on and look at sets, inventories, pops and all. Should get us through the show next week. Glad this happened after sets got updated and judged for awards. Hopefully, I can get the new server database connection problem solved before I leave. But I will only do that after I have done my powerpoint and largely packed to fly.
The current status is then that the new server is completely built and has the code and database. Any porting issues seem to be resolved. The remaining DB connection is probably an easy thing to fix. Just not at 1:00 am.
So I set the real registry server to respond now to the original URL but it will hand it over to the temporary server. The temporary server now has a red warning bar on the login page warning that registrations and set changes will not be saved.
Everyone can still go on and look at sets, inventories, pops and all. Should get us through the show next week. Glad this happened after sets got updated and judged for awards. Hopefully, I can get the new server database connection problem solved before I leave. But I will only do that after I have done my powerpoint and largely packed to fly.
The current status is then that the new server is completely built and has the code and database. Any porting issues seem to be resolved. The remaining DB connection is probably an easy thing to fix. Just not at 1:00 am.
Re: SSDC Registry Status
The old box shut down at about 10:30pm last light. It only overheated. I moved the physical box to the garage where the internet broadband connection is and where my wife can get to it in my absence. If it shuts down from overheating while at the show, I can call my wife and have her turn it back on. Put a bold label where the ON button is. I cannot get a new CPU fan today. We'll make it through the week with perhaps brief interruptions.
On the bright side, the new Registry server is doing well. As soon as we get the CGI connection to the database fixed, we will be back better than ever.
On the bright side, the new Registry server is doing well. As soon as we get the CGI connection to the database fixed, we will be back better than ever.
Re: SSDC Registry Status
Interesting. This came up in my Facebook "Memories" this morning. So this means that we got 12 years out of the last server.
- FirstRehosting.jpg (62.66 KiB) Viewed 1128 times
Re: SSDC Registry Status
@alefzero
Wow! Twelve years is dinosaur territory for that kind of equipment, isn't it?
Wow! Twelve years is dinosaur territory for that kind of equipment, isn't it?
When in doubt... don't.
Re: SSDC Registry Status
I found out there is armor in the newest versions that do not allow httpd to connect to mysql, sendmail, etc. Ran a net advised tool and it destroyed the root filesystem and would not reboot. Rebuilding from scratch. The copying will require 12 hours and then I can do all of the reconfiguration. I should have noted all of the packages needed and all. This is going to be extremely stressful. I will rush doing that VAM Thing powerpoint later.
Re: SSDC Registry Status
The message answered my question about SSDC .. Down for a long time .
My old windows 7 quit and im am working on a new system up load . I am not a computer person . Three days of BS
and things are starting to work .
Good luck JC .
My old windows 7 quit and im am working on a new system up load . I am not a computer person . Three days of BS
and things are starting to work .
Good luck JC .
Re: SSDC Registry Status
The problem is that twelve years later the database service, the operating system, and the web service daemon all have changed quite significantly. Even after locating all the new places configurations are, the OS implemented new security beyond just the firewall (which also changed) that was prudent. In this, various services cannot normally talk with other services. For instance the web service cannot send emails and texts or even do database transactions. That last one was a bear to get going but it was solved. Everything now works except that there is a generic error message in the logs that I need to resolve. Might do it tonight before I fly out or remotely in Orlando. It is definitely doable.
As for the old machine on which it is temporarily hosted, I moved it into the garage out of the data center. This way my wife can turn it back on if it shuts down from the CPU overheating. I put a big label on the power button as it is not easy to see otherwise in the dark. The only thing that you might not do on this temporary installation is upload image files. All database transactions will be preserved, including set changes and new registrations.
When the new server problem is solved, the temporary server will be stopped and the latest database will be backups up and transferred to the new server. The database on that new one will be deleted and replaced by the transferred last one. The entry page will be changed from transferring the client to the temporary server to the standard login on the new server. This is not at all a long process.
I stopped working on it last night and spent this morning making a 50-slide powerpoint for my VAM Thing presentation. Glad to have that done and ready.
As for the old machine on which it is temporarily hosted, I moved it into the garage out of the data center. This way my wife can turn it back on if it shuts down from the CPU overheating. I put a big label on the power button as it is not easy to see otherwise in the dark. The only thing that you might not do on this temporary installation is upload image files. All database transactions will be preserved, including set changes and new registrations.
When the new server problem is solved, the temporary server will be stopped and the latest database will be backups up and transferred to the new server. The database on that new one will be deleted and replaced by the transferred last one. The entry page will be changed from transferring the client to the temporary server to the standard login on the new server. This is not at all a long process.
I stopped working on it last night and spent this morning making a 50-slide powerpoint for my VAM Thing presentation. Glad to have that done and ready.