Topic: Problems with user accounts after affa restore

[jameswilson]

Breif History
Built new sme 8 box, restored from affa backup.

All websites seem operational however i have an issue as no users can login to email etc (horde)

If i try to reset the passwords from the server manager the page just hangs. If i try to lock an account it fails with

   
Operation status report
ERR_OCCURRED_LOCKING

in red.

However i can edit the user, ie enable and or disable vpn access.

Any ideas?

[jameswilson]

messages log

Code: [Select]

Jun 12 13:43:43 sme1 esmith::event[3977]: Processing event: user-lock angiewhitehouse
Jun 12 13:43:43 sme1 esmith::event[3977]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Jun 12 13:43:43 sme1 esmith::event[3977]: expanding /etc/rssh.conf 
Jun 12 13:43:43 sme1 esmith::event[3977]: expanding /etc/ftpusers 
Jun 12 13:43:43 sme1 esmith::event[3977]: expanding /etc/raddb/radiusd.conf 
Jun 12 13:43:43 sme1 esmith::event[3977]: expanding /etc/raddb/users 
Jun 12 13:43:43 sme1 esmith::event[3977]: generic_template_expand=action|Event|user-lock|Action|generic_template_expand|Start|1339505023 14517|End|1339505023 261052|Elapsed|0.246535
Jun 12 13:43:43 sme1 esmith::event[3977]: Running event handler: /etc/e-smith/events/user-lock/S15user-lock-passwd
Jun 12 13:43:43 sme1 esmith::event[3977]: Error listing smb passwords 
Jun 12 13:43:43 sme1 esmith::event[3977]: S15user-lock-passwd=action|Event|user-lock|Action|S15user-lock-passwd|Start|1339505023 261368|End|1339505023 334281|Elapsed|0.072913|Status|65280
Jun 12 13:43:43 sme1 esmith::event[3977]: Running event handler: /etc/e-smith/events/user-lock/S25count-active-user-accounts
Jun 12 13:43:43 sme1 esmith::event[3977]: S25count-active-user-accounts=action|Event|user-lock|Action|S25count-active-user-accounts|Start|1339505023 334524|End|1339505023 416238|Elapsed|0.081714
Jun 12 13:43:43 sme1 esmith::event[3977]: Running event handler: /etc/e-smith/events/user-lock/S55ldap-update-simple
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=contact,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=lisajames,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=james.wilson,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=tony,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=derekjames,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=edimaxcam,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=carlbryan,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=eaglegold1,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=nickporter,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=kengumbley,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=elarmemail,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: failed to add entry cn=angiewhitehouse,ou=Groups,dc=mycompany,dc=local: no attributes provided at /etc/e-smith/events/user-lock/S55ldap-update-simple line 227. 
Jun 12 13:43:43 sme1 esmith::event[3977]: S55ldap-update-simple=action|Event|user-lock|Action|S55ldap-update-simple|Start|1339505023 416649|End|1339505023 703885|Elapsed|0.287236
Jun 12 13:43:43 sme1 esmith::event[3977]: Running event handler: /etc/e-smith/events/actions/adjust-services
Jun 12 13:43:43 sme1 esmith::event[3977]: adjusting supervised radiusd (sigterm) 
Jun 12 13:43:43 sme1 esmith::event[3977]: adjusting supervised radiusd (up) 
Jun 12 13:43:43 sme1 esmith::event[3977]: adjust-services=action|Event|user-lock|Action|adjust-services|Start|1339505023 704150|End|1339505023 786257|Elapsed|0.082107


[Stefano]

Any ideas?

bugzilla -> file a new bug

thank you

[janet]

jameswilson

Built new sme 8 box, restored from affa backup.

Did you restore to a fresh install of the sme 8 OS, and if so did you use these instructions
http://wiki.contribs.org/Moving_SME_to_new_Hardware
or did you use
http://wiki.contribs.org/Affa#Full_restore

[jameswilson]

I used the full restore method as I didn't want to rise my backup server as the yum upgrade of the old vm killed it.

[janet]

jameswilson

I used the full restore method....

That appears to be the wrong method, you should use
http://wiki.contribs.org/Moving_SME_to_new_Hardware

[jameswilson]

Mary
Thankyou. I could of done the rise method before but the yum upgrade broke the virtual machine. So I can no longer back it up. The backup server is still sme 7.6 and I dare not yum upgrade that in case that dies too.
So I built a new sme 8 and perfomed a restore. Everything else appears to be fine all websites etc and dats is there. I can login to server manager etc. It seems to only be an issue with the user accounts. They are all there but I can't reset passwords or lock accounts. I'm assuming if I delete the accounts I will loose all email etc

[jameswilson]

http://bugs.contribs.org/show_bug.cgi?id=6983

bug reported

[jameswilson]

Seen as my only issues with sme really are due to using it on unsupported Xen server and using an unsupported backup method, i need to plough on here. Thanks for those that are trying to help it would appear it not a sme bug as such.

So im going to risk my only backup left and rise my backup server to replace the dead one that the yum upgrade killed (upgrading from 7.5.1 to 8 via yum, as side note dont do it!)
then im going to disable all internet access on it. Build a new 8.0 vm, I cant build a 7.6 one and backup as i cant upgrade it to 8 without killing it.

Once i rise the backup server ill make a backup via server manager, but i cant easily use this as they are vm's i cant plug the usb device holding this backup into the machine at install.

Then ill backup the risen 7.5.1 backup machine using the affa move sme to new hardware guide. Then rise again.
Fortunatly one 1 day of email lost.

Im going to have to drop xen, affa or sme as im not going through this again. I thought i had my backup stratagy sorted with affa and mutiple sites backing each other up. I always live and learn

[janet]

jameswilson

Im going to have to drop xen, affa or sme as im not going through this again. I thought i had my backup stratagy sorted with affa and mutiple sites backing each other up. I always live and learn

I answered your other posts before seeing you had lodged a bug report re this thread.

With your backup strategy did you just focus on the backing up part, and not test fully the restore part ?
You should use a completely tested & known fully working backup & restore process, one where you test and prove your whole process yourself, every step of the way.
It is important if your data is critical & valuable.

Quoting from the other post, as I think it's an important concept for other users to be aware of.

"I would strongly suggest you test any upgrade first, particularly when a new operating system has been released, and particularly when you have a non standard setup (meaning anything other than a standalone dedicated server hardware setup).
You should always backup before ANY upgrade, and you should be using a backup & restore solution that you have fully tested and proven works correctly & completely, for both the backup and the restore process.

It's easy to do a test upgrade & resolve issues on a test server, then upgrade your live server.
It's usually much harder to fix problems on a live server & where downtime is usually a factor requiring urgency of resolution."