[Solved] OMG! Upgrade crashed!

This forum is for general chat between members about Mageia.

Technical questions are supposed to be posted in support forums. Not here !

[Solved] OMG! Upgrade crashed!

Postby msdobrescu » Sep 16th, '19, 21:50

Hello,

After a long time, I have decided to upgrade from 6 to 7.1.
I never get the applet notifying me, despite is apparently configured to do it.
So, I've started by following the upgrade procedure, using urpmi, erased the mirrors, fetched the new ones, started the upgrading.
And at some point, lost the network connection due to some power failure somewhere around.
Then, goodbye Internet! All my systems connected and resolved fine any Internet address.
All the URLs worked, but not Mageia!
It failed, although network worked for it, so I could access it through the LAN.
And that's it, the KDE plasma network applet simply could not work anymore.
Restarting Mageia showed KDE/Plasma gone, could not start, trying desperately to connect to the Internet, but to no avail.
Now I'm trying a recovery from a ISO.

IMHO, packages should be downloaded ALL first, then do the upgrade, unless specified not to.

Ohh, this hurts!
Last edited by msdobrescu on Oct 17th, '19, 18:58, edited 2 times in total.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby benmc » Sep 16th, '19, 22:05

not sure it you have re-started your upgrade via dvd.
from a terminal you should be able to connect to the LAN via
Code: Select all
# drak-connect
or wifi via
Code: Select all
# drak-roam

you could then restart your upgrade via
Code: Select all
# urpmi --auto-update

upon completion, if Plasma is not working run
Code: Select all
#urpmi task-plasma5 sddm
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 16th, '19, 22:20

Thank you!
Of course I've tried exactly that, but could not connect to the Internet.
After the DVD upgrade, it could not connect either, but at the end of the wizard it asked to look for updates, that worked, now I wait for the process to complete.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 17th, '19, 01:43

msdobrescu wrote:IMHO, packages should be downloaded ALL first, then do the upgrade, unless specified not to.

Not everybody has that much space available.

Apart from that, this is mentioned in the "Please note!" section here on how to do that:
https://wiki.mageia.org/en/Mageia_7_Rel ... _.28CLI.29
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 17th, '19, 07:33

I have followed exactly that section.
But failed as described.
Each time (since version 1), the upgrade has let tons of not upgraded packages, I have had to manually remove/install the equivalents.
Regarding the space, I think there must be 6 GB needed in my case, it's not much.
The upgrade procedure should warn about the needed space and should be able to assess if it is enough to download everything first.
Or a reliable recovery/unattended setup should be possible.

So far, I have managed to upgrade and run, but the strange thing is I have two network management applets in KDE.
One is Mageia's, the other one is KDE's standard one. But KDE's one can't see other's setup and this is so wrong.

Also, I depend on x2go, it seems broken for the moment, although it should not have reset the settings.

Postgres 9.6 refuses to upgrade the old one, which is 9.4. I'll have to find out why.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 17th, '19, 12:50

As a general hint and golden rule: Please only one problem per thread.

msdobrescu wrote:I have followed exactly that section.
But failed as described.

So you did use --download-all and it did not download all packages? If that's a reproducible issue, please feel free to report that as a bug, after searching if it hasn't been reported yet already: https://wiki.mageia.org/en/How_to_report_a_bug_properly

msdobrescu wrote:Each time (since version 1), the upgrade has let tons of not upgraded packages, I have had to manually remove/install the equivalents.

And where did you report that, so that it maybe could get fixed? Also, how does this relate to this topic in particular?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 17th, '19, 13:02

doktor5000 wrote:And where did you report that, so that it maybe could get fixed? Also, how does this relate to this topic in particular?

Well, after Mandriva, I thought it is a hard time to come and ask for things, I was happy it was not discontinued!
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 17th, '19, 13:05

Sorry, I don't understand what you're trying to say.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 17th, '19, 13:21

