Waldur deploy
Asked by Redouane IT:

Hi,

Thank you so much.

Just one problem.

I have a problem

Loading assets, please wait. {#toc-hId-1849877722}
--------------------------------------------------

After.

Unable to bootstrap application. {#toc-hId--702279239}
------------------------------------------------------

Unfortunately, connection to server has failed. Please check if you can connect to <http://localhost:8080/> from your browser and contact support if the error continues.

Please, help me.

Best regards.


Answers:
author: Nic Brough -Adaptavist-
body: What does going to the localhost address get you?

If it still fails, what do the logs say?

comments: author: Redouane IT
body: Hi,

Thank you with localhost I recive same message.

FOR LOG

\[root@waldur \~\]# tailf /var/log/waldur/uwsgi.log  
your server socket listen backlog is limited to 100 connections  
your mercy for graceful operations on workers is 60 seconds  
mapped 291680 bytes (284 KB) for 4 cores  
\*\*\* Operational MODE: preforking \*\*\*  
WSGI app 0 (mountpoint='') ready in 86 seconds on interpreter 0x1dbfcc0 pid: 6884 (default app)  
\*\*\* uWSGI is running in multiple interpreter mode \*\*\*  
spawned uWSGI worker 1 (pid: 6884, cores: 1)  
spawned uWSGI worker 2 (pid: 7287, cores: 1)  
spawned uWSGI worker 3 (pid: 7288, cores: 1)  
spawned uWSGI worker 4 (pid: 7289, cores: 1)

\[root@waldur \~\]# tailf /var/log/waldur/  
celerybeat.log celery-celery1.log celery-celery2.log celery-celery3.log core.log events.log uwsgi.log  
\[root@waldur \~\]# tailf /var/log/waldur/celerybeat.log  
\[2018-12-11 14:43:45,880: INFO/MainProcess\] Scheduler: Sending due task update-monthly-slas (waldur_core.zabbix.update_sla)  
\[2018-12-11 14:48:45,853: INFO/MainProcess\] Scheduler: Sending due task update-monitoring-items (waldur_core.zabbix.update_monitoring_items)  
\[2018-12-11 14:48:45,880: INFO/MainProcess\] Scheduler: Sending due task update-monthly-slas (waldur_core.zabbix.update_sla)  
\[2018-12-11 14:48:45,975: INFO/MainProcess\] Scheduler: Sending due task openstacktenant-schedule-backups (openstack_tenant.ScheduleBackups)  
\[2018-12-11 14:48:49,030: INFO/MainProcess\] Scheduler: Sending due task openstacktenant-schedule-snapshots (openstack_tenant.ScheduleSnapshots)  
\[2018-12-11 14:48:52,076: INFO/MainProcess\] Scheduler: Sending due task openstacktenant-delete-expired-backups (openstack_tenant.DeleteExpiredBackups)  
\[2018-12-11 14:48:58,384: INFO/MainProcess\] Scheduler: Sending due task waldur-freeipa-sync-groups (waldur_freeipa.sync_groups)  
\[2018-12-11 14:48:58,420: INFO/MainProcess\] Scheduler: Sending due task openstacktenant-delete-expired-snapshots (openstack_tenant.DeleteExpiredSnapshots)  
\[2018-12-11 14:49:01,656: INFO/MainProcess\] Scheduler: Sending due task update-yearly-slas (waldur_core.zabbix.update_sla)  
\[2018-12-11 14:53:45,970: INFO/MainProcess\] Scheduler: Sending due task update-monthly-slas (waldur_core.zabbix.update_sla)

\[root@waldur \~\]# tailf /var/log/waldur/celery-celery1.log  
\[2018-12-11 14:43:45,898: INFO/MainProcess\] Received task: waldur_core.zabbix.update_sla\[6ba6d2de-a90d-4556-b623-d0439f260b85\]  
\[2018-12-11 14:43:45,941: INFO/ForkPoolWorker-1\] Task waldur_core.zabbix.update_sla\[6ba6d2de-a90d-4556-b623-d0439f260b85\] succeeded in 0.0363982959998s: None  
\[2018-12-11 14:48:45,882: INFO/MainProcess\] Received task: waldur_core.zabbix.update_sla\[bea9507a-d31c-40ed-912a-9ecfbade5981\]  
\[2018-12-11 14:48:45,993: INFO/ForkPoolWorker-1\] Task waldur_core.zabbix.update_sla\[bea9507a-d31c-40ed-912a-9ecfbade5981\] succeeded in 0.00728444000015s: None  
\[2018-12-11 14:48:58,393: INFO/MainProcess\] Received task: waldur_freeipa.sync_groups\[88ec933c-87da-42f4-9708-daebb8cace35\]  
\[2018-12-11 14:48:58,399: INFO/ForkPoolWorker-1\] Task waldur_freeipa.sync_groups\[88ec933c-87da-42f4-9708-daebb8cace35\] succeeded in 0.00195026600022s: None  
\[2018-12-11 14:49:01,659: INFO/MainProcess\] Received task: waldur_core.zabbix.update_sla\[51d30d8a-548d-4c5b-a5a1-14fba56fc40f\]  
\[2018-12-11 14:49:01,928: INFO/ForkPoolWorker-1\] Task waldur_core.zabbix.update_sla\[51d30d8a-548d-4c5b-a5a1-14fba56fc40f\] succeeded in 0.267881494s: None  
\[2018-12-11 14:53:45,973: INFO/MainProcess\] Received task: waldur_core.zabbix.update_sla\[800e8a50-684a-41ca-92da-c53aeb7cca1a\]  
\[2018-12-11 14:53:45,984: INFO/ForkPoolWorker-1\] Task waldur_core.zabbix.update_sla\[800e8a50-684a-41ca-92da-c53aeb7cca1a\] succeeded in 0.00884403700002s: None


author: Nic Brough -Adaptavist-
body: Those are not Confluence logs. We need to see the Confluence logs to debug a Confluence failure.


author: Redouane IT
body: do you know file log exactly?


author: Nic Brough -Adaptavist-
body: It will be in \<confluence home\>/log - the main application log is atlassian-confluence.log


author: Redouane IT
body: I am sorry, I don't have atlassian-confluence.log


author: Nic Brough -Adaptavist-
body: Ok, so whatever your process is in Waldur, it's failing to even start Confluence. I'd check the \<confluence install\>/logs/catalina.out to see if there's a problem there. If that doesn't exist, then Waldur isn't even trying to start your installation of Confluence and you'll need to debug that (it's not an Atlassian application, so we can't help you with it really)


author: Redouane IT
body: Thank you so much, I am sorry.