How to upgrade to 12.3 from 12.1/2. Cant get any services running.

English Install/Boot/Login
1

Ok. I been tring this couple months now. From a live working 12.1 => 12.3 , 12.1 => 12.2 => 12.3 and with dvd and zypper from command line. Tried 12.2 both with and without online update. Same result on all cases.

12.3 keeps loosing inittab, /etc/init.d/boot and rc so 1st of all having hard time to get it even to boot. Yes, my ssd disks have been checked. Box is i7 k2600 @8x3,4mhz 16gb ram year old intel mobo, 3ware raid cards, ssd system disks. 2x1gbit nic. One to outside world and the other to lan.

Next after get 12.3 to boot networks dissapeared in the ozone and nothing network related will load: apache, squid, dhcpd, mysql etc…I tried to get rid of that networkmanager, but no luck. Cant even change in yast network settings from networkmanager to ifup. Just get a popup saying that no network running. Heh. Deleted with yast everything networkmanager related, but no change not even after reboot. Dunno if had a gui if would be easier.

12.1 => 12.2 went smoothly. Dvd installed in lil over 30 mins and online update about same. All worked ok. But this 12.3…I have been reading past couple months that someone actually been able to upgrade to it from older SuSe. I been using SuSe since mid 90’s and 1’st time having this much difficulties.

Would anyone have any clue? Clean install might work, but dont have a week to reconf everything. 12.1 was a clean install. My web sites are running on box and 4am so need now put 12.2 back into it so can get it back up before ppl start to wake up.

I will try some nite again if just can get a clue whats wrong. Putting my hopes on that someone here would. I ran outta ideas.

2

On 2013-07-04 02:56, Gholkro wrote:
>
> Ok. I been tring this couple months now. From a live working 12.1 =>
> 12.3 , 12.1 => 12.2 => 12.3 and with dvd and zypper from command line.
> Tried 12.2 both with and without online update. Same result on all
> cases.

Upgrade instructions:

Online upgrade
method Offline
upgrade method
Chapter 16. Upgrading the System and System Changes
openSUSE 12.3 Release Notes

Choose your method :slight_smile:

> 12.3 keeps loosing inittab, /etc/init.d/boot and rc

12.3 does not have any of that, as it uses systemd.

> Next after get 12.3 to boot networks dissapeared in the ozone and
> nothing network related will load:

Read the release notes: network does not run till after the 2nd reboot.
Plus, you may have hit another bug: bot NF and ifup are started. You
have to manually disable one.

> 12.1 => 12.2 went smoothly. Dvd installed in lil over 30 mins and
> online update about same. All worked ok. But this 12.3…I have been
> reading past couple months that someone actually been able to upgrade to
> it from older SuSe. I been using SuSe since mid 90’s and 1’st time
> having this much difficulties.

Many. Me, for instance.

> Would anyone have any clue? Clean install might work, but dont have a
> week to reconf everything. 12.1 was a clean install. My web sites are
> running on box and 4am so need now put 12.2 back into it so can get it
> back up before ppl start to wake up.

Choose one method, follow the instructions, then solve each problem one
by one. I might be able to help you further, one problem at a time - if
you followed the instructions to the letter.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

3

That exactly how tried to do it. From both 12.1 and 12.2.

](http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/cha.update.html)
openSUSE 12.3 Release Notes

Choose your method :slight_smile:

4.0 System upgrade.

I get error on almost all commands…except ln and rm lines via sysctl:
Systemctl -p Id show network.service
>>failed to get D-bus connection: no connection to service manager

/etc/init.d/network status
>>/etc/init.d/network is diabled, cant find any
>>another service enabled as the network.service

And so on.

> 12.3 keeps loosing inittab, /etc/init.d/boot and rc

12.3 does not have any of that, as it uses systemd.

I rebooted maybe 15 times and hung up on error saying that inittab missing. After got inittab in place started to give thoce rc/boot errors.

> Next after get 12.3 to boot networks dissapeared in the ozone and
> nothing network related will load:

Read the release notes: network does not run till after the 2nd reboot.
Plus, you may have hit another bug: bot NF and ifup are started. You
have to manually disable one.

I think that neither one is running