We have a long troubleshooting on it here: viewtopic.php?f=7&t=2544, and some here: viewtopic.php?f=7&t=4939
I would really have been very disappointed if Mageia would have not been available at the time of Mandriva decision to become commercial and fired a lot of people.
At the time I was watching all the process in horror. Really. Thinking about all the people there, needing to find a new living and still trying to continue their work.
I did not ask more than having something to continue this fine software.
Especially first rebranding, I was expecting problems. Then, slowly, it become a habit. Each upgrade was like this. Letting behind lots of packages I have upgraded gradually by myself.
I report this now... Don't know how to check for the reason.
Maybe next time I can provide some logs? Or check some upgrade scripts for assessing the potential issues, if somebody provides them to me...
Now, I need to cleanup and fix things one at a time, indeed.
For instance, the systemd applet enters a state that makes KDE simply restart and ask for logon. I'll go command line now.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 17th, '19, 13:34

msdobrescu wrote:We have a long troubleshooting on it here: viewtopic.php?f=7&t=2544, and some here: viewtopic.php?f=7&t=4939


I don't see any actual troubleshooting regarding the old packages in either thread, nor an actual listing. And my answers in both threads still apply, and it's the same I told you here when you brought this up:
doktor5000 wrote:There was no time and resources to do a full rebuild of the distro before release, so there are still many .mga1 packages there, but they should still work. If there are issues with those packages, report them so we can put out updates for those.


Also you don't seem to understand that there are usually always some old packages still in the new release, this is the same with Mageia 7 as noted in the errata:
https://wiki.mageia.org/en/Mageia_7_Err ... ga6_suffix

msdobrescu wrote:Each upgrade was like this. Letting behind lots of packages I have upgraded gradually by myself.
I report this now... Don't know how to check for the reason.
Maybe next time I can provide some logs?

Well, how do you assume this would work itself out? If you don't provide an actual list of what packages have not been upgraded AND which you had to upgrade yourself (at least those packages that come from regular Mageia repositories) then how do you expect that this will be fixed if you never report the details somewhere ?

First step would be to add the output of
Code: Select all
urpmq --not-available

after a completed upgrade to a new Mageia release, and after enabling repos that were enabled before, like tainted and nonfree.

But you never provided such a listing, yet you still complain that there are thousands of packages that you manually need to upgrade / replace, since Mageia 1. Don't you see the problem with this ?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 17th, '19, 13:59

OK, when I get home. I know some packages are left. I have meant that I have had to choose mga7 packages that should have replaced mga6 ones. There are always shades...
Anyway, now, I might provide some long orphans list it reports, despite it finds some that are not really orphaned, so won't remove them.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 17th, '19, 19:37

Hello, my first issue solved: x2go upgrade needed to re-create the DB. Awkward. But I\m back to comfort!

Now, I wait about 3 minutes at boot time for a job that says: "Failed to start LSB :Bring up/down Networking". What is this?

And the postgresql upgrade issue:

Code: Select all
installing postgresql9.6-server-9.6.15-1.mga7.x86_64.rpm from /var/cache/urpmi/rpms                                                                                                         
Preparing...                     ##########################################################################################################################################################

You currently have database tree for Postgresql 9.4
You must use postgresql9.4-server
To update you Postgresql server, dump your databases
delete /var/lib/pgsql/data/ content, upgrade the server, then
restore your databases from your backup

error: %prein(postgresql9.6-server-9.6.15-1.mga7.x86_64) scriptlet failed, exit status 1
ERROR: 'script' failed for postgresql9.6-server-9.6.15-1.mga7.x86_64
error: postgresql9.6-server-9.6.15-1.mga7.x86_64: install failed
error: postgresql9.4-server-9.4.24-1.mga6.x86_64: erase skipped
----------------------------------------------------------------------
More information on package postgresql9.6-server-9.6.15-1.mga7.x86_64

