Topic: what is this sme box used for?

[janet]

winecooler

sme7.6 went end of life in 2012 over a year ago. The issue is you are updating a system well after support has discontinued, it was problematic then because centos suddenly moved all files to a different vault repository & eventually so did sme server (to obsolete tree).
Now it is even more difficult because I have forgotten much of what was happening then.
Those old posts are probably less applicable now than they were then.

If your repository settings are not correct & pointing to the CURRENT centos vault & smeserver obsolete locations, then you will keep getting errors.
The goal here is to get the repo settings correct in the yum_repositories database on sme server.
If you had shown me the respository info requested then we would know what is going on, but your supply of precise information is lacking.

As you have updated to a recent version of smeserver-yum then try
cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases

Then do
yum clean all

This will reset repos to standard as per the version of smeserver-yum you have installed, which is hopefully the current values & then you can do a normal yum update

[janet]

winecooler

This post in the sme 7 closed forums is essentially what we were trying to do.
http://forums.contribs.org/index.php/topic,49361.0.html

It seems to imply that you need to have the -17 version installed, so please do that.
Then yum update your system & see if all your other problems have gone away.

As you were having ongoing issues getting the rpms installed, then I suggested other workaround methods.
Just get -17 installed & see how you go then.

[winecooler]

This post in the sme 7 closed forums is essentially what we were trying to do.
http://forums.contribs.org/index.php/topic,49361.0.html

Since I can't cut & paste between my Windows forum reading of this and my terminal session, I have to manually type the commands out. I don't understand the "\" at the end of the lines is? I copied them exactly in 1 long line but it errors out. Do I leave out the "\" or ?

[Stefano]

Since I can't cut & paste between my Windows forum reading of this and my terminal session

use putty

[janet]

winecooler

Since I can't cut & paste between my Windows forum reading of this and my terminal session, I have to manually type the commands out. I don't understand the "\" at the end of the lines is? I copied them exactly in 1 long line but it errors out. Do I leave out the "\" or ?

With the slash at the end you DO NOT put everything in one long line.
After each slash (as shown at the end of each line) you press the Enter key, this will allow more input on the next line, but it remains as part of the one long command.

So either enter the command all on 1 long line WITHOUT the slash(es) (\), or do it line by line as shown in the forum post, WITH the slash at the end of each line followed by pressing Enter key.

Just install VERSION -17 & get on with it, I have given you two ways, either yum localinstall or rpm -Uvh download/install.
Come on !

This whole thing was really a 5 or 10 minute job & it has gone on for days.
Just DO IT please.

[winecooler]

I think it would go a lot faster if I could cut and paste, but when I run putty to the sme server it says "connection refused". Stefano, any idea on how to fix this?

It is taking long probably because of timing, I run a few commands while you are presumably sleeping, then await for you to return the next day, but then I don't get back here to see them until typically until you are offline again. Probably just a time zone issue. As well if you recall, I wanted to see if this server was used for backups because the main office file server boot drive failed, and I've been focusing on recovering that (which I did without backups). But I'm still curious to see what this box is used for.

Anyhow it looks like we're at .17 now, though I'm still getting the "cannot find a baseurl for repo: smeaddons", but I'll try to fix that once I can get connected with putty. It should make trying out commands using cut'n'paste significantly faster than memorizing 20 characters at a time and switching computers until a line is complete.

cheers

[winecooler]

I followed the wiki's "useful commands": Enable SSH. I tried both public and private access (followed by a signal-event remoteaccess-update) and using putty on a windows workstation on the same network I get "connection refused"... sigh.

[janet]

winecooler

Anyhow it looks like we're at .17 now, though I'm still getting the "cannot find a baseurl for repo: smeaddons",

One thing at a time please, let's stay focussed.
Get this machine updated at least, with the intent that server manager becomes functional, then you can more easily change settings to get local access using web browser GUI server manager & also Putty ssh access.
That then allows you to see what this machine is doing.
We are following a path to the stated goal, keep going & keep focussed.

Use this command to ignore smeaddons repo as it is no longer used in sme7.6 anyway.

yum update --disablerepo=smeaddons
signal-event post-upgrade
signal-event reboot

Just write the above commands on a piece of paper & then sit in front of the server terminal & re-enter them exactly as shown, it's easy, so let's not make out it's hard to do. Press Enter key at the end of each line.

After that please reset all repos to default values as follows

cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases

