USM - Updates fail
USM - Updates fail
Greetings,
I have installed Porteus on a Wyse R90L thin client machine and all appears to run in pretty good order. I next wanted to install Xastir. I decided to first go through the update manager tool. As soon as I start the application, it pops up with a notice that indicates missing database files with an instructional message to run 'updates'. I run the updates by selecting 'update all' from the drop down menu and a terminal window opens showing the progress of file downloads etc. The process consistently fails at one point - txt.gz (I think this is the correct name - I am not in front of the machine currently as I write this). It comes up with a 'failure' message. I am not sure what to look for and why it consistently quits the process at this same point each time. Any ideas? Thanks
I have installed Porteus on a Wyse R90L thin client machine and all appears to run in pretty good order. I next wanted to install Xastir. I decided to first go through the update manager tool. As soon as I start the application, it pops up with a notice that indicates missing database files with an instructional message to run 'updates'. I run the updates by selecting 'update all' from the drop down menu and a terminal window opens showing the progress of file downloads etc. The process consistently fails at one point - txt.gz (I think this is the correct name - I am not in front of the machine currently as I write this). It comes up with a 'failure' message. I am not sure what to look for and why it consistently quits the process at this same point each time. Any ideas? Thanks
- Ed_P
- Contributor
- Posts: 8367
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
USM - Updates fail
It means one of the mirrors has a corrupted file. There are a couple of options to try. Check out this thread: [INFO & SCRIPT] Slackware Mirror Settings for USM for one approach. And this posting for another: Re: Save files (Post by Ed_P #54673).
-edit-
Changed links to http from https.
-edit-
Changed links to http from https.
Ed
USM - Updates fail
I'm a fellow newbie but this was my simple solution to the USM update failing on the salix repository:
1. Create the following folder path in rootcopy: /mnt/sda1/porteus/rootcopy/etc/usm
2. Copy in mirrors-salix.txt from etc/usm
3. Edit this mirrors-salix by commenting out the uncommented mirror (i.e. the dud one) and uncommenting any other one
4. Reboot and Hey Presto!
1. Create the following folder path in rootcopy: /mnt/sda1/porteus/rootcopy/etc/usm
2. Copy in mirrors-salix.txt from etc/usm
3. Edit this mirrors-salix by commenting out the uncommented mirror (i.e. the dud one) and uncommenting any other one
4. Reboot and Hey Presto!
- Ed_P
- Contributor
- Posts: 8367
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
USM - Updates fail
Actually this approach works just editing the file in /etc/usm and restarting USM.
Ed
USM - Updates fail
OH - I had missed these responses (the response notifier must have died on me) and moved on to give Puppy Linux a try. Puppy installed and updated itself, however, I have not been able to successfully get Wine to install and run so I could get the APRS program up and running. I still have my Porteus ISO file, so I may go back to this distribution (I do like the appearance of it better than Puppy) and then give the above steps a try. Thanks
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
USM - Updates fail
For a newbie you did surprisingly well! This is exactly what I would have done. Everything exactly the same, except for the puppy part.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
USM - Updates fail
Hi - this issue continues to be a pest... I tried the steps outlined by Cestrian in #3 above - commented / un commented different mirror sites and still am not having any luck at getting this to work. At one point it made it to the point of updating the database for slackware and then upon completion - it died while updating the confg file. Any other solutions? I wonder if all the mirrors are down..... Thanks
USM - Updates fail
Thanks - Ed, please give me a little bit more explanation for this.
- Ed_P
- Contributor
- Posts: 8367
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
USM - Updates fail
It's in the link I posted previously. [INFO & SCRIPT] Slackware Mirror Settings for USM
-edit-
Changed https to http in above link.
-edit-
Changed https to http in above link.
Ed
USM - Updates fail
Hi Ed - I tried the link you provided above as well as the one further up in this thread and both are blocked by my virus/malware filtering as an 'unsafe site'. There might be a virus or other buggy running around on the site. Do you know if that site has ads? It might be in one of the ads. I will continue to search for other ways around this. Right now, my Porteus install is dead since I am not able to install any other applications such as Wine and my APRS applications.
-
- Full of knowledge
- Posts: 2069
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
USM - Updates fail
@geocacher + @all
these links are https ones
the reason a browser claims that is is a 'unsafe site' is because
The certificate expired on 12/14/2017 03:02 PM.
shorten the links to http to open them.
these links are https ones
the reason a browser claims that is is a 'unsafe site' is because
The certificate expired on 12/14/2017 03:02 PM.
shorten the links to http to open them.
- Ed_P
- Contributor
- Posts: 8367
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
USM - Updates fail
I looked in my crystal ball and it said you're doing something wrong.fighter fish wrote: ↑02 Apr 2019, 16:24I can't get the first two scripts working in the first place. Any idea what's going on? Thanks!
With a little more information, like what happens when you try the sesm.sh script would help and knowing if you performed a chmod +x on the scripts after you saved them.
Ed