----------------------------------------------------------------------


The package information is empty.

I think x2go depends on 9.4 and that's the reason it can't upgrade...
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 17th, '19, 22:29

msdobrescu wrote:Now, I wait about 3 minutes at boot time for a job that says: "Failed to start LSB :Bring up/down Networking". What is this?

You would need to find out on your box why it's failing
Code: Select all
systemctl status network.service -al -n50


msdobrescu wrote:And the postgresql upgrade issue:

[...]
You currently have database tree for Postgresql 9.4
You must use postgresql9.4-server
To update you Postgresql server, dump your databases
delete /var/lib/pgsql/data/ content, upgrade the server, then
restore your databases from your backup


It spells out pretty clearly what you should do, no ?

FWIW postgresql is not being shipped in several different 9.x branches anymore, and you need to take manual steps that cannot be done during the upgrade, otherwise the old postgresql9.4-server packages cannot be removed and hence they cannot be upgraded.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 18th, '19, 04:57

The network is weird.
I have two applets, for some reason, one asks for the root password at startup.
I use a router and I don't need a pppoe, but seems to be there somewhere, while the network applets do no show it.

Code: Select all
systemctl status network.service -al -n50
? network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; generated)
   Active: failed (Result: exit-code) since Wed 2019-09-18 06:03:51 EEST; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1054 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Sep 18 06:01:31 mynas pppoe[1505]: Timeout waiting for PADO packets
Sep 18 06:02:02 mynas pppd[1460]: LCP: timeout sending Config-Requests
Sep 18 06:02:02 mynas network[1054]: LCP: timeout sending Config-Requests
Sep 18 06:02:02 mynas network[1054]: Connection terminated.
Sep 18 06:02:02 mynas pppd[1460]: Connection terminated.
Sep 18 06:02:02 mynas pppd[1460]: Modem hangup
Sep 18 06:02:02 mynas network[1054]: Modem hangup
Sep 18 06:02:06 mynas network[1054]: pppoe: Timeout waiting for PADO packets
Sep 18 06:02:06 mynas network[1054]: Using interface ppp0
Sep 18 06:02:06 mynas network[1054]: Connect: ppp0 <--> /dev/pts/1
Sep 18 06:02:06 mynas pppoe[2418]: Timeout waiting for PADO packets
Sep 18 06:02:06 mynas pppd[1460]: Using interface ppp0
Sep 18 06:02:06 mynas pppd[1460]: Connect: ppp0 <--> /dev/pts/1
Sep 18 06:02:37 mynas pppd[1460]: LCP: timeout sending Config-Requests
Sep 18 06:02:37 mynas network[1054]: LCP: timeout sending Config-Requests
Sep 18 06:02:37 mynas network[1054]: Connection terminated.
Sep 18 06:02:37 mynas pppd[1460]: Connection terminated.
Sep 18 06:02:37 mynas pppd[1460]: Modem hangup
Sep 18 06:02:37 mynas network[1054]: Modem hangup
Sep 18 06:02:41 mynas pppd[1460]: Using interface ppp0

























? network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; generated)
   Active: failed (Result: exit-code) since Wed 2019-09-18 06:03:51 EEST; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1054 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Sep 18 06:01:31 mynas pppoe[1505]: Timeout waiting for PADO packets