> 12.1 => 12.2 went smoothly. Dvd installed in lil over 30 mins and
> online update about same. All worked ok. But this 12.3…I have been
> reading past couple months that someone actually been able to upgrade to
> it from older SuSe. I been using SuSe since mid 90’s and 1’st time
> having this much difficulties.

Many. Me, for instance.

> Would anyone have any clue? Clean install might work, but dont have a
> week to reconf everything. 12.1 was a clean install. My web sites are
> running on box and 4am so need now put 12.2 back into it so can get it
> back up before ppl start to wake up.

Choose one method, follow the instructions, then solve each problem one
by one. I might be able to help you further, one problem at a time - if
you followed the instructions to the letter.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

I have basically tried everyting that you just gave links to. Or then I have just missed something.

4

On 07/04/2013 04:26 AM, Gholkro wrote:
> I have basically tried everyting that you just gave links to. Or then I
> have just missed something.

there is SO MANY changes between 12.1 and 12.3 if i were in your
situation i would not try to “upgrade”, instead i would:

-do a full system backup and save it to an off machine location

-test that a restore from that media is possible…

-additionally save all data and configs to a different safe, off
machine location

-test that it is possible to read and transfer the data

[NOTE: Read the sig caveat before continuing!]

-do a full format (including /home) and then install 12.3

-run in all the updates via “zypper patch” or YaST Online Updates

-add all the needed applications

-run “zypper patch” or YaST Online Updates again

-make another full system backup (of the new system, do NOT overwrite
the old system backup)

-rejoin the data to the new system (you may/will have to hunt around
to see where your (for example) old emails need to be placed in your
new email client…

when done you will have a new systemd which won’t support your old
init.d stuff, and a new grub2 which will require you to learn how to
feed and care for it…and, lots of other new stuff…

ymmv–you can find other opinions but i think ‘upgrade’ is not the
path to most stable…

–
dd
http://tinyurl.com/DD-Caveat

5

On 2013-07-04 04:26, Gholkro wrote:
>
> robin_listas;2569288 Wrote:

>> Upgrade instructions:
>>
>> ’ Online upgrade
>> method’ (http://en.opensuse.org/SDB:System_upgrade) ’ Offline
>> upgrade method’ (http://en.opensuse.org/SDB:Offline_upgrade)
>>
>>
>> Chapter 16. Upgrading the System and System Changes
>>
>
>
> That exactly how tried to do it. From both 12.1 and 12.2.

There are two different methods above - which one exactly did you use?

Please describe your steps in detail - I’m not there looking over your
shoulder, I really need to know what you have done.

Specifically, if you used the offline method, have you done the extra
steps after the upgrade? Did you do any variation on the procedure?

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

6

On 2013-07-04 09:23, dd wrote:
> On 07/04/2013 04:26 AM, Gholkro wrote:
>> I have basically tried everyting that you just gave links to. Or then I
>> have just missed something.
>
> there is SO MANY changes between 12.1 and 12.3 if i were in your
> situation i would not try to “upgrade”, instead i would:

The upgrade is certainly possible, I did it. However, it requires
certain effort and following the procedure. The results are good, stable
and rewarding, but not easy to reach :wink:

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

7

On 07/04/2013 11:38 AM, Carlos E. R. wrote:
> The results are good, stable
> and rewarding, but not easy to reach;-)

yes, i agree…but only by completely and correctly following the
correct path…without getting creative and mixing around the steps
or skipping some or trying to go from 12.1 direct to 12.3 or or or or or

and, being a little lucky (by not running into any of the three
caveats: “due to some third-party packages and the myriad of possible
configurations, it is possible for some combinations to cause
failure” or “Depending on your customizations, some steps (or the
entire upgrade procedure) may fail” or “it is to be considered a
“best effort”: it should work, but it can also fail.”)

of course, also the full fresh install i advocate can also fail for
any number of hardware, software of user knowledge reasons…

which is why the terms backup, copy, save are so often used in the
descriptions of all methods of moving from one version to any other.

–
dd

8

On 2013-07-04 11:59, dd wrote:
> On 07/04/2013 11:38 AM, Carlos E. R. wrote:
>> The results are good, stable
>> and rewarding, but not easy to reach;-)
>
> yes, i agree…but only by completely and correctly following the
> correct path…without getting creative and mixing around the steps or
> skipping some or trying to go from 12.1 direct to 12.3 or or or or or

I did go direct O:-)

