Hi George, Instead of renaming or moving files or directories, you can always clean the cache on a safe way by performing this console command:
bin/otrs.Console.pl Maint::Cache::Delete ((enjoy)) Carlos Rodríguez > On Aug 26, 2016, at 4:52 AM, Dimitrakakis Georgios > <[email protected]> wrote: > > Solution FOUND (in case someone else bumps into this)!!! > > It doesn’t matter whatever you do with the DB because OTRS is caching system > data for 20days…. > > What I did was to rename “~otrs/var/tmp/CacheFileStorable” to something else… > I must admit here that it would have been probably enough to just rename the > “~otrs/var/tmp/CacheFileStorable/SystemData” , but in the heat > of trying to solve it I ‘ve renamed the parent folder J > > As soon as I visited the GUI Page new cache was created from the new DB > entries and ta-da everything came back on screen and could perform updates > etc. > > Best, > > George > > > From: Dimitrakakis Georgios > Sent: Friday, August 26, 2016 10:14 AM > To: User questions and discussions about OTRS. > Subject: RE: System registration issue > > OK! I have managed to insert the data to the “system_data” table. > > I have now there 10 entries which are the following: > > 1) Registration::State > > | registered > 2) Registration::UniqueID > > | (The ID) > 3) Registration::APIKey > > | (The KEY) > 4) Registration::LastUpdateID > > | (The ID) > 5) Registration::LastUpdateTime > | > (The TIMESTAMP) > 6) Registration::Description > > | (The Descrption) > 7) Registration::SupportDataSending > | No > 8) Registration::Type > > | Production > 9) Registration::NextUpdateTime > | > (The TIMESTAMP-àhas already passed) > 10) > Kernel::System::SupportDataCollector::PluginAsynchronous::OTRS::ConcurrentUsers > | [{"CustomerSession":0,"TimeStamp":"2016-08-22 > 15:00:00","UserSessionUnique":0,"CustomerSessionUnique":0,"UserSession":0},{"CustomerSession":0,"TimeStamp":"2016-08-22 > 16:00:00","UserSessionUnique":1,"CustomerSessionUnique":0,"UserSession":1}] > > The web GUI shows the following: > > <image001.jpg> > > As said before I still cannot either update the data with the error: > > error > OTRS-CGI-02 > RegistrationUpdate - Can not update system Need UniqueID! > > Or Deregister the system with the error: > > error > OTRS-CGI-02 > Deregistration - Can not deregister system: Need APIKey > > > > These are totally contradicting what I see from the CLI > > $ ./otrs.Console.pl Maint::Registration::UpdateSend > Sending system registration update... > System is not registered, skipping... > Done. > > Using --force doesn’t have any effect at all…. > > How is this possible? GUI shows the system registered but CLI doesn’t know > about it… > > Is there another point I may be missing in the database on where I can > specify the values in order to have it back working correctly??? > > > Any ideas are mostly welcome! > > Best regards, > > George > > > > From: otrs [mailto:[email protected] > <mailto:[email protected]>] On Behalf Of Dimitrakakis Georgios > Sent: Friday, August 26, 2016 8:44 AM > To: User questions and discussions about OTRS. > Subject: [otrs] System registration issue > > Dear OTRS community, > > I had performed an initial installation of OTRS which was registered > successfully @ cloud.otrs.com > > Unfortunately due to DB encoding problem I had to drop and recreate the DB > and after that my > system is no longer updated @ cloud.otrs.com. > > I have tried to “Edit” the data from the “System Registration” option but the > error log show this: > > error > OTRS-CGI-02 > Got no SessionID!! > > I have a backup of the old DB (on which the system was successfully > registered) and I can see > that in the “system_data” table there is the UniqueID (matches the one @ > otrs.cloud.com). APIKey and > all other relevant information. > > How can I restore that information to my running instance?? > > I ‘ve already tried a full database restore which didn’t work and I ‘ve also > tried to “Deregister” which > also didn’t work this time with the error: > > error > OTRS-CGI-02 > Deregistration - Can not deregister system: Need APIKey > > Regards, > > George > ______________________________________________________________________________ > Το περιεχόμενο αυτού του ηλεκτρονικού μηνύματος και τυχόν συνημμένα αρχεία > είναι εμπιστευτικά. Απευθύνεται μόνο στους αναφερόμενους παραλήπτες. Αν > λάβατε αυτό το μήνυμα εκ παραδρομής, παρακαλείσθε να επικοινωνήσετε αμέσως με > τον αποστολέα του μηνύματος ή τον διαχειριστή του συστήματος και να μην > αποκαλύψετε σε κανένα το περιεχόμενο. Οι απόψεις που εκφράζονται ανήκουν στον > συγγραφέα και δεν εκφράζουν κατ' ανάγκη τις απόψεις της Παγκρήτιας > Συνεταιριστικής Τράπεζας. > > > The contents of this email and any attachments are confidential. It is > intended for the named recipients only. If you have received this email in > error please notify the system administrator or the sender immediately and do > not disclose the contents to anyone. Any views or opinions presented are of > the author and not necessarily represent those of Pancretan Cooperative Bank > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
signature.asc
Description: Message signed with OpenPGP using GPGMail
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
