[QUOTE=malcolmlewis;33843]Hi
Just dd you backup images back, restart the system and will start
again…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.27-27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]
Oh ok! I thought you meant some kind of an automatic repair application or perhaps a package manager of some kind.
Yep, first action plan next week is to dd with the system rescue disk… thanks again, malcom and smflood! I’ll let you both know how everything turns out on Monday…
[QUOTE=malcolmlewis;33843]Hi
Just dd you backup images back, restart the system and will start
again… :([/QUOTE]
Okay! So, I came in early this morning for the dd restoration using the rescue disk, and everything went swimmingly. We are now back to where we were when I posted the thread at the beginning, which still doesn’t have a GUI, but at least is stable. My manager and I agreed that once we got the system stable again, our best bet is to wait until our active work season dies down, and then plan a rebuild of the server. The last time it was rebuilt was over a weekend two years ago after a crash, so it was an emergency-level, “gotta get up and running again” kind of rebuild. Until we can do it over again, I’m not going to run any updates or upgrades on the system.
What I’d like to do now is spin up a VM with SLES 11 SP3 and get a base configuration going that I can then image onto the production server later this year. I’ve read in my troubleshooting research that there are a number of tools for building base systems for deployment and later configuration. Do either of you have a preferred method for building that kind of system, malcom and smflood?
Thanks again to both of you for your help… I can’t say enough how thankful I am for communities like this and the people like you guys that make them so awesome.
Hi
When you say vm, what type vmware, virtualbox, kvm?
Ideally create an autoyast file from the existing system, but in your
case it’s a bit foobar at present… Maybe try creating one and maybe
then edit out offending stuff?
If you get a chance, rollback those glibc files and see if it comes
back up.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.27-27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
[QUOTE=malcolmlewis;33869]Hi
When you say vm, what type vmware, virtualbox, kvm?
Ideally create an autoyast file from the existing system, but in your
case it’s a bit foobar at present… Maybe try creating one and maybe
then edit out offending stuff?
If you get a chance, rollback those glibc files and see if it comes
back up.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.27-27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]
I mean virtualbox. I’d like to make a virtualbox installation and then create an autoyast configuration out of it that I can load into the server in the future.
What do you mean, rollback the glibc files? Right now they’re glibc 2.14, which was installed from the openSUSE repo that was added accidentally.
Hi
I would just start with the basic install from the SLES 11 SP3 iso
image and work from there (Maybe get an eval code for 60 days of
updates? Any SLES eval code should work, just needs to point to the
Microsoft (aka Novell) servers rather than SUSE).
With zypper you can select the specific version to install/rollback, for
example on SLES 12 SP1;
zypper se -s glibc-devel
S | Name | Type | Version | Arch | Repository
--+--------------------+---------+-----------+--------+---------------------------------
i | glibc-devel | package | 2.19-38.2 | x86_64 | SLES12-SP1-Updates for x86_64
v | glibc-devel | package | 2.19-35.1 | x86_64 | SLES12-SP1-Updates for x86_64
v | glibc-devel | package | 2.19-31.9 | x86_64 | SLES12-SP1-Pool for x86_64
zypper in glibc-devel = 2.19-31.9
If you could try that and see if it gets things started for the rest of
the packages?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.27-27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
[QUOTE=malcolmlewis;33876]Hi
I would just start with the basic install from the SLES 11 SP3 iso
image and work from there (Maybe get an eval code for 60 days of
updates? Any SLES eval code should work, just needs to point to the
Microsoft (aka Novell) servers rather than SUSE).[/QUOTE]
Okay, cool.
[QUOTE]With zypper you can select the specific version to install/rollback, for
example on SLES 12 SP1;
zypper se -s glibc-devel
S | Name | Type | Version | Arch | Repository
--+--------------------+---------+-----------+--------+---------------------------------
i | glibc-devel | package | 2.19-38.2 | x86_64 | SLES12-SP1-Updates for x86_64
v | glibc-devel | package | 2.19-35.1 | x86_64 | SLES12-SP1-Updates for x86_64
v | glibc-devel | package | 2.19-31.9 | x86_64 | SLES12-SP1-Pool for x86_64
zypper in glibc-devel = 2.19-31.9
If you could try that and see if it gets things started for the rest of
the packages?[/QUOTE]
Wouldn’t rolling glibc-devel back cause the zypper to uninstall glibc and bork the system again like it did last time? How would rolling back through zypper be any different than zypper dup?
Btw, this is my output for zypper se -s glibc-devel >>
Hi
You can rollback zypper etc all at the same time, just one big long
line of <package = version> <package = version> <package = version>.
Again, it does ask with y/n, just press n.
I have a feeling, your best is to go with your virtual machine and try
and get a similar system rolling along…
Is there any reason you can update to a later release? At present SLES
12 SP2 is in public beta?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.27-27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
[QUOTE=malcolmlewis;33878]Hi
You can rollback zypper etc all at the same time, just one big long
line of <package = version> <package = version> <package = version>.
Again, it does ask with y/n, just press n.
I have a feeling, your best is to go with your virtual machine and try
and get a similar system rolling along…
Is there any reason you can update to a later release? At present SLES
12 SP2 is in public beta?
[/QUOTE]
I think I’m just going to go with the VM and leave the production system alone for now… we can do everything we need to do by CLI for the time being.
We will probably update to a later release after I’ve gotten a base configuration prepared for deployment.
We are now back to where we were when I posted the thread at the beginning, which still doesn’t have a GUI, but at least is stable. My manager and I agreed that once we got the system stable again, our best bet is to wait until our active work season dies down, and then plan a rebuild of the server. The last time it was rebuilt was over a weekend two years ago after a crash, so it was an emergency-level, “gotta get up and running again” kind of rebuild. Until we can do it over again, I’m not going to run any updates or upgrades on the system.