And I was creative. But then, as you know that I wrote part of the
documentation, I was intentionally experimenting a variation, which
failed horribly. I had to go back and redo without the experimental part.

(which reminds me that I wanted to publish it somewhere…)

> and, being a little lucky (by not running into any of the three caveats:
> “due to some third-party packages and the myriad of possible
> configurations, it is possible for some combinations to cause failure”
> or “Depending on your customizations, some steps (or the entire upgrade
> procedure) may fail” or “it is to be considered a “best effort”: it
> should work, but it can also fail.”)

:slight_smile:

> of course, also the full fresh install i advocate can also fail for any
> number of hardware, software of user knowledge reasons…

True.

> which is why the terms backup, copy, save are so often used in the
> descriptions of all methods of moving from one version to any other.

Absolutely :slight_smile:

An upgrade is more demanding, the admin has to know his way with Linux
to solve problems as they arrive. It is not something for the unskilled.
Or be more patient, have another computer, and start asking patiently…
(with the computer running and waiting for that advice).

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

9

Sounds like you try to use sysvinit-init on 12.3. That doesn’t work!
Just installing that package removes half of your system (or even more? zypper wants to switch my whole system to 32bit if I try that).

Stick with systemd and your system should boot.

10

Thats why installed 12.2 1st. Cant do a full system backup as dont have spare 10 tb of extra hdd anywhere sigh

-run in all the updates via “zypper patch” or YaST Online Updates

-add all the needed applications

-run “zypper patch” or YaST Online Updates again

-make another full system backup (of the new system, do NOT overwrite
the old system backup)

