iTop - IT Service Management & CMDB / Tickets / #2073 Connect to iTop Hub fails after instance clone

#2073 Connect to iTop Hub fails after instance clone

Milestone: 2.7.7

Status: assistance

Owner: Pierre Goiffon

Labels: None

Resolution:

Component: User Interface

Priority: Critical

Version: 2.6.0

Type: defect

Updated: 2022-07-26

Created: 2022-06-03

Creator: Marco Musolesi

Private: No

After cloning itop, hub goes in timeout
https://www.itophub.io/wiki/page?id=itop_hub%3Ainstances_identification did not solve
both priv_db_properties.name and instance.txt were deleted and setup was launched
new ID are available in DB and file

any idea?

Related

Tickets: ~~#2073~~

Discussion

Marco Musolesi - 2022-06-03

update: some times itophub.io also got

500 Internal Server Error

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-06-07

Hello,
How did you clone your instance ?
Check this page : Moving iTop under a different URL [iTop Documentation]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Marco Musolesi - 2022-06-07
  
  Hi Pierre,
  
  Nice to meet you. I will give you all steps:
  
  Create a new apache virtual host on the same server but different fqdn and web directory
  
  Create a new mysql DB and new username/pwd
  
  Copy all files from existing directory to the new one
  
  Dump and import exiting DB to the new one
  
  Edit itop config /conf/production/config-itop replacing:
  
  session_name
  
  app_root_url
  
  db_name
  
  db_user
  
  db_pwd
  
  delete /data/instance.txt
  
  delete mysql record database_uuid from priv_db_properties
  
  restart apache
  
  chmod +w sewtup
  
  accessing new fqdn (all data and function are ok)
  
  executing iTop setup fqdn/setup
  
  check new /data/instance.txt and database_uuid (recreated)
  
  trying access iTop Hub (fail)
  
  Did I make something wrong?
  
  Kind Regards
  
  PS: if I skip from point 6 I am able to access hub but the instance is recognized as the old one receiving a warning that suggests https://www.itophub.io/wiki/page?id=itop_hub%3Ainstances_identification
  It seems an identification issue
  
  Marco Musolesi
  m.musolesi@elogic.it
  Head of Cloud Services
  Cloud Services
  eLogic s.r.l. - Società del Gruppo Maggioli
  Via Paolo Nanni Costa, 30
  40133 - Bologna
  0513145611
  elogic.cloud
  
  The information contained in this e-mail and any attachments are confidential. The contents may not be copied or used by anyone other than the addressee and must not be further disclosed without our permission. If you have received this e-mail by mistake, please notify the sender immediately and delete this e-mail and any attachments.
  
  Da: tickets@itop.p.re.sourceforge.net tickets@itop.p.re.sourceforge.net Per conto di Pierre Goiffon
  Inviato: martedì 7 giugno 2022 10:27
  A: [itop:tickets] 2073@tickets.itop.p.re.sourceforge.net
  Oggetto: [itop:tickets] #2073 Connect to iTop Hub fails after instance clone
  
  Hello,
  How did you clone your instance ?
  Check this page : Moving iTop under a different URL [iTop Documentation]https://www.itophub.io/wiki/page?id=latest:install:moving_itop
  
  [tickets:#2073]https://sourceforge.net/p/itop/tickets/2073/ Connect to iTop Hub fails after instance clone
  
  Status: new
  Milestone: 2.7.7
  Created: Fri Jun 03, 2022 05:06 PM UTC by Marco Musolesi
  Last Updated: Fri Jun 03, 2022 05:10 PM UTC
  Owner: nobody
  
  After cloning itop, hub goes in timeout
  https://www.itophub.io/wiki/page?id=itop_hub%3Ainstances_identification did not solve
  both priv_db_properties.name and instance.txt were deleted and setup was launched
  new ID are available in DB and file
  
  any idea?
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/itop/tickets/2073/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Tickets: ~~#2073~~
  
  alternate
  
  image121127.png
  
  image199152.png
  
  image282046.png
  
  image370281.jpg
  
  image849622.png
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-06-07

status: new --> more-info-needed

assigned_to: Pierre Goiffon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-06-07

Thanks for all the informations !
I've asked in Combodo

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Marco Musolesi - 2022-06-07
  
  Thanks a lot Pierre
  I will looking hearing from you
  
  Kind Regards
  
  Marco Musolesi
  m.musolesi@elogic.it
  Head of Cloud Services
  Cloud Services
  eLogic s.r.l. - Società del Gruppo Maggioli
  Via Paolo Nanni Costa, 30
  40133 - Bologna
  0513145611
  elogic.cloud
  
  The information contained in this e-mail and any attachments are confidential. The contents may not be copied or used by anyone other than the addressee and must not be further disclosed without our permission. If you have received this e-mail by mistake, please notify the sender immediately and delete this e-mail and any attachments.
  
  Da: tickets@itop.p.re.sourceforge.net tickets@itop.p.re.sourceforge.net Per conto di Pierre Goiffon
  Inviato: martedì 7 giugno 2022 13:59
  A: [itop:tickets] 2073@tickets.itop.p.re.sourceforge.net
  Oggetto: [itop:tickets] #2073 Connect to iTop Hub fails after instance clone
  
  Thanks for all the informations !
  I've asked in Combodo
  
  [tickets:#2073]https://sourceforge.net/p/itop/tickets/2073/ Connect to iTop Hub fails after instance clone
  
  Status: more-info-needed
  Milestone: 2.7.7
  Created: Fri Jun 03, 2022 05:06 PM UTC by Marco Musolesi
  Last Updated: Tue Jun 07, 2022 08:26 AM UTC
  Owner: Pierre Goiffon
  
  After cloning itop, hub goes in timeout
  https://www.itophub.io/wiki/page?id=itop_hub%3Ainstances_identification did not solve
  both priv_db_properties.name and instance.txt were deleted and setup was launched
  new ID are available in DB and file
  
  any idea?
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/itop/tickets/2073/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Tickets: ~~#2073~~
  
  alternate
  
  image060288.jpg
  
  image151783.png
  
  image285299.png
  
  image606213.png
  
  image952931.png
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-06-07

Hello, could you post your query as a hub request ? That means, connect to https://www.itophub.io/ than click on the balloon icon "contact us" on the middle right.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Marco Musolesi - 2022-06-07
  
  Hi Pierre I am going to move to hub request
  
  Now I am more confused:
  I tried to clone production instance to 2 other instance: test and staging. Total 3 instance
  
  Same procedure for both clones
  
  On Friday both fails...
  
  Today I tried again and now I can see all of them.
  
  So I cloned again test instance and I have the same error.... But I did not delete from itop hub the test instance
  
  So I deleted on itop hub test instance and now it works....
  
  Finally I think that there was some issue or latency on itop hub the did not detect new and old ID that now works
  
  Everything is fine now so you can archive this thread
  
  Thank a lot!!!
  
  Kind Regards
  
  Marco Musolesi
  m.musolesi@elogic.it
  Head of Cloud Services
  Cloud Services
  eLogic s.r.l. - Società del Gruppo Maggioli
  Via Paolo Nanni Costa, 30
  40133 - Bologna
  0513145611
  elogic.cloud
  
  The information contained in this e-mail and any attachments are confidential. The contents may not be copied or used by anyone other than the addressee and must not be further disclosed without our permission. If you have received this e-mail by mistake, please notify the sender immediately and delete this e-mail and any attachments.
  
  Da: tickets@itop.p.re.sourceforge.net tickets@itop.p.re.sourceforge.net Per conto di Pierre Goiffon
  Inviato: martedì 7 giugno 2022 18:10
  A: [itop:tickets] 2073@tickets.itop.p.re.sourceforge.net
  Oggetto: [itop:tickets] #2073 Connect to iTop Hub fails after instance clone
  
  Hello, could you post your query as a hub request ? That means, connect to https://www.itophub.io/ than click on the balloon icon "contact us" on the middle right.
  
  [tickets:#2073]https://sourceforge.net/p/itop/tickets/2073/ Connect to iTop Hub fails after instance clone
  
  Status: more-info-needed
  Milestone: 2.7.7
  Created: Fri Jun 03, 2022 05:06 PM UTC by Marco Musolesi
  Last Updated: Tue Jun 07, 2022 11:59 AM UTC
  Owner: Pierre Goiffon
  
  After cloning itop, hub goes in timeout
  https://www.itophub.io/wiki/page?id=itop_hub%3Ainstances_identification did not solve
  both priv_db_properties.name and instance.txt were deleted and setup was launched
  new ID are available in DB and file
  
  any idea?
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/itop/tickets/2073/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Tickets: ~~#2073~~
  
  alternate
  
  image263075.png
  
  image399554.jpg
  
  image538193.png
  
  image914638.png
  
  image998949.png
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Pierre Goiffon - 2022-06-10
  
  Thanks for your feedback !
  Really happy to see your problem solved !
  Indeed there were some alerts this week on the iTop hub infrastructure, this should be fixed by now.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Marco Musolesi - 2022-06-10
    
    Thanks again Pierre
    Have you a Nice weekend!
    
    Marco Musolesi
    m.musolesi@elogic.it
    Head of Cloud Services
    Cloud Services
    eLogic s.r.l. - Società del Gruppo Maggioli
    Via Paolo Nanni Costa, 30
    40133 - Bologna
    0513145611
    elogic.cloud
    
    The information contained in this e-mail and any attachments are confidential. The contents may not be copied or used by anyone other than the addressee and must not be further disclosed without our permission. If you have received this e-mail by mistake, please notify the sender immediately and delete this e-mail and any attachments.
    
    Da: tickets@itop.p.re.sourceforge.net tickets@itop.p.re.sourceforge.net Per conto di Pierre Goiffon
    Inviato: venerdì 10 giugno 2022 18:29
    A: [itop:tickets] 2073@tickets.itop.p.re.sourceforge.net
    Oggetto: [itop:tickets] Re: #2073 Connect to iTop Hub fails after instance clone
    
    Thanks for your feedback !
    Really happy to see your problem solved !
    Indeed there were some alerts this week on the iTop hub infrastructure, this should be fixed by now.
    
    [tickets:#2073]https://sourceforge.net/p/itop/tickets/2073/ Connect to iTop Hub fails after instance clone
    
    Status: assistance
    Milestone: 2.7.7
    Created: Fri Jun 03, 2022 05:06 PM UTC by Marco Musolesi
    Last Updated: Tue Jun 07, 2022 04:09 PM UTC
    Owner: Pierre Goiffon
    
    After cloning itop, hub goes in timeout
    https://www.itophub.io/wiki/page?id=itop_hub%3Ainstances_identification did not solve
    both priv_db_properties.name and instance.txt were deleted and setup was launched
    new ID are available in DB and file
    
    any idea?
    
    Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/itop/tickets/2073/
    
    To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
    
    Related
    
    Tickets: ~~#2073~~
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-06-07

status: more-info-needed --> assistance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Benjamin DALSASS - 2022-07-22

status: assistance --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-07-26

status: closed --> assistance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pierre Goiffon - 2022-07-26

Discussed with Benjamin : this ticket status was modified by mistake. I'm restoring the previous status !

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.