Thanks for the reply. I'm not using LDAP at all. All the post I've read on this so far are mentioning LDAP, but no I'm not using LDAP.
When I lookup into mysql database, I can see all my users in system_user table in my otrs database, but at the login screen it's throwing
Panic! No UserData!!!.
I took a look at my system log as well, I'm only getting the same error in there.
Thanks for helping
I'm guessing you are using LDAP? If not just disregard..
----
Most notably is in the old otrs it(the Config.pm) was:
# UserSyncLDAPMap
# (map if agent should create/synced from LDAP to DB after login)
$Self->{UserSyncLDAPMap} = {
# DB -> LDAP
Firstname => 'givenName',
Lastname => 'sn',
Email => 'mail',
};
--
If so make sure that it looks like this now:
# UserSyncLDAPMap
# (map if agent should create/synced from LDAP to DB after login)
$Self->{UserSyncLDAPMap} = {
# DB -> LDAP
UserFirstname => 'givenName',
UserLastname => 'sn',
UserEmail => 'mail',
};
That got me for about 45 minutes until I looked into the OTRS logs and saw the error it was logging.
-Andy
On 11/6/07 2:19 PM, "touraman traore" <medtraore@gmail.com> wrote:
Hi All,
I tried the upgrade this weekend on a test server. I'm getting this error message: Panic! No UserData!!!...
I followed the instructions below.
Any thoughts?
Thanks for your help...
On 10/18/07, Franz Ferdinand Esberger <ffe@technikum-wien.at <mailto:ffe@technikum-wien.at> > wrote:
Ivan De Masi schrieb am 17.10.2007 17:12 Uhr:Archive: http://lists.otrs.org/pipermail/otrs <http://lists.otrs.org/pipermail/otrs>
> Hello,
>
> we have a bit older installation of OTRS (v. 2.0.4 from the
> sources) and want to upgrade to v. 2.2.3. Can this be realized in
> one step or do I have to install some versions beetween (e.g. 2.1.
> an than 2.2. etc.) Has anyone expierence in such a major upgrade,
> especially with possible problems with the database (mysql) etc.
>
> I have found this post in this month with very helpful hints:
> http://lists.otrs.org/pipermail/otrs/2007-October/020536.html
>
> Is there somebody having also any other experience - any feedback
> is welcome!
>
We run OTRS since the 1.3.x Series, upgraded to 2.0.4 and now to 2.2.1
recently. We are running with the same DB holding the Tickets ever
since and are happy with this.
The only thing you have to asure is to execute EVERY DB Upgrade Skript
since your actual Version:
.) backup everything eg.:
cp -r /opt/otrs/Kernel/ <destination>
/usr/bin/mysqldump -A -u otrs -p <destination>/backup.sql
cat crontab -u otrs -e > <destination>
.) make sure you backuped everything
.) update source to 2.2.x (our your desired Version)
.) execute upgrade skript <your.db> to 2.x
.) execute upgrade skript <your.db> to 2.1
.) execute upgrade skript <your.db> to 2.2
Worked like a charm for me.
hth
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/ <http://www.otrs.com/>
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/