Topic: Correcting user and group id values

[charlies]

I have a production server running 6.0.1 that started its life at around e-smith server 4.0 (maybe even 3!). In preparation to upgrade to 7.0, I backed up the production server using backup2ws. I then installed 6.0.1 fresh onto a test server and restored the backup. After rebooting, I noticed that some services would not start (mysql and squid among others). It turns out that by upgrading my server over the years, the built-in userids and groupids have changed. This is now causing restoration/upgrade issues. I have manually edited the group and passwd files of my restored data to make the userids and groupids match the clean install and things seem to be working much better. My questions are:
1) Is there a tool/script that can be used to synchronize the userid and groupid values (and all owned files) to match a standard install for system files?
2) I have users that have user and group ids that, while unique, are in a numerical range that is inconsistent with new installations. Should I update their user and group ids to be in a range consistent with the new installations? If yes, how?

Your assistance and guidance is greatly appreciated.

- Charlie

[CharlieBrady]

I have a production server running 6.0.1 that started its life at around e-smith server 4.0 (maybe even 3!). In preparation to upgrade to 7.0, I backed up the production server using backup2ws. I then installed 6.0.1 fresh onto a test server and restored the backup. After rebooting, I noticed that some services would not start (mysql and squid among others). It turns out that by upgrading my server over the years, the built-in userids and groupids have changed. This is now causing restoration/upgrade issues.

Please report all malfunctions via the Bug Tracker. We want to fix any problems. To do that, we need to be aware that they exist, and we only want to look in one place. Thanks for your co-operation.

[charlies]

I did not consider this a bug. And if it is, it seems that it was in a significantly earlier version sme server as the buggered up user and group ids have been present on my system for quite some time I am sure. This is a latent issue from performing system upgrades over s span of years starting with version ~ 4 up to present. Do you really want this listed as a bug?

[CharlieBrady]

I did not consider this a bug. And if it is, it seems that it was in a significantly earlier version sme server as the buggered up user and group ids have been present on my system for quite some time I am sure. This is a latent issue from performing system upgrades over s span of years starting with version ~ 4 up to present. Do you really want this listed as a bug?

Yes. It's certainly a bug. The question is, where is the bug? I suspect in backup2ws, or rather, its restore process. But we definitely want to make sure that it's not a bug in the base system. To the bug tracker, please.