-rejoin the data to the new system (you may/will have to hunt around
to see where your (for example) old emails need to be placed in your
new email client…

when done you will have a new systemd which won’t support your old
init.d stuff, and a new grub2 which will require you to learn how to
feed and care for it…and, lots of other new stuff…

ymmv–you can find other opinions but i think ‘upgrade’ is not the
path to most stable…

–
dd
DD Caveat

I kinda have noticed in past couple months that lotsa have changed…

11

hmmm…I been typing these posts here from iPad as couldnt get network running…But now after installing 16th time from dvd (counting both dvd and zypper installs, this box came online :slight_smile:

uname -a

Linux KiD2.KiD2 3.7.10-1.1-desktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013 (82d3f21) x86_64 x86_64 x86_64 GNU/Linux

But, this is in that “safe mode”. Not normal boot. So looks like quite close getting all running.

and, being a little lucky (by not running into any of the three
caveats: “due to some third-party packages and the myriad of possible
configurations, it is possible for some combinations to cause
failure” or “Depending on your customizations, some steps (or the
entire upgrade procedure) may fail” or “it is to be considered a
“best effort”: it should work, but it can also fail.”)

of course, also the full fresh install i advocate can also fail for
any number of hardware, software of user knowledge reasons…

which is why the terms backup, copy, save are so often used in the
descriptions of all methods of moving from one version to any other.

–
dd

Ii guess I was lucky. Now just need to find that last bit fixed so can get a normal boot. Even added monitor and KDE so can use GUI now.

12

Making online update now. Lets see if that fixes rest of probs


# /etc/init.d/network status
Checking mandatory network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8
    lo        is up                                                                                                              running
    eth0      device: Realtek Semiconductor Co., Ltd. RTL8169 PCI G
    eth0      DHCP4 client (dhcpcd) is running
    eth0      IP address: 88.112.79.168/20
    eth0      IP address: 88.112.79.168/20
    eth0      is up                                                                                                              running
    eth1      device: Intel Corporation 82579V Gigabit Network Conn
    eth1      IP address: 10.0.0.10/24
    eth1      is up                                                                                                              running
    lo        
    lo        IP address: 127.0.0.1/8
    lo        is up                                                                                                              running
Checking service network .  .  .  .  .  .  .  .  .  .  .  .  .  .                                                                running
redirecting to "systemctl  status network.service"
network.service - LSB: Configure network interfaces and set up routing
          Loaded: loaded (/etc/init.d/network)
          Active: active (running) since Thu, 2013-07-04 13:59:34 EEST; 31min ago
         Process: 613 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/network.service
                  â 3786 /sbin/dhcpcd --netconfig -L -E -c /etc/sysconfig/network/scripts/dhcpcd-hook -t 0 -h KiD2 eth0

Dunno if that how it should go but atleast got it online now…hopefully get services up after online update done. Didnt wanna try yet.

Edit: Services up!!! gonna try reboot in 30 mins and see if my hopes are flushed down the drain…

13

On 2013-07-04 13:46, Gholkro wrote:
>
> Making online update now. Lets see if that fixes rest of probs

Tell them one by one and we can help.

> Dunno if that how it should go but atleast got it online
> now…hopefully get services up after online update done. Didnt wanna
> try yet.

The correct way now is “systemctl status network.service”. Also, check
“NetworkManager.service” to see that it is not running nor enabled.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

14

Works ok now

NetworkManager was the one giving all the probs.

I’ll just put shortly what did the final trick as looks like quite a few been fighting with same prob on this forum:

1st I deleted in yast ALL NetworkManager files
mkdir /var/log/journal
systemd-logger <- installed in yast

pico /boot/grub/menu.lst <- added init=/usr/lib/systemd/systemd to kernel options
pico /etc/sysconfig/network/config <- added to the end of file: NETWORKMANAGER=“no” NM_CONTROLLED=“no” ONBOOT=“yes”
reboot

systemctl stop network.service
systemctl disable NetworkManager.service
systemctl start network.service
systemctl -p Id show network.service <- should return Id=network.service = just a check that got rid off NM

pico /boot/grub/menu.lst <- added init=/usr/lib/systemd/systemd to kernel options
pico /etc/sysconfig/network/config <- added to the end of file: NETWORKMANAGER=“no” NM_CONTROLLED=“no” ONBOOT=“yes”

reboot

Was actually quite a simple solution. once got all the pieces together. Tnx all here for quick replies :slight_smile:

15

Rebooting usually fixes the network on install problem at worst in yast switch the method. What you did really should not be necessary

16

On 2013-07-04 21:56, gogalthorp wrote:
>
> Rebooting usually fixes the network on install problem at worst in yast
> switch the method. What you did really should not be necessary

It is on an upgrade, at least from 12.1 to 12.3: Both network manager
and ifup are started and compete one another during boot, causing
network service to fail, and this causes many other services to fail on
boot. Even if you reboot several times the problem is not solved. Worse:
if you have nfsserver enabled, boot takes up to five minutes.

Known problem, but not on the release notes.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

17

ok but still you should be able to fix it from yast,right?

18

On 2013-07-05 04:16, gogalthorp wrote:
>
> ok but still you should be able to fix it from yast,right?

Nope.

I fought this particular problem for many hours, days in fact. YaST can
not handle it because it fails to activate/deactivate services properly
with systemd. It is not the same network problem as the one you get when
installing fresh.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

19

This is why I did what posted few posts up. Cant do all in yast. Couldnt dissable NetworkManager in yast/network settings as ifup checkbox didnt work. And I went from 12.2 to 12.3. NM might be good in laptops but I need www/dhcp/ssh/ftp servers so not good in my case.

That disabling of NM I did is a collection of info from this thread and quite a few posts in this forum. All in one ‘menu’ now as there were bits and pieces here and there. So next person will save lotsa time as dont need to do trial and error like I did.

Was just reading about 13.1 going to try to put everything under system(d). Then upgrading sure will be a biatch if any services running. Maybe clean install only way to go at that point. Or maybe it goes nicely from 12.3 as lillbit same way handling the stuff. Will see by xmas :0)

But can say that after all that tinkering, I do have a steady system now. I overloaded it and tried to crash it but couldnt. So agree to ealier replies that upgrading works. Although takes a lil effort.

20

On 2013-07-05 12:46, Gholkro wrote:

> That disabling of NM I did is a collection of info from this thread and
> quite a few posts in this forum. All in one ‘menu’ now as there were
> bits and pieces here and there. So next person will save lotsa time as
> dont need to do trial and error like I did.

I told you you this, half an hour after you posted your question, first
answer in the thread.

> But can say that after all that tinkering, I do have a steady system
> now. I overloaded it and tried to crash it but couldnt. So agree to
> ealier replies that upgrading works. Although takes a lil effort.

Yes, it does :slight_smile:

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)