Sep 18 06:02:02 mynas pppd[1460]: LCP: timeout sending Config-Requests
Sep 18 06:02:02 mynas network[1054]: LCP: timeout sending Config-Requests
Sep 18 06:02:02 mynas network[1054]: Connection terminated.
Sep 18 06:02:02 mynas pppd[1460]: Connection terminated.
Sep 18 06:02:02 mynas pppd[1460]: Modem hangup
Sep 18 06:02:02 mynas network[1054]: Modem hangup
Sep 18 06:02:06 mynas network[1054]: pppoe: Timeout waiting for PADO packets
Sep 18 06:02:06 mynas network[1054]: Using interface ppp0
Sep 18 06:02:06 mynas network[1054]: Connect: ppp0 <--> /dev/pts/1
Sep 18 06:02:06 mynas pppoe[2418]: Timeout waiting for PADO packets
Sep 18 06:02:06 mynas pppd[1460]: Using interface ppp0
Sep 18 06:02:06 mynas pppd[1460]: Connect: ppp0 <--> /dev/pts/1
Sep 18 06:02:37 mynas pppd[1460]: LCP: timeout sending Config-Requests
Sep 18 06:02:37 mynas network[1054]: LCP: timeout sending Config-Requests
Sep 18 06:02:37 mynas network[1054]: Connection terminated.
Sep 18 06:02:37 mynas pppd[1460]: Connection terminated.
Sep 18 06:02:37 mynas pppd[1460]: Modem hangup
Sep 18 06:02:37 mynas network[1054]: Modem hangup
Sep 18 06:02:41 mynas pppd[1460]: Using interface ppp0
Sep 18 06:02:41 mynas network[1054]: Using interface ppp0
Sep 18 06:02:41 mynas network[1054]: Connect: ppp0 <--> /dev/pts/2
Sep 18 06:02:41 mynas pppd[1460]: Connect: ppp0 <--> /dev/pts/2
Sep 18 06:02:41 mynas network[1054]: pppoe: Timeout waiting for PADO packets
Sep 18 06:02:41 mynas pppoe[2522]: Timeout waiting for PADO packets
Sep 18 06:03:12 mynas pppd[1460]: LCP: timeout sending Config-Requests
Sep 18 06:03:12 mynas network[1054]: LCP: timeout sending Config-Requests
Sep 18 06:03:12 mynas network[1054]: Connection terminated.
Sep 18 06:03:12 mynas pppd[1460]: Connection terminated.
Sep 18 06:03:12 mynas pppd[1460]: Modem hangup
Sep 18 06:03:12 mynas network[1054]: Modem hangup
Sep 18 06:03:16 mynas pppd[1460]: Using interface ppp0
Sep 18 06:03:16 mynas network[1054]: Using interface ppp0
Sep 18 06:03:16 mynas network[1054]: Connect: ppp0 <--> /dev/pts/1
Sep 18 06:03:16 mynas pppd[1460]: Connect: ppp0 <--> /dev/pts/1
Sep 18 06:03:16 mynas network[1054]: pppoe: Timeout waiting for PADO packets
Sep 18 06:03:16 mynas pppoe[2581]: Timeout waiting for PADO packets
Sep 18 06:03:47 mynas pppd[1460]: LCP: timeout sending Config-Requests
Sep 18 06:03:47 mynas network[1054]: LCP: timeout sending Config-Requests
Sep 18 06:03:47 mynas network[1054]: Connection terminated.
Sep 18 06:03:47 mynas pppd[1460]: Connection terminated.
Sep 18 06:03:47 mynas pppd[1460]: Modem hangup
Sep 18 06:03:47 mynas network[1054]: Modem hangup
Sep 18 06:03:51 mynas network[1054]: pppoe: Timeout waiting for PADO packets
Sep 18 06:03:51 mynas pppoe[2635]: Timeout waiting for PADO packets
Sep 18 06:03:51 mynas pppd[1460]: Exit.
Sep 18 06:03:51 mynas network[1054]: [FAILED]
Sep 18 06:03:51 mynas systemd[1]: network.service: Control process exited, code=exited, status=1/FAILURE
Sep 18 06:03:51 mynas systemd[1]: network.service: Failed with result 'exit-code'.
Sep 18 06:03:51 mynas systemd[1]: Failed to start LSB: Bring up/down networking.


The x2go postgres pacakge seems to depend on 9.4 and can't remove postgres 9.4 without removing x2g postgres support.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 18th, '19, 10:39

Please provide the output of the following commands as root:

Code: Select all
ps -ef|grep -v grep|grep -iE "net|wpa"
ifconfig -a
ls -al /etc/sysconfig/network-scripts/ifcfg*
ls -alR /etc/ppp/


msdobrescu wrote:The x2go postgres pacakge seems to depend on 9.4 and can't remove postgres 9.4 without removing x2g postgres support.

No it does not, it only depends on the virtual Requires postgresql-server which is provided by every postgresql-server package.

Code: Select all
[doktor5000@Mageia7]─[10:35:09]─[~] urpmq --requires x2goserver-postgresql
--requires behaviour changed, use --requires-recursive to get the old behaviour
perl-DBD-Pg
postgresql-server
[doktor5000@Mageia7]─[10:38:28]─[~]
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 18th, '19, 18:40

Hi, here we go:

Code: Select all
ps -ef|grep -v grep|grep -iE "net|wpa"
root        33     2  0 17:35 ?        00:00:00 [netns]
root       883     1  0 17:35 ?        00:00:02 /usr/sbin/NetworkManager --no-daemon
root      3021     1  0 17:39 ?        00:00:00 /usr/sbin/xinetd -stayalive -dontfork
root      4484  4463  0 19:35 pts/3    00:00:00 /usr/libexec/webkit2gtk-4.0/WebKitNetworkProcess 5 14


