i tried upgrade 2.4.5 to 3.0.1
and it went bad script dbupdate to 3.0 didnt went to the end my ssh is goin to connection timeout
"ERROR 1061 (42000) at line 10: Duplicate key name 'ticket_create_time_unix'
ERROR 1025 (HY000) at line 45: Error on rename of './otrs1/#sql-8fc_7cd6' to './otrs1/article_flag' (errno: 150)
"
i had 1-2 more errors - forgot to copy them
and now when i want login i get message
"Panic, user authenticated but no user data can be found in OTRS DB!! Perhaps the user is invalid."
on all accounts, how do i fix it?
files and database restore or something else?
otrs 2.4.5 -> 3.0.1
Moderator: crythias
Re: otrs 2.4.5 -> 3.0.1
Hi
you should have a close look on errors on migrating! Looks like myISAM/InnoDB issues.
You may have an inconsistent database now. (make a restore, start again, would be my first suggestion)
You last error message sais that you have no customers in you Database, and you use LDAP?
than you should configure a CustomerUser Section in Config.pm and delete all ZZZAuto.pm settings (or reset settings) concerning LDAP.
Florian
you should have a close look on errors on migrating! Looks like myISAM/InnoDB issues.
You may have an inconsistent database now. (make a restore, start again, would be my first suggestion)
You last error message sais that you have no customers in you Database, and you use LDAP?
than you should configure a CustomerUser Section in Config.pm and delete all ZZZAuto.pm settings (or reset settings) concerning LDAP.
Florian
OTRS 2025 SILVER (Prod)
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
Re: otrs 2.4.5 -> 3.0.1
i restore it to 2.4.5
yes i use LDAP.
i use postfix on it and now some tickets are lost, any way to return them trough postfix? like resend everything from friday? ( if yes will OTRS read every email as new ticket or will merge them in existing)
its most likely we will go fresh install on new server - can OTRS be set just outgoing mail so on old OTRS new mails arn't coming anymore? since this version has 40GB in database
yes i use LDAP.
i use postfix on it and now some tickets are lost, any way to return them trough postfix? like resend everything from friday? ( if yes will OTRS read every email as new ticket or will merge them in existing)
its most likely we will go fresh install on new server - can OTRS be set just outgoing mail so on old OTRS new mails arn't coming anymore? since this version has 40GB in database
Re: otrs 2.4.5 -> 3.0.1
Hi,
Resending is posslible, but your new created tickets numbers will not match perhaps. So you'll get a mismatch.
You can try to activate "searchFollowUpInReferences" that could help.
for incoming:
stop your mailserver/mailforwarding/fetching cronjobs... depends on your installation
Florian
once tickets are created in otrs (and you have no backup of your e-mails) and you restore an old version, the mails are lost.NTHuser wrote:i restore it to 2.4.5
yes i use LDAP.
i use postfix on it and now some tickets are lost, any way to return them trough postfix? like resend everything from friday? ( if yes will OTRS read every email as new ticket or will merge them in existing)
Resending is posslible, but your new created tickets numbers will not match perhaps. So you'll get a mismatch.
You can try to activate "searchFollowUpInReferences" that could help.
for mail-send stop you need sysconfig settings "sendmail" -> "do not send mail"NTHuser wrote: its most likely we will go fresh install on new server - can OTRS be set just outgoing mail so on old OTRS new mails arn't coming anymore? since this version has 40GB in database
for incoming:
stop your mailserver/mailforwarding/fetching cronjobs... depends on your installation
Florian
OTRS 2025 SILVER (Prod)
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
-
- Znuny newbie
- Posts: 3
- Joined: 26 Jun 2013, 21:33
- Znuny Version: 2.4.7
- Real Name: Eduard Lazu
Re: otrs 2.4.5 -> 3.0.1
Did u managed to resolve the issue with "Panic User ...................." ?
If not, one possible reason could be that you have wrong date in USERS table. You must change the column name from 'Salutation' (old name) to 'Title' (new name)
If not, one possible reason could be that you have wrong date in USERS table. You must change the column name from 'Salutation' (old name) to 'Title' (new name)
Re: otrs 2.4.5 -> 3.0.1
i restore it and will install 2 different otrs now and will disable old one once tickets are solved (do you know how can i disable incoming new tickets but can reply on old ones - maybe two email accounts?)eduardl wrote:Did u managed to resolve the issue with "Panic User ...................." ?
If not, one possible reason could be that you have wrong date in USERS table. You must change the column name from 'Salutation' (old name) to 'Title' (new name)
i open my issue about installing 2 otrs on sameserver have issue with css - cant recall how did i resolve that issue on other server few months ago