Koozali.org: home of the SME Server
Obsolete Releases => SME Server 8.x => Topic started by: winecooler on September 12, 2013, 06:27:35 PM
-
So I have a couple of other active threads going.... put simply the old tech who installed this back up sme server is gone and I want to know what it was backing up. I believe it was windows server data, unsure if it was a full server backup or workstations or a share folder or ....?
What I need is to hire a new tech with sme or linux expertise but the win server has crashed and I need to see if there is a full backup on this sme server, it's been 2 days and the staff are all standing around with pitchforks. ;)
I have limited linux expertise but I can "cd" and "ls" my way around. server-manager is not working, but to fix that I have to fix the certificate issue, and that's not working... so I'm hoping someone can show me:
1. where to look for volumes on that machine that might contain backups, if any
2. where to look for what kind of backup software package might have been used, so if need be I can use it to restore
3. is it even possible for sme server to back up a baremetal windows server? Or is it likely it was used just to back up user data?
I will continue to pursue the technical fixes to the sme server issues so that at least I can run server-manager and have a look, but until then if anyone can offer any quicker answers to the above, it would be appreciated ;)
-
pm me and I will help out.
Update: bummer, somebody forbids the use of PM on these forums.
-
on the console:
rpm -qa |grep affa
if it returns a positive feedback like an installed affa RPM:
- Backups are in /var/affa
see: http://wiki.contribs.org/Affa
-
Thank you RequestedDeletion... there is no Affa on the machine. I think there's 2 hard drives on the machine, maybe there's some data on the 2nd one?
-
I think there's 2 hard drives on the machine, maybe there's some data on the 2nd one?
The two drives are likely being used in a RAID1 mirror pair for the SME server software and files.
-
winecooler
So you have root access now to the command prompt after resetting the root & admin passwords, correct ?
At present you are NOT able to access the web GUI server manager using https://yourdomain/server-manager, correct ?
What error or message do you receive ?
Can you access the admin console menu from the command prompt ?:" ie type
console
If so, can you then access the text based server manager from the console admin menu ?
What happens or what error message do you get ?
To discover more about your server & how it is configured & potentially what it is doing,
here are a few commands to show us the output of:
df -h
cat /proc/mdstat
cat /proc/version
fdisk -l
/sbin/e-smith/audittools/newrpms
/sbin/e-smith/audittools/templates
/sbin/e-smith/audittools/repositories
This should tell us a lot about your server & what it is doing
-
So you have root access now to the command prompt after resetting the root & admin passwords, correct ?
At present you are NOT able to access the web GUI server manager using https://yourdomain/server-manager, correct ?
What error or message do you receive ?
Yes I have root. Correct, I cannot access web gui, if I use http://... it gives me (111) connection refused, and if I use https://... I get "couldn't establish a connection to the server". I can ping the machine from that Windows workstation, so I know it's there.
Can you access the admin console menu from the command prompt ?:" ie type
console
If so, can you then access the text based server manager from the console admin menu ?
What happens or what error message do you get ?
Whaaaat, there's a text based server manager?! Coolbeans.... server status is up, internet access = good, raid in a clean state, but when I try to access the text based server manager from there, it says "connection refused". This probably has something to do with its expired certificate issue (http://forums.contribs.org/index.php/topic,50195)?
To discover more about your server & how it is configured & potentially what it is doing,
here are a few commands to show us the output of:
These are handwritten notes carried to another machine, so bear with me if i leave out details, i can run them again if need be:
df -h
/dev/mapper/main-root 82% use% on /
/dev/md1 44% on /boot
none 0% on /dev/shm
cat /proc/mdstat
active raid1
cat /proc/version
Linux 2.6.9-89.31.1 ELsmp
fdisk -l
/dev/hda 320gb linux raid autodetect
/dev/md1 106mb
/dev/md2 319gb
/dev/dm-0 319gb
/dev/dm-1 536mb
/sbin/e-smith/audittools/newrpms
cannot find a valid baseurl for repo: base
plugins: installonlyn, smeserver, fastestsomething (can't read my writing lol), protect packages, not using ftp, http(s), or file for repos, skipping 4 is not a valid release
/sbin/e-smith/audittools/templates
..templates-custom/home/e-smith/ssl.crt: manually_added, override
.../etc/crontab/weeklybackup.cronjob manually added, addition
dailybackup.cronjob manually added, addition
disk space watchdog.cronjob manually added, addition
syncwindowsshare.cronjob manually added, addition
dailypurge.cronjob manually added, addition
monthlybackup.cronjob manually added, addition
/smb.conf/11serverstring.cronjob manually added, override
/sbin/e-smith/audittools/repositories
disabled: addons, centosplus, extras, smecontribs,smedev,smetest,smeupdates-testing
enabled: base, smeaddons, smeextras,smeos,smeupdates
The thing that sticks out to me is: syncwindowsshare.cronjob ... that might suggest its backing up windows shares?
-
winecooler
cat /proc/version
Linux 2.6.9-89.31.1 ELsmp
That appears to be a sme7.x server
We do need the complete output details of those commands to see the whole picture.
Do these first
df -h
cat /proc/mdstat
Does midnight commander run ? type
mc
The thing that sticks out to me is: syncwindowsshare.cronjob ... that might suggest its backing up windows shares?
You can navigate the menus/folders using mc & read the file contents of the cron job(s) to see what they are doing
That will give some more clues
or at command prompt do
cat /etc/cron.daily/cronjobname
(put in the actual correct details)
I think you need to stabilize your machine before you investigate what it is doing backup wise.
See my queries in your certificate post
-
okay here (http://minus.com/mTNSGKG8KMZiW)are some more pics. The cron jobs look like they are old, i'm guessing they came with the install.
-
winecooler
/sbin/e-smith/audittools/newrpms
cannot find a valid baseurl for repo: base
plugins: installonlyn, smeserver, fastestsomething (can't read my writing lol), protect packages, not using ftp, http(s), or file for repos, skipping 4 is not a valid release
You are getting errors here & the command cannot complete, because sme7.6 went EOL (end of life) some time ago.
The repos had to be changed on the server.
There were updates to fix this IIRC
You need to reconfigure the repos correctly.
We then start getting into a lot of troubleshooting issues with a dysfunctional sme 7.6 server, and we do not know how long that will take & how much will need to be fixed.
We are not even sure if your sme7.x is really up to date ie does it have the last set of releases for sme7.6.
It may be better (less effort on our part) for you to upgrade to sme8 & sort out any problems you have then.
My guess is that many issues may resolve themselves.
Not sure if this is the wisest approach as it would be good to know what is functional in you server first, ie is the RAID really RAID1, are both drives alive or is the array degraded, ie only one drive functioning.
Do you have backups of the server if something went wrong during the sme7.x to sme8 upgrade.
Many questions ???
please show output of
db yum_repositories show base
db yum_repositories show smeupdates
What does this show
yum update
cancel the update by answering n to play safe for now
If that errors out too much, then do (& show us the output) we just need the list of rpms to be updated
yum update --disablerepo=base --disablerepo=smeupdates
also cancel with n to be safe for now
-
winecooler
OK those pics show us you have 2 x320Gb drives hda & hdc in RAID1 array
The array is in sync & healthy (the UU part)
This all looks good.
show us a pic of
df -h
to check space usage, lack of space is known to stop http
-
winecooler
show us a pic of
df -h
Oops sorry, I see that now.
53Gb available space
& 53M available om boot
so all that is OK too.
-
I really appreciate your help, this board is lucky to have someone as responsive as you.
Although I understand what you are saying about fixing the problems/upgrading etc, all I really want to know is, what is the purpose of this server? If the server is doing nothing useful, then there's no point upgrading it, I'll just shut it down forever. Even if it is actually running some kind of backup, I'll just replace it with something I know asap.
I will get photos of the yum things you ask for if it will help
thanks again janet!
-
winecooler
....what is the purpose of this server?
.....Even if it is actually running some kind of backup, I'll just replace it with something I know asap.
I cannot answer that at this stage, more info needed.
It would be very useful to get access to server manager to see if any backups are configured there.
There could be other systems/contribs/whatever running from command line cron jobs that do not even appear in server manager.
We need to get a proper listing of the rpms installed, so need to resolve the old repos issue, catch 22.
Read my earlier post queries & respond.
-
yummy stuff (http://minus.com/mbgNG6AZPpPlXk)
-
winecooler
yummy stuff
The issue is as explained before, you have old repos, at least for base.
The centos vault location now needs to be set.
I suggest some reading on the closed sme7 forums, here is a starting point.
http://forums.contribs.org/index.php/topic,48424.0.html
Update your server as described & eventually you will get the right repos setup & the the right packages installed.
PS Then you will be able to run the earlier requested command to see what other rpms are installed, which will give us clues about what that server is doing.
It may even fix your certificate issues.
I have asked you for some feedback in that other post, so still waiting for those answers.
You should be able to reset the certificate if done correctly, so it's just a matter of finding out what is wrong.
-
Now that the certificates issue is fixed, I followed the instructions in that link above to update. Unfortunately, I'm getting:
...
setting up repositories
cannot find a valid baseurl for repo: smeaddons
Error: cannot find a valid baseurl for repo: smeaddons
When I run rpm -q smeserver-yum it reports version smeserver-yum-2.0.0-11.sme, even when I run the update again. The thread talks about upgrading .14 or .15 to .16, but I can't even get to .14 as it appears to be stuck on .11. Going to try a signal-event post-upgrade and reboot next.... stand by
-
oops didn't notice the last post on that thread with new commands...
ran it and got error: cannot find a valid baseurl for repo: smeos
running upgrade and reboot again....
-
winecooler
running upgrade and reboot again....
Has that fixed your repos ?
Can you do a
yum update
now without getting errors ?
If you stll cannot get the latest smeserver-yum installed,
then for 32 bit system there is v 2.0.0-17
At sme command prompt do
wget http://distro.ibiblio.org/smeserver/releases/obsolete/7.6/smeupdates/i386/RPMS/smeserver-yum-2.0.0-17.el4.sme.noarch.rpm
(the above is all on one line)
yum localinstall smeserver-yum
signal-event post-upgrade
signal-event reboot
You may have to also download using wget some other dependency packages if that is indicated by error messages, so wget those too, to the same folder & then repeat the yum localinstall command as above
Then I assume you will be able to do
yum update
signal-event post-upgrade
signal-event reboot
PS The whole tree showing the current sme obsolete repos for sme7.6 are here.
http://distro.ibiblio.org/smeserver/releases/obsolete/7.6/
-
No it didn't work, still stuck at smeserver-yum-2.0.0-11.sme. Still get same error. Okay will try .17 install and report back here.
-
It downloaded the file successfully, "...response 200 OK," " smeserver-yum-2.0.0-17.el4.sme.noarch.rpm saved" 86976 (bytes I'm assuming)
But when I tried to install it, it says:
Setting up Local Package Process. Cannot open file smeserver-yum. Skipping. Nothing to do.
I'm in /root, do I need to be in a particular folder?
-
winecooler
Did you use exactly the same commands I advised ?
It sounds to me like the downloaded file is corrupt. Delete it, download it again, & try the yum localinstall command again.
It is OK to be in /root (or any folder for that matter), as long as the file has been downloaded to the same folder.
To check do
la -al
-
I reviewed your commands, they are identical. I rm'd the file, wgetted it again, did a yum localinstall and it failed again with that same error message. Just in case the file was corrupted during the download process, I tried it 4 more times, all with the same result. Perhaps the file itself on the site is corrupt?
-
winecooler
Seems odd. Try the -16 version from here. Change the wget command appropriately
http://distro.ibiblio.org/smeserver/releases/obsolete/7.6/smeos/i386/SME/RPMS/
-
I deleted the rpm, wgetted the 16 version:
wget http://distro.ibiblio.org/smeserver/releases/obsolete/7.6/smeos/i386/SME/RPMS/smeserver-yum-2.0.0.16-el4.sme.noarch.rpmResponse 200-OK, file saved. Ran "yum localinstall smeserver-yum" Exact same error message:
Setting up Local Package Process. Cannot open file smeserver-yum. Skipping. Nothing to do.
-
winecooler
Oops, it was late here when answering you.
Specify the full rpm name or packagename* when doing yum localinstall
ie
wget http://distro.ibiblio.org/smeserver/releases/obsolete/7.6/smeupdates/i386/RPMS/smeserver-yum-2.0.0-17.el4.sme.noarch.rpm
(the above is all on one line)
yum localinstall smeserver-yum-2.0.0-17.el4.sme.noarch.rpm
(the above is all on one line)
then follow with
signal-event post-upgrade
signal-event reboot
You may have to also download using wget some other dependency packages if that is indicated by error messages, so wget those too, to the same folder & then repeat the yum localinstall command as above
-
Aha! I didn't realize I needed to spell out the whole thing. 16 worked successfully, I will do the same with 17 and anything else and report back here later tonight. :D
-
winecooler
I usually use
yum localinstall smeserver-yum*
but inadvertantly left the * out
-
winecooler
With the latest smeserver-yum installed, you should be able to successfully run
yum update
The correct repos should be set by the smeserver-yum install
Check them with
db yum_repositories show |more
You should see references to sme obsolete repos & centos vault repos in the MirrorList settings
-
I'm not sure what you are saying. when you say I should be able to successfully run yum update, do you mean the last post in here (http://forums.contribs.org/index.php/topic,48424.msg242366.html#msg242366)?
If so I get the error "Cannot find a valid baseurl for repo: smeos"
and I thought Windows updates were a pain :mad:
-
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
-
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.
-
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 ?
-
Since I can't cut & paste between my Windows forum reading of this and my terminal session
use putty ;-)
-
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.
-
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
-
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.
-
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.
-
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
-
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 ;)
-
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?
-
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
-
yum update --disablerepo=smeaddons --disablerepo=smeextras
[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 ?
-
fyi:
[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
-
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
-
winecooler
I just reviewed the earlier post about resetting default repos.
Please do this
confirm you have version 17 smeserver-yum installed
rpm -q smeserver-yum
If it is not installed then do this
yum clean all
(copy and paste the following lines, note the "obsolete" tree location):
rpm -Uhv \
http://mirror.canada.pialasse.com/releases/obsolete/\
/7.6/smeupdates/i386/RPMS/smeserver-yum-2.0.0-17.el4.sme.noarch.rpm
then do
signal-event yum-update
and check with
rpm -q smeserver-yum
When you are sure v 17 is installed
then do
mv /home/e-smith/db/yum_repositories /home/e-smith/db/yum_repositories.po2
/etc/e-smith/events/actions/initialize-default-databases
signal-event post-upgrade
signal-event reboot
The post-upgrade & reboot were missing from the earlier command in this thread & perhaps the default repos did not get reset correctly.
It's worth trying again as that is probably the easiest way to reset them.
-
this will help me move along a little faster now ;)
Good. Now to get back to your original problem, you can see what files are located on that server by doing:
ls -R /home/e-smith/files | less
Or use 'mc' to browse around.
I haven't been following in detail - why are you going to so much trouble to update that system?
-
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
output:
[root@backup ~]# rpm -q smeserver-yum
warning: only V3 signatures can be verified, skipping V4 signature
smeserver-yum-2.0.0-17.el4.sme
[root@backup ~]# db yum_repositories show smeos
smeos=repository
EnableGroups=yes
GPGCheck=yes
MirrorList=http://mirrorlist.contribs.org/mirrorlist/smeos-7
Name=SME Server - os
Visible=yes
status=enabled
[root@backup ~]# db yum_repositories show smeupdates
smeupdates=repository
EnableGroups=yes
GPGCheck=yes
MirrorList=http://mirrorlist.contribs.org/mirrorlist/smeupdates-7
Name=SME Server - updates
Visible=yes
status=enabled
[root@backup ~]# db yum_repositories show smecontribs
smecontribs=repository
EnableGroups=yes
GPGCheck=yes
MirrorList=http://mirrorlist.contribs.org/mirrorlist/smecontribs-7
Name=SME Server - contribs
Visible=no
status=disabled
[root@backup ~]# db yum_repositories show base
base=repository
BaseURL=http://vault.centos.org/4.9/os/$basearch
EnableGroups=no
Exclude=kernel,kernel-smp,kernel-xenU,mkinitrd,mdadm,initscripts
GPGCheck=yes
Name=CentOS - os
Visible=yes
status=enabled
[root@backup ~]# db yum_repositories show updates
updates=repository
BaseURL=http://vault.centos.org/4.9/updates/$basearch
EnableGroups=no
Exclude=kernel,kernel-smp,kernel-xenU,mkinitrd,mdadm,initscripts
GPGCheck=yes
Name=CentOS - updates
Visible=yes
status=enabled
[root@backup ~]#
-
Good. Now to get back to your original problem, you can see what files are located on that server by doing:
ls -R /home/e-smith/files | less
Or use 'mc' to browse around.
I haven't been following in detail - why are you going to so much trouble to update that system?
From the OP: "put simply the old tech who installed this back up sme server is gone and I want to know what it was backing up. I believe it was windows server data, unsure if it was a full server backup or workstations or a share folder or ....?" There is a new Windows back up system in place now, but I am still curious what the purpose of this smeserver box is/was. Actually I had no plans whatsoever to update it, but janet has been graciously helping me and insists on it.
I found some backup data in an ibays folder, the weekly is from 2012 only, and there appears to be dailies from this year but only for a few selected employees rather than all. hmm. The old tech couldn't print his own name properly let alone document anything he did, job security I'm guessing, and now the company has paid the price for it.
-
winecooler
The reason for suggesting to update was to get rid of repo errors, which were interfering with running diagnostics.
You do not have to update if you do not want to.
I saw it as a simple way to get your box fixed, but your lack of knowledge & skills has hampered a simple enough exercise.
The base & updates repos appear correct, I'm not sure about the other repos, would have to check an old sme7 box.
Maybe someone else can advise.
Can you do these now (without errors) ?
/sbin/e-smith/audittools/newrpms
This will advise what backup contribs (if any) are installed.
Does server manager work from a workstation ?
https://serverIP/server-manager
replace with your server local IP
In server manager you can see what backup jobs are setup.
Also see this to see if a default backup is set
config show backupwk
-
Yes, server manager works from a workstation now. root doesn't work I found out, but Admin does.
In server manager, when I click on Backups, it says "tape backups are disabled. workstation backups are disabled."
There is no tape drive in the backup server.
When I go to "Configure workstation backup", it shows:
Workstation IP or hostname = host <--- there is no machine on the network named "host"
backup share = share <--- I cannot find a share on the network called "share"
My guess is that these are default values, and it was never configured?
There are, however, a bunch of entries under ibays that correspond to company resources. Am going to see what I can find under these. None are configured for web or ftp access. Where on the folder structure are these ibays located? I can't seem to find them using mc.
[root@backup files]# clear
[root@backup files]# /sbin/e-smith/audittools/newrpms
Cannot find a valid baseurl for repo: smeupdates
Loading "installonlyn" plugin
Loading "smeserver" plugin
Loading "fastestmirror" plugin
Loading "protect-packages" plugin
[root@backup files]# config show backupwk
backupwk=service
BackupTime=22:00
Compression=6
CompressionProg=gzip
DaysInSet=1
IncOnlyTimeout=no
Login=backup
Password=backup
Program=dar
SetsMax=1
SmbHost=host
SmbShare=share
Timeout=8
VFSType=cifs
status=disabled
-
Where on the folder structure are these ibays located?
All ibays are located in a subfolder of the "/home/e-smith/files/ibays" folder. Log in with PuTTY and type:
mc /home/e-smith/files/ibays
You'll see a directory listing of all ibays. The "Primary" ibay is SME's default ibay. If there's no web access enabled for a particular ibay, it's files will be located in a subfolder "files", e.g. if there's an ibay called "foobar" then it's files are located in "/home/e-smith/files/ibays/foobar/files".
-
When I do an "ls -al" or use mc, it shows the dates on the backup files as "20 Sept" but it doesn't say a year. How do I get it to display the year?
Also, the files are in .tar.gz format, is there I tool I can use to browse these gzip files?
-
Okay poked around some more and it looks like the backup files are from 2009 - 2011. Awesome. (not)
Thank you guys, especially Janet, for all your help. :)
-
winecooler
Cannot find a valid baseurl for repo: smeupdates
For the time being you could temporarily disable that repo using
db yum_repositories setprop smeupdates status disabled
signal-event yum-modify
Then try
/sbin/e-smith/audittools/newrpms
server manager works from a workstation now. root doesn't work I found out, but Admin does.
Only admin user can access server manager
it shows the dates on the backup files as "20 Sept" but it doesn't say a year. How do I get it to display the year?
IIRC, usually they are recent files & it is the current year. Older file dates will show the year.
-
winecooler
config show backupwk
backupwk=service
BackupTime=22:00
status=disabled
The backup is disabled.
I would be looking more closely at the cron jobs you mentioned earlier in this thread.
I gave instructions how to read them, or you can use the viewer (F3) in mc.
-
winecooler
The sme 7 mirror repos were removed so the MirrorList property is non functional.
Setting the repos to something that works ie looks at the obsolete tree locations, should resolve your errors
db yum_repositories set smecontribs repository \
BaseURL 'http://mirror.canada.pialasse.com/releases/obsolete/7.6/smecontribs/$basearch' \
EnableGroups yes \
GPGCheck yes \
Name 'SME Server - smecontribs' \
Visible yes \
status disabled
db yum_repositories set smeos repository \
BaseURL 'http://mirror.canada.pialasse.com/releases/obsolete/7.6/smeos/$basearch' \
EnableGroups yes \
GPGCheck yes \
Name 'SME Server - smeos' \
Visible yes \
status enabled
db yum_repositories set smeupdates repository \
BaseURL 'http://mirror.canada.pialasse.com/releases/obsolete/7.6/smeupdates/$basearch' \
EnableGroups yes \
GPGCheck yes \
Name 'SME Server - smeupdates' \
Visible yes \
status enabled
db yum_repositories delprop smecontribs MirrorList
db yum_repositories delprop smeos MirrorList
db yum_repositories delprop smeupdates MirrorList
signal-event yum-modify
yum clean all