(press Enter key at end of each line)

Then do
yum clean all

Then re-run the yum update procedure with just
yum update
signal-event post-upgrade
signal-event reboot

(press Enter key after each line)

Report back here your progress
We can then see if you can access the text based server manager, which will allow you to configure remote access settings for GUI server manager & ssh & any other settings necessary for your network.
We can then also see if you are still receiving any error messages.

[CharlieBrady]

I followed the wiki's "useful commands": Enable SSH. I tried both public and private access (followed by a signal-event remoteaccess-update) and using putty on a windows workstation on the same network I get "connection refused"... sigh.

Perhaps the previous administrator moved sshd to a non-standard port. You'd be able to see that from:

config show sshd

[winecooler]

Perhaps the previous administrator moved sshd to a non-standard port. You'd be able to see that from:

config show sshd

Indeed, it was changed, now I can connect, thanks CB! this will help me move along a little faster now

[winecooler]

yum update --disablerepo=smeaddons
signal-event post-upgrade
signal-event reboot

At the end of the above, it produced this message: "can't find a baseurl for repo: smeextras"

After that please reset all repos to default values as follows

cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases

(press Enter key at end of each line)

Then do
yum clean all

Then re-run the yum update procedure with just
yum update

After the above yum update, it also said "can't find a baseurl for repo: smeextras" but everything else ran just fine with no errors.

signal-event post-upgrade
signal-event reboot

(press Enter key after each line)

Report back here your progress

Everything ran fine except for the smeextras baseurl not found.

We can then see if you can access the text based server manager, which will allow you to configure remote access settings for GUI server manager & ssh & any other settings necessary for your network.
We can then also see if you are still receiving any error messages.

Got putty working now, much easier to work on one machine now. Do we need to fix the smeextras the same way we fixed the smeaddons by doing a disablerepo, or can we ignore it?

[janet]

winecooler

smeextras repo is also no longer used in sme7.6.
I would have thought the smeserver-yum v 17 update would have removed that, but hey maybe your system has not yet updated itself properly ?

Do
yum update --disablerepo=smeaddons --disablerepo=smeextras
signal-event post-upgrade
signal-event reboot

Hopefully many packages will get updated.

To disable those repos permanently do
db yum_repositories setprop smeaddons status disabled
db yum_repositories setprop smeextras status disabled
signal-event yum-modify

After doing all the above successfully without errors, check which repos are enabled
/sbin/e-smith/audittools/repositories

and getting back to the original task you can then do
/sbin/e-smith/audittools/newrpms

And while you are at it, does server manager work from a workstation ?
use
https://serverIP/server-manager
eg
https://192.168.1.33/server-manager
replace with your server local IP

[winecooler]

yum update --disablerepo=smeaddons --disablerepo=smeextras

Code: [Select]

[root@backup ~]# yum update --disablerepo=smeaddons --disablerepo=smeextras
Loading "installonlyn" plugin
Loading "smeserver" plugin
Loading "fastestmirror" plugin
Loading "protect-packages" plugin
Setting up Update Process
Setting up repositories
Cannot find a valid baseurl for repo: smeos
Error: Cannot find a valid baseurl for repo: smeos
[root@backup ~]#

first it's smeaddons, then it's smeextras, now it's smeos... should I --disablerepo=smeos ?

[winecooler]

fyi:

Code: [Select]

[root@backup ~]# /sbin/e-smith/audittools/repositories
addons: disabled
base: enabled
centosplus: disabled
contrib: disabled
extras: disabled
smeaddons: disabled
smecontribs: disabled
smedev: disabled
smeextras: disabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: disabled
updates: enabled


[janet]

winecooler

Looks like you still cannot update due to wrong repo settings.

The updates & base repos are from Centos, so we want those enabled (for normal use).
The other three repos that sme has online for sme7.6 in the obsolete tree are smeos, smeupdates and smecontribs. Normally smeos & smeupdates are enabled, & smecontribs is disabled, so those settings looks right.

What is probably not right are the actual BaseURL or MirrorList locations for those repos, so we need to check them. The smseserver-yum update should have fixed those. Please show output of:
rpm -q smeserver-yum
db yum_repositories show smeos
db yum_repositories show smeupdates
db yum_repositories show smecontribs
db yum_repositories show base
db yum_repositories show updates

/sbin/e-smith/audittools/repositories
base: enabled
smeos: enabled
smeupdates: enabled
updates: enabled