Topic: SME 7.0beta4 to current

[schmerold]

We have a production (yes I know shame on me) server running SME 7.0beta4

Out of the blue dnscache quit working, all we get in the logs is input/output error.

I have this wishful thought that if I upgrade it to current, dnscache will start resolving names again and things will be good.

When I run yum update, I get errors related to name resolution, however I add the IP address for mirror.contribs.org it does not correct the problem.

Anyone know what may be going on and best way to get this box current without loosing data and user accounts?

[pfloor]

Beta4??? I will slap you now and get that over with... SLAP, SLAP, SLAP

MANY MANY changes since B4 so I would suggest you download the 7.2 CD and do an in-place upgrade.  That "should" work.

If you still have the B4 CD and a test machine handy, you might want to try a dry run first.

Remember...ALWAYS BACK UP YOUR DATA FIRST!!!

[CharlieBrady]

Out of the blue dnscache quit working, all we get in the logs is input/output error.

I have this wishful thought that if I upgrade it to current, dnscache will start resolving names again and things will be good.

Wishful thinking indeed. dnscache won't have suddenly stopped working because of "bit rot" and won't be changed by an upgrade. I expect you have some sort of network problem (or ISP filtering of DNS queries, which is a "network problem").

[mmccarn]

dnscache is the first thing to fail when I let my SME hard drive fill up - how's your disk space?

Also, the system I run that has been updated from SME 7 beta 2 to SME 7.2 turned out not to have the 'shadow' file enabled - a recent set of updates (November, I think) made me unable to change user passwords from /server-manager until I ran pwconv manually to create /etc/shadow. (If this applies to your system, you won't have /etc/shadow at all).

[schmerold]

Thanks for the input. df reports plenty of free space.

I haven't don't the update. Still fighting with why dnscache died for no apparent reason