/etc/ifmap-server/basicauthusers.properties It is mentioned here: https://github.com/Juniper/contrail-controller/wiki/OpenContrail-bring-up-and-provisioning
________________________________________ From: Users <[email protected]> on behalf of Phil Bedard <[email protected]> Sent: Friday, March 13, 2015 11:30 AM To: Nipa Kumar; [email protected] Subject: Re: [Users] Issues installing Contrail 2.1 So the issue seems to be related to contrail-control not being able to connect to the IFMap server. I see these in the ifmap-server.log. I can't remember ever setting a username/password. 2015-03-13 14:27:26,394 [pool-6-thread-74] WARN - ChannelThread: Authentication on 10.4.7.75:52348:79136 failed: Bad username/password 2015-03-13 14:27:26,395 [pool-6-thread-74] DEBUG - ChannelThread: 10.4.7.75:52348:79136 closed Likewise I see these in the contrail-control log. 2015-03-13 Fri 14:29:18:050.165 EDT contrail-main-1 [Thread 140324515297024, Pid 7963]: IFMapPeer [SYS_WARN]: IFMapServerConnection: Received 401 Unauthorized. Incorrect username/password. controller/src/ifmap/client/ifmap_channel.cc 642 Where is this username/password stored? Phil -----Original Message----- From: Nipa Kumar Date: Thursday, March 12, 2015 at 21:11 To: Phil Bedard, "[email protected]" Subject: Re: [Users] Issues installing Contrail 2.1 >Could u please send the output of /etc/contrail/contrail-vroute-agent.conf > > > >On 3/12/15 5:40 PM, "Phil Bedard" <[email protected]> wrote: > >>I'm installing Contrail in a test lab on three VMs, Ubuntu 14.04 on all >>the nodes. >> >>I've installed Contrail a couple times before in a similar setup and >>haven't had too many issues but this time nothing seems to work. I >>populated the testbed.py file with three nodes. One node acting as the >>main config/controller/etc. and then two compute nodes. The fab install >>and fab setup commands all completed with no issues, however when I go >>into the web UI, it shows the control node (running on the same node as >>the webui) and two vrouters as down. It also shows no config nodes or >>analytics nodes present. >> >>On the compute nodes I see the following in the vrouter agent logs on >>both hosts: >> >>2015-03-12 Thu 19:35:59:182.489 EDT contrail-compute-1 [Thread >>140269914363648, Pid 1602]: SANDESH: Send FAILED: 1426203359182474 >>[SYS_INFO]: XmppConnectionLog: connection= [ ip_address = 10.4.7.75 state >>= Connect event = Connect Event local_port = 39683 remote_port = >>4294967295 ] file = controller/src/xmpp/xmpp_state_machine.cc line = 1264 >>2015-03-12 Thu 19:35:59:182.641 EDT contrail-compute-1 [Thread >>140270072567680, Pid 1602]: SANDESH: Send FAILED: 1426203359182631 XMPP >>[SYS_NOTICE]: XmppEventLog: Mode Client: Event: Tcp Connect Fail >>peer: 10.4.7.75 controller/src/xmpp/xmpp_state_machine.cc 1051 >>2015-03-12 Thu 19:35:59:182.714 EDT contrail-compute-1 [Thread >>140269914363648, Pid 1602]: SANDESH: Send FAILED: 1426203359182704 >>[SYS_INFO]: XmppConnectionLog: connection= [ ip_address = 10.4.7.75 state >>= Connect next_state = Active event = EvTcpConnectFail ] file = >>controller/src/xmpp/xmpp_state_machine.cc line = 1264 >>2015-03-12 Thu 19:35:59:182.743 EDT contrail-compute-1 [Thread >>140269914363648, Pid 1602]: SANDESH: Send FAILED: 1426203359182736 >>[SYS_INFO]: XmppConnectionLog: connection= [ ip_address = 10.4.7.75 state >>= Active event = Connect failed after retries ] file = >>controller/src/xmpp/xmpp_state_machine.cc line = 1264 >>2015-03-12 Thu 19:36:02:792.498 EDT contrail-compute-1 [Thread >>140270072567680, Pid 1602]: SANDESH: Send FAILED: 1426203362792487 TCP >>[SYS_DEBUG]: TcpSessionMessageLog: Session >>10.4.7.76:52563::10.4.7.75:8086(-1) < Active session connection complete >>controller/src/io/tcp_session.cc 182 >>2015-03-12 Thu 19:36:10:794.678 EDT contrail-compute-1 [Thread >>140270072567680, Pid 1602]: SANDESH: Send FAILED: 1426203370794666 TCP >>[SYS_DEBUG]: TcpSessionMessageLog: Session >>10.4.7.76:52575::10.4.7.75:8086(-1) < Active session connection complete >>controller/src/io/tcp_session.cc 182 >> >> >> >>About the only thing that seems to work is the BGP peering session from >>the control node to an external MX. >> >>Any pointers? >> >>Thanks, >> >>Phil >> >> >> >>_______________________________________________ >>Users mailing list >>[email protected] >>http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.or >>g > _______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org _______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