Code: Select all
ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet a.b.c.d  netmask 255.255.255.0  broadcast a.b.c.255
        inet6 fe80::225:22ff:fe26:90f3  prefixlen 64  scopeid 0x20<link>
        ether 00:25:22:26:90:f3  txqueuelen 1000  (Ethernet)
        RX packets 77600  bytes 21976827 (20.9 MiB)
        RX errors 0  dropped 3  overruns 0  frame 0
        TX packets 63397  bytes 199824317 (190.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 91246  bytes 201504938 (192.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 91246  bytes 201504938 (192.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Code: Select all
ls -al /etc/sysconfig/network-scripts/ifcfg*
-rwxr-xr-x 1 root root 234 Sep 16 23:08 /etc/sysconfig/network-scripts/ifcfg-enp0s10*
-rwxr-xr-x 1 root root 422 Sep 18 06:18 /etc/sysconfig/network-scripts/ifcfg-eth0*
-rw-r--r-- 1 root root 254 Feb 15  2019 /etc/sysconfig/network-scripts/ifcfg-lo
-rwxr-xr-x 1 root root  88 Jun 27  2013 /etc/sysconfig/network-scripts/ifcfg-ppp0*


Code: Select all
ls -alR /etc/ppp/
/etc/ppp/:
total 108
drwxr-xr-x   5 root root    4096 Sep 17 21:58 ./
drwxr-xr-x 178 root root   20480 Sep 18 18:40 ../
-rw-------   1 root daemon   111 Jun 27  2013 chap-secrets
-rw-------   1 root daemon    78 Oct 15  2016 chap-secrets.rpmnew
lrwxrwxrwx   1 root root      32 Feb 22  2019 connect-errors -> ../../var/log/ppp/connect-errors
-rw-r--r--   1 root root    2276 Oct  1  2018 firewall-masq
-rw-r--r--   1 root root     978 Oct  1  2018 firewall-standalone
-rwxr-xr-x   1 root root     938 Aug 30  2014 ip-down*
drwxr-xr-x   2 root root    4096 Sep 16 06:01 ip-down.d/
-rwxr-xr-x   1 root root    3218 Aug 30  2014 ip-down.ipv6to4*
-rwxr-xr-x   1 root root    1084 Aug 30  2014 ip-up*
drwxr-xr-x   2 root root    4096 Sep 16 06:01 ip-up.d/
-rwxr-xr-x   1 root root    6430 Aug 30  2014 ip-up.ipv6to4*
-rwxr-xr-x   1 root root    1691 Aug 30  2014 ipv6-down*
-rwxr-xr-x   1 root root    3191 Aug 30  2014 ipv6-up*
-rw-------   1 root daemon    36 Feb 22  2019 options
-rw-------   1 root root     422 Sep 29  2018 options.pptp
-rw-------   1 root daemon   110 Jun 27  2013 pap-secrets
-rw-------   1 root daemon    77 Oct 15  2016 pap-secrets.rpmnew
drwxr-xr-x   2 root root    4096 Jan 22  2014 peers/
-rw-r--r--   1 root root    4524 Oct  1  2018 pppoe.conf
-rw-r--r--   1 root root     104 Oct  1  2018 pppoe-server-options
lrwxrwxrwx   1 root root      25 Feb 22  2019 resolv.conf -> ../../run/ppp/resolv.conf

/etc/ppp/ip-down.d:
total 12
drwxr-xr-x 2 root root 4096 Sep 16 06:01 ./
drwxr-xr-x 5 root root 4096 Sep 17 21:58 ../
-rwxr-xr-x 1 root root  777 Apr  1 01:36 postfix*

/etc/ppp/ip-up.d:
total 12
drwxr-xr-x 2 root root 4096 Sep 16 06:01 ./
drwxr-xr-x 5 root root 4096 Sep 17 21:58 ../
-rwxr-xr-x 1 root root  750 Apr  1 01:36 postfix*

/etc/ppp/peers:
total 12
drwxr-xr-x 2 root root 4096 Jan 22  2014 ./
drwxr-xr-x 5 root root 4096 Sep 17 21:58 ../
-rwxr-xr-x 1 root root  251 Jun 27  2013 ppp0*
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 18th, '19, 20:11

Something new: "Unable to authenticate/execute the action: 4" at system settings systemd commands to enable services, start services etc..
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 18th, '19, 22:23

Can you please stop mangling all different kinds of issues into one thread?

Regarding the pppoe issue, either you try to run drakconnect --del and see if the ppp interface is selectable there for removal or you manually delete / move away /etc/sysconfig/network-scripts/ifcfg-ppp0 and /etc/ppp/peers/ppp0
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby msdobrescu » Sep 18th, '19, 23:55

Thanks! This one solved it, but still, I don't understand why are there several applets for the same thing, that should see both the same settings, but they don't...
I've removed Postgres as it was not used anymore, actually.
msdobrescu
 
Posts: 213
Joined: Jun 2nd, '11, 07:28

Re: OMG! Upgrade crashed!

Postby doktor5000 » Sep 20th, '19, 00:03

Please mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: OMG! Upgrade crashed!

Postby morgano » Sep 22nd, '19, 17:42

doktor5000 wrote:
msdobrescu wrote:IMHO, packages should be downloaded ALL first, then do the upgrade, unless specified not to.

Not everybody has that much space available.

Apart from that, this is mentioned in the "Please note!" section here on how to do that:
https://wiki.mageia.org/en/Mageia_7_Rel ... _.28CLI.29


That description is good, except the mention of needed free space of 40% of the /var partition which i find cryptic and started a thread on doc and qa mailing lists for it.


Anyhow, you can download the classic installer iso, boot and upgrade using that. If your internet connection is somewhat reliable, add updates repos when asked - if not then do an update after install.


msdobrescu wrote:I don't understand why are there several applets for the same thing, that should see both the same settings, but they don't...

It is complicated to support several desktops in one distro, there will be several tools available for the same thing, doing slightly differently. But wifi configuration is being improved for Mageia 8.
Mandriva since 2006, Mageia 2011 at home & work. Thinkpad T40, T43, T400, T510, Dell M4400, M6300, Acer Aspire 7. Workstation using LVM, LUKS, VirtualBox, BOINC
morgano
 
Posts: 1306
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden


Return to General discussions about Mageia

Who is online

Users browsing this forum: No registered users and 1 guest