RNIS Registration issue and RabbitMQ Credentials
Forked branch --> https://gitlab.eurecom.fr/turletti/blueprints/-/tree/r2lab?ref_type=head[logs__1_.txt](/uploads/841d4e71f6b3d1b6fd428ca10342164e/logs__1_.txtlogs__1_.txt
2023-11-04 14:51:28,610 Not able to register service rnis reason {
"message":"no Route matched with those values"
}
2023-11-04 14:51:28,610 Registered OAI-RNIS to OAI-MEP, it is available via mp1 -->
2023-11-04 14:51:28,662 [Main] A new rnis app has been registered!
service type: rnisApp
service name: Notification Service
active: True
workers: 1
storage: default
2023-11-04 14:51:28,662 [Main] A new rnis app has been registered!
service type: rnisApp
service name: Data Convergence Repository
active: True
workers: 0
storage: local
2023-11-04 14:51:28,663 [Notification Service] new subscriber for NewCellSubscription
2023-11-04 14:51:28,669 [CM Handler] healthcheck passed!
2023-11-04 14:51:28,689 [Main] A new rnis app has been registered!
service type: rnisApp
service name: CN
cn IP:192.168.70.168
cn port:80
active: True
workers: 1
storage: default
Configuration file /usr/local/etc/configuration.yaml is ready
* Serving Flask app 'oai_rnis.__main__' (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: off
2023-11-04 14:51:30,396 * Running on http://192.168.90.169:80/ (Press CTRL+C to quit)
2023-11-04 14:58:04,633 [CM Handler] A new UE-AMF context has been created
2023-11-04 14:58:04,633 [CM Handler] UE has registered
2023-11-04 14:58:04,635 Pika version 1.3.1 connecting to ('192.168.80.166', 5672)
2023-11-04 14:58:04,635 Socket connected: <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.90.169', 39052), raddr=('192.168.80.166', 5672)>
2023-11-04 14:58:04,636 Streaming transport linked up: (<pika.adapters.utils.io_services_utils._AsyncPlaintextTransport object at 0x7fafd700d810>, _StreamingProtocolShim: <SelectConnection PROTOCOL transport=<pika.adapters.utils.io_services_utils._AsyncPlaintextTransport object at 0x7fafd700d810> params=<ConnectionParameters host=192.168.80.166 port=5672 virtual_host=/ ssl=False>>).
2023-11-04 14:58:04,641 Aborting transport connection: state=1; <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.90.169', 39052), raddr=('192.168.80.166', 5672)>
2023-11-04 14:58:04,641 _AsyncTransportBase._initate_abort(): Initiating abrupt asynchronous transport shutdown: state=1; error=None; <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.90.169', 39052), raddr=('192.168.80.166', 5672)>
2023-11-04 14:58:04,641 Deactivating transport: state=1; <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.90.169', 39052), raddr=('192.168.80.166', 5672)>
2023-11-04 14:58:04,641 AMQP stack terminated, failed to connect, or aborted: opened=False, error-arg=None; pending-error=ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'
2023-11-04 14:58:04,642 Connection closed while authenticating indicating a probable authentication error
2023-11-04 14:58:04,642 Connection setup terminated due to ProbableAuthenticationError: Client was disconnected at a connection stage indicating a probable authentication error: ("ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'",)
2023-11-04 14:58:04,642 AMQPConnector - reporting failure: AMQPConnectorAMQPHandshakeError: ProbableAuthenticationError: Client was disconnected at a connection stage indicating a probable authentication error: ("ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'",)
2023-11-04 14:58:04,642 AMQP connection workflow failed: AMQPConnectionWorkflowFailed: 1 exceptions in all; last exception - AMQPConnectorAMQPHandshakeError: ProbableAuthenticationError: Client was disconnected at a connection stage indicating a probable authentication error: ("ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'",); first exception - None.
2023-11-04 14:58:04,642 AMQPConnectionWorkflow - reporting failure: AMQPConnectionWorkflowFailed: 1 exceptions in all; last exception - AMQPConnectorAMQPHandshakeError: ProbableAuthenticationError: Client was disconnected at a connection stage indicating a probable authentication error: ("ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'",); first exception - None
2023-11-04 14:58:04,642 Closing transport socket and unlinking: state=3; <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.90.169', 39052), raddr=('192.168.80.166', 5672)>
2023-11-04 14:58:04,642 Connection workflow failed: AMQPConnectionWorkflowFailed: 1 exceptions in all; last exception - AMQPConnectorAMQPHandshakeError: ProbableAuthenticationError: Client was disconnected at a connection stage indicating a probable authentication error: ("ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'",); first exception - None
2023-11-04 14:58:04,642 Error in _create_connection().
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pika/adapters/blocking_connection.py", line 451, in _create_connection
raise self._reap_last_connection_workflow_error(error)
pika.exceptions.ProbableAuthenticationError: ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'
[RNIS xApp] Cannot connect to broker
2023-11-04 14:58:05,639 [CM Handler] A new UE-SMF context has been created
2023-11-04 14:58:05,639 [CM Handler] A new pdu session has been created for 208990100001120
2023-11-04 14:58:05,639 a new pdu session has been pushed